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.

hsh4449/blrent-accident

https://github.com/hsh4449/blrent-accident · scanned 2026-06-16 04:27 UTC (2 months ago)

10 raw signals (0 security + 10 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 10 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 10 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 5 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 10 Crowd 0 Layer: Frontend 1 Security 2 Quality 7

Exclude dismissed / FP Exclude test files

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

Jun 16 04:27

v#	ID	Status	Score	Gaps	Nodes	Commit	Started
v	`scan_b689cb8f0be0`	ok	80.7	10	50	—	Jun 16 04:27

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/3f50647b-b40a-4262-abbe-2da69019d79c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3f50647b-b40a-4262-abbe-2da69019d79c/

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.