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

anki2003ta/Museum

https://github.com/anki2003ta/Museum · scanned 2026-08-30 06:42 UTC (1 week, 5 days ago)

350 raw signals (0 security + 350 graph)

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

Complete repo analysis

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

JSON
Combined
74.7
/100
Security checks
75
0 findings
System graph
75
100.0% cov · 348 findings
Critical
6
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 6 High 96 Medium 207 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 348 Crowd 0 Layer: Security 159 Hardware 2 Cicd 2 Quality 7 Dependencies 177 Api 1

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

v1
Aug 30 06:41
v#IDStatusScoreGapsNodesCommitStarted
v scan_task_9884b0a2c69d200cac959eedbf7832f3 ok 74.7 350 211 f998b46 Aug 30 06:41
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/9177c925-64f4-4724-8ecc-6e5ecd1976ca/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9177c925-64f4-4724-8ecc-6e5ecd1976ca/

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.