Oakane — Watchdog Audit

Executive summary

This system holds an adequate overall standing of 54%, indicating a workable asset that carries significant operational risk. While the code itself is clean and well-structured, the low readiness score suggests the team lacks the safety nets required for reliable, daily delivery. The business value here is moderate, with a rebuild effort estimated at roughly 0.2 person-years or €32,000. This relatively low cost of change means the organization can afford to invest in stability without facing prohibitive technical debt penalties.

The primary concern is operational fragility. With a readiness score of just 25%, the system lacks the automated checks and disaster recovery procedures needed to ensure consistent uptime. This gap exposes the business to potential outages and slow incident response times, as there is no verified process for restoring service after a failure. The absence of a changelog further complicates release management, making it difficult to track what has shipped or to roll back changes if issues arise.

Conversely, the code quality and architecture are strong. The codebase is free of boilerplate and exhibits excellent domain modeling, meaning the logic is clear and maintainable. This high level of craftsmanship ensures that when changes are made, they are less likely to introduce defects. However, this strength is undermined by the lack of automated testing in the delivery pipeline, which prevents the team from confidently deploying these well-written changes.

The highest-leverage action is to implement a continuous integration workflow that builds and runs tests on every change. This single step provides immediate protection against regressions and lays the foundation for faster, safer releases. Following this, the team should document recovery procedures to address the readiness gap. While some areas like performance and event sourcing were not measured, the current picture is sufficient to prioritize these foundational improvements.

Code Health 100% ★ Exemplary Architecture 95% ★ Exemplary Maturity 59% Adequate · gated by M2 Readiness 25% ⚠ Critical · gated by P1, P3 Security 100% ★ Exemplary Domain Modelling 100% ★ Exemplary

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.

Readiness 25% · 46% weightMaturity 59% · 25% weightArchitecture 95% · 14% weightCode Health 100% · 8% weightSecurity 100% · 4% weightDomain Modelling 100% · 2% weight

Raise Readiness 25 → 70 (the Healthy floor) ⇒ headline 54 → ~72.

Code composition — where the lines go

Tests 100%

New since the last scan (36+)

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

