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.

Qrust66/Mix-Analyzer

https://github.com/Qrust66/Mix-Analyzer · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

205 raw signals (0 security + 205 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 188 actionable findings from 1 signal source. 17 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 · 188 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 13 Low 93 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 188 Crowd 0 Layer: Software 23 Frontend 1 Security 2 Cicd 1 Quality 161

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

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 4 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 2 findings

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.

2 matching findings on this repo

low Old/deprecated-named symbol `eq8_legacy` in tests/test_als_utils_eq8_disambig.p…
low Old/deprecated-named symbol `_detect_clicks_legacy` in scripts/audit/audit_s7_s…

View all legacy markers findings →

Commented-out code 80 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 tests/test_als_locators.py:199
info Commented-code block (5 lines) in tests/test_cli_mix_analyzer.py:266
info Commented-code block (11 lines) in tests/test_knowledge_beacon.py:1596
info Commented-code block (6 lines) in tests/test_shareable_report.py:130
info Commented-code block (8 lines) in tests/test_v25_integration.py:122
info Commented-code block (8 lines) in tests/test_automation_writer.py:649
info Commented-code block (6 lines) in tests/test_als_utils_m4l_dispatch.py:18
info Commented-code block (5 lines) in tests/test_spectral_evolution.py:466
info Commented-code block (7 lines) in tests/test_cde_f1c2_integration.py:270
info Commented-code block (7 lines) in tests/test_cross_track_follow_source.py:297
info Commented-code block (5 lines) in tests/test_dynamics_configurator.py:1479
info Commented-code block (7 lines) in tests/test_apply_mix_decisions_cli.py:144

View all commented-out code findings →

Config drift 15 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 Very large file: tests/test_dynamics_configurator.py (2165 lines)
low Very large file: tests/test_eq8_configurator.py (1771 lines)
low Very large file: tests/test_master_bus_configurator.py (1392 lines)
low Very large file: mix_engine/writers/dynamics_configurator.py (1352 lines)
low Old/deprecated-named symbol `ref_copy` in tests/test_spatial_configurator.py:69
low Old/deprecated-named symbol `ref_copy` in tests/test_routing_configurator.py:105
low Old/deprecated-named symbol `ref_copy` in tests/test_dynamics_configurator.py:75
info Commented-code block (5 lines) in tests/test_dynamics_configurator.py:1479
low Old/deprecated-named symbol `ref_copy` in tests/test_eq8_configurator.py:164
info Commented-code block (5 lines) in tests/test_eq8_configurator.py:1200
low Old/deprecated-named symbol `ref_copy` in tests/test_master_bus_configurator.py…
info Commented-code block (7 lines) in mix_engine/writers/master_bus_configurator.py…

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/00553c92-a3f0-4ac8-9d36-20ae1ac1754b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/00553c92-a3f0-4ac8-9d36-20ae1ac1754b/

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.