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.
38 of your 71 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.15s · analysis 8.59s · 6.9 MB · GitHub API rate-limit (preflight)

sveltejs/svelte

https://github.com/sveltejs/svelte · scanned 2026-06-05 07:08 UTC (6 days ago) · 10 languages

1192 raw signals (62 security + 1130 graph) 11/13 scanners ran 81st percentile · Javascript · large (100-500K LoC) System graph score 75 (higher by 10)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 6 days ago · v2 · 567 actionable findings from 2 signal sources. 60 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 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 85.0 0.20 17.00
documentation_score 88.0 0.15 13.20
practices_score 87.0 0.15 13.05
code_quality 80.0 0.10 8.00
Overall 1.00 85.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
1 warning
GET /
warning
endpoint 1 gap risk 0.05
auth
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/39da5584-b756-4d91-a62c-f67af07c51a5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/39da5584-b756-4d91-a62c-f67af07c51a5/

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.