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

proplace-co/wargame

https://github.com/proplace-co/wargame · scanned 2026-06-15 23:45 UTC (2 months, 4 weeks ago)

663 raw signals (0 security + 663 graph)

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

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 660 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
Combined
89.9
/100
Security checks
90
0 findings
System graph
90
77.8% cov · 660 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 518 Low 141 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 660 Crowd 0 Layer: Frontend 517 Security 1 Cicd 2 Quality 140

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

v1
Jun 15 23:40
v#IDStatusScoreGapsNodesCommitStarted
v scan_368c8db026df ok 89.9 663 70133 575b405 Jun 15 23:40
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/abdd16d4-7802-46e4-9529-874316cfa86e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/abdd16d4-7802-46e4-9529-874316cfa86e/

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.