D4 · Duplicated block (16–17 lines × 2) core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt
D4 · Duplicated block (12 lines × 2) core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt
D4 · Duplicated block (11 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt
D4 · Duplicated block (11 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt
D4 · Duplicated block (9 lines × 6) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt
D4 · Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt
D4 · Duplicated block (9 lines × 11) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt
D4 · Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt
D4 · Duplicated block (9 lines × 2) core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt
D4 · Duplicated block (10 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt
D15 · Hotspot: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt
D15 · Hotspot: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt
D17 · TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt
D17 · TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt
D17 · TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt
D17 · TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/wallet/PrimaryWalletIcon.kt
D35 · Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt
D35 · Boundary-crossing change coupling: TransactionsTopAppBarView.kt ↔ TransactionsViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt
D35 · Boundary-crossing change coupling: PrimaryWalletView.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt
D35 · Boundary-crossing change coupling: GoalItemView.kt ↔ CommonModule.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt
D35 · Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt
D35 · Boundary-crossing change coupling: SelectIconVIew.kt ↔ CategoriesViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt
D35 · Boundary-crossing change coupling: MonthlyBudgetView.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt
D35 · Boundary-crossing change coupling: CategoriesSheetView.kt ↔ CategoriesViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt
D35 · Change coupling: WalletRepositoryImpl.kt ↔ WalletLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt
D35 · Change coupling: WalletRepository.kt ↔ WalletLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/WalletRepository.kt
D35 · Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasource.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt
D35 · Change coupling: MonthlyBudgetRepositoryImpl.kt ↔ MonthlyBudgetViewModel.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/MonthlyBudgetRepositoryImpl.kt
D35 · Change coupling: CreateWalletSheetView.swift ↔ WalletsScreen.swift iosApp/iosApp/designSystem/ui/sheet/CreateWalletSheetView.swift
D35 · Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt
D35 · Change coupling: TransactionRepositoryImpl.kt ↔ TransactionLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/TransactionRepositoryImpl.kt
D35 · Change coupling: MainActivity.kt ↔ OakaneNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/MainActivity.kt
D35 · Change coupling: CreateCategoryContentView.kt ↔ SelectIconVIew.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/CreateCategoryContentView.kt
D35 · Change coupling: WalletMapper.kt ↔ WalletRepositoryImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/model/WalletMapper.kt
D35 · Change coupling: MySqlDriverFactory.kt ↔ CommonModule.kt core/database/src/androidMain/kotlin/com/kakapo/database/MySqlDriverFactory.kt
D35 · Change coupling: CategoryLocalDatasourceImpl.kt ↔ CategoriesViewModel.kt core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/CategoryLocalDatasourceImpl.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 — €11,000–€53,000

Cost to rebuild	€11,000–€53,000 (0.1–0.3 person-years (177–562 h), ~1 engineer)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.8× (at 54% quality) — the last 20% of quality is most of the work
Size & shape	Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~0.2 person-years of build effort (about ~€32,000 to rebuild). Its weakest lens is Readiness at 25% — 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.

Add a CI workflow that builds and runs the test suite on every push/PR.

+25.6 pts · Medium effort · CI/CD gates

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).

+22.3 pts · Medium effort · DR & Backup

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

+19.8 pts · Medium effort · Release Hygiene

Diagnosis — what's actually going on

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

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

Evidence: valuation: Medium, ~0.2 person-years rebuild (28,120 LoC) · weakest lens: Readiness 25%

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

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.

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

→ Add a CI workflow that builds and runs the test suite on every push/PR.

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

237 modules, 376 dependencies. 7 dependency cycles across 16 modules, marked above the diagonal.

Showing the 40 most-connected modules; 197 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 →	2 database.model	3 model.reminder	4 model.system	5 oakane.presentation.model	6 model.category	8 model.transaction	9 model.goal	10 model	11 model.monthlyBudget	12 model.report	13 model.wallet	14 data.model	15 model.wallet.WalletLogItem	16 data.repository.base	17 domain.usecase.base	24 oakane.presentation.viewModel.goal	26 oakane.presentation.viewModel.home	31 oakane.presentation.viewModel.reports
1 app.buildlogic
2 database.model
3 model.reminder
4 model.system
5 oakane.presentation.model
6 model.category						1		1
7 oakane			1
8 model.transaction					1			1
9 model.goal						1		1
10 model						1	1
11 model.monthlyBudget								2
12 model.report					1			1
13 model.wallet					2	2		3
14 data.model	8	1			3	1	2	7	1	2	3
15 model.wallet.WalletLogItem						4	1				4
16 data.repository.base		1	1		2	1	2	1	1	2	3	5
17 domain.usecase.base						2	1		1		1	5
18 data.repository.impl		1	1		2	1	2	1	1	2	3	5		13
19 domain.usecase.impl					2	2	1		1		1	6	3	30	11
20 oakane.presentation.viewModel.addGoal							1	1						2	1
21 oakane.presentation.viewModel.addTransaction			1		1	4		1			2	2		4	2
22 oakane.presentation.viewModel.categories			1	1	2	1								2
23 oakane.presentation.viewModel.createWallet					1			1			3			2
24 oakane.presentation.viewModel.goal			1				2	1			1	1		4	1
25 oakane.presentation.viewModel.goals			1				1							2
26 oakane.presentation.viewModel.home			1			1	1		1		1			5	1
27 oakane.presentation.viewModel.main			1											1	1
28 oakane.presentation.viewModel.monthlyBudget			1		2			1	1			2		4	2
29 oakane.presentation.viewModel.onboarding				1				2						4
30 oakane.presentation.viewModel.reminder		2												1
31 oakane.presentation.viewModel.reports			1					1	1	1	2			4	1
32 oakane.presentation.viewModel.settings			1					2						4
33 oakane.presentation.viewModel.termAndService			1											1
34 oakane.presentation.viewModel.transaction			1			1		1			1			3	1
35 oakane.presentation.viewModel.transactions			1		2	4								2
36 oakane.presentation.viewModel.wallet			1								6	1		2	2
37 oakane.presentation.viewModel.wallets			1					1			1			2
38 oakane.presentation.feature.goal.component			1				1	1								2
39 oakane.presentation.feature.home.component			1			1		2	1								4
40 oakane.presentation.feature.reports.component			2					1	1	1								3

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

At a glance — Code Health · 100% · Exemplary ·

The Good

D1 · Kotlin Cyclomatic Complexity 10.0 D2 · Kotlin Cognitive Complexity 10.0 D3 · Kotlin God Classes 10.0 D4 · Kotlin Code Duplication 9.8 D17 · Kotlin Explicit Debt 10.0

At a glance — Architecture · 95% · Exemplary ·

The Good

D35 · Kotlin Change Coupling 9.2 AX10 · Repo Code composition 9.6 AX9 · Repo CQS / query purity 10.0

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

The Good

D15 · Kotlin Churn × Complexity Hotspots 10.0 D21 · Kotlin Naming Consistency 10.0 M1 · Repo Documentation (README) 8.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

D19 · Kotlin Documentation Quality 6.0 D34 · Kotlin Knowledge Freshness 6.0

The Ugly

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

At a glance — Readiness · 25% · Critical · gated by P1, P3 ·

The Good

D13 · Kotlin Secret Scanning 10.0

The Bad

P6 · Repo Release Hygiene 5.0

The Ugly

P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P5 · Repo DR & Backup 4.0

At a glance — Security · 100% · Exemplary ·

The Good

D28 · Kotlin Secrets (history) 10.0 D29 · Kotlin Static Analysis (SAST) 10.0

At a glance — Domain Modelling · 100% · Exemplary ·

The Good

DM12 · Repo Ambient inputs in the domain 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 10.0

Roadmap

First, establish a CI workflow to automatically build and test every push or pull request to ensure code quality. Second, document your disaster recovery strategy by defining RTO and RPO targets and maintaining a tested restore procedure. Third, maintain a changelog to track what ships in each release, and finally, create architecture decision records to document significant design choices and their consequences.

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

Do this	Helps	Effort	Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.	+25.6 pts	Medium	CI/CD gates
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).	+22.3 pts	Medium	DR & Backup
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+19.8 pts	Medium	Release Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+8.5 pts	Low	ADR Quality
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness.	+5.2 pts	Low	Knowledge Freshness
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).	+10.0 pts	Medium	Architecture documentation
Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2).	+3.4 pts	Low	Documentation Quality
Add a README to the 9 of 9 project(s) that lack one — worth up to 2 pts.	+5.1 pts	Medium	Documentation (README)

