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

Scan timing: clone 2.95s · analysis 71.51s · 6.3 MB · GitHub preflight 471ms

libnyanpasu/clash-nyanpasu

https://github.com/libnyanpasu/clash-nyanpasu · scanned 2026-06-05 17:18 UTC (4 days, 22 hours ago) · 10 languages

471 raw signals (211 security + 260 graph) 22nd percentile · Typescript · medium (20-100K LoC) System graph score 78 (lower by 20)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 189 actionable findings from 2 signal sources. 152 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 55.0 0.25 13.75
testing_score 15.0 0.20 3.00
documentation_score 89.6 0.15 13.44
practices_score 91.0 0.15 13.65
code_quality 57.6 0.10 5.76
Overall 1.00 58.6
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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.

Commented-out code 6 findings
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/`.
6 matching findings on this repo
  • info Commented-code block (6 lines) in frontend/interface/src/provider/mutation-prov…
  • info Commented-code block (5 lines) in frontend/interface/src/hooks/use-kv-storage.t…
  • info Commented-code block (6 lines) in frontend/interface/src/openapi/geoip/ipsb.ts:…
  • info Commented-code block (7 lines) in frontend/nyanpasu/src/components/ui/text-marq…
  • info Commented-code block (7 lines) in frontend/nyanpasu/src/pages/(main)/main/setti…
  • info Commented-code block (7 lines) in frontend/nyanpasu/src/pages/(main)/main/profi…
View all commented-out code findings →
Config drift 8 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.
8 matching findings on this repo
  • low File has no detected symbols: commitlint.config.js
  • low File has no detected symbols: knip.config.ts
  • low File has no detected symbols: frontend/nyanpasu/vite.config.ts
  • low File has no detected symbols: frontend/nyanpasu/tailwind.config.ts
  • low File has no detected symbols: frontend/nyanpasu/postcss.config.js
  • info TODO/FIXME marker in shipping code — frontend/nyanpasu/vite.config.ts:38
  • low Old/deprecated-named symbol `common_copy` in frontend/nyanpasu/src/pages/(main)…
  • info Commented-code block (7 lines) in frontend/nyanpasu/src/pages/(main)/main/setti…
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/2f46b2d1-2838-44e3-ad93-6e6b582c017b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2f46b2d1-2838-44e3-ad93-6e6b582c017b/

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.