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.

switchroom/switchroom

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

780 raw signals (0 security + 780 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 10 Medium 133 Low 126 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 757 Crowd 0 Layer: Software 9 Api 1 Frontend 71 Network 2 Hardware 1 Security 108 Cicd 2 Quality 563

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 3 places repo-level
low Near-duplicate function bodies in 6 places repo-level

View all duplicates & near-duplicates findings →

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

6 matching findings on this repo

low Old/deprecated-named symbol `shouldFallBackToLegacy` in telegram-plugin/server.…
low Old/deprecated-named symbol `shouldFallBackToLegacy` in telegram-plugin/tests/f…
low Old/deprecated-named symbol `shouldFallBackToLegacy` in telegram-plugin/gateway…
low Old/deprecated-named symbol `specLegacy` in telegram-plugin/gateway/answer-thre…
low Old/deprecated-named symbol `vg_legacy` in src/vault/write-grants.test.ts:88
low Old/deprecated-named symbol `AgentLegacy` in src/auth/migrate-schema.ts:92

View all legacy markers findings →

Commented-out code 486 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 (15 lines) in vitest.config.ts:3
info Commented-code block (5 lines) in telegram-plugin/plugin-logger.ts:27
info Commented-code block (11 lines) in telegram-plugin/subagent-watcher.ts:570
info Commented-code block (5 lines) in telegram-plugin/permission-title.ts:204
info Commented-code block (6 lines) in telegram-plugin/session-tail.ts:230
info Commented-code block (8 lines) in telegram-plugin/scoped-approval.ts:86
info Commented-code block (6 lines) in telegram-plugin/history.ts:63
info Commented-code block (5 lines) in telegram-plugin/tool-labels.ts:192
info Commented-code block (7 lines) in telegram-plugin/chat-lock.ts:94
info Commented-code block (6 lines) in telegram-plugin/pty-tail.ts:164
info Commented-code block (6 lines) in telegram-plugin/quota-check.ts:21
info Commented-code block (5 lines) in telegram-plugin/stream-controller.ts:264

View all commented-out code findings →

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

medium Insecure pattern 'node_child_process' in src/host-control/config-edit-validator… src/host-control/config-edit-validator.ts:43
medium Insecure pattern 'node_child_process' in src/mcp/agent-config/server.ts:29 src/mcp/agent-config/server.ts:29
medium Insecure pattern 'node_child_process' in src/cli/agent-config-write.ts:64 src/cli/agent-config-write.ts:64
medium Insecure pattern 'node_child_process' in src/web/config-diff.ts:23 src/web/config-diff.ts:23
medium Insecure pattern 'node_child_process' in src/web/config-diff.test.ts:2 src/web/config-diff.test.ts:2
low Very large file: src/config/schema.ts (3202 lines)
info Commented-code block (15 lines) in vitest.config.ts:3
info Commented-code block (6 lines) in telegram-plugin/gateway/config-approval-handl…
info Commented-code block (6 lines) in telegram-plugin/gateway/config-approval-handl…
info Commented-code block (6 lines) in tests/host-control/config-propose-edit.test.t…
info Commented-code block (6 lines) in tests/host-control/config-propose-edit-idempo…
info Commented-code block (5 lines) in src/host-control/config-edit-validator.ts:542

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/90246bb6-ee10-46b2-97f9-2fe8b597d9fd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/90246bb6-ee10-46b2-97f9-2fe8b597d9fd/

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.