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

r2jitu/waitless

https://github.com/r2jitu/waitless · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

64 raw signals (0 security + 64 graph)

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

Complete repo analysis

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

JSON
Combined
79.7
/100
Security checks
80
0 findings
System graph
80
77.8% cov · 59 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 0 Medium 17 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 59 Crowd 0 Layer: Software 2 Network 6 Hardware 7 Frontend 1 Security 1 Cicd 1 Quality 41

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

v1
Jun 15 23:44
v#IDStatusScoreGapsNodesCommitStarted
v scan_703f09e7cd16 ok 79.7 64 757 f5d75c6 Jun 15 23:44
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/6ab37f4e-c7ad-44b2-b9f9-672d7e93fe56/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6ab37f4e-c7ad-44b2-b9f9-672d7e93fe56/

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.