farion1231/cc-switch

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.

45 of your 98 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 14.51s · analysis 7.46s · 32.5 MB · GitHub preflight 424ms

https://github.com/farion1231/cc-switch · scanned 2026-06-05 06:56 UTC (6 days ago) · 10 languages

387 raw signals (89 security + 298 graph) 11/13 scanners ran 81st percentile · Typescript · large (100-500K LoC) System graph score 66 (higher by 18)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 125 findings

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`	69.0	0.20	13.80
`documentation_score`	89.0	0.15	13.35
`practices_score`	80.0	0.15	12.00
`code_quality`	70.0	0.10	7.00
Overall		1.00	83.9

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 2 High 7 Medium 8 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 29 System graph 125 Crowd 0 Layer: Quality 64 Security 6 Software 54 Cicd 4 Api 1 Frontend 25

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.

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 Old/deprecated-named symbol `remoteIsLegacy` in src/components/settings/WebdavS…

View all legacy markers findings →

Commented-out code 7 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/`.

7 matching findings on this repo

info Commented-code block (5 lines) in src/types.ts:408
info Commented-code block (5 lines) in src/config/claudeProviderPresets.ts:48
info Commented-code block (5 lines) in src/config/mcpPresets.ts:26
info Commented-code block (5 lines) in src/config/hermesProviderPresets.ts:385
info Commented-code block (7 lines) in src/components/settings/AboutSection.tsx:223
info Commented-code block (5 lines) in src/components/providers/forms/hooks/useApiKe…
info Commented-code block (13 lines) in src/components/icons/TerminalIcons.tsx:60

View all commented-out code findings →

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

12 matching findings on this repo

low File has no detected symbols: vite.config.ts
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: tests/config/mimoTokenPlanPresets.test.ts
low File has no detected symbols: tests/config/codexTemplates.test.ts
low File has no detected symbols: tests/config/opencodeProviderPresets.test.ts
low File has no detected symbols: tests/config/codexChatProviderPresets.test.ts
low File has no detected symbols: tests/config/therouterOpenCodeOpenClawPresets.tes…
low File has no detected symbols: tests/utils/providerConfigUtils.codex.test.ts
low File has no detected symbols: tests/utils/omoConfig.test.ts
low File has no detected symbols: tests/components/CommonConfigModalBehavior.test.t…
low File has no detected symbols: tests/hooks/useCommonConfigSave.test.tsx
low File has no detected symbols: src/config/appConfig.tsx

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/3a523c99-d690-4781-991f-275ac44f425e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3a523c99-d690-4781-991f-275ac44f425e/

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.