clash-verge-rev/clash-verge-rev

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

Scan timing: clone 18.23s · analysis 5.32s · 30.2 MB · GitHub API rate-limit (preflight)

https://github.com/clash-verge-rev/clash-verge-rev · scanned 2026-06-05 05:07 UTC (5 hours, 16 minutes ago) · 10 languages

370 findings (116 legacy + 254 scanner) 11/13 scanners ran 59th percentile · Typescript · medium (20-100K LoC) Scanner says 72 (higher by 4)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 hours, 16 minutes ago · v2 · 243 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`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	15.0	0.20	3.00
`documentation_score`	85.0	0.15	12.75
`practices_score`	99.0	0.15	14.85
`code_quality`	80.0	0.10	8.00
Overall		1.00	76.3

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 71 Medium 40 Low 104 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 116 9-layer 127 Crowd 0 Layer: Quality 75 Security 8 Software 69 Api 1 Frontend 5 Cicd 85

Exclude dismissed / FP Exclude test files

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 73 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 React interval is created without an explicit cleanup src/components/setting/mods/auto-backup-settings.…:55
medium localStorage write failures are swallowed silently src/components/proxy/use-head-state.ts:92
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/hooks/use-system-proxy-state.ts:63
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/hooks/use-service-uninstaller.ts:39
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/components/setting/setting-clash.tsx:89
low robots.txt does not advertise a sitemap pnpm-lock.yaml
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 Duplicated implementation block across source files src/utils/uri-parser/socks.ts:34

View all fragile runtime findings →

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Legacy-named symbol `create_webdav_backup` in src/services/cmds.ts:457

View all legacy markers findings →

Config drift 3 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.

3 matching findings on this repo

low File has no detected symbols: eslint.config.ts
low File has no detected symbols: src/components/setting/mods/config-viewer.tsx
low File has no detected symbols: src/services/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/70d8c93a-fc81-4ae3-82eb-6ef2d0458c0b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/70d8c93a-fc81-4ae3-82eb-6ef2d0458c0b/

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.