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.
Sign up free Scan another repo

zuplo/zudoku

https://github.com/zuplo/zudoku · scanned 2026-06-16 01:14 UTC (2 months, 1 week ago)

165 raw signals (0 security + 165 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 151 actionable findings from 1 signal source. 14 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
54.2
/100
Security checks
54
0 findings
System graph
54
88.9% cov · 151 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 19 Medium 35 Low 58 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 151 Crowd 0 Layer: Frontend 42 Security 8 Cicd 3 Quality 77 Api 21

Last 1 scan of this repo. Each new scan persists a full payload — historical comparison is exact, not lossy.

v1
Jun 16 01:13
v#IDStatusScoreGapsNodesCommitStarted
v scan_2c0eeadf3adc ok 54.2 165 3171 f97ea70 v0.0.0-zf97ea70c Jun 16 01:13
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/555a956c-836c-409c-83ee-42d751367b63/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/555a956c-836c-409c-83ee-42d751367b63/

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.