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.

schollz/croc

https://github.com/schollz/croc · scanned 2026-07-23 10:34 UTC (1 month, 2 weeks ago)

26 raw signals (0 security + 26 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v5 · last Δ +6.9 (diff) · 23 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: search: "config-drift" × excluding tests × Reset all
Scan summary Repository scanned at 59.9/100 with 60.0% coverage. It contains 118 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in security (12), cicd (6), network (3). Risk profile is low: 0 critical, 0 high, 20 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 0 of 23 actionable findings. 26 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

No findings match the active filters. Reset →
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/d1cdc690-a6a0-46b0-b14b-1d4764b72da6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d1cdc690-a6a0-46b0-b14b-1d4764b72da6/

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.