android — Watchdog Audit

Executive summary

⚠ A critical security finding caps this grade — resolve it before relying on the score below; see the Security lens.

The system holds a 58% health score, marking it as at risk. While the underlying code is clean and the architecture is sound, the business logic layer is fragile. This gap threatens delivery speed and long-term maintainability, as the core domain model fails to enforce its own rules. The asset is substantial, comprising over 100,000 lines of production code. Rebuilding it would cost approximately €190,000 and require 1.3 person-years, highlighting the significant value tied up in this codebase. The low boilerplate ratio indicates that most code represents unique business logic, making it critical to protect rather than replace.

The primary risk is unprotected domain logic. With a domain modeling score of 48%, the system lacks robust encapsulation. Public setters and primitive identifiers allow data to be corrupted before business rules are even applied. This creates a high risk of defects and data integrity issues that are difficult to trace. The cost of these errors manifests as delayed releases and increased debugging time, as engineers must constantly work around weak invariants rather than relying on them.

Secondary concerns involve operational maturity and security readiness. Scores in the low 60s for maturity and readiness suggest the system is not fully optimized for safe, independent operation. While not immediately critical, these gaps increase the likelihood of operational friction and potential security exposure if not addressed. The lack of measured event-driven patterns adds uncertainty to how changes might ripple through the system, though the strong architecture score suggests the foundation can support necessary improvements.

Strengths lie in the clean code and solid architecture. The high scores in code health and architecture indicate that the system is well-structured and easy to understand technically. This provides a stable foundation for remediation. The best immediate action is to enforce strict encapsulation on aggregates. By using guarded constructors or factories that refuse invalid states, the team can immediately reduce defect rates. This single change offers the highest leverage, protecting the most valuable part of the system with minimal effort.

Code Health 85% Strong Architecture 90% Adequate · gated by D26 Maturity 63% Adequate · gated by M2 Readiness 62% Adequate · gated by P3 Security 66% Adequate · gated by D29 Domain Modelling 48% Weak · gated by DM2, DM4, DM11 Performance 85% Strong

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Domain Modelling 48% · 46% weightReadiness 62% · 25% weightMaturity 63% · 14% weightSecurity 66% · 8% weightPerformance 85% · 4% weightCode Health 85% · 2% weightArchitecture 90% · 1% weight

Raise Domain Modelling 48 → 70 (the Healthy floor) ⇒ headline 58 → ~65.

Code composition — where the lines go

Tests 100%

New since the last scan (51+)

51 finding(s) are new versus the previous scan (2026-09-11) — surfaced by this scheduled scan itself, no pull request required.

D1 · SettingsActivity.onCreate (cyclomatic 16) app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt
D2 · MessagingManager.handleActions (cognitive 19) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt
D4 · Near-duplicate member pair (38 shared lines) wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt
D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt
D4 · Duplicated block (12–13 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt
D5 · Off the main sequence: home-assistant-android:common
D6 · Low cohesion: MainViewModel (LCOM4 6) wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt
D6 · Low cohesion: DeveloperSettingsFragment (LCOM4 4) app/src/main/kotlin/io/homeassistant/companion/android/settings/developer/DeveloperSettingsFragment.kt
D15 · Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt
D17 · TodoComment app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D29 · REDACTED
D30 · REDACTED
PF3 · Sync-over-async blocking wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €62,000–€310,000

Cost to rebuild	€62,000–€310,000 (0.6–1.9 person-years (1,026–3,254 h), ~1–3 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.8× (at 58% quality) — the last 20% of quality is most of the work
Size & shape	Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~1.3 person-years of build effort (about ~€190,000 to rebuild). Its weakest lens is Domain Modelling at 48% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — domain model × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

+9.0 pts · Medium effort · Constructible invalid state

Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.

+9.0 pts · Medium effort · Strongly-typed ids

Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.

+9.0 pts · Medium effort · Rich vs anemic model

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk

This is a Large asset (~1.3 person-years to rebuild), and its weakest lens is Domain Modelling at 48%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Large, ~1.3 person-years rebuild (103,939 LoC) · weakest lens: Domain Modelling 48%

→ Direct remediation budget at Domain Modelling first — highest risk-reduction per euro on an asset this size.

Root cause: an un-encapsulated domain · Medium · Root cause

22 findings across public setters, anemic types and primitive ids share one root cause — the domain layer doesn't protect its own invariants. Fixing the encapsulation pattern resolves them together, rather than chasing each finding.

Evidence: DM5 setters: 0 · DM4 anemic: 13 · DM2 primitive ids: 9

→ Address encapsulation as one pattern (private setters + behaviour + strongly-typed ids), not 100 separate findings.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

571 modules, 883 dependencies. 11 dependency cycles across 58 modules, marked above the diagonal.

Showing the 40 most-connected modules; 531 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 common.compose.composable	2 common.data	3 common.sensors.SensorManager	4 common.util.di	5 data	6 database.settings	7 database.widget	8 frontend.error	9 common.data.network	10 common.data.websocket.impl.entities	11 database.server	12 frontend.externalbus	13 common.data.authentication	14 common.data.websocket	15 common.data.integration.impl	16 common.data.integration	17 common.data.prefs	18 database.sensor	19 common.sensors	21 common.data.servers	22 common.data.integration.display	24 common.util	25 matter	27 frontend.improv	28 home	30 util	31 io.homeassistant.companion.android	32 frontend.handler	34 launch	36 frontend.navigation	37 settings	39 frontend
1 common.compose.composable
2 common.data
3 common.sensors.SensorManager
4 common.util.di
5 data
6 database.settings
7 database.widget
8 frontend.error
9 common.data.network																				2
10 common.data.websocket.impl.entities																4						1
11 database.server		1
12 frontend.externalbus																																1
13 common.data.authentication		1		2							1									1
14 common.data.websocket				1						24	1					1				2
15 common.data.integration.impl		1								3	1			1		7				2
16 common.data.integration		1		1						4					2					1		2
17 common.data.prefs		4		1												2						4
18 database.sensor			1													1
19 common.sensors			26			1					2							8		26		1
20 database						2	12				2							2
21 common.data.servers		1				1			3		8		3	4		4	1		1
22 common.data.integration.display										8				1		25				1
23 common.data.websocket.impl		4								27	1			6		1				4
24 common.util				2							2									1
25 matter										2	1			1						4
26 sensors			17			1										2	1		39	18
27 frontend.improv									1			1								1		1
28 home			1		3					12				2		2	1		2	1	3
29 settings.qs	1																			1	3
30 util			1		1			2			2		1	1		1		3	3	4	1	18
31 io.homeassistant.companion.android																						4				3
32 frontend.handler												1										1	1	1								2
33 home.views			2		1											3		2	3		7				1
34 launch									2		1						1			1		1				2				2
35 assist										1										1		3					1
36 frontend.navigation																													2
37 settings						5					3						1			2							1
38 widgets.todo							7				2									2	6						1
39 frontend								6				1					3			1		3		1		3		2	1	2
40 settings.sensor			1			1											1	3	4	1							1				1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 85% · Strong ·

The Good

D3 · Kotlin God Classes 8.7 D4 · Kotlin Code Duplication 9.8 D17 · Kotlin Explicit Debt 9.9

The Bad

D1 · Kotlin Cyclomatic Complexity 5.5 D2 · Kotlin Cognitive Complexity 6.0

At a glance — Architecture · 90% · Adequate · gated by D26 ·

The Good

D5 · Kotlin Coupling 10.0 D6 · Kotlin Cohesion (LCOM4) 9.9 D35 · Kotlin Change Coupling 9.8 AX10 · Repo Code composition 9.2 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0

The Ugly

D26 · Kotlin Project Cohesion 2.5

At a glance — Maturity · 63% · Adequate · gated by M2 ·

The Good

D15 · Kotlin Churn × Complexity Hotspots 9.7 D19 · Kotlin Documentation Quality 8.0 D21 · Kotlin Naming Consistency 10.0 D34 · Kotlin Knowledge Freshness 9.7 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

D16 · Kotlin Bus Factor 6.6 M1 · Repo Documentation (README) 6.7

The Ugly

D20 · Kotlin ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 62% · Adequate · gated by P3 ·

The Good

D12 · Kotlin Dependency Hygiene 10.0 D13 · Kotlin Secret Scanning 10.0 D14 · Kotlin License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P4 · Repo Deployment & Rollback 7.0

The Bad

P6 · Repo Release Hygiene 5.0

The Ugly

P3 · Repo Security & performance tooling 3.0

At a glance — Security · 66% · Adequate · gated by D29 ·

The Good

D28 · Kotlin Secrets (history) 10.0 D30 · Kotlin Dependency Vulnerabilities 8.2 D43 · Kotlin Malicious Dependencies 10.0

The Bad

D36 · Kotlin Supply-chain Provenance & Signing 5.0

The Ugly

D29 · Kotlin Static Analysis (SAST) 0.0

At a glance — Domain Modelling · 48% · Weak · gated by DM2, DM4, DM11 ·

The Good

DM5 · Repo Encapsulated state 10.0 DM7 · Repo Repository granularity 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0

The Ugly

DM11 · Repo Constructible invalid state 3.4 DM2 · Repo Strongly-typed ids 3.0 DM4 · Repo Rich vs anemic model 3.0

At a glance — Performance · 85% · Strong ·

The Good

PF3 · Repo Async & latency hygiene 8.5

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A03:2021 — Injection	82	High / Critical
A06:2021 — Vulnerable & Outdated Components	4	High / Critical

Roadmap

First, eliminate invalid object states by enforcing validation through guarded constructors or factories, and complete the migration to strongly-typed identifiers to prevent argument errors. Next, shift business logic into aggregates to enforce invariants at the source rather than relying on anemic services. Finally, enable security scanning on pull requests to gate changes and maintain a changelog to track release history.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.	+9.0 pts	Medium	Constructible invalid state
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.	+9.0 pts	Medium	Strongly-typed ids
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.	+9.0 pts	Medium	Rich vs anemic model
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+2.1 pts	Low	ADR Quality
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.	+2.4 pts	Medium	Security & performance tooling
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+2.4 pts	Medium	Release Hygiene
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.	+1.1 pts	Low	Bus Factor
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).	+2.1 pts	Medium	Architecture documentation

File quality

Per-file score 0–10 — a quality signature. Of 108 files carrying findings, judged against the Production bar: 1% slop · 60% mixed · 39% near-clean.

File	Score	Band	Worst signal
REDACTED	3.5	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt	5.0	Mixed	Change Coupling: Boundary-crossing change coupling: MessagingManager.kt ↔ NotificationFunctions.kt
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): Medium: REDACTED
app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt	6.0	Mixed	Explicit Debt: TodoComment
app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt	6.0	Mixed	Explicit Debt: TodoComment
common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt	6.0	Mixed	Explicit Debt: TodoComment
app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt	6.0	Mixed	Explicit Debt: TodoComment
app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt	6.0	Mixed	Explicit Debt: TodoComment
wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt	6.0	Mixed	Explicit Debt: TodoComment
REDACTED	6.1	Mixed	Static Analysis (SAST): Medium: REDACTED
common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt	6.5	Mixed	Explicit Debt: TodoComment
common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorManager.kt	6.7	Mixed	Explicit Debt: TodoComment
app/src/main/kotlin/io/homeassistant/companion/android/widgets/camera/CameraWidgetConfigureActivity.kt	6.7	Mixed	Explicit Debt: TodoComment
common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketRepositoryImpl.kt	6.7	Mixed	Explicit Debt: TodoComment
app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt	6.7	Mixed	Explicit Debt: TodoComment
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 44

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 334

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 19

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 49

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 38 of 42 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 42 dimensions across the health lenses

