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

seeker71/Coherence-Network

https://github.com/seeker71/Coherence-Network · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

1014 raw signals (0 security + 1014 graph)

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

Complete repo analysis

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

JSON
Combined
49.4
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 945 findings
Critical
1
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 1 High 275 Medium 165 Low 184 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 945 Crowd 0 Layer: Software 12 Frontend 83 Network 5 Hardware 8 Security 282 Cicd 3 Quality 480 Api 72

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

v1
Jun 16 00:06
v#IDStatusScoreGapsNodesCommitStarted
v scan_147a0bfc477a ok 49.4 1014 24085 4d0efe3 Jun 16 00:06
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/51db0f09-ad22-4d27-98be-e13e3506533e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/51db0f09-ad22-4d27-98be-e13e3506533e/

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.