Public report of nikbulavin/cashsense, published 16 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 17:42 UTC · Survey ID cd_1b403763ae104031a43d50a9094a088d

nikbulavin/cashsense

Measured 16 November 2026, 17:41 UTC, at code version 57e919e

First survey, so nothing to compare with yet
CAI score 57.9out of 100 Adequate
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 26,579 lines of product code in 47 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 49.7

Findings by how serious they are

9 critical 86 serious 17 minor

15 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 17:41 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

47of 47 dimensions measured by tools.
89of 112 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
47dimensions across 7 lenses, read from 26,579 lines of product code in 47 projects.
Chapters

Executive summary

nikbulavin/cashsense falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 57.9 out of 100 and is rated Adequate, and seven of its nine critical findings are security problems in the build pipeline.

Production Readiness, at 49.7, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 6.3 points. Improving the documentation comes next, worth about 2.6 points. Raising Production Readiness to 70 would lift the score to about 63.2.

Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and two sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, limiting the secret to its own step and making the hidden dependencies explicit would close these risks.

The product code is 26,579 lines, about €32,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 49.7 · counts for 46%Domain Modelling 53.3 · counts for 25%Maturity 65.7 · counts for 14%Security and Compliance 71.0 · counts for 8%Code Health 93.8 · counts for 4%Performance 94.3 · counts for 2%Architecture 96.3 · counts for 1%

If Production Readiness rose from 49.7 to 70, the lowest score rated Strong, the score would rise from 57.9 to about 63.2.

