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

sirBenhenry/musicplayer

https://github.com/sirBenhenry/musicplayer · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

138 raw signals (0 security + 138 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 127 actionable findings from 1 signal source. 11 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
56.7
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 127 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 33 Medium 10 Low 80 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 127 Crowd 0 Layer: Software 20 Hardware 3 Cicd 1 Quality 19 Security 33 Api 51
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 56.7/100 with 100.0% coverage. It contains 1165 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 138 findings — concentrated in api (51), security (33), software (27). Risk profile is high: 0 critical, 33 high, 10 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 123 of 127 actionable findings. 138 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/sirBenhenry/musicplayer/releases/latest (mobile/app/settings.tsx:59)
`mobile/app/settings.tsx:59` calls `GET https://api.github.com/repos/sirBenhenry/musicplayer/releases/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/sirbenhenry/musicplayer/releas…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_download` without auth dependency — backend/app/api/downloads.py:246
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/downloads.py:246 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_playlist` without auth dependency — backend/app/api/playlists.py:108
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playlists.py:108 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_profile` without auth dependency — backend/app/api/profiles.py:87
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/profiles.py:87 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_song` without auth dependency — backend/app/api/library.py:196
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:196 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `remove_song` without auth dependency — backend/app/api/playlists.py:149
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playlists.py:149 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `unfollow_artist` without auth dependency — backend/app/api/library.py:492
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:492 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `set_song_profile` without auth dependency — backend/app/api/library.py:221
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:221 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_artist` without auth dependency — backend/app/api/library.py:461
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:461 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_song` without auth dependency — backend/app/api/playlists.py:117
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playlists.py:117 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cancel_download` without auth dependency — backend/app/api/downloads.py:222
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/downloads.py:222 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_playlist` without auth dependency — backend/app/api/playlists.py:72
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playlists.py:72 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_profile` without auth dependency — backend/app/api/profiles.py:59
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/profiles.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dismiss_all_notifications` without auth dependency — backend/app/api/notifications.py:73
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/notifications.py:73 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dismiss_notification` without auth dependency — backend/app/api/notifications.py:59
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/notifications.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `download_all_artist` without auth dependency — backend/app/api/library.py:296
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:296 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `download_artist` without auth dependency — backend/app/api/downloads.py:190
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/downloads.py:190 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `download_track_v2` without auth dependency — backend/app/api/downloads.py:176
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/downloads.py:176 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `download_track` without auth dependency — backend/app/api/library.py:285
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:285 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `follow_artist` without auth dependency — backend/app/api/library.py:474
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:474 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_artist` without auth dependency — backend/app/api/library.py:364
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/library.py:364 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_spotify_playlist` without auth dependency — backend/app/api/playlists.py:174
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playlists.py:174 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `lidarr_webhook` without auth dependency — backend/app/api/webhooks.py:10
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/webhooks.py:10 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `listen_through` without auth dependency — backend/app/api/playback.py:109
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playback.py:109 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mark_for_deletion` without auth dependency — backend/app/api/deletion.py:62
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/deletion.py:62 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `notification_action` without auth dependency — backend/app/api/notifications.py:88
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/notifications.py:88 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `report_progress` without auth dependency — backend/app/api/playback.py:44
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playback.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `rescue_song` without auth dependency — backend/app/api/deletion.py:47
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/deletion.py:47 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `retry_download` without auth dependency — backend/app/api/downloads.py:210
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/downloads.py:210 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `review_download` without auth dependency — backend/app/api/downloads.py:114
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/downloads.py:114 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `skip_song` without auth dependency — backend/app/api/playback.py:75
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playback.py:75 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `rename_playlist` without auth dependency — backend/app/api/playlists.py:93
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/playlists.py:93 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_profile` without auth dependency — backend/app/api/profiles.py:72
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/profiles.py:72 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mobile/lib/api.ts:151
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mobile/lib/PlaybackService.ts:20
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: CLAUDE.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
CLAUDE.md:248 Supply chainClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 33 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 161 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 37 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/services/essentia_svc.py:analyse_pending_songs, backend/app/services/essentia_svc.py:analyse_all_songs This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/app/api/downloads.py:retry_download, backend/app/api/downloads.py:cancel_download, backend/app/api/downloads.py:delete_download This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene).…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `download_track_v2` in backend/app/api/downloads.py:177
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_tmp
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/janitor.py:24
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_unresolvable_playlist_songs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/playlist_health.py:158
low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/env.py:41
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
backend/alembic/versions/0001_initial.py:164
backend/alembic/versions/0002_download_jobs_extend.py:28
backend/alembic/versions/0004_user_playlists.py:28
backend/alembic/versions/0014_song_mb_recording_id.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: download_artist_discography
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/lidarr.py:116
low System graph software Dead code conf 1.00 Possibly dead Python function: enforce_no_upload
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/qbit_watchdog.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: extract_mood_from_stored_vector
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/essentia_svc.py:228
low System graph software Dead code conf 1.00 Possibly dead Python function: identify_recording
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/fingerprint_svc.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: import_artist_discography
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/discography_importer.py:10
low System graph software Dead code conf 1.00 Possibly dead Python function: morning_playlist_readiness
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/playlist_health.py:106
low System graph software Dead code conf 1.00 Possibly dead Python function: poll_completed_downloads
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/download_poller.py:173
low System graph software Dead code conf 1.00 Possibly dead Python function: require_auth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/core/auth.py:33
low System graph software Dead code conf 1.00 Possibly dead Python function: retry_missing_covers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/cover_art_job.py:206
low System graph software Dead code conf 1.00 Possibly dead Python function: retry_playlist_songs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/playlist_health.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: search_tracks
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/lidarr.py:88
low System graph software Dead code conf 1.00 Possibly dead Python function: ts_now
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/models/base.py:16
low System graph software Dead code conf 1.00 5 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
5 files, 5 locations
backend/alembic/versions/0001_initial.py:17
backend/alembic/versions/0002_download_jobs_extend.py:17
backend/alembic/versions/0004_user_playlists.py:17
backend/alembic/versions/0010_mood_features.py:16
backend/alembic/versions/0014_song_mb_recording_id.py:16
low System graph software Dead code conf 1.00 Possibly dead Python function: upgrade_bad_quality_downloads
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/download_retry.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: utcnow
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/models/base.py:8
low System graph software Dead code conf 1.00 Possibly dead Python function: uuid_pk
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/models/base.py:12
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/downloads/{job_id}
`backend/app/api/downloads.py` declares `DELETE /api/v1/downloads/{job_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /artists/{artist_id}/follow
`backend/app/api/library.py` declares `DELETE /artists/{artist_id}/follow` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /songs/{song_id}
`backend/app/api/library.py` declares `DELETE /songs/{song_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /albums
`backend/app/api/library.py` declares `GET /albums` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1
`backend/app/api/history.py` declares `GET /api/v1` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/analysis-status
`backend/app/api/admin.py` declares `GET /api/v1/analysis-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/auto-radio
`backend/app/api/queue.py` declares `GET /api/v1/auto-radio` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/auto-radio-batch
`backend/app/api/queue.py` declares `GET /api/v1/auto-radio-batch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/downloads
`backend/app/api/downloads.py` declares `GET /api/v1/downloads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/downloads/failed
`backend/app/api/downloads.py` declares `GET /api/v1/downloads/failed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/downloads/{job_id}
`backend/app/api/downloads.py` declares `GET /api/v1/downloads/{job_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/downloads/{job_id}/pipeline
`backend/app/api/downloads.py` declares `GET /api/v1/downloads/{job_id}/pipeline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/import-guide
`backend/app/api/admin.py` declares `GET /api/v1/import-guide` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/notifications
`backend/app/api/notifications.py` declares `GET /api/v1/notifications` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/notifications/count
`backend/app/api/notifications.py` declares `GET /api/v1/notifications/count` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/system-status
`backend/app/api/admin.py` declares `GET /api/v1/system-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /artists
`backend/app/api/library.py` declares `GET /artists` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /artists/search
`backend/app/api/library.py` declares `GET /artists/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /artists/{artist_id}
`backend/app/api/library.py` declares `GET /artists/{artist_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cover/{navidrome_id}
`backend/app/api/library.py` declares `GET /cover/{navidrome_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /songs
`backend/app/api/library.py` declares `GET /songs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /songs/stamp
`backend/app/api/library.py` declares `GET /songs/stamp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /songs/{song_id}
`backend/app/api/library.py` declares `GET /songs/{song_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stream/{navidrome_id}
`backend/app/api/library.py` declares `GET /stream/{navidrome_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /tracks/search
`backend/app/api/library.py` declares `GET /tracks/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /songs/{song_id}/profile
`backend/app/api/library.py` declares `PATCH /songs/{song_id}/profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/analyse
`backend/app/api/admin.py` declares `POST /api/v1/analyse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/analyse-all
`backend/app/api/admin.py` declares `POST /api/v1/analyse-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/analyse-resume
`backend/app/api/admin.py` declares `POST /api/v1/analyse-resume` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/analysis-retry-failed
`backend/app/api/admin.py` declares `POST /api/v1/analysis-retry-failed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/login
`backend/app/api/auth.py` declares `POST /api/v1/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/downloads/artist
`backend/app/api/downloads.py` declares `POST /api/v1/downloads/artist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/downloads/track
`backend/app/api/downloads.py` declares `POST /api/v1/downloads/track` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/downloads/{job_id}/cancel
`backend/app/api/downloads.py` declares `POST /api/v1/downloads/{job_id}/cancel` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/downloads/{job_id}/retry
`backend/app/api/downloads.py` declares `POST /api/v1/downloads/{job_id}/retry` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/downloads/{job_id}/review
`backend/app/api/downloads.py` declares `POST /api/v1/downloads/{job_id}/review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/fetch-covers
`backend/app/api/admin.py` declares `POST /api/v1/fetch-covers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/generate
`backend/app/api/admin.py` declares `POST /api/v1/generate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/lidarr
`backend/app/api/webhooks.py` declares `POST /api/v1/lidarr` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/notifications/dismiss-all
`backend/app/api/notifications.py` declares `POST /api/v1/notifications/dismiss-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/notifications/{notif_id}/action
`backend/app/api/notifications.py` declares `POST /api/v1/notifications/{notif_id}/action` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/notifications/{notif_id}/dismiss
`backend/app/api/notifications.py` declares `POST /api/v1/notifications/{notif_id}/dismiss` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/retry-downloads
`backend/app/api/admin.py` declares `POST /api/v1/retry-downloads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/sync
`backend/app/api/admin.py` declares `POST /api/v1/sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/{history_id}/redownload
`backend/app/api/history.py` declares `POST /api/v1/{history_id}/redownload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /artists/import
`backend/app/api/library.py` declares `POST /artists/import` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /artists/{artist_id}/add
`backend/app/api/library.py` declares `POST /artists/{artist_id}/add` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /artists/{artist_id}/download-all
`backend/app/api/library.py` declares `POST /artists/{artist_id}/download-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /artists/{artist_id}/follow
`backend/app/api/library.py` declares `POST /artists/{artist_id}/follow` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /tracks/download
`backend/app/api/library.py` declares `POST /tracks/download` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/download_pipeline.py (1160 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/284c63ed-9419-45a5-b31b-32a6ada9f9d6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/284c63ed-9419-45a5-b31b-32a6ada9f9d6/

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.