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

Scan timing: clone 4.03s · analysis 1.83s · 6.4 MB · GitHub preflight 484ms

CloakBrowser

https://github.com/CloakHQ/CloakBrowser.git · scanned 2026-05-20 05:09 UTC (2 weeks, 2 days ago) · 10 languages

123 findings 94th percentile · Python · medium (20-100K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

123 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 90.4 0.25 22.60
testing_score 100.0 0.20 20.00
documentation_score 97.0 0.15 14.55
practices_score 80.0 0.15 12.00
code_quality 48.5 0.10 4.85
Overall 1.00 85.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

No actionable gaps — clean repo.

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/049d2004-44a2-4aa6-95dc-82395d96730f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/049d2004-44a2-4aa6-95dc-82395d96730f/

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.