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

sherlockfeng/helm

https://github.com/sherlockfeng/helm · scanned 2026-06-16 00:10 UTC (2 months, 2 weeks ago)

198 raw signals (84 security + 114 graph)

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

Complete repo analysis

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

JSON
Combined
62.0
/100
Security checks
62
8 findings
System graph
62
100.0% cov · 96 findings
Critical
2
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 2 High 6 Medium 24 Low 15 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 96 Crowd 0 Layer: Quality 83 Security 14 Api 1 Frontend 2 Network 2 Cicd 2

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

v1
Jun 16 00:10
v#IDStatusScoreGapsNodesCommitStarted
v scan_c4fa9ad2378c ok 62.0 114 2242 612c3a7 Jun 16 00:10
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/ce7af115-1b31-4910-9984-9cddcb153800/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ce7af115-1b31-4910-9984-9cddcb153800/

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.