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

sh4npeiris/claugentic-dev-harness

https://github.com/sh4npeiris/claugentic-dev-harness · scanned 2026-06-16 00:08 UTC (2 months, 2 weeks ago)

36 raw signals (0 security + 36 graph)

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

Complete repo analysis

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

JSON
Combined
80.3
/100
Security checks
80
0 findings
System graph
80
77.8% cov · 36 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 1 Medium 4 Low 17 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 36 Crowd 0 Layer: Software 7 Frontend 1 Security 2 Quality 23 Api 3

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

v1
Jun 16 00:08
v#IDStatusScoreGapsNodesCommitStarted
v scan_7fa87291afc0 ok 80.3 36 428 d23b631 Jun 16 00:08
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/4a6377b0-7f34-460f-abf6-17b41ee7bc47/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4a6377b0-7f34-460f-abf6-17b41ee7bc47/

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.