Borehole · Project · free tier
home-assistant/frontend
Free reading: not for reliance
2c6cf8e · 23,242 commits · 4,138 files
Read 2026-11-03

home-assistant/frontend: technical due diligence, read from its repository

What Borehole read in home-assistant/frontend's code and history at 2c6cf8e: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • .github/PULL_REQUEST_TEMPLATE.md:66: states a policy on AI-generated contributions
  • AGENTS.md:62: names Open Home Foundation

Architecture & Codebase — including AI provenance

strong
01.6

src/data/energy.ts is 2,585 lines, 22× this codebase's median file

adequate

The median source file here is 116 lines. 44 files exceed 1,160 lines, the largest being 2,585. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

Evidence
src/data/energy.ts:1 — 2,585 lines (22× median)
src/fake_data/demo_services.ts:1 — 2,361 lines (20× median)
src/components/chart/ha-chart-base.ts:1 — 2,349 lines (20× median)
src/resources/jinja_ha_completions.ts:1 — 2,294 lines (19× median)
src/components/data-table/ha-data-table.ts:1 — 2,190 lines (18× median)

Engineering Process & SDLC Maturity

strong
02.16

Tests are retried until they pass

adequate

The suite is configured to retry failing tests (test/e2e/playwright.app.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

Evidence
test/e2e/playwright.app.config.ts:14 — test retry

Product & Engineering Maturity

adequate
04.3

94 direct dependencies in a single manifest

adequate

package.json declares 94 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.

Evidence
package.json — 94 declared
04.19

6% of bug fixes add or change a test

adequate

Of 1858 fixes in the last 24 months, 118 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.

Evidence
118 of 1858
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, 20261028.3, is not on the branch this survey read; the newest release on it is 20261028.0. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag 20261028.3

Security & Reliability Posture

strong
05.26

19 locked dependencies have published vulnerabilities, 16 high or critical

adequate

19 of 1,676 locked dependencies match 39 published advisories in OSV, 16 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. None of the high or critical ones is in what the product ships: they are development dependencies.

Evidence
pnpm-lock.yaml — shell-quote 1.10.0: GHSA-pqg4-j6r4-53mv (critical), fixed in 1.11.0; a development dependency
pnpm-lock.yaml — brace-expansion 1.1.18: GHSA-6j4f-fj2g-mc7p (high), fixed in 1.1.19; a development dependency
pnpm-lock.yaml — brace-expansion 2.1.4: GHSA-6j4f-fj2g-mc7p (high), fixed in 2.1.5; a development dependency

Observability & Operations

not assessable

Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on home-assistant/frontend: every dimension, the questions for the room, and the audit log.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.