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

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, 1 day ago) · 10 languages

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

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

Complete repo analysis

Last scanned 1 week, 1 day 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
Combined
86.8
/100
Repobility
80
24 legacy
9-layer
93
88.9% cov · 9 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
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: excluding tests × Reset all
Severity: Critical 0 High 6 Medium 7 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 24 9-layer 9 Crowd 0 Layer: Quality 18 Security 7 Software 3 Api 1 Frontend 2 Data 1 Cicd 1

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 14 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Public web service has no security.txt .well-known/security.txt
  • medium Public web app has no Content Security Policy index.html
  • medium Frontend API reference is not matched by discovered backend routes components/visits/TabelogUrlInput.tsx:26
  • low Public web app has no humans.txt humans.txt
  • low Public docs site has no llms.txt llms.txt
  • low Public web app has no sitemap sitemap.xml
  • low Public web app has no robots.txt robots.txt
  • low Duplicated implementation block across source files app/(auth)/signup/page.tsx:61
  • info [MINED045] Ts Non Null Assertion: x! asserts not null - bypasses null checks - … components/visits/VisitForm.tsx:82
  • info [MINED047] Emoji In Source: Emoji ✅ ❌ 🚀 in code/comments — common AI output unl… components/visits/VisitForm.tsx:187
  • info [MINED047] Emoji In Source: Emoji ✅ ❌ 🚀 in code/comments — common AI output unl… components/visits/VisitCard.tsx:6
  • info [MINED047] Emoji In Source: Emoji ✅ ❌ 🚀 in code/comments — common AI output unl… components/dashboard/SpendingTrendChart.tsx:51
View all fragile runtime findings →
Config drift 2 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
2 matching findings on this repo
  • medium No CI/CD configuration found
  • low File has no detected symbols: next.config.ts
View all config drift findings →
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.