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.

Tzeusy/butlers

https://github.com/Tzeusy/butlers · scanned 2026-06-16 03:52 UTC (2 months ago)

2118 raw signals (130 security + 1988 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v5 · last Δ -0.7 (diff) · 985 actionable findings from 2 signal sources. 418 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 · 977 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 201 Medium 92 Low 266 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 977 Crowd 0 Layer: Quality 606 Security 211 Software 13 Frontend 82 Network 2 Hardware 3 Cicd 3 Api 65

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

7 matching findings on this repo

low Near-duplicate function bodies in 7 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 9 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.

9 matching findings on this repo

low Old/deprecated-named symbol `memory_module_legacy` in roster/relationship/tests…
low Old/deprecated-named symbol `memory_module_legacy` in roster/relationship/api/r…
low Old/deprecated-named symbol `memory_module_legacy` in roster/relationship/api/m…
low Old/deprecated-named symbol `bot_legacy` in roster/switchboard/tests/test_contr…
low Old/deprecated-named symbol `cfg_legacy` in tests/config/test_config.py:411
low Old/deprecated-named symbol `_insert_legacy` in tests/api/test_audit_grouping_u…
low Old/deprecated-named symbol `fp_legacy` in tests/core/healing/test_tracking.py:…
low Old/deprecated-named symbol `_insert_legacy` in tests/migrations/test_backfill_…
low Old/deprecated-named symbol `_emit_kind_legacy` in src/butlers/api/routers/appr…

View all legacy markers findings →

Commented-out code 344 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 (10 lines) in frontend/tests/e2e/secrets-passport.spec.ts:…
info Commented-code block (5 lines) in frontend/tests/e2e/oauth-roundtrip.spec.ts:43
info Commented-code block (40 lines) in frontend/tests/e2e/secrets-passport-parity.s…
info Commented-code block (5 lines) in frontend/tests/e2e/ingestion-visual-parity.sp…
info Commented-code block (5 lines) in frontend/tests/e2e/entity-redesign.spec.ts:206
info Commented-code block (6 lines) in frontend/src/router.tsx:7
info Commented-code block (5 lines) in frontend/src/router-config.tsx:146
info Commented-code block (5 lines) in frontend/src/api/client.ts:2130
info Commented-code block (5 lines) in frontend/src/api/types.ts:3000
info Commented-code block (5 lines) in frontend/src/test/setup.ts:43
info Commented-code block (5 lines) in frontend/src/components/layout/Sidebar.test.t…
info Commented-code block (6 lines) in frontend/src/components/layout/PageHeader.tes…

View all commented-out code findings →

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

info `truncate` class without `title=` for hover reveal — frontend/src/components/bu…
info `truncate` class without `title=` for hover reveal — frontend/src/components/se…
low Very large file: frontend/src/components/secrets/passport/ProviderConfigDrawer.…
info Commented-code block (5 lines) in frontend/src/router-config.tsx:146
info Commented-code block (6 lines) in frontend/src/components/secrets/passport/Prov…
low Old/deprecated-named symbol `cfg_legacy` in tests/config/test_config.py:411
low Old/deprecated-named symbol `_reminders_backup` in tests/config/test_migrations…
low Old/deprecated-named symbol `_reminders_backup` in tests/config/test_schema_mat…
high FastAPI PATCH `patch_runtime_config` without auth dependency — src/butlers/api/… src/butlers/api/routers/runtime_config.py:146
high FastAPI POST `configure_ha` without auth dependency — src/butlers/api/routers/h… src/butlers/api/routers/home_assistant.py:248
high FastAPI DELETE `delete_ha_config` without auth dependency — src/butlers/api/rou… src/butlers/api/routers/home_assistant.py:298
high FastAPI POST `update_spotify_config` without auth dependency — src/butlers/api/… src/butlers/api/routers/spotify.py:414

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/1a9e783e-6332-4c3b-a29c-ce15ce4c870a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1a9e783e-6332-4c3b-a29c-ce15ce4c870a/

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.