D1D2D3D4D5D6D12D13D14D15D16D17D19D20D21D26D28D29D30D34D35D36D43AX10AX3AX4DM11DM2DM4DM5DM7DM8DM9M1M2M3M4P1P3P4P6PF3

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 383 of 397 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0e8ca-b01e-795f-9c12-4a29f16bea54.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (common/build.gradle.kts), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX2 Stateful singletons — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, or a Dockerfile. None was found, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not declare whether a construction is produced or passed, which arm two needs to tell a producer from a mapping, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The frontend declares that it computes whether a construction is produced or passed, yet 830 of 830 constructions arrived without the answer. Arm two skipped them; it did not clear them.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P10 Library API & versioning — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads NuGet packaging and C# public API only, and no .NET project was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF1 Benchmark discipline — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF2 Allocation hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity5.5 / 10Adequate✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.5 / 10 · rule-coverage 100% · ceiling Prevented

41 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EntityKt.getIcon at 169. A further 10 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HealthServicesSensorManager.getActivityIcon at 49 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/kotlin/io/homeassistant/companion/android/frontend/handler/FrontendMessageHandler.kt (FrontendMessageHandler.handleMessage at 27), app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt (FrontendViewModel.handleMessageResult at 24), common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorWithAttributes.kt (SensorWithAttributes.toSensorRegistration at 20), app/src/main/kotlin/io/homeassistant/companion/android/frontend/navigation/FrontendNavigation.kt (FrontendNavigationKt.FrontendEventHandler at 19), app/src/main/kotlin/io/homeassistant/companion/android/frontend/barcode/FrontendBarcodeScannerHandler.kt (FrontendBarcodeScannerHandlerKt.toFrontendWireFormat at 18), and 3 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

EntityKt.getIcon (cyclomatic 169)common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850

FriendlyStateKt.stateResource (cyclomatic 104)common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/FriendlyState.kt:76

MessagingManager.handleMessage (cyclomatic 71)app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:302

EntityKt.sensorIcon (cyclomatic 63)common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1192

MessagingManager.handleDeviceCommands (cyclomatic 55)app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:670

+ 36 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 1 EntityKt.getIcon (cyclomatic 169) finding(s) in Cyclomatic Complexity — start with Entity.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FriendlyStateKt.stateResource (cyclomatic 104) finding(s) in Cyclomatic Complexity — start with FriendlyState.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 MessagingManager.handleMessage (cyclomatic 71) finding(s) in Cyclomatic Complexity — start with MessagingManager.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity6.0 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

55 method(s) exceeded the cognitive complexity threshold of 15; the worst was EntityKt.getIcon at 101.

EntityKt.getIcon (cognitive 101)common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850

ThreadManagerImpl.fullSyncPreferredDataset (cognitive 94)app/src/full/kotlin/io/homeassistant/companion/android/thread/ThreadManagerImpl.kt:87

MessagingManager.handleMessage (cognitive 85)app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:302

SensorUpdater.syncSensorsWithServer (cognitive 70)common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt:177

FriendlyStateKt.stateResource (cognitive 65)common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/FriendlyState.kt:76

+ 50 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 1 EntityKt.getIcon (cognitive 101) finding(s) in Cognitive Complexity — start with Entity.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ThreadManagerImpl.fullSyncPreferredDataset (cognitive 94) finding(s) in Cognitive Complexity — start with ThreadManagerImpl.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 MessagingManager.handleMessage (cognitive 85) finding(s) in Cognitive Complexity — start with MessagingManager.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes8.7 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Prevented

44 god class(es) detected.

TooManyMethods: FakePlayer · ×12app/src/main/kotlin/io/homeassistant/companion/android/util/compose/media/player/FakePlayer.kt:26

FileTooLong: notifications/MessagingManager.kt · ×12app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt

MethodTooLong: MediaPlayerControlsWidget.getWidgetRemoteViews · ×12app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:66

ClassTooLong: LocationSensorManager · ×8app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:60

What to do

Resolve the 12 TooManyMethods finding(s) in God Classes — start with FakePlayer.kt, PrefsRepositoryImpl.kt, MessagingManager.kt. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 FileTooLong finding(s) in God Classes — start with MessagingManager.kt, Entity.kt, LocationSensorManager.kt. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 MethodTooLong finding(s) in God Classes — start with DatabaseMigration.kt (2), MediaPlayerControlsWidget.kt, MainView.kt. — One of this dimension's main actionable groups (12 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Stronggated by 46 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

43 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (12 lines × 2) · ×3app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:467

Duplicated block (10 lines × 2) · ×3wear/src/main/kotlin/io/homeassistant/companion/android/home/views/DetailsPanelView.kt:219

Duplicated block (8 lines × 2) · ×3app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:2126

Duplicated block (7 lines × 2) · ×3app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:429

Duplicated block (31 lines × 2) · ×2app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:514

+ 26 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with AssistViewModel.kt, FullApplicationModule.kt, EntityWidgetConfigureScreen.kt. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with DetailsPanelView.kt, ManualServerScreen.kt, Entity.kt. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MessagingManager.kt, BaseWidgetProvider.kt, EntityWidget.kt. — One of this dimension's main actionable groups (3 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D5 · Coupling10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

10 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 8 of the 10 (the rest declare no modelled class or interface, export only macros, or are not Gradle/Maven modules or Cargo crates).

Off the main sequence: home-assistant-android:common

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

2 of 209 classes have LCOM4 above 3.

Low cohesion: MainViewModel (LCOM4 6) · ×2wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt:49

What to do

Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with MainViewModel.kt, DeveloperSettingsFragment.kt. — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 outdated direct gem(s), 0 pinning defect(s). 2 declaration(s) graded against rubygems.org, 2 of them against a version resolved in a committed Gemfile.lock. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 104 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 104 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 23 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt (11×169=1859); app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt (10×71=710); app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt (10×24=240)

Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt · ×23common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850

What to do

Resolve the 23 Hotspot finding(s) in Churn × Complexity Hotspots — start with Entity.kt, MessagingManager.kt, FrontendViewModel.kt. — One of this dimension's main actionable groups (23 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D16 · Bus Factor6.6 / 10Adequate✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Documented

167 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt. Counted over 491 of the 942 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 32 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

32 deducted task-comment markers across 103939 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×32app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:1304

What to do

Resolve the 32 TodoComment finding(s) in Explicit Debt — start with HATextField.kt (6), LocationSensorManager.kt (3), AssistPipelineEvent.kt (2). — One of this dimension's main actionable groups (32 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

The repository's single README is a well-written overview of the Home Assistant companion app for Android, with clear branding (Play Store links), an engaging welcome paragraph, a bulleted list of features, and a direct 'Get the app' link plus Beta instructions. The architecture document SKILL.md provides detailed module/flavor breakdowns, layering, dependency rules, and a full outline, making it the only substantive architecture resource in the set. Both documents are well written but the README alone gives no installation/usage guidance for an Android app.

What to do

Improve Documentation Quality — currently 8.0/10. — The repository's single README is a well-written overview of the Home Assistant companion app for Android, with clear branding (Play Store links), an engaging welcome paragraph, a bulleted list of features, and a direct 'Get the app' link plus Beta instructions. The architecture document SKILL.md provides detailed module/flavor breakdowns, layering, dependency rules, and a full outline, making it the only substantive architecture resource in the set. Both documents are well written but the README alone gives no installation/usage guidance for an Android app.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion2.5 / 10Weak✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

3 of 8 build units (Gradle) flagged as possibly oversized/incoherent.

Split app

Split wear

What to do

Resolve the 1 Split app finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Split wear finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

