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

VSN2015/concerns_on_rails

https://github.com/VSN2015/concerns_on_rails · scanned 2026-06-16 00:53 UTC (2 months, 1 week ago)

28 raw signals (0 security + 28 graph)

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

Complete repo analysis

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

JSON
Combined
70.9
/100
Security checks
71
0 findings
System graph
71
88.9% cov · 24 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 15 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 24 Crowd 0 Layer: Hardware 3 Frontend 1 Security 6 Cicd 4 Quality 10

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

v1
Jun 16 00:53
v#IDStatusScoreGapsNodesCommitStarted
v scan_6269454b954e ok 70.9 28 227 4d2f8b6 v1.19.0 Jun 16 00:53
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/e82dfb70-1d6f-4770-bb5c-71c6129027ea/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e82dfb70-1d6f-4770-bb5c-71c6129027ea/

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.