Code composition: what the lines of code are
Product code 99%Tests 1%
Rebuild cost: about €32,000 · Estimate
Cost to rebuild€11,000 to €54,000, for 178 to 564 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 26,579 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 6.3 points · Medium effort · Security & performance tooling
2
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Raises the score by about 2.6 points · Low effort · Documentation Quality
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Raises the score by about 2.6 points · Low effort · ADR Quality

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €32,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 49.7 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 8 Domain Modelling findings · Common cause
8 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Rich vs anemic model (5 findings) · Strongly-typed ids (3 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 6.3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch cashsense:core:common cashsense:core:common cashsense:core:data cashsense:core:data cashsense:core:data->cashsense:core:common cashsense:core:domain cashsense:core:domain cashsense:core:domain->cashsense:core:data cashsense:core:model cashsense:core:model cashsense:core:domain->cashsense:core:model cashsense:core:locales cashsense:core:locales cashsense:core:navigation cashsense:core:navigation cashsense:core:shortcuts cashsense:core:shortcuts cashsense:core:shortcuts->cashsense:core:common cashsense:core:shortcuts->cashsense:core:data cashsense:core:shortcuts->cashsense:core:locales cashsense:core:shortcuts->cashsense:core:model cashsense:core:ui cashsense:core:ui cashsense:core:ui->cashsense:core:common cashsense:core:ui->cashsense:core:locales cashsense:core:ui->cashsense:core:model cashsense:feature:category:detail:impl cashsense:feature:category:detail:impl cashsense:feature:category:detail:impl->cashsense:core:data cashsense:feature:category:detail:impl->cashsense:core:domain cashsense:feature:category:detail:impl->cashsense:core:locales cashsense:feature:category:editor:api cashsense:feature:category:editor:api cashsense:feature:category:detail:impl->cashsense:feature:category:editor:api cashsense:feature:transaction:detail:api cashsense:feature:transaction:detail:api cashsense:feature:category:detail:impl->cashsense:feature:transaction:detail:api cashsense:feature:category:editor:api->cashsense:core:navigation cashsense:feature:category:list:impl cashsense:feature:category:list:impl cashsense:feature:category:list:impl->cashsense:core:data cashsense:feature:category:list:impl->cashsense:core:locales cashsense:feature:category:list:impl->cashsense:feature:category:editor:api cashsense:feature:subscription:dialog:api cashsense:feature:subscription:dialog:api cashsense:feature:category:list:impl->cashsense:feature:subscription:dialog:api cashsense:feature:wallet:dialog:api cashsense:feature:wallet:dialog:api cashsense:feature:category:list:impl->cashsense:feature:wallet:dialog:api cashsense:feature:home:impl cashsense:feature:home:impl cashsense:feature:home:impl->cashsense:core:data cashsense:feature:home:impl->cashsense:core:domain cashsense:feature:home:impl->cashsense:core:locales cashsense:feature:home:impl->cashsense:feature:category:editor:api cashsense:feature:home:impl->cashsense:feature:subscription:dialog:api cashsense:feature:home:impl->cashsense:feature:transaction:detail:api cashsense:feature:transaction:editor:api cashsense:feature:transaction:editor:api cashsense:feature:home:impl->cashsense:feature:transaction:editor:api cashsense:feature:transaction:overview:api cashsense:feature:transaction:overview:api cashsense:feature:home:impl->cashsense:feature:transaction:overview:api cashsense:feature:home:impl->cashsense:feature:wallet:dialog:api cashsense:feature:subscription:dialog:api->cashsense:core:navigation cashsense:feature:transaction:detail:api->cashsense:core:navigation cashsense:feature:transaction:detail:impl cashsense:feature:transaction:detail:impl cashsense:feature:transaction:detail:impl->cashsense:core:data cashsense:feature:transaction:detail:impl->cashsense:core:domain cashsense:feature:transaction:detail:impl->cashsense:core:locales cashsense:feature:transaction:detail:impl->cashsense:feature:transaction:detail:api cashsense:feature:transaction:detail:impl->cashsense:feature:transaction:editor:api cashsense:feature:transaction:editor:api->cashsense:core:model cashsense:feature:transaction:editor:api->cashsense:core:navigation cashsense:feature:transaction:editor:api->cashsense:feature:transaction:overview:api cashsense:feature:transaction:overview:api->cashsense:core:navigation cashsense:feature:transaction:overview:impl cashsense:feature:transaction:overview:impl cashsense:feature:transaction:overview:impl->cashsense:core:data cashsense:feature:transaction:overview:impl->cashsense:core:domain cashsense:feature:transaction:overview:impl->cashsense:core:locales cashsense:feature:transaction:overview:impl->cashsense:feature:transaction:detail:api cashsense:feature:transaction:overview:impl->cashsense:feature:transaction:editor:api cashsense:feature:transaction:overview:impl->cashsense:feature:transaction:overview:api cashsense:feature:transaction:overview:impl->cashsense:feature:wallet:dialog:api cashsense:feature:wallet:dialog:api->cashsense:core:navigation cashsense:mobile cashsense:mobile cashsense:mobile->cashsense:core:data cashsense:mobile->cashsense:core:domain cashsense:mobile->cashsense:core:model cashsense:mobile->cashsense:core:shortcuts cashsense:mobile->cashsense:core:ui cashsense:mobile->cashsense:feature:category:detail:impl cashsense:mobile->cashsense:feature:category:editor:api cashsense:mobile->cashsense:feature:category:list:impl cashsense:mobile->cashsense:feature:home:impl cashsense:mobile->cashsense:feature:subscription:dialog:api cashsense:mobile->cashsense:feature:transaction:detail:api cashsense:mobile->cashsense:feature:transaction:detail:impl cashsense:mobile->cashsense:feature:transaction:editor:api cashsense:mobile->cashsense:feature:transaction:overview:api cashsense:mobile->cashsense:feature:transaction:overview:impl cashsense:mobile->cashsense:feature:wallet:dialog:api __more__ +27 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

137 modules, with 171 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 97 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 cashsense.core.analytics2 cashsense.core.model3 cashsense.core.network.model4 core.navigation5 cashsense.core.database.model6 cashsense.core.database.util7 cashsense.core.datastore8 cashsense.core.network9 cashsense.core.notifications10 cashsense.core.ui.component11 cashsense.core.ui.util12 cashsense.feature.home.impl.model13 cashsense.feature.transaction.overview.api14 cashsense.core.data.repository15 cashsense.core.database.dao16 cashsense.core.network.ktor17 cashsense.feature.transaction.editor.api18 cashsense.core.data.util19 cashsense.core.database20 cashsense.core.domain21 cashsense.core.network.di22 cashsense.core.shortcuts23 cashsense.feature.category.editor.impl24 cashsense.feature.category.list.impl25 cashsense.feature.subscription.dialog.impl26 cashsense.feature.subscription.list.impl27 cashsense.feature.transaction.detail.impl28 cashsense29 cashsense.core.data.repository.impl30 cashsense.core.database.di31 cashsense.feature.category.detail.impl32 cashsense.feature.home.impl33 cashsense.feature.settings.impl34 cashsense.feature.transaction.editor.impl35 cashsense.feature.transaction.importer.impl36 cashsense.feature.transaction.overview.impl37 cashsense.feature.transfer.impl38 cashsense.feature.wallet.dialog.impl39 cashsense.MainActivityUiState40 cashsense.core.data.di
1 cashsense.core.analytics
2 cashsense.core.model
3 cashsense.core.network.model
4 core.navigation
5 cashsense.core.database.model7
6 cashsense.core.database.util1
7 cashsense.core.datastore1
8 cashsense.core.network1
9 cashsense.core.notifications2
10 cashsense.core.ui.component9
11 cashsense.core.ui.util15
12 cashsense.feature.home.impl.model1
13 cashsense.feature.transaction.overview.api1
14 cashsense.core.data.repository81
15 cashsense.core.database.dao7
16 cashsense.core.network.ktor11
17 cashsense.feature.transaction.editor.api211
18 cashsense.core.data.util112
19 cashsense.core.database5
20 cashsense.core.domain57
21 cashsense.core.network.di11
22 cashsense.core.shortcuts2
23 cashsense.feature.category.editor.impl111
24 cashsense.feature.category.list.impl411
25 cashsense.feature.subscription.dialog.impl32
26 cashsense.feature.subscription.list.impl31
27 cashsense.feature.transaction.detail.impl21
28 cashsense11231
29 cashsense.core.data.repository.impl81121651
30 cashsense.core.database.di152
31 cashsense.feature.category.detail.impl311
32 cashsense.feature.home.impl2131
33 cashsense.feature.settings.impl411
34 cashsense.feature.transaction.editor.impl8211
35 cashsense.feature.transaction.importer.impl922
36 cashsense.feature.transaction.overview.impl13132
37 cashsense.feature.transfer.impl411
38 cashsense.feature.wallet.dialog.impl121
39 cashsense.MainActivityUiState12
40 cashsense.core.data.di6106
Uses a module listed above itPart of a loopThe module itself
1 cashsense.core.analytics2 cashsense.core.model3 cashsense.core.network.model4 core.navigation5 cashsense.core.database.model6 cashsense.core.database.util7 cashsense.core.datastore8 cashsense.core.network9 cashsense.core.notifications10 cashsense.core.ui.component11 cashsense.core.ui.util12 cashsense.feature.home.impl.model13 cashsense.feature.transaction.overview.api14 cashsense.core.data.repository15 cashsense.core.database.dao16 cashsense.core.network.ktor17 cashsense.feature.transaction.editor.api18 cashsense.core.data.util19 cashsense.core.database20 cashsense.core.domain21 cashsense.core.network.di22 cashsense.core.shortcuts23 cashsense.feature.category.editor.impl24 cashsense.feature.category.list.impl25 cashsense.feature.subscription.dialog.impl26 cashsense.feature.subscription.list.impl27 cashsense.feature.transaction.detail.impl28 cashsense29 cashsense.core.data.repository.impl30 cashsense.core.database.di31 cashsense.feature.category.detail.impl32 cashsense.feature.home.impl33 cashsense.feature.settings.impl34 cashsense.feature.transaction.editor.impl35 cashsense.feature.transaction.importer.impl36 cashsense.feature.transaction.overview.impl37 cashsense.feature.transfer.impl38 cashsense.feature.wallet.dialog.impl39 cashsense.MainActivityUiState40 cashsense.core.data.dicashsense.core.analytics1cashsense.core.model2cashsense.core.network.model3core.navigation4cashsense.core.database.model5cashsense.core.database.util6cashsense.core.datastore7cashsense.core.network8cashsense.core.notifications9cashsense.core.ui.component10cashsense.core.ui.util11cashsense.feature.home.impl.model12cashsense.feature.transaction.overview.api13cashsense.core.data.repository14cashsense.core.database.dao15cashsense.core.network.ktor16cashsense.feature.transaction.editor.api17cashsense.core.data.util18cashsense.core.database19cashsense.core.domain20cashsense.core.network.di21cashsense.core.shortcuts22cashsense.feature.category.editor.impl23cashsense.feature.category.list.impl24cashsense.feature.subscription.dialog.impl25cashsense.feature.subscription.list.impl26cashsense.feature.transaction.detail.impl27cashsense28cashsense.core.data.repository.impl29cashsense.core.database.di30cashsense.feature.category.detail.impl31cashsense.feature.home.impl32cashsense.feature.settings.impl33cashsense.feature.transaction.editor.impl34cashsense.feature.transaction.importer.impl35cashsense.feature.transaction.overview.impl36cashsense.feature.transfer.impl37cashsense.feature.wallet.dialog.impl38cashsense.MainActivityUiState39cashsense.core.data.di4071112915118171121111255711211141132312111231811216511523112131411821192213132411121126106+97 more modules (most-connected shown)

At a glance — Code Health · 93.8 · Exemplary ·

At a glance — Architecture · 96.3 · Exemplary ·

At a glance — Maturity · 65.7 · Adequate · gated by M2 ·

At a glance — Readiness · 49.7 · Weak · gated by P3 ·

At a glance — Security · 71.0 · Adequate · gated by D36 ·

At a glance — Domain Modelling · 53.3 · Adequate · gated by DM2, DM4, DM11 ·

At a glance — Performance · 94.3 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection7High / Critical
A03:2025 — Software Supply Chain Failures6Medium

Roadmap

Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release; Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

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

Do thisHelpsEffortDimension
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+6.3 ptsMediumSecurity & performance tooling
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.+2.6 ptsLowDocumentation Quality
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.+2.6 ptsLowADR Quality
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+4.2 ptsMediumRelease Hygiene
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.+2.9 ptsMediumConstructible invalid state
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.+2.9 ptsMediumStrongly-typed ids
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.+2.9 ptsMediumRich vs anemic model
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+2.1 ptsMediumArchitecture documentation

File quality

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

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt7.1MixedCognitive Complexity: TransactionEditorScreenKt.TransactionEditorScreen (cognitive 16)
feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt7.1MixedGod Classes: MethodTooLong: WalletCardKt.WalletCard
core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt7.2MixedCode Duplication: Edited copy of a member (28 corresponding lines)
feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt7.4MixedCode Duplication: Edited copy of a member (27 corresponding lines)
mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt7.8MixedCognitive Complexity: CsAppKt.CsApp (cognitive 18)
core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TransactionItem.kt7.8MixedCognitive Complexity: TransactionItemKt.TransactionItem (cognitive 16)
feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/TransactionImporterScreen.kt7.8MixedGod Classes: MethodTooLong: TransactionImporterScreenKt.TransactionImporterScreen
core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/FinancePanel.kt7.8MixedGod Classes: MethodTooLong: FinancePanelKt.FinancePanel
feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/navigation/CategoryEditorEntryProvider.kt7.8MixedCode Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens)
core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt7.8MixedCode Duplication: Edited copy of a member (23 corresponding lines)
core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt7.8MixedCode Duplication: Edited copy of a member (27 corresponding lines)
core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt7.8MixedChange Coupling: Change coupling: WalletEntity.kt ↔ WalletCard.kt
build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt7.8MixedChange Coupling: Change coupling: AndroidApplicationConventionPlugin.kt ↔ AndroidLibraryConventionPlugin.kt
core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Transaction.kt7.8MixedChange Coupling: Change coupling: Transaction.kt ↔ CsDatabase.kt
feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/navigation/HomeEntryProvider.kt8.0Near-cleanChange Coupling: Boundary-crossing change coupling: HomeEntryProvider.kt ↔ CsApp.kt
feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/navigation/CategoriesEntryProvider.kt8.0Near-cleanChange Coupling: Boundary-crossing change coupling: CategoriesEntryProvider.kt ↔ CsApp.kt
core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/theme/Theme.kt8.5Near-cleanCognitive Complexity: ThemeKt.selectSchemeForContrast (cognitive 23)
feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewScreen.kt8.5Near-cleanCognitive Complexity: TransactionOverviewScreenKt.TopBar (cognitive 20)
feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/AppBarWithSearch.kt8.5Near-cleanGod Classes: MethodTooLong: AppBarWithSearchKt.CsAppBarWithSearch

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

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

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

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