File quality

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

File	Score	Band	Worst signal
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt	5.5	Mixed	Change Coupling: Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewContract.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt	6.2	Mixed	Change Coupling: Boundary-crossing change coupling: GoalItemView.kt ↔ CommonModule.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt	7.0	Mixed	Code Duplication: Duplicated block (10 lines × 2)
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt	7.0	Mixed	Change Coupling: Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewModel.kt
core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt	7.8	Mixed	Change Coupling: Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasource.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt	8.0	Near-clean	Change Coupling: Boundary-crossing change coupling: TransactionsTopAppBarView.kt ↔ TransactionsViewModel.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt	8.0	Near-clean	Change Coupling: Boundary-crossing change coupling: PrimaryWalletView.kt ↔ HomeViewModel.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt	8.0	Near-clean	Change Coupling: Boundary-crossing change coupling: SelectIconVIew.kt ↔ CategoriesViewContract.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt	8.0	Near-clean	Change Coupling: Boundary-crossing change coupling: MonthlyBudgetView.kt ↔ HomeViewModel.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt	8.0	Near-clean	Change Coupling: Boundary-crossing change coupling: CategoriesSheetView.kt ↔ CategoriesViewModel.kt
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt	8.2	Near-clean	Explicit Debt: TodoComment
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt	8.2	Near-clean	Explicit Debt: TodoComment
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/wallet/PrimaryWalletIcon.kt	8.2	Near-clean	Explicit Debt: TodoComment
core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt	8.5	Near-clean	Code Duplication: Duplicated block (16–17 lines × 2)
core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt	8.5	Near-clean	Code Duplication: Duplicated block (12 lines × 2)
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt	8.5	Near-clean	Code Duplication: Duplicated block (11 lines × 2)
composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt	8.5	Near-clean	Code Duplication: Duplicated block (11 lines × 2)
shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt	8.5	Near-clean	Code Duplication: Duplicated block (9 lines × 6)
shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt	8.5	Near-clean	Code Duplication: Duplicated block (9 lines × 2)
shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt	8.5	Near-clean	Code Duplication: Duplicated block (9 lines × 11)

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

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 — 32

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 — 8

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

Could not be resolved — 48

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. 24 of 27 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — 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 — 27 dimensions across the health lenses

D1D2D3D4D13D15D17D19D20D21D28D29D34D35AX10AX9DM12DM6DM8M1M2M3M4P1P3P5P6

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, 43 of 50 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 01a0c0ba-10dc-7f7e-82be-d3b0cf176d6c.

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.

