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.

Johnny-Z13/death-match-pool

https://github.com/Johnny-Z13/death-match-pool · scanned 2026-06-16 04:29 UTC (2 months ago)

12 raw signals (0 security + 12 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 11 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 6 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 11 Crowd 0 Layer: Hardware 2 Frontend 1 Security 2 Quality 6

Exclude dismissed / FP Exclude test files

1 healthy

USE /__bb_save_table_glb

healthy

endpoint

auth

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/36b1944c-46f6-4eaf-8f0e-74dc361fff54/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/36b1944c-46f6-4eaf-8f0e-74dc361fff54/

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.