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.

Asurelia/Shugu_stream

https://github.com/Asurelia/Shugu_stream · scanned 2026-06-17 01:19 UTC (1 month, 2 weeks ago)

276 raw signals (0 security + 276 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -27.8 (diff) · 224 actionable findings from 1 signal source. 52 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 · 224 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 41 Medium 9 Low 79 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 224 Crowd 0 Layer: Software 6 Frontend 16 Hardware 2 Security 9 Cicd 2 Quality 104 Api 85

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 repo-level

View all duplicates & near-duplicates findings →

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 `settings_no_legacy` in backend/tests/integration/t…

View all legacy markers findings →

Commented-out code 79 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 backend/tests/unit/test_director_vip_and_sile…
info Commented-code block (5 lines) in backend/tests/unit/test_director_workers.py:5…
info Commented-code block (6 lines) in backend/tests/unit/test_arch_memory_isolation…
info Commented-code block (5 lines) in backend/tests/unit/test_editor_ws.py:274
info Commented-code block (6 lines) in backend/tests/unit/test_director_orchestrator…
info Commented-code block (5 lines) in backend/tests/unit/voice/test_livekit_agent.p…
info Commented-code block (11 lines) in backend/tests/integration/test_agent_runner_…
info Commented-code block (6 lines) in backend/tests/integration/voice/test_audio_cl…
info Commented-code block (5 lines) in backend/alembic/versions/0011_compactor_field…
info Commented-code block (5 lines) in backend/alembic/versions/0007_scene_editor_ta…
info Commented-code block (5 lines) in backend/alembic/versions/0006_memory_facts_hn…
info Commented-code block (6 lines) in backend/alembic/versions/0002_asset_registry.…

View all commented-out code findings →

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

7 matching findings on this repo

low Old/deprecated-named symbol `eleven_multilingual_v2` in backend/shugu/config.py…
info Commented-code block (5 lines) in backend/shugu/config.py:71
info Commented-code block (5 lines) in backend/shugu/observability/log_config.py:65
info Commented-code block (5 lines) in frontend/next.config.js:4
info Commented-code block (7 lines) in frontend/eslint.config.mjs:5
info Commented-code block (7 lines) in frontend/playwright.config.ts:24
info Commented-code block (5 lines) in frontend/tailwind.config.js:33

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/376ce451-5dab-48a1-8dc7-18645a36dd71/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/376ce451-5dab-48a1-8dc7-18645a36dd71/

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.