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

stuartb55/ionic5-ohme-autocharge

https://github.com/stuartb55/ionic5-ohme-autocharge · scanned 2026-06-16 00:23 UTC (2 months, 2 weeks ago)

40 raw signals (0 security + 40 graph)

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

Complete repo analysis

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

JSON
Combined
60.7
/100
Security checks
61
0 findings
System graph
61
100.0% cov · 31 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 5 Medium 5 Low 16 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 31 Crowd 0 Layer: Hardware 5 Security 6 Cicd 2 Quality 8 Api 10

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

v1
Jun 16 00:23
v#IDStatusScoreGapsNodesCommitStarted
v scan_dc7c3de21e3b ok 60.7 40 390 c2fd125 Jun 16 00:23
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/9de11ff5-9c44-4e0e-97d1-1ad0d5e24155/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9de11ff5-9c44-4e0e-97d1-1ad0d5e24155/

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.