82 finding(s): 0 critical, 41 high, 41 medium, 0 low. semgrep hit a parse error in 3 file(s) — `app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt` (line 464), `gradlew` (line 74, line 178), `wear/src/main/kotlin/io/homeassistant/companion/android/splash/SplashActivity.kt` (line 8, line 12, line 15, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

What to do

Resolve the 39 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (22), REDACTED (12), REDACTED. — One of this dimension's main actionable groups (39 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities8.2 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir/Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex, Go, Java and Kotlin via Maven/Gradle, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Documented

4 finding(s): 1 critical, 0 high, 3 medium, 0 low.

REDACTED

What to do

Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness9.7 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

16 of 491 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/kotlin/io/homeassistant/companion/android/widgets/common/WidgetDynamicFieldAdapter.kt. Counted over 491 of the 942 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling9.8 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: MessagingManager.kt↔NotificationFunctions.kt 73%; EntityGridVehicleScreen.kt↔MapVehicleScreen.kt 73%; LaunchActivity.kt↔HANavHost.kt 65%

Boundary-crossing change coupling: MessagingManager.kt ↔ NotificationFunctions.kt · ×2app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt

Change coupling: EntityGridVehicleScreen.kt ↔ MapVehicleScreen.kt · ×10app/src/main/kotlin/io/homeassistant/companion/android/vehicle/EntityGridVehicleScreen.kt

What to do

Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with MessagingManager.kt, NotificationFunctions.kt. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 10 Change coupling finding(s) in Change Coupling — start with HomeView.kt (2), EntityGridVehicleScreen.kt, LaunchActivity.kt. — One of this dimension's main actionable groups (10 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.2 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

Do you agree with this assessment?

DM11 · Constructible invalid state3.4 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

`Authentication`'s public constructor takes `host`, `username`, `password` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Authentication` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/authentication/Authentication.kt:8
`LocationHistoryItem`'s public constructor takes `latitude`, `longitude`, `locationName`, `data` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LocationHistoryItem` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/location/LocationHistoryItem.kt:14
`NotificationItem`'s public constructor takes `message`, `data`, `source` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `NotificationItem` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/notification/NotificationItem.kt:8
`TileEntity`'s public constructor takes `tileId`, `iconName`, `entityId`, `label`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TileEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/qs/TileEntity.kt:8
`Attribute`'s public constructor takes `sensorId`, `name`, `value`, `valueType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Attribute` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Attribute.kt:7
`Sensor`'s public constructor takes `id`, `state`, `lastSentState`, `lastSentIcon`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Sensor` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Sensor.kt:7
`SensorSetting`'s public constructor takes `sensorId`, `name`, `value` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `SensorSetting` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorSetting.kt:22
`Server`'s public constructor takes `_name`, `nameOverride`, `_version`, `deviceRegistryId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Server` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/server/Server.kt:14
`CameraTile`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CameraTile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/CameraTile.kt:12
`EntityStateComplications`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `EntityStateComplications` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/EntityStateComplications.kt:11
`FavoriteCaches`'s public constructor takes `id`, `name`, `icon` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `FavoriteCaches` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/FavoriteCaches.kt:11
`Favorites`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Favorites` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/Favorites.kt:11
`ThermostatTile`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ThermostatTile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/ThermostatTile.kt:12
`ButtonWidgetEntity`'s public constructor takes `iconName`, `domain`, `service`, `serviceData`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ButtonWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/widget/ButtonWidgetEntity.kt:8
`CameraWidgetEntity`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CameraWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/widget/CameraWidgetEntity.kt:8
`MediaPlayerControlsWidgetEntity`'s public constructor takes `entityId`, `label`, `textColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `MediaPlayerControlsWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/widget/MediaPlayerControlsWidgetEntity.kt:8
`StaticWidgetEntity`'s public constructor takes `entityId`, `attributeIds`, `label`, `stateSeparator`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `StaticWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/widget/StaticWidgetEntity.kt:8
`TemplateWidgetEntity`'s public constructor takes `template`, `lastUpdate`, `textColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TemplateWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/widget/TemplateWidgetEntity.kt:8
`TodoWidgetEntity`'s public constructor takes `entityId`, `textColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TodoWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — common/src/main/kotlin/io/homeassistant/companion/android/database/widget/TodoWidgetEntity.kt:14

What to do

Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

Do you agree with this assessment?

DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

`LocationHistoryItem.serverId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/location/LocationHistoryItem.kt:34
`NotificationItem.serverId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/notification/NotificationItem.kt:20
`Attribute.sensorId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Attribute.kt:9
`Sensor.serverId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Sensor.kt:11
`SensorSetting.sensorId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorSetting.kt:24
`Server.deviceRegistryId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/server/Server.kt:24
`CameraTile.entityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/CameraTile.kt:19
`EntityStateComplications.entityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/EntityStateComplications.kt:16
`ThermostatTile.entityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/ThermostatTile.kt:19

What to do

Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.

Do you agree with this assessment?

DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

`Authentication` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/authentication/Authentication.kt:8
`LocationHistoryItem` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/location/LocationHistoryItem.kt:14
`NotificationItem` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/notification/NotificationItem.kt:8
`Attribute` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Attribute.kt:7
`Sensor` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Sensor.kt:7
`SensorSetting` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorSetting.kt:22
`Server` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/server/Server.kt:14
`Setting` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/settings/Setting.kt:8
`CameraTile` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/CameraTile.kt:12
`EntityStateComplications` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/EntityStateComplications.kt:11
`FavoriteCaches` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/FavoriteCaches.kt:11
`Favorites` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/Favorites.kt:11
`ThermostatTile` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — common/src/main/kotlin/io/homeassistant/companion/android/database/wear/ThermostatTile.kt:12

What to do

Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.

Do you agree with this assessment?

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

Do you agree with this assessment?

DM7 · Repository granularity10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

Do you agree with this assessment?

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

Do you agree with this assessment?

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

Do you agree with this assessment?

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 9 of 9 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

`REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.

What to do

Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

PF3 · Async & latency hygiene8.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

`updateHealthServices` is async and calls runBlocking — a blocking call inside async code stalls the coroutine's thread, and every coroutine dispatched to it for as long as it runs. — wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt:188

What to do

Kotlin: call the suspend function directly instead of wrapping it in runBlocking, use delay() instead of Thread.sleep, and move unavoidable blocking I/O into withContext(Dispatchers.IO).

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	85%	Strong	Strongest area.
Architecture	90%	Adequate — gated by D26	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	63%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	62%	Adequate — gated by P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	66%	Adequate — gated by D29	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	48%	Weak — gated by DM2, DM4, DM11	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	85%	Strong	Solid.

Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 84 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~51074 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P10 Library API & versioning — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P2 Observability — This repository's JVM source (7 module(s), 919 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
PF2 Allocation hygiene — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 44 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 14 more in this group — see findings.md.

D35 · Change Coupling · Boundary-crossing change coupling · ×2

Boundary-crossing change coupling: MessagingManager.kt ↔ NotificationFunctions.kt app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt — `app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt` (context main) and `common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/NotificationFunctions.kt` (context common) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `25eb107c` Move Emoji.parseToUnicode to Dispatcher.IO (#7108); `d21e938c` Allow assistant volume control (#7068); `6b56bc57` mobile_app_notification_cleared for wearos (#4035) (at that commit the files were still `app/src/main/java/io/homeassistant/companion/android/notifications/MessagingManager.kt` and `common/src/main/java/io/homeassistant/companion/android/common/notifications/NotificationFunctions.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: NotificationFunctions.kt ↔ MessagingManager.kt common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/NotificationFunctions.kt — `common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/NotificationFunctions.kt` (context common) and `wear/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt` (context wear) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `25eb107c` Move Emoji.parseToUnicode to Dispatcher.IO (#7108); `6b56bc57` mobile_app_notification_cleared for wearos (#4035) (at that commit the files were still `common/src/main/java/io/homeassistant/companion/android/common/notifications/NotificationFunctions.kt` and `wear/src/main/java/io/homeassistant/companion/android/notifications/MessagingManager.kt`); `cda25479` Add clear_notification support to Wear OS (#3956) (at that commit the files were still `common/src/main/java/io/homeassistant/companion/android/common/notifications/NotificationFunctions.kt` and `wear/src/main/java/io/homeassistant/companion/android/notifications/MessagingManager.kt`) — run `git show` on any of them.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×1

REDACTED

Serious — 334 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 15 more in this group — see findings.md.

D17 · Explicit Debt · TodoComment · ×32

TodoComment app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:1304 — // TODO drop this requirement https://github.com/home-assistant/android/issues/5931
TodoComment app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:1314 — // TODO drop this requirement https://github.com/home-assistant/android/issues/5931
TodoComment app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:1323 — // TODO drop this requirement https://github.com/home-assistant/android/issues/5931
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/util/compose/LocationPermissionState.kt:15 — // TODO drop this requirement https://github.com/home-assistant/android/issues/5931
TodoComment app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt:108 — // TODO use new theme for Material3 components https://github.com/home-assistant/android/issues/6300
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/settings/qs/ui/ManageTilesScreen.kt:83 — // TODO Migrate IconDialog to Material 3 https://github.com/home-assistant/android/issues/7156
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt:171 — // TODO Drop the explicit HATheme once SensorDetailView is migrated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt:298 — // TODO use new theme for Material3 components https://github.com/home-assistant/android/issues/6258
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/settings/vehicle/views/AndroidAutoFavoritesView.kt:115 — // TODO use new theme for Material3 components https://github.com/home-assistant/android/issues/6302
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/util/compose/entity/EntityPicker.kt:513 — // TODO if we make a multi entity picker we should share part of the remember that prepare the entitiesWithFields — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/util/vehicle/TemplateComponents.kt:157 — // TODO most probably this is always false since the launch will update the boolean after we actually test — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt:55 — // TODO Migrate to compose https://github.com/home-assistant/android/issues/6305
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/widgets/camera/CameraWidgetConfigureActivity.kt:33 — // TODO Migrate to compose https://github.com/home-assistant/android/issues/6306
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/widgets/todo/TodoWidgetStateUpdater.kt:88 — // TODO send error to the widget??? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/widgets/todo/TodoWidgetConfigureActivity.kt:234 — // TODO use new theme for Material3 components https://github.com/home-assistant/android/issues/6303
TodoComment app/src/main/kotlin/io/homeassistant/companion/android/widgets/todo/TodoWidgetActions.kt:133 — // TODO we could modify the entry in DB to add the error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/test/kotlin/io/homeassistant/companion/android/widgets/todo/TodoGlanceAppWidgetTest.kt:290 — // TODO I don't know how to assert the imageProvider or event if it possible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt:72 — // TODO probably replace the text composable by strings to control the applied style — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt:114 — // TODO Change colors with design team (current value are picked approximatively) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt:140 — // TODO Verify colors with design team — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt:146 — // TODO Verify colors with design team — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt:152 — // TODO Verify colors with design team — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/composable/HATextField.kt:158 — // TODO Verify colors with design team — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/compose/theme/HAColors.kt:190 — // TODO validate with design team if this color are immutable or not (not changeable by the users and also stay the same — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/ZoneAttributes.kt:10 — // TODO Introduce back ZoneAttribute class https://github.com/home-assistant/android/issues/5340
+ 7 more in this group — see findings.md.

D15 · Churn × Complexity Hotspots · Hotspot · ×23

Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850 — common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 169 in EntityKt.getIcon at line 850. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:302 — app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in MessagingManager.handleMessage at line 302. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt:887 — app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in FrontendViewModel.handleMessageResult at line 887. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt:94 — app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in ManageShortcutsViewKt.CreateShortcutView at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt:100 — app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in SensorDetailViewKt.SensorDetailView at line 100. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:532 — app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in LocationSensorManager.shouldEnableHighAccuracyMode at line 532. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/DeviceCommands.kt common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/DeviceCommands.kt:124 — common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/DeviceCommands.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in DeviceCommandsKt.commandBleTransmitter at line 124. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/DeviceCommands.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt:177 — common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in SensorUpdater.syncSensorsWithServer at line 177. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/frontend/handler/FrontendMessageHandler.kt app/src/main/kotlin/io/homeassistant/companion/android/frontend/handler/FrontendMessageHandler.kt:155 — app/src/main/kotlin/io/homeassistant/companion/android/frontend/handler/FrontendMessageHandler.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in FrontendMessageHandler.handleMessage at line 155. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/frontend/handler/FrontendMessageHandler.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:82 — app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in HomeAssistantApplication.onCreate at line 82. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/frontend/navigation/FrontendNavigation.kt app/src/main/kotlin/io/homeassistant/companion/android/frontend/navigation/FrontendNavigation.kt:169 — app/src/main/kotlin/io/homeassistant/companion/android/frontend/navigation/FrontendNavigation.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in FrontendNavigationKt.FrontendEventHandler at line 169. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/frontend/navigation/FrontendNavigation.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt:52 — wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in MainViewKt.MainView at line 52. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/settings/controls/views/ManageControlsView.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/controls/views/ManageControlsView.kt:71 — app/src/main/kotlin/io/homeassistant/companion/android/settings/controls/views/ManageControlsView.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ManageControlsViewKt.ManageControlsView at line 71. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/settings/controls/views/ManageControlsView.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorManager.kt common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorManager.kt:317 — common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorManager.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SensorManager.onSensorUpdated at line 317. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt:440 — app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in HealthConnectSensorManager.requestSensorUpdate at line 440. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt:598 — common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in NetworkSensorManager.updateNetworkType at line 598. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/qs/TileExtensions.kt app/src/main/kotlin/io/homeassistant/companion/android/qs/TileExtensions.kt:145 — app/src/main/kotlin/io/homeassistant/companion/android/qs/TileExtensions.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in TileExtensions.setTileData at line 145. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/qs/TileExtensions.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt:91 — app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in SettingsFragment.onCreatePreferences at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt:188 — wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in HealthServicesSensorManager.updateHealthServices at line 188. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/AudioSensorManager.kt common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/AudioSensorManager.kt:283 — common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/AudioSensorManager.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AudioSensorManager.updateAudioState at line 283. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/AudioSensorManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt:82 — app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsActivity.onCreate at line 82. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt:68 — wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ThermostatTile.onTileRequest at line 68. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt:212 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ButtonWidgetConfigureActivity.onCreate at line 212. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 16:33:30 +02:00' --until='2026-09-28 16:33:30 +02:00' --full-history --no-merges -- app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

DM11 · Constructible invalid state · Constructible in an invalid state · ×19

Constructible in an invalid state: Authentication common/src/main/kotlin/io/homeassistant/companion/android/database/authentication/Authentication.kt:8 — `Authentication`'s public constructor takes `host`, `username`, `password` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Authentication` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: LocationHistoryItem common/src/main/kotlin/io/homeassistant/companion/android/database/location/LocationHistoryItem.kt:14 — `LocationHistoryItem`'s public constructor takes `latitude`, `longitude`, `locationName`, `data` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LocationHistoryItem` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: NotificationItem common/src/main/kotlin/io/homeassistant/companion/android/database/notification/NotificationItem.kt:8 — `NotificationItem`'s public constructor takes `message`, `data`, `source` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `NotificationItem` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: TileEntity common/src/main/kotlin/io/homeassistant/companion/android/database/qs/TileEntity.kt:8 — `TileEntity`'s public constructor takes `tileId`, `iconName`, `entityId`, `label`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TileEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Attribute common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Attribute.kt:7 — `Attribute`'s public constructor takes `sensorId`, `name`, `value`, `valueType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Attribute` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Sensor common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Sensor.kt:7 — `Sensor`'s public constructor takes `id`, `state`, `lastSentState`, `lastSentIcon`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Sensor` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: SensorSetting common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorSetting.kt:22 — `SensorSetting`'s public constructor takes `sensorId`, `name`, `value` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `SensorSetting` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Server common/src/main/kotlin/io/homeassistant/companion/android/database/server/Server.kt:14 — `Server`'s public constructor takes `_name`, `nameOverride`, `_version`, `deviceRegistryId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Server` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: CameraTile common/src/main/kotlin/io/homeassistant/companion/android/database/wear/CameraTile.kt:12 — `CameraTile`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CameraTile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: EntityStateComplications common/src/main/kotlin/io/homeassistant/companion/android/database/wear/EntityStateComplications.kt:11 — `EntityStateComplications`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `EntityStateComplications` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: FavoriteCaches common/src/main/kotlin/io/homeassistant/companion/android/database/wear/FavoriteCaches.kt:11 — `FavoriteCaches`'s public constructor takes `id`, `name`, `icon` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `FavoriteCaches` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Favorites common/src/main/kotlin/io/homeassistant/companion/android/database/wear/Favorites.kt:11 — `Favorites`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Favorites` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: ThermostatTile common/src/main/kotlin/io/homeassistant/companion/android/database/wear/ThermostatTile.kt:12 — `ThermostatTile`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ThermostatTile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: ButtonWidgetEntity common/src/main/kotlin/io/homeassistant/companion/android/database/widget/ButtonWidgetEntity.kt:8 — `ButtonWidgetEntity`'s public constructor takes `iconName`, `domain`, `service`, `serviceData`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ButtonWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: CameraWidgetEntity common/src/main/kotlin/io/homeassistant/companion/android/database/widget/CameraWidgetEntity.kt:8 — `CameraWidgetEntity`'s public constructor takes `entityId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CameraWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: MediaPlayerControlsWidgetEntity common/src/main/kotlin/io/homeassistant/companion/android/database/widget/MediaPlayerControlsWidgetEntity.kt:8 — `MediaPlayerControlsWidgetEntity`'s public constructor takes `entityId`, `label`, `textColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `MediaPlayerControlsWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: StaticWidgetEntity common/src/main/kotlin/io/homeassistant/companion/android/database/widget/StaticWidgetEntity.kt:8 — `StaticWidgetEntity`'s public constructor takes `entityId`, `attributeIds`, `label`, `stateSeparator`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `StaticWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: TemplateWidgetEntity common/src/main/kotlin/io/homeassistant/companion/android/database/widget/TemplateWidgetEntity.kt:8 — `TemplateWidgetEntity`'s public constructor takes `template`, `lastUpdate`, `textColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TemplateWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: TodoWidgetEntity common/src/main/kotlin/io/homeassistant/companion/android/database/widget/TodoWidgetEntity.kt:14 — `TodoWidgetEntity`'s public constructor takes `entityId`, `textColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TodoWidgetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.

DM4 · Rich vs anemic model · Anemic entity · ×13

Anemic entity: Authentication common/src/main/kotlin/io/homeassistant/companion/android/database/authentication/Authentication.kt:8 — `Authentication` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: LocationHistoryItem common/src/main/kotlin/io/homeassistant/companion/android/database/location/LocationHistoryItem.kt:14 — `LocationHistoryItem` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: NotificationItem common/src/main/kotlin/io/homeassistant/companion/android/database/notification/NotificationItem.kt:8 — `NotificationItem` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Attribute common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Attribute.kt:7 — `Attribute` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Sensor common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Sensor.kt:7 — `Sensor` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: SensorSetting common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorSetting.kt:22 — `SensorSetting` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Server common/src/main/kotlin/io/homeassistant/companion/android/database/server/Server.kt:14 — `Server` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Setting common/src/main/kotlin/io/homeassistant/companion/android/database/settings/Setting.kt:8 — `Setting` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: CameraTile common/src/main/kotlin/io/homeassistant/companion/android/database/wear/CameraTile.kt:12 — `CameraTile` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: EntityStateComplications common/src/main/kotlin/io/homeassistant/companion/android/database/wear/EntityStateComplications.kt:11 — `EntityStateComplications` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: FavoriteCaches common/src/main/kotlin/io/homeassistant/companion/android/database/wear/FavoriteCaches.kt:11 — `FavoriteCaches` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Favorites common/src/main/kotlin/io/homeassistant/companion/android/database/wear/Favorites.kt:11 — `Favorites` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: ThermostatTile common/src/main/kotlin/io/homeassistant/companion/android/database/wear/ThermostatTile.kt:12 — `ThermostatTile` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.

D3 · God Classes · TooManyMethods · ×12

TooManyMethods: FakePlayer app/src/main/kotlin/io/homeassistant/companion/android/util/compose/media/player/FakePlayer.kt:26 — TooManyMethods — 123 methods. The bar is 30 methods; this is 93 over it, 4.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PrefsRepositoryImpl common/src/main/kotlin/io/homeassistant/companion/android/common/data/prefs/PrefsRepositoryImpl.kt:106 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× the bar. Most of these members implement prefs.PrefsRepository (68 of 69 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: MessagingManager app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:126 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IntegrationRepositoryImpl common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/impl/IntegrationRepositoryImpl.kt:72 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. Most of these members implement integration.IntegrationRepository (39 of 54 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: FrontendViewModel app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt:115 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HealthConnectSensorManager app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt:69 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainViewModel wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt:49 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebSocketRepositoryImpl common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketRepositoryImpl.kt:60 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. Most of these members implement websocket.WebSocketRepository (34 of 40 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: WebSocketCoreImpl common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt:142 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LocationSensorManager app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:60 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HomePresenterImpl wear/src/main/kotlin/io/homeassistant/companion/android/home/HomePresenterImpl.kt:33 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. Most of these members implement home.HomePresenter (33 of 35 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: SensorRepositoryImpl common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorRepositoryImpl.kt:19 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · FileTooLong · ×12

FileTooLong: notifications/MessagingManager.kt app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt — FileTooLong — 1497 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 997 over it, 2.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: integration/Entity.kt common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt — FileTooLong — 1030 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 530 over it, 2.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sensors/LocationSensorManager.kt app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt — FileTooLong — 980 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: LocationSensorManager (60-1390). The bar is 500 significant lines; this is 480 over it, 1.96× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: sensors/HealthConnectSensorManager.kt app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt — FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: HealthConnectSensorManager (69-1167). The bar is 500 significant lines; this is 404 over it, 1.81× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: impl/WebSocketCoreImpl.kt common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt — FileTooLong — 754 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: WebSocketCoreImpl (142-1263). The bar is 500 significant lines; this is 254 over it, 1.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: frontend/FrontendScreen.kt app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt — FileTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 242 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: frontend/FrontendViewModel.kt app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt — FileTooLong — 677 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: FrontendViewModel (115-1346). The bar is 500 significant lines; this is 177 over it, 1.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: migration/DatabaseMigration.kt common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt — FileTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 111 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: views/SensorDetailView.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt — FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 67 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mediaplayer/MediaPlayerControlsWidget.kt app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt — FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: MediaPlayerControlsWidget (42-768). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ui/AssistSheet.kt app/src/main/kotlin/io/homeassistant/companion/android/assist/ui/AssistSheet.kt — FileTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 25 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: impl/IntegrationRepositoryImpl.kt common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/impl/IntegrationRepositoryImpl.kt — FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: IntegrationRepositoryImpl (72-750). The bar is 500 significant lines; this is 7 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.

D3 · God Classes · MethodTooLong · ×12

MethodTooLong: MediaPlayerControlsWidget.getWidgetRemoteViews app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:66 — MethodTooLong — getWidgetRemoteViews runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainViewKt.MainView wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt:52 — MethodTooLong — MainView runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EntityKt.getIcon common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850 — MethodTooLong — getIcon runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ManageShortcutsViewKt.CreateShortcutView app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt:94 — MethodTooLong — CreateShortcutView runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HomeAssistantApplication.onCreate app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:82 — MethodTooLong — onCreate runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsViewKt.SettingsView wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SettingsView.kt:75 — MethodTooLong — SettingsView runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SensorUpdater.syncSensorsWithServer common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt:177 — MethodTooLong — syncSensorsWithServer runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SsidViewKt.SsidView app/src/main/kotlin/io/homeassistant/companion/android/settings/ssid/views/SsidView.kt:68 — MethodTooLong — SsidView runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Migration37to38.onPostMigrate common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:596 — MethodTooLong — onPostMigrate runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LocationSensorManager.sendLocationUpdate app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:872 — MethodTooLong — sendLocationUpdate runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ButtonWidgetConfigureActivity.onCreate app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt:212 — MethodTooLong — onCreate runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Migration16to17.migrate common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:272 — MethodTooLong — migrate runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D35 · Change Coupling · Change coupling · ×10

Change coupling: EntityGridVehicleScreen.kt ↔ MapVehicleScreen.kt app/src/main/kotlin/io/homeassistant/companion/android/vehicle/EntityGridVehicleScreen.kt — `app/src/main/kotlin/io/homeassistant/companion/android/vehicle/EntityGridVehicleScreen.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/vehicle/MapVehicleScreen.kt` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `2bdcbfd6` Mutualize Android Auto navigation_started event firing (#7468); `62b81a18` Remove runBlocking from ServerManager.activeServerId (#5722); `90bf7369` Clean up some left over code after update to getIcon (#3827) (at that commit the files were still `app/src/main/java/io/homeassistant/companion/android/vehicle/EntityGridVehicleScreen.kt` and `app/src/main/java/io/homeassistant/companion/android/vehicle/MapVehicleScreen.kt`) — run `git show` on any of them.
Change coupling: LaunchActivity.kt ↔ HANavHost.kt app/src/main/kotlin/io/homeassistant/companion/android/launch/LaunchActivity.kt — `app/src/main/kotlin/io/homeassistant/companion/android/launch/LaunchActivity.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/util/compose/HANavHost.kt` change together 65% of the time (11 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `26154d92` Add dedicated screen for invitation flow instead of WelcomeScreen (#6…; `99655c59` Add support for PiP for FrontendScreen (#6812); `c84d7f44` Add ExoPlayer support for FrontendScreen from frontend request (#6771) — run `git show` on any of them.
Change coupling: EntityWidget.kt ↔ TemplateWidget.kt app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt — `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidget.kt` change together 64% of the time (14 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `514d6c10` Move away from Main in Widgets (#6415); `e838330d` Code quality: use compat functions for Android 13 type extras (#4501) (at that commit the files were still `app/src/main/java/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt` and `app/src/main/java/io/homeassistant/companion/android/widgets/template/TemplateWidget.kt`); `7953f81b` Fix websocket stays subscribed after widget edit due to multiple inst… (at that commit the files were still `app/src/main/java/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt` and `app/src/main/java/io/homeassistant/companion/android/widgets/template/TemplateWidget.kt`) — run `git show` on any of them.
Change coupling: HomeView.kt ↔ SetFavoriteView.kt wear/src/main/kotlin/io/homeassistant/companion/android/home/views/HomeView.kt — `wear/src/main/kotlin/io/homeassistant/companion/android/home/views/HomeView.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SetFavoriteView.kt` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `64a425ac` Use ViewState in some views of the watch to avoid concurrent issues (…; `dbb1e8bf` Use suspend and transactions for Favorites dao (#2398) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/views/HomeView.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/views/SetFavoriteView.kt`); `47962841` Add areas to entity list on Wear (#2118) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/views/HomeView.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/views/SetFavoriteView.kt`) — run `git show` on any of them.
Change coupling: ServerSettingsFragment.kt ↔ WebViewActivity.kt app/src/main/kotlin/io/homeassistant/companion/android/settings/server/ServerSettingsFragment.kt — `app/src/main/kotlin/io/homeassistant/companion/android/settings/server/ServerSettingsFragment.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/webview/WebViewActivity.kt` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `2717a340` Introduce FrontendTarget and use it instead of WebViewActivity (#7087); `17e03ca3` Add app lock feature to FrontendScreen (#6756); `793bf01d` Add set security level when not set while opening a server (#6097) — run `git show` on any of them.
Change coupling: ConversationActivity.kt ↔ ConversationView.kt wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationActivity.kt — `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationActivity.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/views/ConversationView.kt` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f3071e79` Wear Assist: show login when logged out, scroll first item into view … (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/conversation/ConversationActivity.kt` and `wear/src/main/java/io/homeassistant/companion/android/conversation/views/ConversationView.kt`); `edf6ba5b` Use Assist pipeline STT/TTS on Wear OS (#3611) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/conversation/ConversationActivity.kt` and `wear/src/main/java/io/homeassistant/companion/android/conversation/views/ConversationView.kt`); `3c706bb7` Update Wear Assist with continued conversations, pipelines (#3604) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/conversation/ConversationActivity.kt` and `wear/src/main/java/io/homeassistant/companion/android/conversation/views/ConversationView.kt`) — run `git show` on any of them.
Change coupling: SensorReceiverBase.kt ↔ SensorWorker.kt common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorReceiverBase.kt — `common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorReceiverBase.kt` and `common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorWorker.kt` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `2c3406fe` Extract SensorReceiverBase update logic into SensorUpdater (#7107); `7d93d38b` Remove DatabaseEntryPoint (#7106) (at that commit the file was still `common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorWorkerBase.kt`); `2b2ece82` Remove appdatabase get instance (#6234) (at that commit the file was still `common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorWorkerBase.kt`) — run `git show` on any of them.
Change coupling: HomeView.kt ↔ ChooseEntityView.kt wear/src/main/kotlin/io/homeassistant/companion/android/home/views/HomeView.kt — `wear/src/main/kotlin/io/homeassistant/companion/android/home/views/HomeView.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/views/ChooseEntityView.kt` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `64a425ac` Use ViewState in some views of the watch to avoid concurrent issues (…; `d00c8236` Faster entity selection Wear OS (#2804) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/views/HomeView.kt` and `wear/src/main/java/io/homeassistant/companion/android/views/ChooseEntityView.kt`); `131296ad` Show names on shortcuts tile (#2142) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/views/HomeView.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/views/ChooseEntityView.kt`) — run `git show` on any of them.
Change coupling: HomeActivity.kt ↔ HomePresenterImpl.kt wear/src/main/kotlin/io/homeassistant/companion/android/home/HomeActivity.kt — `wear/src/main/kotlin/io/homeassistant/companion/android/home/HomeActivity.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/home/HomePresenterImpl.kt` change together 50% of the time (12 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `6a21a1c2` Add missing catch when interacting with network (#6264); `a8a73633` Implement support for multiple Shortcut Tiles on Wear OS (#3697) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/HomeActivity.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/HomePresenterImpl.kt`); `047abe93` Add new option to only show favorites on home screen (#3276) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/HomeActivity.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/HomePresenterImpl.kt`) — run `git show` on any of them.
Change coupling: MainViewModel.kt ↔ SetFavoriteView.kt wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt — `wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SetFavoriteView.kt` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `64a425ac` Use ViewState in some views of the watch to avoid concurrent issues (…; `dbb1e8bf` Use suspend and transactions for Favorites dao (#2398) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/MainViewModel.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/views/SetFavoriteView.kt`); `47962841` Add areas to entity list on Wear (#2118) (at that commit the files were still `wear/src/main/java/io/homeassistant/companion/android/home/MainViewModel.kt` and `wear/src/main/java/io/homeassistant/companion/android/home/views/SetFavoriteView.kt`) — run `git show` on any of them.

D3 · God Classes · ClassTooLong · ×8

ClassTooLong: LocationSensorManager app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:60 — ClassTooLong — 923 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 523 over it, 2.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HealthConnectSensorManager app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt:69 — ClassTooLong — 838 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 438 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebSocketCoreImpl common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt:142 — ClassTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 210 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FrontendViewModel app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt:115 — ClassTooLong — 583 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 183 over it, 1.46× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MediaPlayerControlsWidget app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:42 — ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: IntegrationRepositoryImpl common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/impl/IntegrationRepositoryImpl.kt:72 — ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 39 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NetworkSensorManager common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt:39 — ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 38 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CarSensorManager app/src/main/kotlin/io/homeassistant/companion/android/sensors/CarSensorManager.kt:35 — ClassTooLong — 426 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 26 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D30 · Dependency Vulnerabilities · Medium CVE · ×3

REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3

Duplicated block (12 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:467 — app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:467-478 | wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:319-330 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:464` calls `restartInactivityTimer` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:317` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) app/src/full/kotlin/io/homeassistant/companion/android/FullApplicationModule.kt:25 — app/src/full/kotlin/io/homeassistant/companion/android/FullApplicationModule.kt:25-36 | wear/src/main/kotlin/io/homeassistant/companion/android/ApplicationModule.kt:43-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `wear/src/main/kotlin/io/homeassistant/companion/android/ApplicationModule.kt:56` calls `OptIn` and `app/src/full/kotlin/io/homeassistant/companion/android/FullApplicationModule.kt:38` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:249 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:249-260 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt:171-182 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3

Duplicated block (10 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/home/views/DetailsPanelView.kt:219 — wear/src/main/kotlin/io/homeassistant/companion/android/home/views/DetailsPanelView.kt:219-228 | wear/src/main/kotlin/io/homeassistant/companion/android/home/views/DetailsPanelView.kt:273-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wear/src/main/kotlin/io/homeassistant/companion/android/home/views/DetailsPanelView.kt:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/onboarding/manualserver/ManualServerScreen.kt:113 — app/src/main/kotlin/io/homeassistant/companion/android/onboarding/manualserver/ManualServerScreen.kt:113-123 | app/src/main/kotlin/io/homeassistant/companion/android/onboarding/nameyourdevice/NameYourDeviceScreen.kt:106-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/onboarding/manualserver/ManualServerScreen.kt:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:526 — common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:526-535 | common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:548-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:526` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3

Duplicated block (8 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:2126 — app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:2126-2133 | app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:2172-2179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:2126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/BaseWidgetProvider.kt:81 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/BaseWidgetProvider.kt:81-88 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidget.kt:101-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/BaseWidgetProvider.kt:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt:79 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt:79-86 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidget.kt:232-239 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidget.kt:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3

Duplicated block (7 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:429 — app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:429-435 | wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:287-293 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `AssistMessage` names `io.homeassistant.companion.android.assist.ui.AssistMessage` in one and `io.homeassistant.companion.android.conversation.views.AssistMessage` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/tiles/CameraTile.kt:77 — wear/src/main/kotlin/io/homeassistant/companion/android/tiles/CameraTile.kt:77-83 | wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt:74-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `wear/src/main/kotlin/io/homeassistant/companion/android/tiles/CameraTile.kt:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:134 — common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:134-140 | common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:192-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (31 lines × 2) · ×2

Duplicated block (31 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:514 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:514-544 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:612-642 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:514` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SelectCameraTileView.kt:21 — wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SelectCameraTileView.kt:21-51 | wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SelectThermostatTileView.kt:21-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `tiles` to `List<CameraTile>` in one and `List<ThermostatTile>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2

Duplicated block (21 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:144 — app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:144-164 | wear/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:56-76 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:144` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:167` calls `addAction` and `wear/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/sensors/NotificationListenerSensorManager.kt:158 — app/src/main/kotlin/io/homeassistant/companion/android/sensors/NotificationListenerSensorManager.kt:158-178 | app/src/main/kotlin/io/homeassistant/companion/android/sensors/NotificationListenerSensorManager.kt:197-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/sensors/NotificationListenerSensorManager.kt:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2

Duplicated block (19 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:445 — app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:445-463 | wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:299-317 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:445` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:464` calls `restartInactivityTimer` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:318` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:379 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:379-397 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt:264-282 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt:264` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2

Duplicated block (16 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureViewModel.kt:250 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureViewModel.kt:250-265 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureViewModel.kt:189-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureViewModel.kt:250` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:345 — app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:345-362 | wear/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:70-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:345` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2

Duplicated block (15 lines × 2) app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt:73 — app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt:73-87 | app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearLandingView.kt:54-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt:73` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearFavoritesView.kt:72` calls `dismiss` and `app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearLandingView.kt:53` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:149 — common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:149-163 | common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:207-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:149` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:165` calls `execSQL` and `common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:222` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2

Duplicated block (14 lines × 2) app/src/debug/kotlin/io/homeassistant/companion/android/developer/catalog/HAUserInputScreen.kt:110 — app/src/debug/kotlin/io/homeassistant/companion/android/developer/catalog/HAUserInputScreen.kt:110-123 | app/src/debug/kotlin/io/homeassistant/companion/android/developer/catalog/HAUserInputScreen.kt:158-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/debug/kotlin/io/homeassistant/companion/android/developer/catalog/HAUserInputScreen.kt:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:132 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:132-145 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidgetConfigureScreen.kt:128-141 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidgetConfigureScreen.kt:143` calls `fillMaxSize` and `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:147` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2

Duplicated block (13 lines × 2) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/PhoneStateSensorManager.kt:283 — common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/PhoneStateSensorManager.kt:283-295 | common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/PhoneStateSensorManager.kt:327-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/PhoneStateSensorManager.kt:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:500 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:500-512 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:596-608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:500` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D6 · Cohesion (LCOM4) · Low cohesion · ×2

Low cohesion: MainViewModel (LCOM4 6) wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt:49 — MainViewModel's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DeveloperSettingsFragment (LCOM4 4) app/src/main/kotlin/io/homeassistant/companion/android/settings/developer/DeveloperSettingsFragment.kt:28 — DeveloperSettingsFragment's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

D1 · Cyclomatic Complexity · EntityKt.getIcon (cyclomatic 169) · ×1

EntityKt.getIcon (cyclomatic 169) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850 — EntityKt.getIcon has cyclomatic complexity 169 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This file is where this pass's cyclomatic complexity CONCENTRATES: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt holds 4 of the 41 methods over the threshold — including the worst — and 252 of the 687 points over it (37%), 2.2× the next-largest file (app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt at 117). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · FriendlyStateKt.stateResource (cyclomatic 104) · ×1

FriendlyStateKt.stateResource (cyclomatic 104) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/FriendlyState.kt:76 — FriendlyStateKt.stateResource has cyclomatic complexity 104 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · MessagingManager.handleMessage (cyclomatic 71) · ×1

MessagingManager.handleMessage (cyclomatic 71) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:302 — MessagingManager.handleMessage has cyclomatic complexity 71 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · EntityKt.sensorIcon (cyclomatic 63) · ×1

EntityKt.sensorIcon (cyclomatic 63) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1192 — EntityKt.sensorIcon has cyclomatic complexity 63 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This file is where this pass's cyclomatic complexity CONCENTRATES: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt holds 4 of the 41 methods over the threshold — including the worst — and 252 of the 687 points over it (37%), 2.2× the next-largest file (app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt at 117). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · MessagingManager.handleDeviceCommands (cyclomatic 55) · ×1

MessagingManager.handleDeviceCommands (cyclomatic 55) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:670 — MessagingManager.handleDeviceCommands has cyclomatic complexity 55 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · EntityKt.binarySensorIcon (cyclomatic 51) · ×1

EntityKt.binarySensorIcon (cyclomatic 51) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1113 — EntityKt.binarySensorIcon has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt holds 4 of the 41 methods over the threshold — including the worst — and 252 of the 687 points over it (37%), 2.2× the next-largest file (app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt at 117). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · Migration16to17.migrate (cyclomatic 51) · ×1

Migration16to17.migrate (cyclomatic 51) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:272 — Migration16to17.migrate has cyclomatic complexity 51 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · SensorUpdater.syncSensorsWithServer (cyclomatic 42) · ×1

SensorUpdater.syncSensorsWithServer (cyclomatic 42) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt:177 — SensorUpdater.syncSensorsWithServer has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · SensorDetailViewKt.SensorDetailView (cyclomatic 37) · ×1

SensorDetailViewKt.SensorDetailView (cyclomatic 37) app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt:100 — SensorDetailViewKt.SensorDetailView has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ManageShortcutsViewKt.CreateShortcutView (cyclomatic 32) · ×1

ManageShortcutsViewKt.CreateShortcutView (cyclomatic 32) app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt:94 — ManageShortcutsViewKt.CreateShortcutView has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MessagingManager.addExtrasToIntent (cyclomatic 30) · ×1

MessagingManager.addExtrasToIntent (cyclomatic 30) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:926 — MessagingManager.addExtrasToIntent has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · EntityKt.coverIcon (cyclomatic 29) · ×1

EntityKt.coverIcon (cyclomatic 29) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1143 — EntityKt.coverIcon has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This file is where this pass's cyclomatic complexity CONCENTRATES: common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt holds 4 of the 41 methods over the threshold — including the worst — and 252 of the 687 points over it (37%), 2.2× the next-largest file (app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt at 117). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · WebSocketCoreImpl.handleEvent (cyclomatic 27) · ×1

WebSocketCoreImpl.handleEvent (cyclomatic 27) common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt:915 — WebSocketCoreImpl.handleEvent has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · HealthConnectSensorManager.requestSensorUpdate (cyclomatic 27) · ×1

HealthConnectSensorManager.requestSensorUpdate (cyclomatic 27) app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt:440 — HealthConnectSensorManager.requestSensorUpdate has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · MediaPlayerControlsWidget.getWidgetRemoteViews (cyclomatic 27) · ×1

MediaPlayerControlsWidget.getWidgetRemoteViews (cyclomatic 27) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:66 — MediaPlayerControlsWidget.getWidgetRemoteViews has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ThreadManagerImpl.fullSyncPreferredDataset (cyclomatic 26) · ×1

ThreadManagerImpl.fullSyncPreferredDataset (cyclomatic 26) app/src/full/kotlin/io/homeassistant/companion/android/thread/ThreadManagerImpl.kt:87 — ThreadManagerImpl.fullSyncPreferredDataset has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · LocationSensorManager.shouldEnableHighAccuracyMode (cyclomatic 24) · ×1

LocationSensorManager.shouldEnableHighAccuracyMode (cyclomatic 24) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:532 — LocationSensorManager.shouldEnableHighAccuracyMode has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MainViewKt.MainView (cyclomatic 23) · ×1

MainViewKt.MainView (cyclomatic 23) wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt:52 — MainViewKt.MainView has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DeviceCommandsKt.commandBleTransmitter (cyclomatic 23) · ×1

DeviceCommandsKt.commandBleTransmitter (cyclomatic 23) common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/DeviceCommands.kt:124 — DeviceCommandsKt.commandBleTransmitter has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · SettingsFragment.onCreatePreferences (cyclomatic 22) · ×1

SettingsFragment.onCreatePreferences (cyclomatic 22) app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt:91 — SettingsFragment.onCreatePreferences has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WearToggleChip.entityToggleChipBackgroundColors (cyclomatic 21) · ×1

WearToggleChip.entityToggleChipBackgroundColors (cyclomatic 21) wear/src/main/kotlin/io/homeassistant/companion/android/util/WearToggleChip.kt:36 — WearToggleChip.entityToggleChipBackgroundColors has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WearToggleChipColors.equals (cyclomatic 20) · ×1

WearToggleChipColors.equals (cyclomatic 20) wear/src/main/kotlin/io/homeassistant/companion/android/util/WearToggleChip.kt:364 — WearToggleChipColors.equals has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · HealthServicesSensorManager.updateHealthServices (cyclomatic 19) · ×1

HealthServicesSensorManager.updateHealthServices (cyclomatic 19) wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt:188 — HealthServicesSensorManager.updateHealthServices has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: HealthServicesSensorManager.getActivityIcon (cyclomatic 49) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.

D1 · Cyclomatic Complexity · IntegrationRepositoryImpl.registerSensor (cyclomatic 19) · ×1

IntegrationRepositoryImpl.registerSensor (cyclomatic 19) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/impl/IntegrationRepositoryImpl.kt:579 — IntegrationRepositoryImpl.registerSensor has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · SensorManager.onSensorUpdated (cyclomatic 19) · ×1

SensorManager.onSensorUpdated (cyclomatic 19) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorManager.kt:317 — SensorManager.onSensorUpdated has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · OnSwipeListener.onTouch (cyclomatic 19) · ×1

OnSwipeListener.onTouch (cyclomatic 19) app/src/main/kotlin/io/homeassistant/companion/android/util/OnSwipeListener.kt:39 — OnSwipeListener.onTouch has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Migration37to38.onPostMigrate (cyclomatic 18) · ×1

Migration37to38.onPostMigrate (cyclomatic 18) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:596 — Migration37to38.onPostMigrate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MessagingManager.createOpenUriPendingIntent (cyclomatic 18) · ×1

MessagingManager.createOpenUriPendingIntent (cyclomatic 18) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1704 — MessagingManager.createOpenUriPendingIntent has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MessagingManager.notifyMissingPermission (cyclomatic 18) · ×1

MessagingManager.notifyMissingPermission (cyclomatic 18) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:2125 — MessagingManager.notifyMissingPermission has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · LocationTrackingViewKt.LocationTrackingHistoryRow (cyclomatic 18) · ×1

LocationTrackingViewKt.LocationTrackingHistoryRow (cyclomatic 18) app/src/main/kotlin/io/homeassistant/companion/android/settings/developer/location/views/LocationTrackingView.kt:149 — LocationTrackingViewKt.LocationTrackingHistoryRow has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WidgetDynamicFieldAdapter.onBindViewHolder (cyclomatic 18) · ×1

WidgetDynamicFieldAdapter.onBindViewHolder (cyclomatic 18) app/src/main/kotlin/io/homeassistant/companion/android/widgets/common/WidgetDynamicFieldAdapter.kt:44 — WidgetDynamicFieldAdapter.onBindViewHolder has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · LocationSensorManager.setupLocationTracking (cyclomatic 17) · ×1

LocationSensorManager.setupLocationTracking (cyclomatic 17) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:306 — LocationSensorManager.setupLocationTracking has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · LocationSensorManager.handleGeoUpdate (cyclomatic 17) · ×1

LocationSensorManager.handleGeoUpdate (cyclomatic 17) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:771 — LocationSensorManager.handleGeoUpdate has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ThermostatTile.onTileRequest (cyclomatic 16) · ×1

ThermostatTile.onTileRequest (cyclomatic 16) wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt:68 — ThermostatTile.onTileRequest has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · NotificationManagerExtensionsKt.cancelNotificationGroupIfNeeded (cyclomatic 16) · ×1

NotificationManagerExtensionsKt.cancelNotificationGroupIfNeeded (cyclomatic 16) common/src/main/kotlin/io/homeassistant/companion/android/common/util/NotificationManagerExtensions.kt:43 — NotificationManagerExtensionsKt.cancelNotificationGroupIfNeeded has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · LocationSensorManager.sendLocationUpdate (cyclomatic 16) · ×1

LocationSensorManager.sendLocationUpdate (cyclomatic 16) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:872 — LocationSensorManager.sendLocationUpdate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · HomeAssistantApplication.onCreate (cyclomatic 16) · ×1

HomeAssistantApplication.onCreate (cyclomatic 16) app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:82 — HomeAssistantApplication.onCreate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · AssistViewModel.runAssistPipeline (cyclomatic 16) · ×1

AssistViewModel.runAssistPipeline (cyclomatic 16) app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:428 — AssistViewModel.runAssistPipeline has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CarSensorManager.setListener (cyclomatic 16) · ×1

CarSensorManager.setListener (cyclomatic 16) app/src/main/kotlin/io/homeassistant/companion/android/sensors/CarSensorManager.kt:372 — CarSensorManager.setListener has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · SettingsActivity.onCreate (cyclomatic 16) · ×1

SettingsActivity.onCreate (cyclomatic 16) app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsActivity.kt:82 — SettingsActivity.onCreate has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · SensorDetailFragment.onViewCreated (cyclomatic 16) · ×1

SensorDetailFragment.onViewCreated (cyclomatic 16) app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/SensorDetailFragment.kt:95 — SensorDetailFragment.onViewCreated has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D2 · Cognitive Complexity · EntityKt.getIcon (cognitive 101) · ×1

EntityKt.getIcon (cognitive 101) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:850 — EntityKt.getIcon has cognitive complexity 101 (threshold 15). Drivers by points: if/else 28 (61 pts), match/switch 12 (40 pts) (nesting depth added 61). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ThreadManagerImpl.fullSyncPreferredDataset (cognitive 94) · ×1

ThreadManagerImpl.fullSyncPreferredDataset (cognitive 94) app/src/full/kotlin/io/homeassistant/companion/android/thread/ThreadManagerImpl.kt:87 — ThreadManagerImpl.fullSyncPreferredDataset has cognitive complexity 94 (threshold 15). Drivers by points: error handling 10 (52 pts), if/else 10 (37 pts), boolean chains 5 (nesting depth added 69). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MessagingManager.handleMessage (cognitive 85) · ×1

MessagingManager.handleMessage (cognitive 85) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:302 — MessagingManager.handleMessage has cognitive complexity 85 (threshold 15). Drivers by points: if/else 23 (56 pts), boolean chains 20, match/switch 3 (6 pts), error handling 1 (3 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SensorUpdater.syncSensorsWithServer (cognitive 70) · ×1

SensorUpdater.syncSensorsWithServer (cognitive 70) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorUpdater.kt:177 — SensorUpdater.syncSensorsWithServer has cognitive complexity 70 (threshold 15). Drivers by points: if/else 13 (28 pts), error handling 10 (24 pts), boolean chains 18 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FriendlyStateKt.stateResource (cognitive 65) · ×1

FriendlyStateKt.stateResource (cognitive 65) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/FriendlyState.kt:76 — FriendlyStateKt.stateResource has cognitive complexity 65 (threshold 15). Drivers by points: if/else 22 (60 pts), match/switch 3 (5 pts) (nesting depth added 40). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · MessagingManager.handleDeviceCommands (cognitive 60) · ×1

MessagingManager.handleDeviceCommands (cognitive 60) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:670 — MessagingManager.handleDeviceCommands has cognitive complexity 60 (threshold 15). Drivers by points: if/else 23 (41 pts), match/switch 6 (14 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · Migration16to17.migrate (cognitive 53) · ×1

Migration16to17.migrate (cognitive 53) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:272 — Migration16to17.migrate has cognitive complexity 53 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 24, loops 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · WebSocketCoreImpl.handleEvent (cognitive 51) · ×1

WebSocketCoreImpl.handleEvent (cognitive 51) common/src/main/kotlin/io/homeassistant/companion/android/common/data/websocket/impl/WebSocketCoreImpl.kt:915 — WebSocketCoreImpl.handleEvent has cognitive complexity 51 (threshold 15). Drivers by points: if/else 14 (34 pts), match/switch 2 (14 pts), error handling 2, boolean chains 1 (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ManageShortcutsViewKt.CreateShortcutView (cognitive 51) · ×1

ManageShortcutsViewKt.CreateShortcutView (cognitive 51) app/src/main/kotlin/io/homeassistant/companion/android/settings/shortcuts/legacy/views/ManageShortcutsView.kt:94 — ManageShortcutsViewKt.CreateShortcutView has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (31 pts), loops 3 (8 pts), boolean chains 7, match/switch 1 (5 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MainViewKt.MainView (cognitive 50) · ×1

MainViewKt.MainView (cognitive 50) wear/src/main/kotlin/io/homeassistant/companion/android/home/views/MainView.kt:52 — MainViewKt.MainView has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (38 pts), loops 2 (7 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MediaPlayerControlsWidget.getWidgetRemoteViews (cognitive 49) · ×1

MediaPlayerControlsWidget.getWidgetRemoteViews (cognitive 49) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:66 — MediaPlayerControlsWidget.getWidgetRemoteViews has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (30 pts), error handling 4 (10 pts), boolean chains 6, match/switch 1 (3 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · EntityKt.binarySensorIcon (cognitive 48) · ×1

EntityKt.binarySensorIcon (cognitive 48) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1113 — EntityKt.binarySensorIcon has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (47 pts), match/switch 1 (nesting depth added 23). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · NotificationManagerExtensionsKt.cancelNotificationGroupIfNeeded (cognitive 38) · ×1

NotificationManagerExtensionsKt.cancelNotificationGroupIfNeeded (cognitive 38) common/src/main/kotlin/io/homeassistant/companion/android/common/util/NotificationManagerExtensions.kt:43 — NotificationManagerExtensionsKt.cancelNotificationGroupIfNeeded has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (33 pts), boolean chains 5 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · SensorDetailViewKt.SensorDetailView (cognitive 37) · ×1

SensorDetailViewKt.SensorDetailView (cognitive 37) app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt:100 — SensorDetailViewKt.SensorDetailView has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 4 (11 pts), boolean chains 5 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LocationSensorManager.shouldEnableHighAccuracyMode (cognitive 32) · ×1

LocationSensorManager.shouldEnableHighAccuracyMode (cognitive 32) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:532 — LocationSensorManager.shouldEnableHighAccuracyMode has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 10, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SettingsFragment.onCreatePreferences (cognitive 32) · ×1

SettingsFragment.onCreatePreferences (cognitive 32) app/src/main/kotlin/io/homeassistant/companion/android/settings/SettingsFragment.kt:91 — SettingsFragment.onCreatePreferences has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 4, error handling 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ConversationViewModel.onCreate (cognitive 31) · ×1

ConversationViewModel.onCreate (cognitive 31) wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:65 — ConversationViewModel.onCreate has cognitive complexity 31 (threshold 15). Drivers by points: error handling 4 (16 pts), if/else 8 (14 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ThermostatTile.onTileRequest (cognitive 31) · ×1

ThermostatTile.onTileRequest (cognitive 31) wear/src/main/kotlin/io/homeassistant/companion/android/tiles/ThermostatTile.kt:68 — ThermostatTile.onTileRequest has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (21 pts), error handling 2 (6 pts), boolean chains 3, match/switch 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · WearToggleChip.entityToggleChipBackgroundColors (cognitive 29) · ×1

WearToggleChip.entityToggleChipBackgroundColors (cognitive 29) wear/src/main/kotlin/io/homeassistant/companion/android/util/WearToggleChip.kt:36 — WearToggleChip.entityToggleChipBackgroundColors has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 4 (8 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · OnSwipeListener.onTouch (cognitive 29) · ×1

OnSwipeListener.onTouch (cognitive 29) app/src/main/kotlin/io/homeassistant/companion/android/util/OnSwipeListener.kt:39 — OnSwipeListener.onTouch has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LocationSensorManager.setupBackgroundLocation (cognitive 28) · ×1

LocationSensorManager.setupBackgroundLocation (cognitive 28) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:365 — LocationSensorManager.setupBackgroundLocation has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 5 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · SensorReceiverBase.onReceive (cognitive 27) · ×1

SensorReceiverBase.onReceive (cognitive 27) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/SensorReceiverBase.kt:73 — SensorReceiverBase.onReceive has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2 (8 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Migration37to38.onPostMigrate (cognitive 27) · ×1

Migration37to38.onPostMigrate (cognitive 27) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:596 — Migration37to38.onPostMigrate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (27 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LocationSensorManager.handleGeoUpdate (cognitive 27) · ×1

LocationSensorManager.handleGeoUpdate (cognitive 27) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:771 — LocationSensorManager.handleGeoUpdate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), error handling 1 (3 pts), match/switch 2 (3 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · HealthConnectSensorManager.requestSensorUpdate (cognitive 26) · ×1

HealthConnectSensorManager.requestSensorUpdate (cognitive 26) app/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthConnectSensorManager.kt:440 — HealthConnectSensorManager.requestSensorUpdate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 26. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · EntityKt.coverIcon (cognitive 24) · ×1

EntityKt.coverIcon (cognitive 24) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1143 — EntityKt.coverIcon has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 9 (11 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · TileExtensions.setTileData (cognitive 24) · ×1

TileExtensions.setTileData (cognitive 24) app/src/main/kotlin/io/homeassistant/companion/android/qs/TileExtensions.kt:145 — TileExtensions.setTileData has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (4 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WidgetDynamicFieldAdapter.onBindViewHolder (cognitive 24) · ×1

WidgetDynamicFieldAdapter.onBindViewHolder (cognitive 24) app/src/main/kotlin/io/homeassistant/companion/android/widgets/common/WidgetDynamicFieldAdapter.kt:44 — WidgetDynamicFieldAdapter.onBindViewHolder has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · EntityKt.sensorIcon (cognitive 23) · ×1

EntityKt.sensorIcon (cognitive 23) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/Entity.kt:1192 — EntityKt.sensorIcon has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 3 (11 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ManageControlsViewKt.ManageControlsView (cognitive 23) · ×1

ManageControlsViewKt.ManageControlsView (cognitive 23) app/src/main/kotlin/io/homeassistant/companion/android/settings/controls/views/ManageControlsView.kt:71 — ManageControlsViewKt.ManageControlsView has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 6 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · EntityGridVehicleScreen.createEntityGrid (cognitive 23) · ×1

EntityGridVehicleScreen.createEntityGrid (cognitive 23) app/src/main/kotlin/io/homeassistant/companion/android/vehicle/EntityGridVehicleScreen.kt:139 — EntityGridVehicleScreen.createEntityGrid has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 2 (8 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CameraWidget.getWidgetRemoteViews (cognitive 23) · ×1

CameraWidget.getWidgetRemoteViews (cognitive 23) app/src/main/kotlin/io/homeassistant/companion/android/widgets/camera/CameraWidget.kt:107 — CameraWidget.getWidgetRemoteViews has cognitive complexity 23 (threshold 15). Drivers by points: error handling 4 (12 pts), if/else 6 (9 pts), match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LocationSensorManager.sendLocationUpdate (cognitive 22) · ×1

LocationSensorManager.sendLocationUpdate (cognitive 22) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:872 — LocationSensorManager.sendLocationUpdate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 3, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ButtonWidget.callConfiguredAction (cognitive 21) · ×1

ButtonWidget.callConfiguredAction (cognitive 21) app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidget.kt:264 — ButtonWidget.callConfiguredAction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · IntegrationRepositoryImpl.registerSensor (cognitive 20) · ×1

IntegrationRepositoryImpl.registerSensor (cognitive 20) common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/impl/IntegrationRepositoryImpl.kt:579 — IntegrationRepositoryImpl.registerSensor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MessagingManager.createOpenUriPendingIntent (cognitive 20) · ×1

MessagingManager.createOpenUriPendingIntent (cognitive 20) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1704 — MessagingManager.createOpenUriPendingIntent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, error handling 1 (2 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TileExtensions.tileClicked (cognitive 20) · ×1

TileExtensions.tileClicked (cognitive 20) app/src/main/kotlin/io/homeassistant/companion/android/qs/TileExtensions.kt:211 — TileExtensions.tileClicked has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WebsocketManager.collectNotifications (cognitive 20) · ×1

WebsocketManager.collectNotifications (cognitive 20) app/src/main/kotlin/io/homeassistant/companion/android/websocket/WebsocketManager.kt:204 — WebsocketManager.collectNotifications has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (7 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WearToggleChipColors.equals (cognitive 19) · ×1

WearToggleChipColors.equals (cognitive 19) wear/src/main/kotlin/io/homeassistant/companion/android/util/WearToggleChip.kt:364 — WearToggleChipColors.equals has cognitive complexity 19 (threshold 15). Drivers by points: if/else 19. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · MessagingManager.handleActions (cognitive 19) · ×1

MessagingManager.handleActions (cognitive 19) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1604 — MessagingManager.handleActions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ConversationViewModel.setPipeline (cognitive 18) · ×1

ConversationViewModel.setPipeline (cognitive 18) wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:198 — ConversationViewModel.setPipeline has cognitive complexity 18 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 4 (7 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · HealthServicesSensorManager.updateHealthServices (cognitive 18) · ×1

HealthServicesSensorManager.updateHealthServices (cognitive 18) wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt:188 — HealthServicesSensorManager.updateHealthServices has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · IBeaconMonitor.setBeacons (cognitive 18) · ×1

IBeaconMonitor.setBeacons (cognitive 18) common/src/main/kotlin/io/homeassistant/companion/android/common/bluetooth/ble/IBeaconMonitor.kt:43 — IBeaconMonitor.setBeacons has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DeviceCommandsKt.commandBleTransmitter (cognitive 18) · ×1

DeviceCommandsKt.commandBleTransmitter (cognitive 18) common/src/main/kotlin/io/homeassistant/companion/android/common/notifications/DeviceCommands.kt:124 — DeviceCommandsKt.commandBleTransmitter has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 8 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · HomeAssistantApplication.onCreate (cognitive 18) · ×1

HomeAssistantApplication.onCreate (cognitive 18) app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:82 — HomeAssistantApplication.onCreate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CarSensorManager.requestSensorUpdate (cognitive 18) · ×1

CarSensorManager.requestSensorUpdate (cognitive 18) app/src/main/kotlin/io/homeassistant/companion/android/sensors/CarSensorManager.kt:337 — CarSensorManager.requestSensorUpdate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CameraTile.onTileResourcesRequest (cognitive 17) · ×1

CameraTile.onTileResourcesRequest (cognitive 17) wear/src/main/kotlin/io/homeassistant/companion/android/tiles/CameraTile.kt:115 — CameraTile.onTileResourcesRequest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · LocationTrackingViewKt.LocationTrackingHistoryRow (cognitive 17) · ×1

LocationTrackingViewKt.LocationTrackingHistoryRow (cognitive 17) app/src/main/kotlin/io/homeassistant/companion/android/settings/developer/location/views/LocationTrackingView.kt:149 — LocationTrackingViewKt.LocationTrackingHistoryRow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 4, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · SensorDetailViewModel.setEnabled (cognitive 17) · ×1

SensorDetailViewModel.setEnabled (cognitive 17) app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/SensorDetailViewModel.kt:227 — SensorDetailViewModel.setEnabled has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SensorDetailViewKt.SensorDetailTopPanel (cognitive 17) · ×1

SensorDetailViewKt.SensorDetailTopPanel (cognitive 17) app/src/main/kotlin/io/homeassistant/companion/android/settings/sensor/views/SensorDetailView.kt:373 — SensorDetailViewKt.SensorDetailTopPanel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CameraWidgetConfigureActivity.onCreate (cognitive 17) · ×1

CameraWidgetConfigureActivity.onCreate (cognitive 17) app/src/main/kotlin/io/homeassistant/companion/android/widgets/camera/CameraWidgetConfigureActivity.kt:62 — CameraWidgetConfigureActivity.onCreate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PhoneStateSensorManager.updateSimSensor (cognitive 16) · ×1

PhoneStateSensorManager.updateSimSensor (cognitive 16) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/PhoneStateSensorManager.kt:230 — PhoneStateSensorManager.updateSimSensor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (3 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LocationSensorManager.setupLocationTracking (cognitive 16) · ×1

LocationSensorManager.setupLocationTracking (cognitive 16) app/src/full/kotlin/io/homeassistant/companion/android/sensors/LocationSensorManager.kt:306 — LocationSensorManager.setupLocationTracking has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 7, error handling 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · CarSensorManager.setListener (cognitive 16) · ×1

CarSensorManager.setListener (cognitive 16) app/src/main/kotlin/io/homeassistant/companion/android/sensors/CarSensorManager.kt:372 — CarSensorManager.setListener has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ButtonWidgetConfigureActivity.onCreate (cognitive 16) · ×1

ButtonWidgetConfigureActivity.onCreate (cognitive 16) app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidgetConfigureActivity.kt:212 — ButtonWidgetConfigureActivity.onCreate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, error handling 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Near-duplicate member family (5 members, 28 shared lines) · ×1

Near-duplicate member family (5 members, 28 shared lines) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:463 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:463-496 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:559-592 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:657-690 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:692-725 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:727-760 — These 5 members are variants of one another: a block of 28 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.

D4 · Code Duplication · Near-duplicate member pair (38 shared lines) · ×1

Near-duplicate member pair (38 shared lines) wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:286 — wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:286-337 | app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:428-495 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:973 — app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:973-995 | app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:999-1026 | app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:1030-1053 | app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:1057-1078 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1

Duplicated block (49 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SetCameraTileView.kt:42 — wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SetCameraTileView.kt:42-90 | wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SetThermostatTileView.kt:47-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `wear/src/main/kotlin/io/homeassistant/companion/android/home/views/SetCameraTileView.kt:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: `DEFAULT_REFRESH_INTERVAL` names `io.homeassistant.companion.android.tiles.CameraTile.Companion.DEFAULT_REFRESH_INTERVAL` in one and `io.homeassistant.companion.android.tiles.ThermostatTile.Companion.DEFAULT_REFRESH_INTERVAL` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (45 lines × 2) · ×1

Duplicated block (45 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/OnboardingPresenterImpl.kt:44 — wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/OnboardingPresenterImpl.kt:44-88 | wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/manual/ManualSetupPresenterImpl.kt:36-80 — before extracting anything, compare `wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/OnboardingPresenterImpl.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/manual/ManualSetupPresenterImpl.kt` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/manual/ManualSetupPresenterImpl.kt:36` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1

Duplicated block (40 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:229 — app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:229-268 | wear/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:88-127 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/HomeAssistantApplication.kt:229` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (26–27 lines × 3) · ×1

Duplicated block (26–27 lines × 3) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureViewModel.kt:213 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureViewModel.kt:213-238 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidgetConfigureViewModel.kt:169-195 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureViewModel.kt:152-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.

D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1

Duplicated block (24 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:136 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:136-159 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt:116-139 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt` and `app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidgetConfigureScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/entity/EntityWidgetConfigureScreen.kt:136` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1

Duplicated block (19–20 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/OnboardingPresenterImpl.kt:124 — wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/OnboardingPresenterImpl.kt:124-143 | wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/manual/ManualSetupPresenterImpl.kt:83-101 — before extracting anything, compare `wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/OnboardingPresenterImpl.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/onboarding/manual/ManualSetupPresenterImpl.kt` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1

Duplicated block (18 lines × 2) common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt:441 — common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt:441-458 | common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt:524-541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/kotlin/io/homeassistant/companion/android/common/sensors/NetworkSensorManager.kt:441` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1

Duplicated block (17 lines × 4) app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:979 — app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:979-995 | app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:1010-1026 | app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:1037-1053 | app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:1062-1078 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt:979` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1

Duplicated block (16 lines × 5) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:478 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:478-493 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:574-589 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:672-687 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:707-722 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:742-757 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:478` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1

Duplicated block (14–15 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidget.kt:135 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidget.kt:135-148 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/camera/CameraWidget.kt:226-240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidget.kt:135` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1

Duplicated block (12–13 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:409 — app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:409-421 | wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:271-282 — before extracting anything, compare `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:409` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `AssistMessage` names `io.homeassistant.companion.android.assist.ui.AssistMessage` in one and `io.homeassistant.companion.android.conversation.views.AssistMessage` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/kotlin/io/homeassistant/companion/android/assist/AssistViewModel.kt:423` calls `restartInactivityTimer` and `wear/src/main/kotlin/io/homeassistant/companion/android/conversation/ConversationViewModel.kt:283` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1

Duplicated block (10–11 lines × 2) app/src/full/kotlin/io/homeassistant/companion/android/notifications/FirebaseCloudMessagingService.kt:42 — app/src/full/kotlin/io/homeassistant/companion/android/notifications/FirebaseCloudMessagingService.kt:42-51 | wear/src/main/kotlin/io/homeassistant/companion/android/notifications/FirebaseCloudMessagingService.kt:42-52 — before extracting anything, compare `app/src/full/kotlin/io/homeassistant/companion/android/notifications/FirebaseCloudMessagingService.kt` and `wear/src/main/kotlin/io/homeassistant/companion/android/notifications/FirebaseCloudMessagingService.kt` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/full/kotlin/io/homeassistant/companion/android/notifications/FirebaseCloudMessagingService.kt:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1041 — app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1041-1051 | wear/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:115-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1041` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:1052` calls `isAtLeast` and `wear/src/main/kotlin/io/homeassistant/companion/android/notifications/MessagingManager.kt:126` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1

Duplicated block (7–9 lines × 2) wear/src/main/kotlin/io/homeassistant/companion/android/tiles/TileViews.kt:82 — wear/src/main/kotlin/io/homeassistant/companion/android/tiles/TileViews.kt:82-90 | wear/src/main/kotlin/io/homeassistant/companion/android/tiles/TileViews.kt:170-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1

Duplicated block (9 lines × 2) app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidget.kt:68 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/button/ButtonWidget.kt:68-76 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/template/TemplateWidget.kt:70-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (12 lines × 7) · ×1

Duplicated block (12 lines × 7) app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:464 — app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:464-475 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:499-510 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:560-571 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:595-606 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:658-669 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:693-704 | app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt:728-739 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1

Duplicated block (6 lines × 2) common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:128 — common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:128-133 | common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:186-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: home-assistant-android:common — home-assistant-android:common: abstractness 0.15, instability 0.00, distance 0.85 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

P3 · Security & performance tooling · SAST runs, but gates no merge · ×1

SAST runs, but gates no merge — `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×1

Sync-over-async blocking wear/src/main/kotlin/io/homeassistant/companion/android/sensors/HealthServicesSensorManager.kt:188 — `updateHealthServices` is async and calls runBlocking — a blocking call inside async code stalls the coroutine's thread, and every coroutine dispatched to it for as long as it runs.

Minor — 19 finding(s)

DM2 · Strongly-typed ids · Primitive id on a domain type · ×9

Primitive id on a domain type: LocationHistoryItem.serverId common/src/main/kotlin/io/homeassistant/companion/android/database/location/LocationHistoryItem.kt:34 — `LocationHistoryItem.serverId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
Primitive id on a domain type: NotificationItem.serverId common/src/main/kotlin/io/homeassistant/companion/android/database/notification/NotificationItem.kt:20 — `NotificationItem.serverId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
Primitive id on a domain type: Attribute.sensorId common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Attribute.kt:9 — `Attribute.sensorId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Sensor.serverId common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/Sensor.kt:11 — `Sensor.serverId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
Primitive id on a domain type: SensorSetting.sensorId common/src/main/kotlin/io/homeassistant/companion/android/database/sensor/SensorSetting.kt:24 — `SensorSetting.sensorId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Server.deviceRegistryId common/src/main/kotlin/io/homeassistant/companion/android/database/server/Server.kt:24 — `Server.deviceRegistryId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: CameraTile.entityId common/src/main/kotlin/io/homeassistant/companion/android/database/wear/CameraTile.kt:19 — `CameraTile.entityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: EntityStateComplications.entityId common/src/main/kotlin/io/homeassistant/companion/android/database/wear/EntityStateComplications.kt:16 — `EntityStateComplications.entityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: ThermostatTile.entityId common/src/main/kotlin/io/homeassistant/companion/android/database/wear/ThermostatTile.kt:19 — `ThermostatTile.entityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 166 significant file(s) lose their only recent owner: app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendViewModel.kt, app/src/main/kotlin/io/homeassistant/companion/android/frontend/FrontendScreen.kt, common/src/main/kotlin/io/homeassistant/companion/android/database/migration/DatabaseMigration.kt, common/src/main/kotlin/io/homeassistant/companion/android/common/data/integration/impl/IntegrationRepositoryImpl.kt, app/src/main/kotlin/io/homeassistant/companion/android/widgets/mediaplayer/MediaPlayerControlsWidget.kt, wear/src/main/kotlin/io/homeassistant/companion/android/home/views/HomeView.kt, wear/src/main/kotlin/io/homeassistant/companion/android/home/MainViewModel.kt, app/src/main/kotlin/io/homeassistant/companion/android/util/compose/entity/EntityPicker.kt (+158 more). Pair on, review, or document these before any departure.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split app · ×1

Split app — A sprawling Android frontend with 147 namespaces is a grab-bag of unrelated UI components. Suggested: split into focused android frontend namespaces

D26 · Project Cohesion · Split wear · ×1

Split wear — A large Android wear project with 21 namespaces is a grab-bag of unrelated modules like onboarding/integration/conversation. Suggested: split into focused wear namespaces

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 16 of 491 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 491 of the 942 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: app/src/main/kotlin/io/homeassistant/companion/android/widgets/common/WidgetDynamicFieldAdapter.kt, common/src/main/kotlin/io/homeassistant/companion/android/common/bluetooth/ble/TransmitterManager.kt, common/src/main/kotlin/io/homeassistant/companion/android/common/util/tts/TextToSpeechClient.kt, app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearTemplateTile.kt, app/src/main/kotlin/io/homeassistant/companion/android/util/ForegroundServiceLauncher.kt, app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearOnboardingView.kt, app/src/full/kotlin/io/homeassistant/companion/android/settings/wear/views/SettingsWearTemplateTileList.kt, common/src/main/kotlin/io/homeassistant/companion/android/common/util/tts/AndroidTextToSpeechEngine.kt (and 8 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

P6 · Release Hygiene · No changelog · ×1

No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-39609ff743d247c28be12877a06e5f31/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-39609ff743d247c28be12877a06e5f31/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	82	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	4	artifacts/raw/osv-scanner.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	osv-scanner	—	osv-scanner --format json --recursive .	0	artifacts/raw/osv-scanner.json

Run 01a0e8ca-b01e-795f-9c12-4a29f16bea54 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Home-Assistant/android

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 85% · Strong ·

At a glance — Architecture · 90% · Adequate · gated by D26 ·

At a glance — Maturity · 63% · Adequate · gated by M2 ·

At a glance — Readiness · 62% · Adequate · gated by P3 ·

At a glance — Security · 66% · Adequate · gated by D29 ·

At a glance — Domain Modelling · 48% · Weak · gated by DM2, DM4, DM11 ·

At a glance — Performance · 85% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts