esphome/esphome

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.

131 of your 203 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 5.19s · analysis 33.15s · 27.8 MB · GitHub API rate-limit (preflight)

https://github.com/esphome/esphome · scanned 2026-06-05 20:55 UTC (4 days, 13 hours ago) · 10 languages

728 raw signals (188 security + 540 graph) 11/13 scanners ran 56th percentile · Python · huge (>500K LoC) System graph score 70 (higher by 11)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 13 hours ago · v2 · 321 actionable findings from 2 signal sources. 137 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 · 252 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	59.0	0.20	11.80
`documentation_score`	91.0	0.15	13.65
`practices_score`	100.0	0.15	15.00
`code_quality`	58.0	0.10	5.80
Overall		1.00	80.2

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 10 Medium 41 Low 151 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 69 System graph 252 Crowd 0 Layer: Quality 205 Cicd 8 Security 8 Software 71 Frontend 7 Network 15 Hardware 7

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

10 matching findings on this repo

low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 7 places repo-level
low Near-duplicate function bodies in 5 places repo-level
low Near-duplicate function bodies in 9 places repo-level
low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 13 places
low Near-duplicate function bodies in 26 places
low Near-duplicate function bodies in 11 places

View all duplicates & near-duplicates findings →

Commented-out code 68 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 (7 lines) in tests/integration/test_online_image_bmp.py:10
info Commented-code block (5 lines) in tests/integration/test_addressable_light_tran…
info Commented-code block (8 lines) in tests/integration/test_loop_interval_default_…
info Commented-code block (6 lines) in tests/integration/test_loop_interval_decoupli…
info Commented-code block (6 lines) in tests/integration/test_sensor_filters_sliding…
info Commented-code block (5 lines) in tests/integration/test_alarm_control_panel_st…
info Commented-code block (6 lines) in tests/integration/test_binary_sensor_autorepe…
info Commented-code block (6 lines) in tests/unit_tests/test_main.py:5659
info Commented-code block (5 lines) in tests/unit_tests/core/test_entity_helpers.py:…
info Commented-code block (5 lines) in tests/script/test_determine_jobs.py:1520
info Commented-code block (8 lines) in tests/component_tests/esp32/test_esp32.py:48
info Commented-code block (5 lines) in tests/component_tests/mipi_spi/test_final_val…

View all commented-out code findings →

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

8 matching findings on this repo

high [MINED131] pre-commit hook `https://github.com/PyCQA/flake8` pinned to mutable … .pre-commit-config.yaml:21
high [MINED106] Phantom test coverage: test_local_development_no_remotes_configured:… tests/script/test_helpers.py:368
high [MINED108] `self._add_file` used but never assigned in __init__: Method `discov…
low Very large file: esphome/config_validation.py (2533 lines)
low Old/deprecated-named symbol `test_validate_config_user_config_snapshot_is_deep_…
info Commented-code block (5 lines) in script/merge_component_configs.py:339
info Commented-code block (7 lines) in esphome/config_validation.py:1062
info Commented-code block (11 lines) in esphome/core/config.py:475

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/3747b405-3caf-437f-b665-8b8eaa5a3be4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3747b405-3caf-437f-b665-8b8eaa5a3be4/

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.