Read 2026-10-04
home-assistant/android: technical due diligence, read from its repository
What Borehole read in home-assistant/android's code and history at d120c7d: 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.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.github/pull_request_template.md:30: states a policy on AI-generated contributions.github/pull_request_template.md:30: names Open Home Foundation
Architecture & Codebase — including AI provenance
adequateapp/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt is 2,194 lines, 27× this codebase's median file
adequateThe median source file here is 79 lines. 6 files exceed 1,000 lines, the largest being 2,194. 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.
app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1 — 2,194 lines (27× median) |
common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt:1 — 1,402 lines (17× median) |
app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:1 — 1,391 lines (17× median) |
app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt:1 — 1,347 lines (17× median) |
app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt:1 — 1,168 lines (14× median) |
3 model weight files committed directly to git
adequate3 model weight files are stored in git itself, not in LFS, DVC or a model hub. Every clone carries them, the history keeps every version for good, and nothing records which run or data produced them.
app/src/main/assets/wakeword/hey_jarvis.tflite — weights in git |
app/src/main/assets/wakeword/hey_mycroft.tflite — weights in git |
app/src/main/assets/wakeword/okay_nabu.tflite — weights in git |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateThe app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
app/src/main/res/xml/network_security_config.xml:5 — cleartext allowed app-wide |
wear/src/main/res/xml/network_security_config.xml:5 — cleartext allowed app-wide |
Observability & Operations
not assessableNot 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on home-assistant/android: 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.