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

welshDog/HyperCode-V2.4

https://github.com/welshDog/HyperCode-V2.4 · scanned 2026-06-16 00:57 UTC (2 months, 1 week ago)

588 raw signals (0 security + 588 graph)

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

Complete repo analysis

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

JSON
Combined
34.9
/100
Security checks
35
0 findings
System graph
35
100.0% cov · 371 findings
Critical
4
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 4 High 122 Medium 96 Low 127 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 371 Crowd 0 Layer: Software 26 Frontend 26 Network 4 Hardware 28 Security 119 Cicd 5 Quality 86 Api 77

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

v1
Jun 16 00:57
v#IDStatusScoreGapsNodesCommitStarted
v scan_3b74d1137aae ok 34.9 588 9394 4820fac Jun 16 00:57
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/9a9895ab-0fb4-4600-8c1a-10d7c7977f54/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9a9895ab-0fb4-4600-8c1a-10d7c7977f54/

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.