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

RodrigoAndresHG/centro-builder-heredia

https://github.com/RodrigoAndresHG/centro-builder-heredia · scanned 2026-06-15 23:55 UTC (2 months, 3 weeks ago)

29 raw signals (13 security + 16 graph)

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

Complete repo analysis

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

JSON
Combined
99.4
/100
Security checks
99
7 findings
System graph
99
100.0% cov · 16 findings
Critical
3
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 3 High 3 Medium 6 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 16 Crowd 0 Layer: Quality 15 Cicd 3 Security 1 Api 1 Frontend 3

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

v1
Jun 15 23:54
v#IDStatusScoreGapsNodesCommitStarted
v scan_4387d11a1c19 ok 99.4 16 709 79334bc Jun 15 23:54
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/ff1e672f-9f3b-45af-83b1-1409a386533b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ff1e672f-9f3b-45af-83b1-1409a386533b/

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.