D4 Code Duplication — 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 10 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .swift (8,100 lines, 29% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
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: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency 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. Dependency Hygiene ran out of its 5-minute budget before it had finished, so what it reports here is a floor rather than a complete count. The rows above are real and stand; what is not known is how many more there are. This is a limit of the analysis run, not a finding about this repository.
D14 License Compliance — evaluation did not complete — License Compliance not included (check did not complete) — excluded from the score.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 639 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
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: D22 has no public-API collector for any other ecosystem, and the remedy is to write one — no change to the scan image can close it.
D30 Dependency Vulnerabilities — 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. Osv: the scanner produced no output at all, so no dependency was actually scanned. 'osv-scanner' exited 128 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
D43 Malicious 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. Osv: the scanner produced no output at all, so no dependency was actually scanned. 'osv-scanner' exited 128 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
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, 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.
AX3 Project dependency cycles — 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 which project references which — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
AX4 Dependency direction — 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 direction each project reference points — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's 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.
AX8 Test isolation — 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 which projects are test projects, and what they reference — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
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 — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
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.
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.
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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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.
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").
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.
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.
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").
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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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.
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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 (3): D19, D21, 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 Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 5 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 CategoryIconMapperKt.asIcon at 49 — they are counted neither in the figure above nor in this dimension's score. 5 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: composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/model/CategoryIconMapper.kt (CategoryIconMapperKt.asIcon at 49), iosApp/iosApp/designSystem/model/CategoryIconMapper.swift (CategoryIconName.asIconCategory at 49), iosApp/iosApp/main/ContentView.swift (ContentView.ScreenContent at 18), shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt (AddTransactionViewModel.handleEvent at 18), shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt (CategoriesViewModel.handleEvent at 16). 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.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

Do you agree with this assessment?

D3 · God Classes10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Stronggated by 10 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

10 duplicated block group(s) detected. Measured on part of this repository only: .swift (29% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (9 lines × 2) · ×3shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:148

Duplicated block (11 lines × 2) · ×2composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110

Duplicated block (16–17 lines × 2)core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52

Duplicated block (12 lines × 2)core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:58

Duplicated block (9 lines × 6)shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt:66

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

What to do

Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AddTransactionViewModel.kt, GoalViewModel.kt, MonthlyBudgetMapper.kt. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with SelectCategorySheet.kt, ButtonFilterView.kt. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Duplicated block (16–17 lines × 2) finding(s) in Code Duplication — start with TransactionEntity.kt. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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?

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?

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 2 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt (14×18=252); shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt (2×16=32)

Hotspot: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt · ×2shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:55

What to do

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

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

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Stronggated by 4 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

4 deducted task-comment markers across 28120 LoC (0.0/KLoC) → score 10.0. 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 · ×4composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt:49

What to do

Resolve the 4 TodoComment finding(s) in Explicit Debt — start with ImageGoalPicker.kt, CreateWalletView.kt, GoalItemView.kt. — One of this dimension's main actionable groups (4 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 QualityAdequate◐ 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 Adequate / 10 · rule-coverage 100% · ceiling Documented

Oakane's README is a strong feature-rich description of the app and its cross-platform KMP architecture. It names all features (expense tracking, custom categories, recurring monthly budgeting, backup/import) and outlines project structure with build.gradle.kts files, but it lacks installation/build instructions, an overview of what the project does beyond the features list, and any contribution guidance. The document is clipped mid-structure, so the full outline sections exist but are not flagged as missing.

Documentation: no installation or build instructions · ×2README.md

What to do

Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.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?

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)10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 178) — 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.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

Do you agree with this assessment?

D34 · Knowledge Freshness6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

59 of 150 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Theme.kt. Counted over 150 of the 516 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

What to do

Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling9.2 / 10Adequategated by 10 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.2 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: HomeScreen.kt↔HomeNavigation.kt 92%; WalletRepositoryImpl.kt↔WalletLocalDatasourceImpl.kt 90%; HomeNavigation.kt↔OakaneNavigation.kt 83%

Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewContract.kt · ×10composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt

Change coupling: HomeScreen.kt ↔ HomeNavigation.kt · ×15composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt

What to do

