Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

Scan timing: clone 3.02s · analysis 3.24s · 11.0 MB · GitHub API rate-limit (preflight)

xvirobotics/metabot

https://github.com/xvirobotics/metabot · scanned 2026-05-31 01:23 UTC (5 days, 7 hours ago) · 10 languages

216 findings (85 legacy + 131 scanner) 71st percentile · Typescript · medium (20-100K LoC) Scanner says 72 (higher by 8)

File as issue Image v2 schema
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 7 hours ago · v2 · 150 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
74.4
/100
Repobility
76
85 legacy
9-layer
72
100.0% cov · 65 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 64.3 0.25 16.07
testing_score 95.0 0.20 19.00
documentation_score 92.0 0.15 13.80
practices_score 87.0 0.15 13.05
code_quality 54.6 0.10 5.46
Overall 1.00 80.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 38 Medium 20 Low 53 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 85 9-layer 65 Crowd 0 Layer: Quality 71 Security 15 Cicd 8 Software 44 Api 1 Frontend 7 Hardware 4

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
`dangerouslySetInnerHTML` used in a React component — web/src/components/chat/FilePreviewContent.tsx:155
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#2
Insecure pattern 'dangerous_innerhtml' in web/src/components/chat/FilePreviewContent.tsx:155
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
web/src/components/chat/FilePreviewContent.tsx:155
#3
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docs.yml
#4
Dockerfile runs as root: Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#5
`fetch()` without try/.catch or AbortSignal — web/src/components/MemoryView.tsx:88
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/src/components/MemoryView.tsx:88, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#6
`fetch()` without try/.catch or AbortSignal — web/src/components/VoiceView.tsx:165
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/src/components/VoiceView.tsx:165, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#7
`fetch()` without try/.catch or AbortSignal — web/src/components/chat/CallOverlay.tsx:197
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/src/components/chat/CallOverlay.tsx:197, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#8
`fetch()` without try/.catch or AbortSignal — src/api/routes/sync-routes.ts:113
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/api/routes/sync-routes.ts:113, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#9
`fetch()` without try/.catch or AbortSignal — src/utils/http.ts:4
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/utils/http.ts:4, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#10
`fetch()` without try/.catch or AbortSignal — src/wechat/wechat-client.ts:319
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/wechat/wechat-client.ts:319, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/a731985b-1d29-4908-8399-00852d6c06f2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a731985b-1d29-4908-8399-00852d6c06f2/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.