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.

Scan timing: clone 1.65s · analysis 0.4s · 0.5 MB · GitHub preflight 478ms

RCode12/izakaya-tracker

https://github.com/RCode12/izakaya-tracker.git · scanned 2026-05-27 13:32 UTC (1 week, 2 days ago) · 10 languages

42 findings (24 legacy + 18 scanner) 30th percentile · Typescript · tiny (<2K LoC) Scanner says 93 (lower by 37)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 33 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 84.5 0.25 21.12
testing_score 0.0 0.20 0.00
documentation_score 38.7 0.15 5.81
practices_score 42.0 0.15 6.30
code_quality 79.4 0.10 7.94
Overall 1.00 56.2
Severity distribution — click a segment to filter
Active filters: layer: hardware × excluding tests × Reset all
Scan summary Repository scanned at 93.3/100 with 88.9% coverage. It contains 135 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 9 findings — concentrated in software (2), frontend (2), api (1). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 0 of 33 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

No findings match the active filters. Reset →
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/0f2b42eb-10ba-43f8-9c77-1b61bea63439/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0f2b42eb-10ba-43f8-9c77-1b61bea63439/

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.