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

Scan timing: clone 9.15s · analysis 16.04s · 62.4 MB · GitHub API rate-limit (preflight)

facebook/openzl

https://github.com/facebook/openzl · scanned 2026-06-05 23:57 UTC (4 days, 3 hours ago) · 10 languages

324 raw signals (136 security + 188 graph) 11/13 scanners ran 95th percentile · C · large (100-500K LoC) System graph score 84 (higher by 3)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 3 hours ago · v2 · 104 actionable findings from 2 signal sources. 101 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 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 98.0 0.15 14.70
practices_score 70.0 0.15 10.50
code_quality 66.0 0.10 6.60
Overall 1.00 86.5
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
No flows synthesized yet.
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/3fc8ff8f-9c8b-4248-99e0-1154e8f1198b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3fc8ff8f-9c8b-4248-99e0-1154e8f1198b/

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.