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.

WindyCityJump23/MusicLife

https://github.com/WindyCityJump23/MusicLife · scanned 2026-06-16 00:58 UTC (2 months, 1 week ago)

358 raw signals (172 security + 186 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 186 actionable findings from 2 signal sources. 464 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 · 176 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 86 Medium 28 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 10 System graph 176 Crowd 0 Layer: Quality 51 Security 20 Cicd 2 Software 11 Frontend 11 Network 2 Hardware 5 Api 84

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

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

10 matching findings on this repo

info Commented-code block (5 lines) in api/app/startup_check.py:51
info Commented-code block (7 lines) in api/app/routes/ingest.py:306
info Commented-code block (5 lines) in api/app/services/ranking.py:218
info Commented-code block (5 lines) in api/app/services/track_quality.py:25
info Commented-code block (5 lines) in api/app/services/song_ranking.py:275
info Commented-code block (6 lines) in api/evals/fixtures.py:274
info Commented-code block (5 lines) in web/app/api/playlists/route.ts:70
info Commented-code block (5 lines) in web/app/api/auth/token/route.ts:4
info Commented-code block (6 lines) in web/app/api/import-playlist/route.ts:194
info Commented-code block (5 lines) in web/lib/track-quality.ts:41

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium Runtime service client appears to use placeholder configuration

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/318dd741-8106-4e75-8bf6-5ddd8f4c7d09/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/318dd741-8106-4e75-8bf6-5ddd8f4c7d09/

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.