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
3 of your 14 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Snailclimb/JavaGuide

https://github.com/Snailclimb/JavaGuide · scanned 2026-06-05 04:42 UTC (8 hours, 58 minutes ago) · 10 languages

31 findings (13 legacy + 18 scanner) 11/13 scanners ran 72nd percentile · Typescript · small (2-20K LoC) Scanner says 94 (lower by 19)

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

Complete repo analysis

Last scanned 8 hours, 58 minutes ago · v2 · 22 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.5
/100
Repobility
79
13 legacy
9-layer
94
66.7% 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 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 70.0 0.20 14.00
documentation_score 61.0 0.15 9.15
practices_score 70.0 0.15 10.50
code_quality 80.0 0.10 8.00
Overall 1.00 75.7
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 2 Medium 7 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 13 9-layer 9 Crowd 0 Layer: Quality 13 Software 3 Api 1 Frontend 1 Security 1 Cicd 3

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 10 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).
10 matching findings on this repo
  • medium Service worker is present without a web app manifest manifest.json
  • medium Public web service has no security.txt .well-known/security.txt
  • medium Public web app has no Content Security Policy index.html
  • 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
  • info [MINED045] Ts Non Null Assertion: x! asserts not null - bypasses null checks - … docs/.vuepress/config.ts:79
  • high [SEC128] Async function without await — fire-and-forget Promise (AI mistake): A… sw.js:71
  • medium `fetch()` without try/.catch or AbortSignal — sw.js:24
View all fragile runtime findings →
Commented-out code 1 finding
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
1 matching finding on this repo
  • info Commented-code block (5 lines) in sw.js:28
View all commented-out code 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/54b016de-2795-48fe-a3d0-c2c867a4803d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/54b016de-2795-48fe-a3d0-c2c867a4803d/

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.