lyswhut/lx-music-desktop

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.

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

Scan timing: clone 6.32s · analysis 34.11s · 24.0 MB · GitHub API rate-limit (preflight)

https://github.com/lyswhut/lx-music-desktop · scanned 2026-06-05 11:34 UTC (5 days, 11 hours ago) · 10 languages

1036 raw signals (160 security + 876 graph) 11th percentile · Typescript · medium (20-100K LoC) System graph score 82 (lower by 30)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 412 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	43.4	0.25	10.85
`testing_score`	0.0	0.20	0.00
`documentation_score`	69.7	0.15	10.46
`practices_score`	80.0	0.15	12.00
`code_quality`	60.0	0.10	6.00
Overall		1.00	52.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 5 Medium 26 Low 310 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 69 System graph 412 Crowd 0 Layer: Quality 133 Software 87 Security 8 Cicd 3 Api 1 Frontend 249

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.

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

12 matching findings on this repo

info Commented-code block (6 lines) in publish/utils/updateChangeLog.js:12
info Commented-code block (6 lines) in build-config/pack.js:30
info Commented-code block (31 lines) in build-config/build-pack.js:135
info Commented-code block (5 lines) in src/lang/i18n.ts:34
info Commented-code block (11 lines) in src/renderer/utils/music.ts:144
info Commented-code block (6 lines) in src/renderer/utils/index.ts:46
info Commented-code block (6 lines) in src/renderer/utils/ipc.ts:161
info Commented-code block (10 lines) in src/renderer/utils/musicSdk/xm.js:1
info Commented-code block (12 lines) in src/renderer/utils/musicSdk/api-source-info.…
info Commented-code block (6 lines) in src/renderer/utils/musicSdk/mg/songId.js:15
info Commented-code block (10 lines) in src/renderer/utils/musicSdk/mg/songList.js:1…
info Commented-code block (16 lines) in src/renderer/utils/musicSdk/mg/leaderboard.j…

View all commented-out code findings →

Config drift 32 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: postcss.config.js
low File has no detected symbols: publish/utils/cosConfig.js
low File has no detected symbols: build-config/vue-loader.config.js
low File has no detected symbols: build-config/utils.js
low File has no detected symbols: build-config/build-after-pack.js
low File has no detected symbols: build-config/post-install.js
low File has no detected symbols: build-config/css-loader.config.js
low File has no detected symbols: build-config/webpack-build-config.js
low File has no detected symbols: build-config/renderer/webpack.config.base.js
low File has no detected symbols: build-config/renderer/webpack.config.prod.js
low File has no detected symbols: build-config/renderer/webpack.config.dev.js
low File has no detected symbols: build-config/renderer-scripts/webpack.config.base…

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/1fee4853-1002-43b2-a00d-3f10f3af7890/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1fee4853-1002-43b2-a00d-3f10f3af7890/

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.