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.

thaynes43/hass-sandbox

https://github.com/thaynes43/hass-sandbox · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

128 raw signals (0 security + 128 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 36 Low 35 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 84 Crowd 0 Layer: Software 6 Api 1 Frontend 2 Network 12 Hardware 3 Security 16 Cicd 3 Quality 41

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

4 matching findings on this repo

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

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 `args_legacy` in appdaemon/tests/test_ai_provider_r…

View all legacy markers findings →

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

8 matching findings on this repo

info Commented-code block (5 lines) in appdaemon/tests/test_vestaboard_controller_ap…
info Commented-code block (6 lines) in appdaemon/tests/test_vestaboard_frame_queue.p…
info Commented-code block (5 lines) in appdaemon/apps/vestaboard_apps/_shared/frame_…
info Commented-code block (8 lines) in appdaemon/apps/photo_frame_viewer/photo_frame…
info Commented-code block (5 lines) in appdaemon/apps/door_notify/door_notify.py:503
info Commented-code block (5 lines) in appdaemon/apps/health_checks/checker_apps/ima…
info Commented-code block (5 lines) in appdaemon/apps/health_checks/checker_apps/pro…
info Commented-code block (6 lines) in appdaemon/apps/immich_fetcher/immich-fetcher-…

View all commented-out code findings →

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

9 matching findings on this repo

low Possibly dead Python function: data_provider_config_from_appdaemon_args appdaemon/providers/ai_providers/registry.py:449
low Stray `console.log` in TS/JS — appdaemon/apps/vestaboard_apps/vestaboard_config…
medium Insecure pattern 'direct_innerhtml_assignment' in appdaemon/apps/vestaboard_app… appdaemon/apps/vestaboard_apps/vestaboard_configu…:699
medium Insecure pattern 'direct_innerhtml_assignment' in appdaemon/apps/countdown_app/… appdaemon/apps/countdown_app/cards/countdown-conf…:432
low Very large file: appdaemon/apps/vestaboard_apps/vestaboard_configuration/vestab…
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/rules/security.md .claude/rules/security.md:7
low Old/deprecated-named symbol `test_get_effective_config_returns_copy` in appdaem…
low Old/deprecated-named symbol `test_get_existing_returns_copy` in appdaemon/tests…

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/3b0d2cd8-aafb-4ccd-b3a9-ad5f649336b1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3b0d2cd8-aafb-4ccd-b3a9-ad5f649336b1/

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.