Could not be resolved — 15

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

This survey 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. All 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 47 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D17D19D20D26D28D29D34D35D36D44AX10AX2AX3AX4AX6DM11DM12DM2DM4DM5DM6DM7M1M2M3M4P1P3P6PF1PF3X1X12X2X21X27X3X5

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
  1. 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, 89 of 112 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e573-5883-749d-8a86-d6e88f43a565.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We 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.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — not measured this run — We 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 scored — 48 Maven/Gradle manifest(s) were read, stating a version for 69 dependency(ies) and leaving 20 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • 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-maintainer repository — bus factor is not applicable (4 contributor(s) across 3375 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 3 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — We 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We 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 an ADMISSION gap, not an environment fault: it declares a published package (work/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
  • D24 Comment Value — not measured this run — We 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/theme/Theme.kt`, `core/navigation/src/main/kotlin/ru/resodostudios/core/navigation/Navigator.kt`, `core/notifications/src/main/kotlin/ru/resodostudios/cashsense/core/notifications/SystemTrayNotifier.kt`, `feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/CategoryEditorViewModel.kt`, `work/src/main/kotlin/ru/resodostudios/cashsense/work/worker/DelegatingWorker.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We 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. Subject: a native UI project (mobile/src/prod/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C2 Access Controls — not measured this run — We 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.
  • DM8 Value-object opportunities — not measured this run — We 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 primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
  • DM9 Scattered domain decisions — not measured this run — We 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.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — not measured this run — We 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.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • 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.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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.

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.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity9.2 / 10Stronggated by 5 serious findings✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Prevented

5 method(s) exceeded the cognitive complexity threshold of 15; the worst was ThemeKt.selectSchemeForContrast at 23.

ThemeKt.selectSchemeForContrast (cognitive 23)core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/theme/Theme.kt:291
TransactionOverviewScreenKt.TopBar (cognitive 20)feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewScreen.kt:256
CsAppKt.CsApp (cognitive 18)mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt:102
TransactionItemKt.TransactionItem (cognitive 16)core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TransactionItem.kt:53
TransactionEditorScreenKt.TransactionEditorScreen (cognitive 16)feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:104

What to do

  1. Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with ThemeKt.selectSchemeForContrast (cognitive 23), TransactionOverviewScreenKt.TopBar (cognitive 20), CsAppKt.CsApp (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

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

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

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

10 over-large unit(s) detected — types, modules or files that carry too much.

MethodTooLong: TransactionImporterScreenKt.TransactionImporterScreen · ×10feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/TransactionImporterScreen.kt:101

What to do

  1. Resolve the 10 MethodTooLong finding(s) in God Classes — start with TransactionImporterScreen.kt, WalletCard.kt, TransactionEditorScreen.kt. — One of this dimension's main actionable groups (10 warning-level).

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

D4 · Code Duplication8.3 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

16 duplicated block group(s) detected. 4.3 % of the production lines (1,137 of 26,579) are in a reported copy. A further 16 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (15 lines × 2) · ×4core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:27
Duplicated block (17 lines × 2) · ×3core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:123
Edited copy of a member (28 corresponding lines) · ×2feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorViewModel.kt:116
Edited copy of a member (27 corresponding lines) · ×2feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:27
Edited copy of a member (26 corresponding lines) · ×2core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/FinancePanel.kt:535

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

What to do

  1. Resolve the 4 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with ButtonGroup.kt, TextField.kt, WalletCard.kt. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with IconButton.kt (2), TransactionEditorScreen.kt. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 Edited copy of a member (28 corresponding lines) finding(s) in Code Duplication — start with TransactionEditorViewModel.kt, IconButton.kt. — One of this dimension's main actionable groups (2 warning-level).

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

D5 · Coupling7.6 / 10Strong✓ Tool-verified

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

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

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

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

47 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 15 module(s) off the main sequence, with abstractness counted on 44 of the 47 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: cashsense:core:designsystem · ×14
Off the main sequence: cashsense:core:common

What to do

  1. Resolve the 14 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (14 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 23 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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.

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

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

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

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

0 of 31 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 48 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 20 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 38 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

0 deducted task-comment markers across 26579 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation Quality0.0 / 10Critical✓ Tool-verified

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

0 of 1 documentation facets pass in full; short on: F2 example. 2 document(s) read across 1 unit(s).

Documentation: no build, run or usage exampleREADME.md:1

What to do

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

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

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

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundmobile/build.gradle.kts:4

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — 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.

D26 · Project Cohesion9.6 / 10Exemplary✓ Tool-verified

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

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

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

1 of 44 build units (Gradle) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesioncore/designsystem/build.gradle.kts:1

✓ On the Gold path — maintain.

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

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.

D29 · Static Analysis (SAST)8.4 / 10Adequategated by 7 critical findings✓ Tool-verified

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

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

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

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

7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, 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.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 145 of the 417 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

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

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

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

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

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

Strongest change-coupling: HomeEntryProvider.kt↔CsApp.kt 76%; WalletEntity.kt↔WalletCard.kt 70%; CsPreferencesDataSource.kt↔UserPreferencesSerializer.kt 64%

Boundary-crossing change coupling: HomeEntryProvider.kt ↔ CsApp.kt · ×2feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/navigation/HomeEntryProvider.kt:1
Change coupling: WalletEntity.kt ↔ WalletCard.kt · ×13core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:1

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with HomeEntryProvider.kt, CategoriesEntryProvider.kt. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 13 Change coupling finding(s) in Change Coupling — start with WalletEntity.kt (2), AndroidApplicationConventionPlugin.kt (2), Transaction.kt (2). — One of this dimension's main actionable groups (13 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 69 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

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

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

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `CategoryEntity`'s public constructor takes `id`, `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CategoryEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:11
  • `CurrencyExchangeRateEntity`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CurrencyExchangeRateEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CurrencyExchangeRateEntity.kt:13
  • `SubscriptionEntity`'s public constructor takes `id`, `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `SubscriptionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/SubscriptionEntity.kt:15
  • `TransactionEntity`'s public constructor takes `id`, `walletOwnerId`, `description`, `categoryId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TransactionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:36
  • `WalletEntity`'s public constructor takes `id`, `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WalletEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:13

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
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.

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

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

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

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

  • `CategoryEntity.iconId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:16
  • `TransactionEntity.walletOwnerId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:40
  • `TransactionEntity.categoryId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:51

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified

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

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

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

  • `CategoryEntity` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:11
  • `CurrencyExchangeRateEntity` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CurrencyExchangeRateEntity.kt:13
  • `SubscriptionEntity` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/SubscriptionEntity.kt:15
  • `TransactionEntity` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:36
  • `WalletEntity` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:13

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

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

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

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

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.

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

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

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

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

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

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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 build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

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

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

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

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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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. — REDACTED:8
  • `baselineprofile/build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — baselineprofile/build.gradle.kts:38

What to do

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — 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.
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.
PF1 · Benchmark discipline9.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether suspend functions that make a cancellable request accept or pass on the coroutine's cancellation (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

X5 · Nullable reference types8.8 / 10Strong✓ Tool-verified

Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • ~7.8 `!!` not-null assertions per 1k Kotlin product lines — 222 across the 28612 line(s) of the 368 Kotlin file(s) read (generated, test and sample code not counted). Densest: core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/util/DatabaseTransferManager.kt (4), core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/icon/filled/AccountBalance.kt (2), core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/icon/filled/ArrowDropDown.kt (2). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • Replace `!!` rather than adding to it: each is a run-time null check the compiler could not prove. Narrow the value with a null check, an early return or `?: return`, use `?.` / `?:` where absence is legitimate, `requireNotNull(x) { "why" }` / `checkNotNull` where a missing value is a contract breach worth a message, make the property non-nullable and set it in the constructor (or `by lazy`) instead of `lateinit` plus `!!`, or change the API so the null cannot arrive.

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.

LensScoreRatingImpact
Code Health93.8ExemplarySolid.
Architecture96.3ExemplaryStrongest area.
Maturity65.7Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness49.7Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security71.0Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling53.3Adequate — gated by DM2, DM4, DM11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance94.3ExemplarySolid.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 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.
  • AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
  • 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
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
  • 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.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~261 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
  • D12 Dependency Hygiene — Not scored — 48 Maven/Gradle manifest(s) were read, stating a version for 69 dependency(ies) and leaving 20 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — single-maintainer 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.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
  • 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) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • 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 — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
  • 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
  • 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
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
  • 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
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • 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#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. 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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repository's JVM source (44 module(s), 369 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — 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
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 9 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: HomeEntryProvider.kt ↔ CsApp.kt feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/navigation/HomeEntryProvider.kt:1 — `feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/navigation/HomeEntryProvider.kt` (context feature) and `mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt` (context mobile) sit in DIFFERENT parts of the tree yet change together 76% of the time (13 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) — 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 13 shared commits counted here, the most recent 3 are `055bac6a` Convert transfer dialog to editor screen; `075799ff` Consolidate wallet detail into transaction overview; `4d0a2679` Update FabMenu visibility logic — run `git show` on any of them.
  • Boundary-crossing change coupling: CategoriesEntryProvider.kt ↔ CsApp.kt feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/navigation/CategoriesEntryProvider.kt:1 — `feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/navigation/CategoriesEntryProvider.kt` (context feature) and `mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt` (context mobile) sit in DIFFERENT parts of the tree yet change together 50% of the time (12 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 12 shared commits counted here, the most recent 3 are `4d0a2679` Update FabMenu visibility logic; `7b29907e` Improve category UI: shared elements & selection; `9e6dcac8` Add category detail feature and navigation — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 86 finding(s)
D5 · Coupling · Off the main sequence · ×14
  • Off the main sequence: cashsense:core:designsystem — cashsense:core:designsystem: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:core:model — cashsense:core:model: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:transaction:importer:api — cashsense:feature:transaction:importer:api: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:core:domain — cashsense:core:domain: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:category:editor:api — cashsense:feature:category:editor:api: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:subscription:dialog:api — cashsense:feature:subscription:dialog:api: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:transaction:detail:api — cashsense:feature:transaction:detail:api: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:wallet:dialog:api — cashsense:feature:wallet:dialog:api: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:core:analytics — cashsense:core:analytics: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:home:api — cashsense:feature:home:api: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:transfer:api — cashsense:feature:transfer:api: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:core:navigation — cashsense:core:navigation: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:category:detail:api — cashsense:feature:category:detail:api: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: cashsense:feature:settings:api — cashsense:feature:settings:api: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
D35 · Change Coupling · Change coupling · ×13
  • Change coupling: WalletEntity.kt ↔ WalletCard.kt core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:1 — `core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt` and `feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt` change together 70% of the time (7 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 7 shared commits counted here, the most recent 3 are `1b0be42d` Replace currency type for `WalletEntity` (at that commit the file was still `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/WalletCard.kt`); `96f080ce` Update currency to String type (at that commit the file was still `feature/wallet/src/main/kotlin/ru/resodostudios/cashsense/feature/wallet/WalletCard.kt`); `62273761` Replace Double with BigDecimal (at that commit the file was still `feature/wallet/src/main/kotlin/ru/resodostudios/cashsense/feature/wallet/WalletCard.kt`) — run `git show` on any of them.
  • Change coupling: CsPreferencesDataSource.kt ↔ UserPreferencesSerializer.kt core/datastore/src/main/kotlin/ru/resodostudios/cashsense/core/datastore/CsPreferencesDataSource.kt:1 — `core/datastore/src/main/kotlin/ru/resodostudios/cashsense/core/datastore/CsPreferencesDataSource.kt` and `core/datastore/src/main/kotlin/ru/resodostudios/cashsense/core/datastore/UserPreferencesSerializer.kt` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c94617c1` Refactor: Remove "Show total balance" setting; `fcf1cdd8` Add preference for total balance visibility; `3becd4b7` Set default currency for user preferences — run `git show` on any of them.
  • Change coupling: AndroidApplicationConventionPlugin.kt ↔ AndroidLibraryConventionPlugin.kt build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt:1 — `build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt` and `build-logic/convention/src/main/kotlin/AndroidLibraryConventionPlugin.kt` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `3cb274c9` Update to `targetSdk` `37`; `77951619` Update compileSdk and targetSdk to 36; `cb451b75` Migrate to targetSdk 35 — run `git show` on any of them.
  • Change coupling: AndroidApplicationConventionPlugin.kt ↔ KotlinAndroid.kt build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt:1 — `build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt` and `build-logic/convention/src/main/kotlin/ru/resodostudios/cashsense/KotlinAndroid.kt` change together 64% of the time (7 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 7 shared commits counted here, the most recent 3 are `3cb274c9` Update to `targetSdk` `37`; `77951619` Update compileSdk and targetSdk to 36; `cb451b75` Migrate to targetSdk 35 — run `git show` on any of them.
  • Change coupling: WalletsRepository.kt ↔ WalletDao.kt core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/repository/WalletsRepository.kt:1 — `core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/repository/WalletsRepository.kt` and `core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/dao/WalletDao.kt` change together 61% of the time (11 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 11 shared commits counted here, the most recent 3 are `f5dc0ad9` Refactor wallets repository; `c627ad51` Add distinct currencies retrieval; `63ab200c` Rename wallet functions — run `git show` on any of them.
  • Change coupling: CurrencyDialog.kt ↔ SettingsScreen.kt feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/CurrencyDialog.kt:1 — `feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/CurrencyDialog.kt` and `feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/SettingsScreen.kt` change together 60% of the time (6 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `56096d40` Replace outlined with filled icons in Settings and Design System; `5871b473` Update currency type for `CurrencyDropdownMenu` (at that commit the files were still `feature/settings/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/CurrencyDialog.kt` and `feature/settings/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/SettingsScreen.kt`); `54572bcc` Improve currency handling and validation (at that commit the files were still `feature/settings/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/CurrencyDialog.kt` and `feature/settings/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/SettingsScreen.kt`) — run `git show` on any of them.
  • Change coupling: Wallet.kt ↔ HomeScreen.kt core/model/src/main/kotlin/ru/resodostudios/cashsense/core/model/Wallet.kt:1 — `core/model/src/main/kotlin/ru/resodostudios/cashsense/core/model/Wallet.kt` and `feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/HomeScreen.kt` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `96f080ce` Update currency to String type (at that commit the files were still `core/model/src/main/kotlin/ru/resodostudios/cashsense/core/model/data/Wallet.kt` and `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/HomeScreen.kt`); `62273761` Replace Double with BigDecimal (at that commit the files were still `core/model/src/main/kotlin/ru/resodostudios/cashsense/core/model/data/Wallet.kt` and `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/HomeScreen.kt`); `291f4c13` Add walletState to HomeScreen (at that commit the files were still `core/model/src/main/kotlin/ru/resodostudios/cashsense/core/model/data/Wallet.kt` and `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/HomeScreen.kt`) — run `git show` on any of them.
  • Change coupling: TransactionsRepository.kt ↔ TransactionDao.kt core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/repository/TransactionsRepository.kt:1 — `core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/repository/TransactionsRepository.kt` and `core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/dao/TransactionDao.kt` change together 54% of the time (13 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 13 shared commits counted here, the most recent 3 are `0947e011` Add bulk upsert for transactions; `9e11e30f` Migrate categories into transactions table; `2cf8360f` Implement `getTransfer` in `TransactionsRepository` — run `git show` on any of them.
  • Change coupling: TopAppBar.kt ↔ CsApp.kt core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/TopAppBar.kt:1 — `core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/TopAppBar.kt` and `mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.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 `0c5494e9` Refactor: Move Settings to Home screen top app bar; `9c353963` Remove action button from topbar (at that commit the file was still `app/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt`); `3fde29a4` Remove unnecessary insets paddings (at that commit the file was still `app/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt`) — run `git show` on any of them.
  • Change coupling: Transaction.kt ↔ CsDatabase.kt core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Transaction.kt:1 — `core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Transaction.kt` and `core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/CsDatabase.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 `9e11e30f` Migrate categories into transactions table; `ec6db829` Refactor: Replace `StatusType` enum with a `Boolean`; `c5a10035` Add transferId — run `git show` on any of them.
  • Change coupling: CategoryEntity.kt ↔ CategoriesScreen.kt core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:1 — `core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt` and `feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/CategoriesScreen.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 `35bcc9a2` Add database migration for iconId in category (at that commit the file was still `feature/categories/src/main/kotlin/ru/resodostudios/cashsense/feature/categories/CategoriesScreen.kt`); `35b62808` Add a new method for storing icons in the database (at that commit the file was still `feature/categories/src/main/kotlin/ru/resodostudios/cashsense/feature/categories/CategoriesScreen.kt`); `f56a6d51` Store drawable resource name instead of id (at that commit the file was still `feature/categories/src/main/kotlin/ru/resodostudios/cashsense/feature/categories/CategoriesScreen.kt`) — run `git show` on any of them.
  • Change coupling: Transaction.kt ↔ TransactionEditorViewModel.kt core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Transaction.kt:1 — `core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Transaction.kt` and `feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorViewModel.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 `ec6db829` Refactor: Replace `StatusType` enum with a `Boolean` (at that commit the file was still `feature/transaction/dialog/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/dialog/TransactionDialogViewModel.kt`); `c5a10035` Add transferId (at that commit the file was still `feature/transaction/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/TransactionDialogViewModel.kt`); `4d71f173` Add ignored field to transaction model (at that commit the file was still `feature/transaction/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/TransactionDialogViewModel.kt`) — run `git show` on any of them.
  • Change coupling: WalletEntity.kt ↔ HomeScreen.kt core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:1 — `core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt` and `feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/HomeScreen.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 `96f080ce` Update currency to String type (at that commit the file was still `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/HomeScreen.kt`); `62273761` Replace Double with BigDecimal (at that commit the file was still `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/HomeScreen.kt`); `1f254324` Add edit dialog for wallet (at that commit the file was still `feature/home/src/main/kotlin/ru/resodostudios/cashsense/feature/home/HomeScreen.kt`) — run `git show` on any of them.
D3 · God Classes · MethodTooLong · ×10
  • MethodTooLong: TransactionImporterScreenKt.TransactionImporterScreen feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/TransactionImporterScreen.kt:101 — MethodTooLong — TransactionImporterScreen runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WalletCardKt.WalletCard feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:74 — MethodTooLong — WalletCard runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TransactionEditorScreenKt.TransactionEditorScreen feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:104 — MethodTooLong — TransactionEditorScreen runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TransactionItemKt.TransactionItem core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TransactionItem.kt:53 — MethodTooLong — TransactionItem runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AppBarWithSearchKt.CsAppBarWithSearch feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/AppBarWithSearch.kt:91 — MethodTooLong — CsAppBarWithSearch runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CsAppKt.CsApp mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt:102 — MethodTooLong — CsApp runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SubscriptionDialogKt.SubscriptionDialog feature/subscription/dialog/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/subscription/dialog/impl/SubscriptionDialog.kt:90 — MethodTooLong — SubscriptionDialog runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FinancePanelKt.FinancePanel core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/FinancePanel.kt:86 — MethodTooLong — FinancePanel runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TransactionScreenKt.TransactionScreen feature/transaction/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/detail/impl/TransactionScreen.kt:104 — MethodTooLong — TransactionScreen runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TransferEditorScreenKt.TransferEditorScreen feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/TransferEditorScreen.kt:81 — MethodTooLong — TransferEditorScreen runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
DM11 · Constructible invalid state · Constructible in an invalid state · ×5
  • Constructible in an invalid state: CategoryEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:11 — `CategoryEntity`'s public constructor takes `id`, `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CategoryEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: CurrencyExchangeRateEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CurrencyExchangeRateEntity.kt:13 — `CurrencyExchangeRateEntity`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CurrencyExchangeRateEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: SubscriptionEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/SubscriptionEntity.kt:15 — `SubscriptionEntity`'s public constructor takes `id`, `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `SubscriptionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: TransactionEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:36 — `TransactionEntity`'s public constructor takes `id`, `walletOwnerId`, `description`, `categoryId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TransactionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: WalletEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:13 — `WalletEntity`'s public constructor takes `id`, `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WalletEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
DM4 · Rich vs anemic model · Anemic entity · ×5
  • Anemic entity: CategoryEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:11 — `CategoryEntity` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CurrencyExchangeRateEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CurrencyExchangeRateEntity.kt:13 — `CurrencyExchangeRateEntity` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: SubscriptionEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/SubscriptionEntity.kt:15 — `SubscriptionEntity` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: TransactionEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:36 — `TransactionEntity` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: WalletEntity core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/WalletEntity.kt:13 — `WalletEntity` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4
  • Duplicated block (15 lines × 2) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:27 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:27-41 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:60-74 — 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/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TextField.kt:82 — core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TextField.kt:82-96 | core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TextField.kt:170-184 — 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/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TextField.kt:82` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 2) feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:275 — feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:275-289 | feature/transaction/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/detail/impl/TransactionScreen.kt:384-398 — 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 `feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:275` 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 (15 lines × 2) feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:132 — feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:132-146 | feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/TransferEditorScreen.kt:103-117 — 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 `feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×3
  • Duplicated block (17 lines × 2) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:123 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:123-139 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:163-179 — 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/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:200 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:200-216 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:237-253 — 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/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:200` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:224 — feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:224-240 | feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/TransferEditorScreen.kt:202-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×2
  • Edited copy of a member (28 corresponding lines) feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorViewModel.kt:116 — feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorViewModel.kt:116-143 | feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorViewModel.kt:145-177 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:189 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:189-216 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:226-253 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×2
  • Edited copy of a member (27 corresponding lines) feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:27 — feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:27-53 | feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/navigation/TransactionOverviewEntryProvider.kt:30-59 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:27 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:27-53 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:64-90 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/FinancePanel.kt:535 — core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/FinancePanel.kt:535-560 | core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/FinancePanel.kt:567-598 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/Tag.kt:31 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/Tag.kt:31-58 | feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:329-354 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D2 · Cognitive Complexity · ThemeKt.selectSchemeForContrast (cognitive 23) · ×1
  • ThemeKt.selectSchemeForContrast (cognitive 23) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/theme/Theme.kt:291 — ThemeKt.selectSchemeForContrast has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TransactionOverviewScreenKt.TopBar (cognitive 20) · ×1
  • TransactionOverviewScreenKt.TopBar (cognitive 20) feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewScreen.kt:256 — TransactionOverviewScreenKt.TopBar has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · CsAppKt.CsApp (cognitive 18) · ×1
  • CsAppKt.CsApp (cognitive 18) mobile/src/main/kotlin/ru/resodostudios/cashsense/ui/CsApp.kt:102 — CsAppKt.CsApp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · TransactionItemKt.TransactionItem (cognitive 16) · ×1
  • TransactionItemKt.TransactionItem (cognitive 16) core/ui/src/main/kotlin/ru/resodostudios/cashsense/core/ui/component/TransactionItem.kt:53 — TransactionItemKt.TransactionItem has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · TransactionEditorScreenKt.TransactionEditorScreen (cognitive 16) · ×1
  • TransactionEditorScreenKt.TransactionEditorScreen (cognitive 16) feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:104 — TransactionEditorScreenKt.TransactionEditorScreen has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/navigation/CategoryEditorEntryProvider.kt:24 — feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/navigation/CategoryEditorEntryProvider.kt:24-45 | feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/navigation/LicensesEntryProvider.kt:19-37 | feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/navigation/SettingsEntryProvider.kt:20-39 | feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/navigation/TransactionEditorEntryProvider.kt:24-45 | feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/navigation/TransactionImporterEntryProvider.kt:25-52 | feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/navigation/TransferEditorEntryProvider.kt:24-45 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/TransactionImporterScreen.kt:323 — feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/TransactionImporterScreen.kt:323-373 | feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/TransactionImporterScreen.kt:382-433 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:274 — feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:274-320 | feature/transaction/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/detail/impl/TransactionScreen.kt:383-420 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/LanguageDialog.kt:37 — feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/LanguageDialog.kt:37-92 | feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/ThemeDialog.kt:31-79 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:19 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:19-41 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ButtonGroup.kt:52-74 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:359 — feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:359-383 | feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:388-413 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:45 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:45-67 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:113-139 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/IconButton.kt:153-179 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:277 — feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:277-289 | feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/TransactionEditorScreen.kt:295-307 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/TransferEditorViewModel.kt:99 — feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/TransferEditorViewModel.kt:99-112 | feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/TransferEditorViewModel.kt:114-127 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Subscription.kt:6 — core/data/src/main/kotlin/ru/resodostudios/cashsense/core/data/model/Subscription.kt:6-17 | core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/SubscriptionEntity.kt:31-42 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/CategoryScreen.kt:257 — feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/CategoryScreen.kt:257-281 | feature/transaction/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/detail/impl/TransactionScreen.kt:308-332 — 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 `feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/CategoryScreen.kt:257` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:31 — core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:31-53 | core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:68-90 — 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/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/component/button/ToggleButton.kt:31` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:360 — feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:360-381 | feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:389-410 — 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 `feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/WalletCard.kt:360` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/CategoriesScreen.kt:123 — feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/CategoriesScreen.kt:123-141 | feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/HomeScreen.kt:154-172 — 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 `feature/category/list/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/list/impl/CategoriesScreen.kt:123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:29 — feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:29-41 | feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/navigation/TransactionOverviewEntryProvider.kt:32-44 — 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 `feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:29` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10–11 lines × 6) · ×1
  • Duplicated block (10–11 lines × 6) feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/navigation/CategoryEditorEntryProvider.kt:27 — feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/navigation/CategoryEditorEntryProvider.kt:27-36 | feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/navigation/LicensesEntryProvider.kt:22-32 | feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/navigation/SettingsEntryProvider.kt:23-33 | feature/transaction/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/editor/impl/navigation/TransactionEditorEntryProvider.kt:27-36 | feature/transaction/importer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/importer/impl/navigation/TransactionImporterEntryProvider.kt:28-37 | feature/transfer/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transfer/impl/navigation/TransferEditorEntryProvider.kt:27-36 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `feature/settings/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/settings/impl/navigation/LicensesEntryProvider.kt:22` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:30 — feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:30-40 | feature/transaction/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/detail/impl/navigation/TransactionEntryProvider.kt:28-38 | feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/navigation/TransactionOverviewEntryProvider.kt:33-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature/category/detail/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/detail/impl/navigation/CategoryEntryProvider.kt:30` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt:355 — feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt:355-364 | feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt:397-404 — 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 `feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt:355` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt:365` calls `add` and `feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt:405` 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 (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) feature/subscription/dialog/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/subscription/dialog/impl/navigation/SubscriptionDialogEntryProvider.kt:12 — feature/subscription/dialog/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/subscription/dialog/impl/navigation/SubscriptionDialogEntryProvider.kt:12-23 | feature/wallet/dialog/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/wallet/dialog/impl/navigation/WalletDialogEntryProvider.kt:12-23 — 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.
Minor — 16 finding(s)
DM2 · Strongly-typed ids · Primitive id on a domain type · ×3
  • Primitive id on a domain type: CategoryEntity.iconId core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/CategoryEntity.kt:16 — `CategoryEntity.iconId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: TransactionEntity.walletOwnerId core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:40 — `TransactionEntity.walletOwnerId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: TransactionEntity.categoryId core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/model/TransactionEntity.kt:51 — `TransactionEntity.categoryId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found mobile/build.gradle.kts:4 — 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/`. ADRs are expected here because `mobile/build.gradle.kts` makes this repository a deployable product (line 4).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion core/designsystem/build.gradle.kts:1 — `core/designsystem` (10807 LoC, 140 module-visible types across 6 directories) overshoots its size bounds. 1 of 44 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 9.6/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:8 — 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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation baselineprofile/build.gradle.kts:38 — `baselineprofile/build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
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.)
X10 · Duplicated predicate · Duplicated predicate · ×1
  • Duplicated predicate feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/HomeViewModel.kt:99 — `!it.ignored && it.timestamp.isInCurrentMonthAndYear()` appears character-identically in 2 files — feature/home/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/home/impl/HomeViewModel.kt, feature/transaction/overview/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/transaction/overview/impl/TransactionOverviewViewModel.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X5 · Nullable reference types · Not-null assertions (`!!`) override null safety · ×1
  • Not-null assertions (`!!`) override null safety — ~7.8 `!!` not-null assertions per 1k Kotlin product lines — 222 across the 28612 line(s) of the 368 Kotlin file(s) read (generated, test and sample code not counted). Densest: core/database/src/main/kotlin/ru/resodostudios/cashsense/core/database/util/DatabaseTransferManager.kt (4), core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/icon/filled/AccountBalance.kt (2), core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/icon/filled/ArrowDropDown.kt (2). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 1 finding(s)
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: cashsense:core:common — cashsense:core:common: abstractness 0.22, instability 0.00, distance 0.78 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-e2662eb7fa4141479de8aa55aef68e61/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-e2662eb7fa4141479de8aa55aef68e61/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=2375" --report-format json --report-path /tmp/watchdog-gitleaks-e2662eb7fa4141479de8aa55aef68e61/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e2662eb7fa4141479de8aa55aef68e61/tree.json --exit-code 0 --source .0artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .7artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `core/designsystem/src/main/kotlin/ru/resodostudios/cashsense/core/designsystem/theme/Theme.kt`, `core/navigation/src/main/kotlin/ru/resodostudios/core/navigation/Navigator.kt`, `core/notifications/src/main/kotlin/ru/resodostudios/cashsense/core/notifications/SystemTrayNotifier.kt`, `feature/category/editor/impl/src/main/kotlin/ru/resodostudios/cashsense/feature/category/editor/impl/CategoryEditorViewModel.kt`, `work/src/main/kotlin/ru/resodostudios/cashsense/work/worker/DelegatingWorker.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).0—

Run 01a1e573-5883-749d-8a86-d6e88f43a565 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md