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.

t8y2/dbx

https://github.com/t8y2/dbx · scanned 2026-05-16 22:31 UTC (22 hours, 46 minutes ago) · 10 languages

157 findings (37 legacy + 120 scanner) 51st percentile · Typescript · medium (20-100K LoC) Scanner says 66 (higher by 7)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 22 hours, 46 minutes ago · v1 · 157 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

v1
May 16 22:31
v#IDStatusScoreGapsNodesCommitStarted
v scan_72e639ab6b13 ok 65.5 120 1973 381c92f May 16 22:31
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/446a5605-265f-4dce-86ba-d4c30af53d8e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/446a5605-265f-4dce-86ba-d4c30af53d8e/

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.