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.
77 of your 135 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 45.55s for a 96.4 MB repo slow.
  • Repobility's analysis ran in 29.99s after the clone landed.

MetaMask/metamask-extension

https://github.com/MetaMask/metamask-extension · scanned 2026-06-05 17:50 UTC (4 days, 22 hours ago) · 10 languages

3539 raw signals (115 security + 3424 graph) 11/13 scanners ran 93rd percentile · Typescript · huge (>500K LoC) System graph score 73 (higher by 20)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 1557 actionable findings from 2 signal sources. 270 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 76.0 0.15 11.40
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 92.2
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Possible secret in shared/lib/trace.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in shared/lib/trace.ts:71; move to env var / secrets manager.
shared/lib/trace.ts:71
#2
Possible secret in ui/components/component-library/input/input.types.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in ui/components/component-library/input/input.types.ts:12; move to env var / secrets manager.
ui/components/component-library/input/input.types.ts:12
#3
Possible secret in ui/components/component-library/text-field/text-field.types.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in ui/components/component-library/text-field/text-field.types.ts:19; move to env var / secrets manager.
ui/components/component-library/text-field/text-field.types.ts:19
#4
Possible secret in ui/pages/settings/search-config.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in ui/pages/settings/search-config.ts:81; move to env var / secrets manager.
ui/pages/settings/search-config.ts:81
#5
Possible secret in app/scripts/constants/on-ramp.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in app/scripts/constants/on-ramp.ts:1; move to env var / secrets manager.
app/scripts/constants/on-ramp.ts:1
#6
Possible secret in app/scripts/constants/on-ramp.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in app/scripts/constants/on-ramp.ts:2; move to env var / secrets manager.
app/scripts/constants/on-ramp.ts:2
#7
Possible secret in app/scripts/constants/on-ramp.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in app/scripts/constants/on-ramp.ts:3; move to env var / secrets manager.
app/scripts/constants/on-ramp.ts:3
#8
Possible secret in app/_locales/de/messages.json
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in app/_locales/de/messages.json:7818; move to env var / secrets manager.
app/_locales/de/messages.json:7818
#9
Insecure pattern 'chmod_777' in .devcontainer/setup-browsers.ts:21
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
.devcontainer/setup-browsers.ts:21
#10
Insecure pattern 'exec_used' in development/stable-sync-legacy.js:26
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
development/stable-sync-legacy.js:26

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/b378527f-5e2d-40ba-b1fe-19f929474b0f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b378527f-5e2d-40ba-b1fe-19f929474b0f/

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.