Resolve the 10 Boundary-crossing change coupling finding(s) in Change Coupling — start with HomeNavigation.kt (2), CategoryItemView.kt (2), TransactionsTopAppBarView.kt. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 15 Change coupling finding(s) in Change Coupling — start with TransactionRepository.kt (2), HomeScreen.kt, WalletRepositoryImpl.kt. — One of this dimension's main actionable groups (15 warning-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.6 / 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?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

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?

M1 · Documentation (README)8.0 / 10Strong✓ 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 README to the 9 of 9 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.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.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

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).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.

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 gates0.0 / 10Critical✓ Tool-verified

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.

No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

Add a CI workflow that builds and runs the test suite on every push/PR.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ 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.

No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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?

P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).

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?

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	100%	Exemplary	Solid.
Architecture	95%	Exemplary	Solid.
Maturity	59%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	25%	Critical — gated by P1, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	100%	Exemplary	Strongest area.
Domain Modelling	100%	Exemplary	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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release

Not included — 94 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 — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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 — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
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 — ~193 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 — no .kt test runner
D12 Dependency Hygiene — Dependency Hygiene incomplete (time budget)
D14 License Compliance — License Compliance not included (check did not complete)
D16 Bus Factor — single-contributor repository — bus factor is not applicable
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 — Production source is present (.kt, .swift) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. 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
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
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.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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.
D43 Malicious Dependencies — Scanner failed to run — not a clean result
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a CS/VB/GO/SCALA/SWIFT/DART class graph, and this repository's production source is .kt, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
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
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
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
P12 CI test-gate honesty — no CI workflow found
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from 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
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 — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
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
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
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 — 10 finding(s)

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

Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewContract.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 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) — 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 `efd42ae3` create basic screen for wallet and add navigation to wallets; `62b91df4` add navigation from home to transaction; `585cc116` creating general structure for add budget screen and create navigatio… — run `git show` on any of them.
Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 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) — 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 `efd42ae3` create basic screen for wallet and add navigation to wallets; `62b91df4` add navigation from home to transaction; `585cc116` creating general structure for add budget screen and create navigatio… — run `git show` on any of them.
Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt` (context shared) sit in DIFFERENT parts of the tree yet 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) — 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 7 shared commits counted here, the most recent 3 are `e5cb308b` load category when tapped and create some function to load data categ… (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt`); `8dfb3a2e` saving image from gallery in android side (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt`); `cddc5aee` finishing view for creating category view (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: TransactionsTopAppBarView.kt ↔ TransactionsViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transactions/TransactionsViewModel.kt` (context shared) 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 `586bcbd3` feat: refactor transactions screen state and filtering; `44d84eb6` feat: enhance theme handling and UI components; `3cd62eec` implement filter transactions by date — run `git show` on any of them.
Boundary-crossing change coupling: PrimaryWalletView.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt` (context shared) sit in DIFFERENT parts of the tree yet 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) — 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 7 shared commits counted here, the most recent 3 are `44d84eb6` feat: enhance theme handling and UI components; `5311c51d` feat: add balance visibility toggle (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/WalletBalanceView.kt`); `ca676a99` finishing addjustment for home screen ios (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/WalletBalanceView.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: GoalItemView.kt ↔ CommonModule.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/di/CommonModule.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 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 7 shared commits counted here, the most recent 3 are `327461b0` feat: refactor goal management and add goal validation; `110b28e9` feat: enhance image handling and file management; `46943368` feat: implement add goal saving feature — run `git show` on any of them.
Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewContract.kt` (context shared) sit in DIFFERENT parts of the tree yet 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) — 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 `e5cb308b` load category when tapped and create some function to load data categ… (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt`); `8dfb3a2e` saving image from gallery in android side (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt`); `cddc5aee` finishing view for creating category view (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: SelectIconVIew.kt ↔ CategoriesViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewContract.kt` (context shared) sit in DIFFERENT parts of the tree yet 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) — 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 `84cd6a15` finishing create wallet view and add currency symbols in currency enu…; `f356f8f6` add conditional check before parsing string color into Long color in …; `a182bac5` add adjustment in some swift component, and make some change in ui an… (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/SelectCategoryIconVIew.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: MonthlyBudgetView.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `44d84eb6` feat: enhance theme handling and UI components; `0e43c6f9` feat: implement recurring monthly budget setting and update UI; `1d6528b2` get total transaction income and expense, creating use case to genera… — run `git show` on any of them.
Boundary-crossing change coupling: CategoriesSheetView.kt ↔ CategoriesViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt` (context composeApp) and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt` (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `9f3838bf` implementing icon color selection in select icon view both in ios and…; `79491883` implement select icon from selection icon view; `a2d53c4b` add color picker when creating custom category — run `git show` on any of them.

Serious — 32 finding(s)

D35 · Change Coupling · Change coupling · ×15

Change coupling: HomeScreen.kt ↔ HomeNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt` and `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt` change together 92% of the time (11 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 11 shared commits counted here, the most recent 3 are `efd42ae3` create basic screen for wallet and add navigation to wallets; `62b91df4` add navigation from home to transaction; `585cc116` creating general structure for add budget screen and create navigatio… — run `git show` on any of them.
Change coupling: WalletRepositoryImpl.kt ↔ WalletLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt` and `core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/WalletLocalDatasourceImpl.kt` change together 90% of the time (9 of the 10 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 9 shared commits counted here, the most recent 3 are `036da0ec` feat: implement move balance between wallets; `970fb425` change flow how to create default wallet with make user decide if it …; `3ccb1fd7` implement get total balance in all wallet in reports screen (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/WalletRepositoryImpl.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/WalletLocalDatasourceImpl.kt`) — run `git show` on any of them.
Change coupling: HomeNavigation.kt ↔ OakaneNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt` and `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/navigation/OakaneNavigation.kt` change together 83% of the time (10 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 10 shared commits counted here, the most recent 3 are `efd42ae3` create basic screen for wallet and add navigation to wallets; `62b91df4` add navigation from home to transaction; `585cc116` creating general structure for add budget screen and create navigatio… — run `git show` on any of them.
Change coupling: WalletRepository.kt ↔ WalletLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/WalletRepository.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/WalletRepository.kt` and `core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/WalletLocalDatasourceImpl.kt` change together 80% of the time (8 of the 10 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 `970fb425` change flow how to create default wallet with make user decide if it …; `3ccb1fd7` implement get total balance in all wallet in reports screen (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/WalletRepository.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/WalletLocalDatasourceImpl.kt`); `4cc9fa34` add functionality update wallet in wallet screen (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/WalletRepository.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/WalletLocalDatasourceImpl.kt`) — run `git show` on any of them.
Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasource.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt` and `core/database/src/commonMain/kotlin/com/kakapo/database/datasource/base/TransactionLocalDatasource.kt` change together 77% of the time (10 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) 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 10 shared commits counted here, the most recent 3 are `c3c8a19d` feat: add wallet transfer logging and transaction retrieval by wallet…; `fd85ba53` fixing bug load all transaction without date, and load all transaction (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/base/TransactionLocalDatasource.kt`); `86917fdd` implement filter transaction by month (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/base/TransactionLocalDatasource.kt`) — run `git show` on any of them.
Change coupling: MonthlyBudgetRepositoryImpl.kt ↔ MonthlyBudgetViewModel.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/MonthlyBudgetRepositoryImpl.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/MonthlyBudgetRepositoryImpl.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.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) 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 `d501b7e9` feat: refactor budget input and add currency support; `5b0d4f7f` fixing load budget not change when filter month is changed (at that commit the file was still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/MonthlyBudgetRepositoryImpl.kt`); `1d6528b2` get total transaction income and expense, creating use case to genera… (at that commit the file was still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/MonthlyBudgetRepositoryImpl.kt`) — run `git show` on any of them.
Change coupling: CreateWalletSheetView.swift ↔ WalletsScreen.swift iosApp/iosApp/designSystem/ui/sheet/CreateWalletSheetView.swift — `iosApp/iosApp/designSystem/ui/sheet/CreateWalletSheetView.swift` and `iosApp/iosApp/screen/wallets/WalletsScreen.swift` change together 69% of the time (9 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `b11189a9` feat: implement saving new wallets and update WalletsScreen UI; `17e97bca` feat: refactor sheet presentation and implement dynamic height; `f903f5cb` fixing bug wallet not changed color in wallets screen — run `git show` on any of them.
Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt` and `core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/TransactionLocalDatasourceImpl.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 `c3c8a19d` feat: add wallet transfer logging and transaction retrieval by wallet…; `fd85ba53` fixing bug load all transaction without date, and load all transaction (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt`); `86917fdd` implement filter transaction by month (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt`) — run `git show` on any of them.
Change coupling: TransactionRepositoryImpl.kt ↔ TransactionLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/TransactionRepositoryImpl.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/TransactionRepositoryImpl.kt` and `core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/TransactionLocalDatasourceImpl.kt` change together 57% of the time (12 of the 21 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 12 shared commits counted here, the most recent 3 are `c3c8a19d` feat: add wallet transfer logging and transaction retrieval by wallet…; `fd85ba53` fixing bug load all transaction without date, and load all transaction (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/TransactionRepositoryImpl.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt`); `86917fdd` implement filter transaction by month (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/TransactionRepositoryImpl.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt`) — run `git show` on any of them.
Change coupling: MainActivity.kt ↔ OakaneNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/MainActivity.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/MainActivity.kt` and `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/navigation/OakaneNavigation.kt` change together 56% of the time (10 of the 18 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 10 shared commits counted here, the most recent 3 are `020e0b8c` feat: update dependencies and integrate WorkManager for background tasks; `6ec2eadd` feat: enhance navigation transitions and improve UI components; `0c78b7f3` feat: enhance drawer and navigation behavior — run `git show` on any of them.
Change coupling: OnBoardingScreen.kt ↔ CreateWalletView.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt` and `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt` change together 50% of the time (7 of the 14 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 `64039058` feat: refactor on-boarding and wallet creation flow; `3ab219db` integrate selected currency to create wallet bottom sheet; `970fb425` change flow how to create default wallet with make user decide if it … — run `git show` on any of them.
Change coupling: CreateCategoryContentView.kt ↔ SelectIconVIew.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/CreateCategoryContentView.kt — `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/CreateCategoryContentView.kt` and `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.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 `58959d47` refactoring property name for SelectedIconModel; `83a9aeee` move some file and finishing CategoryLimitDropdownMenuView (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/SelectCategoryIconVIew.kt`); `a182bac5` add adjustment in some swift component, and make some change in ui an… (at that commit the file was still `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/SelectCategoryIconVIew.kt`) — run `git show` on any of them.
Change coupling: WalletMapper.kt ↔ WalletRepositoryImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/model/WalletMapper.kt — `core/data/src/commonMain/kotlin/com/kakapo/data/model/WalletMapper.kt` and `core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt` change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `71801041` Improved currency symbol display in Android by refactoring to use Tex…; `9a45b195` implement load wallets in wallets screen android side (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/model/WalletMapper.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/WalletRepositoryImpl.kt`); `51bc5b05` implement save wallet into database (at that commit the files were still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/model/WalletMapper.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/WalletRepositoryImpl.kt`) — run `git show` on any of them.
Change coupling: MySqlDriverFactory.kt ↔ CommonModule.kt core/database/src/androidMain/kotlin/com/kakapo/database/MySqlDriverFactory.kt — `core/database/src/androidMain/kotlin/com/kakapo/database/MySqlDriverFactory.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/di/CommonModule.kt` change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `df29cef7` feat: refactor recurring budget and add reminder functionality; `bbb32845` feat: add WalletTransferEntity and implement database migration; `800a0af8` refactor: move wallet dropdown component to ui module — run `git show` on any of them.
Change coupling: CategoryLocalDatasourceImpl.kt ↔ CategoriesViewModel.kt core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/CategoryLocalDatasourceImpl.kt — `core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/CategoryLocalDatasourceImpl.kt` and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt` change together 50% of the time (5 of the 10 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 5 shared commits counted here, the most recent 3 are `201da456` implement swipe to delete for category in android side (at that commit the file was still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/CategoryLocalDatasourceImpl.kt`); `0835a21f` implement update category (at that commit the file was still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/CategoryLocalDatasourceImpl.kt`); `e5cb308b` load category when tapped and create some function to load data categ… (at that commit the file was still `shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/CategoryLocalDatasourceImpl.kt`) — run `git show` on any of them.

D17 · Explicit Debt · TodoComment · ×4

TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt:49 — //TODO change with new i con soon — 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 composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt:52 — //Todo change with new i con soon — 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 composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt:46 — // TODO change with new icon soon — 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 composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/wallet/PrimaryWalletIcon.kt:34 — //TODO change with new icon soon — 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.

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

Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:148 — shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:148-156 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:97-105 — 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.
Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:87 — shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:87-95 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallet/WalletViewModel.kt:65-73 — 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.
Duplicated block (9 lines × 2) core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt:19 — core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt:19-27 | core/database/src/commonMain/kotlin/com/kakapo/database/model/MonthlyBudgetEntity.kt:17-25 — 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×2

Hotspot: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:55 — shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt changed 14 times in last 90 days, max cyclomatic complexity 18 in AddTransactionViewModel.handleEvent at line 55. 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 2025-01-09..2025-04-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-01-09 05:45:01 +07:00' --until='2025-04-09 05:45:01 +07:00' --full-history --no-merges -- shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.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: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt:41 — shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt changed 2 times in last 90 days, max cyclomatic complexity 16 in CategoriesViewModel.handleEvent at line 41. 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 2025-01-09..2025-04-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-01-09 05:45:01 +07:00' --until='2025-04-09 05:45:01 +07:00' --full-history --no-merges -- shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.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.

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

Duplicated block (11 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110 — composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110-120 | composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/CategoriesScreen.kt:142-152 — 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 `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110` 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 (11 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:70 — composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:70-80 | composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:126-136 — 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 `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:70` 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 first that the copies are not typed on the same thing: the declarations holding them bind `modifier` to `Modifier` in one and `Modifier = Modifier` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:81` calls `Icon` and `composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:137` 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 (16–17 lines × 2) · ×1

Duplicated block (16–17 lines × 2) core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52 — core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52-67 | core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:75-91 — 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 `core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52` 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 (12 lines × 2) · ×1

Duplicated block (12 lines × 2) core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:58 — core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:58-69 | core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:92-103 — 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 × 6) · ×1

Duplicated block (9 lines × 6) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt:66 — shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt:66-75 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:77-85 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.kt:103-111 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/reports/ReportsViewModel.kt:139-147 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transaction/TransactionViewModel.kt:81-89 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallets/WalletsViewModel.kt:66-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.

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

Duplicated block (9 lines × 11) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt:87 — shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt:87-95 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:152-160 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goals/GoalsViewModel.kt:62-70 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt:131-139 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/main/MainViewModel.kt:43-51 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.kt:113-121 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/reports/ReportsViewModel.kt:149-157 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transaction/TransactionViewModel.kt:101-109 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transactions/TransactionsViewModel.kt:129-137 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallet/WalletViewModel.kt:97-105 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallets/WalletsViewModel.kt:76-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transaction/TransactionViewModel.kt:113` calls `e` and `shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:164` 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 (10 lines × 2) · ×1

Duplicated block (10 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt:62 — composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt:62-71 | composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/settings/SettingsScreen.kt:176-185 — 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.

P1 · CI/CD gates · No CI pipeline · ×1

No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

Minor — 8 finding(s)

D19 · Documentation Quality · Documentation · ×2

Documentation: no installation or build instructions README.md — No build or setup instructions for a KMP multiplatform project with Android/iOS support. Add a 'How to Run' section covering the full build, plugin configuration (google-services.json), and running both platforms.
Documentation: no usage examples README.md — No runnable example showing how to create an expense or add a recurring budget. Add a short usage snippet demonstrating the core flow (expense logging, recurring setup) so readers can run it without code.

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/`.

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

Orphaned files with no living knowledge — 59 of 150 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; 150 of the 516 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: composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Theme.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Color.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/wallet/component/sheet/FilterLogSheetView.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/termAndService/TermAndServiceScreen.kt, iosApp/iosApp/designSystem/theme/IconConstant.swift, core/model/src/commonMain/kotlin/com/kakapo/model/category/CategoryIconName.kt, core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/ImportRecurringBudgetUseCaseImpl.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/component/textField/currency/CurrencyTextFieldState.kt (and 51 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.

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.

M2 · Architecture documentation · No architecture diagram/doc · ×1

No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

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	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-516eab7838ec44a0bcafc570a7cfa762/history.json --exit-code 0 --source .	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-516eab7838ec44a0bcafc570a7cfa762/tree.json --exit-code 0 --source .	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 .	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	—
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.	—
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.	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.	—
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.	—
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.	—
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.	—
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.	—
D43 · Malicious Dependencies	osv-scanner	—	osv-scanner --format json --recursive .	—

Run 01a0c0ba-10dc-7f7e-82be-d3b0cf176d6c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Uwi0/Oakane

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 100% · Exemplary ·

At a glance — Architecture · 95% · Exemplary ·

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

At a glance — Readiness · 25% · Critical · gated by P1, P3 ·

At a glance — Security · 100% · Exemplary ·

At a glance — Domain Modelling · 100% · Exemplary ·

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