Public report of isaacsa51/Minus, published 17 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 reportMeasured 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, 17 November 2026, 15:46 UTC · Survey ID cd_9d8332f173064693b4f400069f6a0009
isaacsa51/Minus
Measured 17 November 2026, 15:44 UTC, at code version 29c306b
First survey, so nothing to compare with yet
CAI scoreWeak
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: 78,185 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Security and Compliance, 26.5
Findings by how serious they are
27 critical484 serious56 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 15:44 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 ▸
66of 66 dimensions measured by tools.
556of 567 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
66dimensions across 8 lenses, read from 78,185 lines of product code in 7 projects.
isaacsa51/Minus falls short of our standard for production because we found no encryption of stored data, no key vault and no enforced HTTPS, and it has pipeline tools referenced by a changeable name. It scores 39.9 out of 100 and is rated Weak, and all 27 of its critical findings are security problems.
Security and Compliance, at 26.5, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 10.8 points. Raising Security and Compliance to 70 would lift the score to about 50.2.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version and passing outside input through environment variables would close both risks. Fixing the weaknesses the scanner points to would fix the four security weaknesses in the code, and updating the vulnerable packages would deal with the two packages with a known security hole.
The product code is 78,185 lines, about €100,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 forThe 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.
If Security and Compliance rose from 26.5 to 70, the lowest score rated Strong, the score would rise from 39.9 to about 50.2.
Code composition: what the lines of code are
Product code 73%Tests 27%
Rebuild cost: about €100,000 · Estimate
Cost to rebuild
€35,000 to €170,000, for 577 to 1,832 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, 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.7 at a score of 40. 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.
Size
Medium: 78,185 lines of product code
What it is not
Not 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
Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault).
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 10.8 points · Medium effort · Data Protection
2
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2).
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 €100,000 to build again, about 0.7 person-years of work. Its weakest lens is Security and Compliance, at 26.5 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Of all the actions in this report, it raises the score most for the work it takes: about 10.8 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
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 6% on every change. The history of the code shows how much it changes: about 99,268 lines over the last 90 days, which is about 402,587 lines a year. At that pace, the extra work comes to an estimated 24.9 to 149.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
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.
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.
234 modules, with 321 dependencies between them. 6 loops run through 18 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 194 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.
serranoie.app.minus.domain.time uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.domain.time, while a change to serranoie.app.minus.domain.time can't break serranoie.app.minus.domain.model.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→12 serranoie.app.minus.domain.time uses serranoie.app.minus.data.repositorypart of a loop✕
Connections
2 pairs of types, where a type in serranoie.app.minus.domain.time uses a type in serranoie.app.minus.data.repository.
serranoie.app.minus.domain.time uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.domain.time, while a change to serranoie.app.minus.domain.time can't break serranoie.app.minus.data.repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
serranoie.app.minus.presentation.util uses serranoie.app.minus.presentation.ui.budget.mvi.intent, so a change to serranoie.app.minus.presentation.ui.budget.mvi.intent can break serranoie.app.minus.presentation.util, while a change to serranoie.app.minus.presentation.util can't break serranoie.app.minus.presentation.ui.budget.mvi.intent.
Position
Below the diagonal: serranoie.app.minus.presentation.util uses a module listed above it, which is the healthy direction.
serranoie.app.wear.minus.presentation uses serranoie.app.wear.minus.data, so a change to serranoie.app.wear.minus.data can break serranoie.app.wear.minus.presentation, while a change to serranoie.app.wear.minus.presentation can't break serranoie.app.wear.minus.data.
Position
Below the diagonal: serranoie.app.wear.minus.presentation uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.model uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.domain.model, while a change to serranoie.app.minus.domain.model can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.domain.model uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.repository uses serranoie.app.minus.data.local.dao, so a change to serranoie.app.minus.data.local.dao can break serranoie.app.minus.data.repository, while a change to serranoie.app.minus.data.repository can't break serranoie.app.minus.data.local.dao.
Position
Below the diagonal: serranoie.app.minus.data.repository uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.repository uses serranoie.app.minus.domain.model.changelog, so a change to serranoie.app.minus.domain.model.changelog can break serranoie.app.minus.data.repository, while a change to serranoie.app.minus.data.repository can't break serranoie.app.minus.domain.model.changelog.
Position
Below the diagonal: serranoie.app.minus.data.repository uses a module listed above it, which is the healthy direction.
38 pairs of types, where a type in serranoie.app.minus.data.repository uses a type in serranoie.app.minus.domain.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
serranoie.app.minus.data.repository uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.data.repository, while a change to serranoie.app.minus.data.repository can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.data.repository uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.calculator uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.domain.calculator, while a change to serranoie.app.minus.domain.calculator can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.domain.calculator uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.calculator uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.domain.calculator, while a change to serranoie.app.minus.domain.calculator can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.domain.calculator uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.shortcut uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.domain.shortcut, while a change to serranoie.app.minus.domain.shortcut can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.domain.shortcut uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses a type in serranoie.app.minus.presentation.ui.budget.mvi.intent.
serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses serranoie.app.minus.presentation.ui.budget.mvi.intent, so a change to serranoie.app.minus.presentation.ui.budget.mvi.intent can break serranoie.app.minus.presentation.ui.home.MainScreenUiIntent, while a change to serranoie.app.minus.presentation.ui.home.MainScreenUiIntent can't break serranoie.app.minus.presentation.ui.budget.mvi.intent.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.home.MainScreenUiIntent, while a change to serranoie.app.minus.presentation.ui.home.MainScreenUiIntent can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses a module listed above it, which is the healthy direction.
15→30 serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses serranoie.app.minus.presentation.ui.homepart of a loop✕
Connections
17 pairs of types, where a type in serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses a type in serranoie.app.minus.presentation.ui.home.
serranoie.app.minus.presentation.ui.home.MainScreenUiIntent uses serranoie.app.minus.presentation.ui.home, so a change to serranoie.app.minus.presentation.ui.home can break serranoie.app.minus.presentation.ui.home.MainScreenUiIntent, while a change to serranoie.app.minus.presentation.ui.home.MainScreenUiIntent can't break serranoie.app.minus.presentation.ui.home.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
serranoie.app.minus.presentation.ui.theme.component uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation.ui.theme.component, while a change to serranoie.app.minus.presentation.ui.theme.component can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.theme.component uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.theme.component, while a change to serranoie.app.minus.presentation.ui.theme.component can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.theme.component.budget.formula uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.theme.component.budget.formula, while a change to serranoie.app.minus.presentation.ui.theme.component.budget.formula can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.budget.formula uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.csv uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.data.csv, while a change to serranoie.app.minus.data.csv can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.data.csv uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.csv uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.data.csv, while a change to serranoie.app.minus.data.csv can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.data.csv uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.csv uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.data.csv, while a change to serranoie.app.minus.data.csv can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.data.csv uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.di uses serranoie.app.minus.data.local.dao, so a change to serranoie.app.minus.data.local.dao can break serranoie.app.minus.data.di, while a change to serranoie.app.minus.data.di can't break serranoie.app.minus.data.local.dao.
Position
Below the diagonal: serranoie.app.minus.data.di uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.di uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.data.di, while a change to serranoie.app.minus.data.di can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.data.di uses a module listed above it, which is the healthy direction.
serranoie.app.minus.data.di uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.data.di, while a change to serranoie.app.minus.data.di can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.data.di uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.notification uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.presentation.notification, while a change to serranoie.app.minus.presentation.notification can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.presentation.notification uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.notification uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.notification, while a change to serranoie.app.minus.presentation.notification can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.notification uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.notification uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.notification, while a change to serranoie.app.minus.presentation.notification can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.notification uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.notification uses serranoie.app.minus.domain.calculator, so a change to serranoie.app.minus.domain.calculator can break serranoie.app.minus.presentation.notification, while a change to serranoie.app.minus.presentation.notification can't break serranoie.app.minus.domain.calculator.
Position
Below the diagonal: serranoie.app.minus.presentation.notification uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.theme.component.expense uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation.ui.theme.component.expense, while a change to serranoie.app.minus.presentation.ui.theme.component.expense can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.expense uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.theme.component.expense uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.theme.component.expense, while a change to serranoie.app.minus.presentation.ui.theme.component.expense can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.expense uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in serranoie.app.minus.presentation.ui.theme.component.expense uses a type in serranoie.app.minus.presentation.ui.theme.component.
serranoie.app.minus.presentation.ui.theme.component.expense uses serranoie.app.minus.presentation.ui.theme.component, so a change to serranoie.app.minus.presentation.ui.theme.component can break serranoie.app.minus.presentation.ui.theme.component.expense, while a change to serranoie.app.minus.presentation.ui.theme.component.expense can't break serranoie.app.minus.presentation.ui.theme.component.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.expense uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.ui.theme.component.numpad uses a type in serranoie.app.minus.presentation.ui.tutorial.
serranoie.app.minus.presentation.ui.theme.component.numpad uses serranoie.app.minus.presentation.ui.tutorial, so a change to serranoie.app.minus.presentation.ui.tutorial can break serranoie.app.minus.presentation.ui.theme.component.numpad, while a change to serranoie.app.minus.presentation.ui.theme.component.numpad can't break serranoie.app.minus.presentation.ui.tutorial.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.numpad uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.theme.component.numpad uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.theme.component.numpad, while a change to serranoie.app.minus.presentation.ui.theme.component.numpad can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.numpad uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.ui.theme.component.numpad uses a type in serranoie.app.minus.presentation.ui.theme.component.
serranoie.app.minus.presentation.ui.theme.component.numpad uses serranoie.app.minus.presentation.ui.theme.component, so a change to serranoie.app.minus.presentation.ui.theme.component can break serranoie.app.minus.presentation.ui.theme.component.numpad, while a change to serranoie.app.minus.presentation.ui.theme.component.numpad can't break serranoie.app.minus.presentation.ui.theme.component.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.theme.component.numpad uses a module listed above it, which is the healthy direction.
22→24 serranoie.app.minus.presentation.ui.theme.component.numpad uses serranoie.app.minus.presentation.ui.editor.categorypart of a loop✕
Connections
1 pair of types, where a type in serranoie.app.minus.presentation.ui.theme.component.numpad uses a type in serranoie.app.minus.presentation.ui.editor.category.
serranoie.app.minus.presentation.ui.theme.component.numpad uses serranoie.app.minus.presentation.ui.editor.category, so a change to serranoie.app.minus.presentation.ui.editor.category can break serranoie.app.minus.presentation.ui.theme.component.numpad, while a change to serranoie.app.minus.presentation.ui.theme.component.numpad can't break serranoie.app.minus.presentation.ui.editor.category.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
serranoie.app.minus.presentation uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.presentation, while a change to serranoie.app.minus.presentation can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.presentation uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation, while a change to serranoie.app.minus.presentation can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation, while a change to serranoie.app.minus.presentation can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation uses serranoie.app.minus.domain.shortcut, so a change to serranoie.app.minus.domain.shortcut can break serranoie.app.minus.presentation, while a change to serranoie.app.minus.presentation can't break serranoie.app.minus.domain.shortcut.
Position
Below the diagonal: serranoie.app.minus.presentation uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation uses serranoie.app.minus.presentation.notification, so a change to serranoie.app.minus.presentation.notification can break serranoie.app.minus.presentation, while a change to serranoie.app.minus.presentation can't break serranoie.app.minus.presentation.notification.
Position
Below the diagonal: serranoie.app.minus.presentation uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.editor.category uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.editor.category, while a change to serranoie.app.minus.presentation.ui.editor.category can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.editor.category uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.editor.category uses serranoie.app.minus.domain.calculator, so a change to serranoie.app.minus.domain.calculator can break serranoie.app.minus.presentation.ui.editor.category, while a change to serranoie.app.minus.presentation.ui.editor.category can't break serranoie.app.minus.domain.calculator.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.editor.category uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.ui.editor.category uses a type in serranoie.app.minus.presentation.ui.theme.component.numpad.
serranoie.app.minus.presentation.ui.editor.category uses serranoie.app.minus.presentation.ui.theme.component.numpad, so a change to serranoie.app.minus.presentation.ui.theme.component.numpad can break serranoie.app.minus.presentation.ui.editor.category, while a change to serranoie.app.minus.presentation.ui.editor.category can't break serranoie.app.minus.presentation.ui.theme.component.numpad.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.editor.category uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.editor uses serranoie.app.minus.presentation.ui.tutorial, so a change to serranoie.app.minus.presentation.ui.tutorial can break serranoie.app.minus.presentation.ui.editor, while a change to serranoie.app.minus.presentation.ui.editor can't break serranoie.app.minus.presentation.ui.tutorial.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.editor uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.editor uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.editor, while a change to serranoie.app.minus.presentation.ui.editor can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.editor uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.editor uses serranoie.app.minus.presentation.ui.editor.category, so a change to serranoie.app.minus.presentation.ui.editor.category can break serranoie.app.minus.presentation.ui.editor, while a change to serranoie.app.minus.presentation.ui.editor can't break serranoie.app.minus.presentation.ui.editor.category.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.editor uses a module listed above it, which is the healthy direction.
25→28 serranoie.app.minus.presentation.ui.editor uses serranoie.app.minus.presentation.ui.budgetpart of a loop✕
Connections
1 pair of types, where a type in serranoie.app.minus.presentation.ui.editor uses a type in serranoie.app.minus.presentation.ui.budget.
serranoie.app.minus.presentation.ui.editor uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.editor, while a change to serranoie.app.minus.presentation.ui.editor can't break serranoie.app.minus.presentation.ui.budget.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
serranoie.app.minus.presentation.ui.budget.controller uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.budget.controller, while a change to serranoie.app.minus.presentation.ui.budget.controller can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget.controller uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget.controller uses serranoie.app.minus.presentation.ui.editor, so a change to serranoie.app.minus.presentation.ui.editor can break serranoie.app.minus.presentation.ui.budget.controller, while a change to serranoie.app.minus.presentation.ui.budget.controller can't break serranoie.app.minus.presentation.ui.editor.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget.controller uses a module listed above it, which is the healthy direction.
26→28 serranoie.app.minus.presentation.ui.budget.controller uses serranoie.app.minus.presentation.ui.budgetpart of a loop✕
Connections
2 pairs of types, where a type in serranoie.app.minus.presentation.ui.budget.controller uses a type in serranoie.app.minus.presentation.ui.budget.
serranoie.app.minus.presentation.ui.budget.controller uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.budget.controller, while a change to serranoie.app.minus.presentation.ui.budget.controller can't break serranoie.app.minus.presentation.ui.budget.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19 pairs of types, where a type in serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses a type in serranoie.app.minus.presentation.ui.budget.mvi.intent.
serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses serranoie.app.minus.presentation.ui.budget.mvi.intent, so a change to serranoie.app.minus.presentation.ui.budget.mvi.intent can break serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent, while a change to serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent can't break serranoie.app.minus.presentation.ui.budget.mvi.intent.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses a type in serranoie.app.minus.domain.model.
serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent, while a change to serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses a type in serranoie.app.minus.presentation.ui.editor.
serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses serranoie.app.minus.presentation.ui.editor, so a change to serranoie.app.minus.presentation.ui.editor can break serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent, while a change to serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent can't break serranoie.app.minus.presentation.ui.editor.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.presentation.ui.budget.mvi.intent, so a change to serranoie.app.minus.presentation.ui.budget.mvi.intent can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.presentation.ui.budget.mvi.intent.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in serranoie.app.minus.presentation.ui.budget uses a type in serranoie.app.minus.domain.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.domain.calculator, so a change to serranoie.app.minus.domain.calculator can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.domain.calculator.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.presentation.notification, so a change to serranoie.app.minus.presentation.notification can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.presentation.notification.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.presentation.ui.editor, so a change to serranoie.app.minus.presentation.ui.editor can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.presentation.ui.editor.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.presentation.ui.budget.controller, so a change to serranoie.app.minus.presentation.ui.budget.controller can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.presentation.ui.budget.controller.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.ui.budget uses a type in serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent, so a change to serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.presentation.ui.budget.mvi.intent.BudgetEditorIntent.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.budget uses a module listed above it, which is the healthy direction.
28→29 serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.domain.usecasepart of a loop✕
Connections
10 pairs of types, where a type in serranoie.app.minus.presentation.ui.budget uses a type in serranoie.app.minus.domain.usecase.
serranoie.app.minus.presentation.ui.budget uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.ui.budget, while a change to serranoie.app.minus.presentation.ui.budget can't break serranoie.app.minus.domain.usecase.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
serranoie.app.minus.domain.usecase uses serranoie.app.minus.domain.model.changelog, so a change to serranoie.app.minus.domain.model.changelog can break serranoie.app.minus.domain.usecase, while a change to serranoie.app.minus.domain.usecase can't break serranoie.app.minus.domain.model.changelog.
Position
Below the diagonal: serranoie.app.minus.domain.usecase uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.usecase uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.domain.usecase, while a change to serranoie.app.minus.domain.usecase can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.domain.usecase uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.usecase uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.domain.usecase, while a change to serranoie.app.minus.domain.usecase can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.domain.usecase uses a module listed above it, which is the healthy direction.
serranoie.app.minus.domain.usecase uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.domain.usecase, while a change to serranoie.app.minus.domain.usecase can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.domain.usecase uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.presentation.ui.tutorial, so a change to serranoie.app.minus.presentation.ui.tutorial can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.presentation.ui.tutorial.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.domain.shortcut, so a change to serranoie.app.minus.domain.shortcut can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.domain.shortcut.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.presentation.ui.home.MainScreenUiIntent, so a change to serranoie.app.minus.presentation.ui.home.MainScreenUiIntent can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.presentation.ui.home.MainScreenUiIntent.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.presentation.ui.theme.component, so a change to serranoie.app.minus.presentation.ui.theme.component can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.presentation.ui.theme.component.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.home uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.home, while a change to serranoie.app.minus.presentation.ui.home can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.home uses a module listed above it, which is the healthy direction.
serranoie.app.minus.wearsync uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.wearsync, while a change to serranoie.app.minus.wearsync can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.wearsync uses a module listed above it, which is the healthy direction.
serranoie.app.minus.wearsync uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.wearsync, while a change to serranoie.app.minus.wearsync can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.wearsync uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a type in serranoie.app.minus.data.repository.
serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver, while a change to serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a type in serranoie.app.minus.presentation.notification.
serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses serranoie.app.minus.presentation.notification, so a change to serranoie.app.minus.presentation.notification can break serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver, while a change to serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver can't break serranoie.app.minus.presentation.notification.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a type in serranoie.app.minus.presentation.ui.budget.
serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver, while a change to serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a type in serranoie.app.minus.domain.usecase.
serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver, while a change to serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.RecurrentNotificationActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a type in serranoie.app.minus.data.repository.
serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver, while a change to serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a type in serranoie.app.minus.presentation.notification.
serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses serranoie.app.minus.presentation.notification, so a change to serranoie.app.minus.presentation.notification can break serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver, while a change to serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver can't break serranoie.app.minus.presentation.notification.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a type in serranoie.app.minus.presentation.ui.budget.
serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver, while a change to serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a type in serranoie.app.minus.domain.usecase.
serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver, while a change to serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.notification.scan.ExpenseScanActionReceiver uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.analytics uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation.ui.analytics, while a change to serranoie.app.minus.presentation.ui.analytics can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.analytics uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.analytics uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.analytics, while a change to serranoie.app.minus.presentation.ui.analytics can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.analytics uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.analytics uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.analytics, while a change to serranoie.app.minus.presentation.ui.analytics can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.analytics uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.analytics uses serranoie.app.minus.domain.calculator, so a change to serranoie.app.minus.domain.calculator can break serranoie.app.minus.presentation.ui.analytics, while a change to serranoie.app.minus.presentation.ui.analytics can't break serranoie.app.minus.domain.calculator.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.analytics uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.analytics uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.analytics, while a change to serranoie.app.minus.presentation.ui.analytics can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.analytics uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.analytics uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.ui.analytics, while a change to serranoie.app.minus.presentation.ui.analytics can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.analytics uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.presentation.ui.tutorial, so a change to serranoie.app.minus.presentation.ui.tutorial can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.presentation.ui.tutorial.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.domain.time, so a change to serranoie.app.minus.domain.time can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.domain.time.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in serranoie.app.minus.presentation.ui.history uses a type in serranoie.app.minus.presentation.ui.theme.component.expense.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.presentation.ui.theme.component.expense, so a change to serranoie.app.minus.presentation.ui.theme.component.expense can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.presentation.ui.theme.component.expense.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.ui.history, while a change to serranoie.app.minus.presentation.ui.history can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.quickadd uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.quickadd, while a change to serranoie.app.minus.presentation.ui.quickadd can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.quickadd uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.quickadd uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.quickadd, while a change to serranoie.app.minus.presentation.ui.quickadd can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.quickadd uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.quickadd uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.quickadd, while a change to serranoie.app.minus.presentation.ui.quickadd can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.quickadd uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.quickadd uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.ui.quickadd, while a change to serranoie.app.minus.presentation.ui.quickadd can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.quickadd uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.settings uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation.ui.settings, while a change to serranoie.app.minus.presentation.ui.settings can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.settings uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.settings uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.settings, while a change to serranoie.app.minus.presentation.ui.settings can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.settings uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.settings uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.settings, while a change to serranoie.app.minus.presentation.ui.settings can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.settings uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.settings uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.ui.settings, while a change to serranoie.app.minus.presentation.ui.settings can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.settings uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.presentation.util, so a change to serranoie.app.minus.presentation.util can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.presentation.util.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.domain.calculator, so a change to serranoie.app.minus.domain.calculator can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.domain.calculator.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.presentation.ui.theme.component, so a change to serranoie.app.minus.presentation.ui.theme.component can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.presentation.ui.theme.component.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in serranoie.app.minus.presentation.ui.subscriptions uses a type in serranoie.app.minus.presentation.ui.theme.component.expense.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.presentation.ui.theme.component.expense, so a change to serranoie.app.minus.presentation.ui.theme.component.expense can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.presentation.ui.theme.component.expense.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.presentation.ui.budget, so a change to serranoie.app.minus.presentation.ui.budget can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.presentation.ui.budget.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.subscriptions uses serranoie.app.minus.domain.usecase, so a change to serranoie.app.minus.domain.usecase can break serranoie.app.minus.presentation.ui.subscriptions, while a change to serranoie.app.minus.presentation.ui.subscriptions can't break serranoie.app.minus.domain.usecase.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.subscriptions uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history.sections uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.history.sections, while a change to serranoie.app.minus.presentation.ui.history.sections can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history.sections uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in serranoie.app.minus.presentation.ui.history.sections uses a type in serranoie.app.minus.presentation.ui.theme.component.
serranoie.app.minus.presentation.ui.history.sections uses serranoie.app.minus.presentation.ui.theme.component, so a change to serranoie.app.minus.presentation.ui.theme.component can break serranoie.app.minus.presentation.ui.history.sections, while a change to serranoie.app.minus.presentation.ui.history.sections can't break serranoie.app.minus.presentation.ui.theme.component.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history.sections uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in serranoie.app.minus.presentation.ui.history.sections uses a type in serranoie.app.minus.presentation.ui.theme.component.expense.
serranoie.app.minus.presentation.ui.history.sections uses serranoie.app.minus.presentation.ui.theme.component.expense, so a change to serranoie.app.minus.presentation.ui.theme.component.expense can break serranoie.app.minus.presentation.ui.history.sections, while a change to serranoie.app.minus.presentation.ui.history.sections can't break serranoie.app.minus.presentation.ui.theme.component.expense.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history.sections uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.history.sections uses serranoie.app.minus.presentation.ui.history, so a change to serranoie.app.minus.presentation.ui.history can break serranoie.app.minus.presentation.ui.history.sections, while a change to serranoie.app.minus.presentation.ui.history.sections can't break serranoie.app.minus.presentation.ui.history.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.history.sections uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.onboarding uses serranoie.app.minus.domain.model, so a change to serranoie.app.minus.domain.model can break serranoie.app.minus.presentation.ui.onboarding, while a change to serranoie.app.minus.presentation.ui.onboarding can't break serranoie.app.minus.domain.model.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.onboarding uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.onboarding uses serranoie.app.minus.data.repository, so a change to serranoie.app.minus.data.repository can break serranoie.app.minus.presentation.ui.onboarding, while a change to serranoie.app.minus.presentation.ui.onboarding can't break serranoie.app.minus.data.repository.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.onboarding uses a module listed above it, which is the healthy direction.
serranoie.app.minus.presentation.ui.onboarding uses serranoie.app.minus.presentation.ui.analytics, so a change to serranoie.app.minus.presentation.ui.analytics can break serranoie.app.minus.presentation.ui.onboarding, while a change to serranoie.app.minus.presentation.ui.onboarding can't break serranoie.app.minus.presentation.ui.analytics.
Position
Below the diagonal: serranoie.app.minus.presentation.ui.onboarding uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 46.1 · Weak · gated by R10, R2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
27
High / Critical
A03:2025 — Software Supply Chain Failures
9
High / Critical
Roadmap
Top priorities: Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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.
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Code Duplication: Edited copy of a member (22 corresponding lines)
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 — 27
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 — 484
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 — 56
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 66 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 — 66 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 556 of 567 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — 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. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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 (2 contributor(s) across 509 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% 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.
D21 Naming Consistency — 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. 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 (island-sdk/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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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. `app/src/main/java/com/serranoie/app/minus/domain/receipt/ReceiptVocabulary.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/util/font/format/DateFormatting.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.
AXR1 Runtime accessibility — 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. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: t4android-openmp:4.9.0.
> Could not get resource 'https://jitpack.io/cz/adaptech/tesseract4android/tesseract4android-openmp/4.9.0/tesseract4android-openmp-4.9.0.pom'.
> Could not…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
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 — 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. The frontend declares that it computes whether a construction is produced or passed, yet 1463 of 1473 constructions arrived without the answer. Arm two skipped them; it did not clear them.
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 this repository's Kotlin, Python is most of its product and 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 this repository's Kotlin, Python is most of its product and 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.
M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
56 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainScreenContentKt.PhoneLayout at 77. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being BudgetViewModel.handleEditorIntent at 21 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt (BudgetViewModel.handleEditorIntent at 21), app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenViewModel.kt (MainScreenViewModel.processIntent at 19), app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryViewModel.kt (HistoryViewModel.processIntent at 17), app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormulaDialog.kt (BudgetFormulaDialogKt.captionText at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 47 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with MainScreenContentKt.PhoneLayout (cyclomatic 77), BudgetPillKt.BudgetPill (cyclomatic 73), AnalyticsKt.Analytics (cyclomatic 71). — 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 3 together lifts Cyclomatic Complexity from 6.2 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 66 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with BudgetPillKt.BudgetPill (cognitive 119), AnalyticsKt.Analytics (cognitive 98), EditorKt.EditingContent (cognitive 80). — 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 4.9 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.4 / 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.
Resolve the 31 MethodTooLong finding(s) in God Classes — start with MainScreenContent.kt (4), MockDisplay.kt (2), BudgetPill.kt. — One of this dimension's main actionable groups (31 warning-level).
Resolve the 15 FileTooLong finding(s) in God Classes — start with MainScreenContent.kt, Analytics.kt, Editor.kt. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 5 TooManyMethods finding(s) in God Classes — start with SettingsRepositoryImpl.kt, BudgetRepositoryImpl.kt, SettingsViewModel.kt. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
120 duplicated block group(s) detected. 7.5 % of the production lines (5,826 of 78,185) are in a reported copy. A further 58 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (20 corresponding lines) · ×5app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:376
+ 96 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with HistoryScreen.kt, TransactionDateTimeRow.kt, PastTransactionDateSections.kt. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with NotificationHelper.kt, SubscriptionsCalendarSection.kt, MultiCategoryChart.kt. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with TransactionPeriodMapper.kt, Analytics.kt, SettingsGroup.kt. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.9 / 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.
7 production modules (Gradle+npm), 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; 2 module(s) off the main sequence.
Off the main sequence: :island-sdk
Off the main sequence: :sync-contract
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
0 outdated direct gem(s), 1 pinning defect(s). 2 declaration(s) graded against rubygems.org, none of them against a committed Gemfile.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. 1 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
No Gemfile.lock committed by an application
What to do
Resolve the 1 No Gemfile.lock committed by an application finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 of 2 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 2 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Resolve the 33 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainScreenContent.kt, Analytics.kt, BudgetPill.kt. — One of this dimension's main actionable groups (33 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 deducted task-comment markers across 78185 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.
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.
2 of 2 documentation facets pass in full. 3 document(s) read across 7 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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.
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.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 54 declarations measured against a convention their peers follow.
`onExportCSV` spells `CSV` where 12 names in the project spell it `Csv`app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:186
`performUIHaptic` spells `UI` where 40 names in the project spell it `Ui`app/src/main/java/com/serranoie/app/minus/presentation/util/haptic/HapticUtils.kt:19
What to do
Resolve the 1 `onExportCSV` spells `CSV` where 12 names in the project spell it `Csv` finding(s) in Naming Consistency — start with Analytics.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `performUIHaptic` spells `UI` where 40 names in the project spell it… finding(s) in Naming Consistency — start with HapticUtils.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 7 build units (Gradle, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionapp/build.gradle.kts:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.5 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
49 % of calls cross a namespace and 30 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
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.
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).
27 finding(s): 0 critical, 25 high, 2 medium, 0 low. 17 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) — `app/src/main/java/com/serranoie/app/minus/presentation/util/font/format/DateFormatting.kt` (line 129) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 17 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 (17 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 319 of the 458 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 5 Change coupling finding(s) in Change Coupling — start with SettingsRepositoryImpl.kt (2), AppNavGraph.kt, MainScreen.kt. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with Editor.kt, BudgetRepositoryImpl.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 85 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.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
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.
`CensorManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (wasNear; e.g. `wasNear` in `onSensorChanged` at line 49). — app/src/main/java/com/serranoie/app/minus/presentation/util/CensorManager.kt:23
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
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.
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.
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.
`TransactionDao` declares 24 abstract methods: `getAllTransactions`, `getTransactionsForDateRange`, `getTransactionsForDay`, `getTotalSpentForDay`, `getTotalSpentForPeriod`, `insert`, `insertOrReplace`, `insertIgnore`, `insertAllOrReplace`, `update`, `delete`, `deleteById`, `deleteAll`, `getByPocketId`, `deleteOneTimeByPeriodId`, `getTransactionById`, `countDistinctPeriods`, `hasTransactionsInPeriod`, `existsByClientGeneratedId`, `getByClientGeneratedId`, `getRecentTransactions`, `markCreditAsPaidInRange`, `markAllCreditAsPaid`, `markTransactionAsPaid`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/com/serranoie/app/minus/data/local/dao/TransactionDao.kt:13
`BudgetRepository` declares 44 abstract methods: `getTransactions`, `getQueuedTransactions`, `getTransactionsForPeriod`, `addTransaction`, `addTransactions`, `addQueuedTransaction`, `addTransactionIfAbsent`, `addPocketWithdrawal`, `addPocketDeposit`, `updateTransaction`, `assignQueuedTransactionsToPeriod`, `upsertTransactions`, `replaceAllTransactions`, `existsTransactionByClientGeneratedId`, `getRecentTransactions`, `deleteTransaction`, `getSpentForDate`, `getSpentForPeriod`, `getBudgetSettings`, `saveBudgetSettings`, `getBudgetSettingsSync`, `getTransactionById`, `getActiveCategories`, `getAllCategories`, `findOrCreateCategory`, `createCategory`, `hideCategory`, `incrementCategoryUsage`, `setCategoryLimit`, `getPeriodCount`, `markCreditTransactionsAsPaid`, `markAllCreditTransactionsAsPaid`, `markTransactionAsPaid`, `getPaidRecurrentOccurrences`, `markRecurrentOccurrencePaid`, `getPaidOccurrenceDatesFor`, `getArchivedBudgets`, `upsertArchivedBudgets`, `replaceAllArchivedBudgets`, `archiveCurrentPeriod`, and 4 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepository.kt:15
`SettingsRepository` declares 64 abstract methods: `observeSettings`, `observeCurrentPeriodRollover`, `observeCurrentPeriodBoundary`, `getCurrentPeriodId`, `getSettings`, `setOnboardingCompleted`, `setEarlyFinishActive`, `setPeriodEndAlreadyHandled`, `setCurrentPeriod`, `setCurrentPeriodRollover`, `setPendingRollover`, `clearPendingRollover`, `setNotificationTime`, `setRecurrentNotificationTime`, `setThemeMode`, `setTypographyMode`, `setContrastMode`, `setAppColorScheme`, `setLanguage`, `setDynamicColorEnabled`, `setRoundedFontEnabled`, `setAmoledEnabled`, `setCreditQuickToggleEnabled`, `setShowPastTransactions`, `setCategoryPickerDirectPopupEnabled`, `setCategoryGridModeEnabled`, `setExtraNoteEnabled`, `setReserveUpcomingChargesEnabled`, `setNewCategoryTagEnabled`, `setNotificationScanEnabled`, `setNotificationScanPackages`, `toggleNotificationScanPackage`, `setTutorialBoxCompleted`, `setAnalyticsTutorialCompleted`, `setHistoryTutorialCompleted`, `setReceiptScanHintShown`, `setSavingsReminderEnabled`, `setAnalyticsSpendsTutorialCompleted`, `setPeriodMappingMode`, `setFirstLaunchTutorialStage`, and 24 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepository.kt:18
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
C1 · Data Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No encryption usage (javax.crypto's Cipher in ENCRYPT_MODE, Tink, Jasypt, Spring Security's Encryptors, Jetpack Security's EncryptedSharedPreferences or EncryptedFile, the Android Keystore, SQLCipher, pgcrypto) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — app/src/main/java/com/serranoie/app/minus/data/local/entity/BudgetSettingsEntity.kt:20
What to do
Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
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.
`ArchivedBudgetEntity`'s public constructor takes `totalBudget`, `spentAmount`, `currencyCode`, `periodType` 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 `ArchivedBudgetEntity` 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/ArchivedBudgetEntity.kt:7
`BudgetSettingsEntity`'s public constructor takes `totalBudget`, `period`, `currencyCode`, `rollOverLimit`, … 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 `BudgetSettingsEntity` 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/BudgetSettingsEntity.kt:7
`CategoryEntity`'s public constructor takes `name`, `limitAmount`, `limitUnit` 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/CategoryEntity.kt:11
`PaidRecurrentOccurrenceEntity`'s public constructor takes `status` 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 `PaidRecurrentOccurrenceEntity` 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/PaidRecurrentOccurrenceEntity.kt:10
`QueuedTransactionEntity`'s public constructor takes `amount`, `comment`, `note` 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 `QueuedTransactionEntity` 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/QueuedTransactionEntity.kt:8
`SavingsPocketEntity`'s public constructor takes `name`, `targetAmount` 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 `SavingsPocketEntity` 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/SavingsPocketEntity.kt:7
`TransactionEntity`'s public constructor takes `amount`, `comment`, `note`, `clientGeneratedId`, … 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. — app/src/main/java/com/serranoie/app/minus/data/local/entity/TransactionEntity.kt:17
What to do
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Do you agree with this assessment?
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.
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.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
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
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.
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.
`PROJECT_OVERVIEW.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `island-sdk`, `sync-contract`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — PROJECT_OVERVIEW.md:31
`fastlane/CHANGELOG_GENERATION.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `island-sdk`, `sync-contract`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — fastlane/CHANGELOG_GENERATION.md:15
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.
Update PROJECT_OVERVIEW.md so it draws the parts the code has today: add island-sdk, sync-contract.
Update fastlane/CHANGELOG_GENERATION.md so it draws the parts the code has today: add island-sdk, sync-contract.
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.
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.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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 5 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:4
`promo/remotion-es/package.json` 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`. — promo/remotion-es/package.json:14
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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
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.
Do you agree with this assessment?
R1 · Type Safety9.2 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
25 of the duplicated blocks reported below have copies in at least two of the sibling directories remotion, remotion-es under promo/. That concentration is one structural fact, not 25 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 25 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — promo/remotion-es/src/components/Phone.tsx:1
promo/remotion-es/src/components/Phone.tsx:1 · promo/remotion/src/components/Phone.tsx:1 — these 2 files are line-for-line copies of one another — 260 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/components/Phone.tsx:1
promo/remotion-es/src/scenes/S05Pill.tsx:1 · promo/remotion/src/scenes/S05Pill.tsx:1 — these 2 files are line-for-line copies of one another — 177 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S05Pill.tsx:1
promo/remotion-es/src/scenes/S09Subs.tsx:1 · promo/remotion/src/scenes/S09Subs.tsx:1 — these 2 files are line-for-line copies of one another — 167 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S09Subs.tsx:1
promo/remotion-es/src/scenes/S06Sheet.tsx:1 · promo/remotion/src/scenes/S06Sheet.tsx:1 — these 2 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S06Sheet.tsx:1
promo/remotion-es/src/scenes/S10Analytics.tsx:1 · promo/remotion/src/scenes/S10Analytics.tsx:1 — these 2 files are line-for-line copies of one another — 144 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S10Analytics.tsx:1
promo/remotion-es/src/scenes/S07Split.tsx:1 · promo/remotion/src/scenes/S07Split.tsx:1 — these 2 files are line-for-line copies of one another — 103 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S07Split.tsx:1
promo/remotion-es/src/scenes/S04Question.tsx:1 · promo/remotion/src/scenes/S04Question.tsx:1 — these 2 files are line-for-line copies of one another — 86 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S04Question.tsx:1
promo/remotion-es/src/components/Icons.tsx:1 · promo/remotion/src/components/Icons.tsx:1 — these 2 files are line-for-line copies of one another — 83 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/components/Icons.tsx:1
promo/remotion-es/src/scenes/S08Choice.tsx:1 · promo/remotion/src/scenes/S08Choice.tsx:1 — these 2 files are line-for-line copies of one another — 79 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S08Choice.tsx:1
promo/remotion-es/src/theme.ts:1 · promo/remotion/src/theme.ts:1 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/theme.ts:1
promo/remotion-es/src/Promo.tsx:1 · promo/remotion/src/Promo.tsx:1 — these 2 files are line-for-line copies of one another — 64 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/Promo.tsx:1
promo/remotion-es/src/components/Logo.tsx:4 · promo/remotion/src/components/Logo.tsx:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — promo/remotion-es/src/components/Logo.tsx:4
promo/remotion-es/src/components/Cursor.tsx:1 · promo/remotion/src/components/Cursor.tsx:1 — these 2 files are line-for-line copies of one another — 58 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/components/Cursor.tsx:1
promo/remotion-es/src/components/Kinetic.tsx:1 · promo/remotion/src/components/Kinetic.tsx:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/components/Kinetic.tsx:1
promo/remotion-es/src/components/Pill.tsx:1 · promo/remotion/src/components/Pill.tsx:1 — these 2 files are line-for-line copies of one another — 54 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/components/Pill.tsx:1
promo/remotion-es/src/components/Backgrounds.tsx:1 · promo/remotion/src/components/Backgrounds.tsx:1 — these 2 files are line-for-line copies of one another — 53 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/components/Backgrounds.tsx:1
promo/remotion-es/src/anim.ts:1 · promo/remotion/src/anim.ts:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/anim.ts:1
promo/remotion-es/src/scenes/S03Splash.tsx:1 · promo/remotion/src/scenes/S03Splash.tsx:1 — these 2 files are line-for-line copies of one another — 50 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — promo/remotion-es/src/scenes/S03Splash.tsx:1
promo/remotion-es/src/scenes/S02Wordmark.tsx:13 · promo/remotion/src/scenes/S02Wordmark.tsx:13 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — promo/remotion-es/src/scenes/S02Wordmark.tsx:13
promo/remotion-es/src/scenes/S11Outro.tsx:10 · promo/remotion/src/scenes/S11Outro.tsx:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — promo/remotion-es/src/scenes/S11Outro.tsx:10
promo/remotion-es/src/components/SplashLogo.tsx:4 · promo/remotion/src/components/SplashLogo.tsx:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — promo/remotion-es/src/components/SplashLogo.tsx:4
promo/remotion-es/src/scenes/S11Outro.tsx:44 · promo/remotion/src/scenes/S11Outro.tsx:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — promo/remotion-es/src/scenes/S11Outro.tsx:44
promo/remotion-es/scripts/mux.mjs:5 · promo/remotion/scripts/mux.mjs:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — promo/remotion-es/scripts/mux.mjs:5
promo/remotion-es/scripts/stills.mjs:5 · promo/remotion/scripts/stills.mjs:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — promo/remotion-es/scripts/stills.mjs:5
promo/remotion-es/remotion.config.ts:3 · promo/remotion/remotion.config.ts:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — promo/remotion-es/remotion.config.ts:3
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
S05Pill has cyclomatic complexity 35 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/scenes/S05Pill.tsx:50, promo/remotion/src/scenes/S05Pill.tsx:50
(anonymous) has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/components/Phone.tsx:273, promo/remotion/src/components/Phone.tsx:273
S04Question has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/scenes/S04Question.tsx:13, promo/remotion/src/scenes/S04Question.tsx:12
(anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/scenes/S09Subs.tsx:105, promo/remotion/src/scenes/S09Subs.tsx:105
(anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/scenes/S10Analytics.tsx:111, promo/remotion/src/scenes/S10Analytics.tsx:111
MinMaxCard has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/scenes/S10Analytics.tsx:64, promo/remotion/src/scenes/S10Analytics.tsx:64
(anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — promo/remotion-es/src/components/Phone.tsx:196, promo/remotion/src/components/Phone.tsx:196
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling6.6 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 4 application, 2 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (4 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — promo/remotion-es/scripts/stills.mjs, promo/remotion/scripts/stills.mjs
Nothing imports this binding — it is safe to review for removal. (×14) — promo/remotion-es/src/anim.ts:44, promo/remotion-es/src/anim.ts:45, promo/remotion-es/src/anim.ts:74, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
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.
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.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. 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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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.
`catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×16) — island-sdk/src/main/java/com/sameerasw/island/sdk/IslandCodec.kt:21, island-sdk/src/main/java/com/sameerasw/island/sdk/IslandIdentity.kt:20, island-sdk/src/main/java/com/sameerasw/island/sdk/IslandIdentity.kt:30, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — island-sdk/src/main/java/com/sameerasw/island/sdk/compose/IslandSnapshot.kt:24
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/com/serranoie/app/minus/presentation/util/font/format/VisualTransformationAsCurrency.kt:280
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.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 2 of 55 WCAG 2.2 Level A/AA success criteria (4%; ≈4% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 53 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Unscored — 2 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 — 22 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 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 image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: t4android-openmp:4.9.0.
> Could not get resource 'https://jitpack.io/cz/adaptech/tesseract4android/tesseract4android-openmp/4.9.0/tesseract4android-openmp-4.9.0.pom'.
> Could not…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~28362 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
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.
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; comments in this repository's .java, .kt, .py source were not judged.
D25 ADR Conformance — no ADRs to check
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.
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
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
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)
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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python 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
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (50 production file(s)) has no JavaScript/TypeScript test, but it is 5.84% of this repository's production source and the other 94.16% carries 28,362 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
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
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — 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 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
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.
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.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:628— app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 77 in MainScreenContentKt.PhoneLayout at line 628. 4 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:206— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in AnalyticsKt.Analytics at line 206. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:129— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in BudgetPillKt.BudgetPill at line 129. 3 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:665— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in EditorKt.EditingContent at line 665. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:80— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in TransactionEditScreenKt.TransactionEditScreen at line 80. 4 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:428— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in TrendingGraphKt.BudgetGraph at line 428. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:659— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in BudgetPeriodSheetKt.EditBudgetContent at line 659. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt:57— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in BudgetTransactionHandler.applyTransaction at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:44— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in BudgetStateCalculator.calculateBudgetState at line 44. 1 of those changes was a fix/bug commit, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt:98— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in EditableCategoryTagKt.EditableCategoryTag at line 98. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt:104— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in BudgetPillMetricsKt.resolveExhaustedMessage at line 104. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt:32— app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in MainScreenKt.MainScreen at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt:46— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in ExpenseItemExpandedContentKt.ExpenseItemExpandedContent at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt:84— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in BudgetPeriodManager.persistBudgetSettings at line 84. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:57— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in UpcomingRecurrentItemRowKt.UpcomingRecurrentItemRow at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:93— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in NumpadKt.Numpad at line 93. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:66— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ExpenseItemKt.ExpenseItem at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.kt:127— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in HistoryCalculationsKt.calculateNextChargeDate at line 127. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillStatusLabel.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillStatusLabel.kt:74— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillStatusLabel.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in BudgetPillStatusLabelKt.StatusLabel at line 74. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillStatusLabel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormula.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormula.kt:62— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormula.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in BudgetFormulaKt.buildBudgetFormula at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormula.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationScheduler.kt app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationScheduler.kt:342— app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationScheduler.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in NotificationScheduler.nextOccurrenceDateTime at line 342. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationScheduler.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/NumpadButton.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/NumpadButton.kt:62— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/NumpadButton.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in NumpadButtonKt.NumpadButton at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/NumpadButton.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt:73— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in LeftoverChoiceListKt.LeftoverChoiceList at line 73. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/receipt/ReceiptScanner.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/receipt/ReceiptScanner.kt:91— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/receipt/ReceiptScanner.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ReceiptScannerKt.rememberReceiptScanner at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/receipt/ReceiptScanner.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillAmountText.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillAmountText.kt:45— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillAmountText.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in BudgetPillAmountTextKt.SegmentedAmountText at line 45. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 00:21:00 -07:00' --until='2026-11-15 00:21:00 -07:00' --full-history --no-merges -- app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillAmountText.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
MethodTooLong: MainScreenContentKt.PhoneLayout app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:628— MethodTooLong — PhoneLayout runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.01× 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: MainScreenContentKt.MainScreenContent app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:146— MethodTooLong — MainScreenContent runs 287 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 187 over it, 2.87× 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: BudgetPillKt.PreviewBudgetPillSmallHeight app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:722— MethodTooLong — PreviewBudgetPillSmallHeight runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× 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: MultiCategoryChartKt.MultiCategoryChart app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:193— MethodTooLong — MultiCategoryChart runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× 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: HistoryScreenKt.HistoryListContent app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:322— MethodTooLong — HistoryListContent runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BudgetPeriodSheetKt.ViewBudgetContent app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:341— MethodTooLong — ViewBudgetContent runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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: RecurrentExpenseDialogKt.RecurrentExpenseDialog app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:77— MethodTooLong — RecurrentExpenseDialog runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: TotalBudgetCardKt.TotalBudgetCard app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:70— MethodTooLong — TotalBudgetCard runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: SavingsPreferencesEditorKt.SavingsPreferencesEditor app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/savings/SavingsPreferencesEditor.kt:82— MethodTooLong — SavingsPreferencesEditor runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: RecurrenceConfigSheetKt.RecurrenceConfigSheet app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt:70— MethodTooLong — RecurrenceConfigSheet runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× 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: ExpenseItemExpandedContentKt.ExpenseItemExpandedContent app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt:46— MethodTooLong — ExpenseItemExpandedContent runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: MultiCategoryHourChartKt.MultiCategoryHourChart app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:98— MethodTooLong — MultiCategoryHourChart 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: LeftoverChoiceListKt.LeftoverChoiceList app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt:73— MethodTooLong — LeftoverChoiceList runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× 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: TutorialBoxKt.TutorialOverlay app/src/main/java/com/serranoie/app/minus/presentation/ui/tutorial/TutorialBox.kt:203— MethodTooLong — TutorialOverlay runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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: MainScreenContentKt.MainScreenNumpadSection app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:1360— MethodTooLong — MainScreenNumpadSection runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: SavingsRecommendationCardKt.SavingsRecommendationCard app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:107— MethodTooLong — SavingsRecommendationCard runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: MockDisplayKt.MockPillScreen app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:299— MethodTooLong — MockPillScreen runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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: SubscriptionItemKt.SubscriptionItem app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionItem.kt:61— MethodTooLong — SubscriptionItem runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: BudgetStateCalculator.calculateBudgetState app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:44— MethodTooLong — calculateBudgetState runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: MainScreenContentKt.TabletLayout app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:1184— MethodTooLong — TabletLayout runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: MockDisplayKt.MockNumpadScreen app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:115— MethodTooLong — MockNumpadScreen 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: SpendBudgetCardKt.SpendBudgetCard app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendBudgetCard.kt:124— MethodTooLong — SpendBudgetCard runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: TrendingDailyGraphKt.GraphHourCanvas app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingDailyGraph.kt:90— MethodTooLong — GraphHourCanvas 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: SubscriptionDayDetailsSheetKt.SubscriptionDayChargeRow app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionDayDetailsSheet.kt:133— MethodTooLong — SubscriptionDayChargeRow runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: FinishDateSelectorKt.FinishDateSelector app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/FinishDateSelector.kt:74— MethodTooLong — FinishDateSelector 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.
Swallowed exception (caught, then discarded) island-sdk/src/main/java/com/sameerasw/island/sdk/IslandCodec.kt:21— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) island-sdk/src/main/java/com/sameerasw/island/sdk/IslandIdentity.kt:20— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) island-sdk/src/main/java/com/sameerasw/island/sdk/IslandIdentity.kt:30— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/presentation/util/font/format/VisualTransformationAsCurrency.kt:280— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:909— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/domain/calculator/ExpressionEvaluator.kt:80— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:68— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:149— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:155— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:204— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:210— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:675— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:683— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:691— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:699— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/csv/MinusCsvParser.kt:214— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) app/src/main/java/com/serranoie/app/minus/data/csv/MinusCsvParser.kt:233— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
FileTooLong: home/MainScreenContent.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt— FileTooLong — 1357 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 857 over it, 2.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: analytics/Analytics.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt— FileTooLong — 1114 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 614 over it, 2.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: editor/Editor.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt— FileTooLong — 1093 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 593 over it, 2.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sheets/BudgetPeriodSheet.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt— FileTooLong — 1011 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 511 over it, 2.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: pill/BudgetPill.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt— FileTooLong — 859 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 359 over it, 1.72× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: budget/BudgetViewModel.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt— FileTooLong — 733 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: BudgetViewModel (108-937). The bar is 500 significant lines; this is 233 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: settings/Settings.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/Settings.kt— FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 223 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: graphs/TrendingGraph.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt— FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 165 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: numpad/Numpad.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt— FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 145 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bugreport/BugReportForm.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/bugreport/BugReportForm.kt— FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 90 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: component/SettingsGroup.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: analytics/AnalyticsViewModel.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt— FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: AnalyticsViewModel (69-721). The bar is 500 significant lines; this is 56 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: appearance/MockDisplay.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: graphs/MultiCategoryChart.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: appearance/AppearanceOptionsScreen.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:222— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:222-234 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/dialogs/TransactionEditDialog.kt:58-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionDateTimeRow.kt:43— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionDateTimeRow.kt:43-55 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionDateTimeRow.kt:74-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionDateTimeRow.kt:43` 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 (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:104— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:104-116 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt:140-152 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionItem.kt:168— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionItem.kt:168-180 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionItem.kt:188-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionItem.kt:168` 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 (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/GraphCanvas.kt:84— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/GraphCanvas.kt:84-96 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:234-246 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:504— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:504-516 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:319-331 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:504` 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 (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:297— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:297-309 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:320-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:297` 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 (13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:426— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:426-438 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:690-702 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:426` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:284— app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:284-293 | app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:347-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:51— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:51-60 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:97-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:210— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:210-219 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:106-115 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:221` calls `stringResource` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:117` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:211— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:211-221 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:237-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt:365— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt:365-374 | app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:927-936 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:174— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:174-183 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:153-162 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1303— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1303-1313 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1329-1338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1303` 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 (9 lines × 2) app/src/main/java/com/serranoie/app/minus/domain/calculator/TransactionPeriodMapper.kt:63— app/src/main/java/com/serranoie/app/minus/domain/calculator/TransactionPeriodMapper.kt:63-71 | app/src/main/java/com/serranoie/app/minus/domain/calculator/TransactionPeriodMapper.kt:88-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/domain/calculator/TransactionPeriodMapper.kt:63` 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 (9 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:941— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:941-949 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/FinishedPeriodHeader.kt:65-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:941` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/FinishedPeriodHeader.kt:63` calls `fillMaxWidth`, `padding` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:940` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:403— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:403-411 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:209-220 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:403` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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. Note first that the copies are not typed on the same thing: `Icon` names `androidx.compose.material3.Icon` in one and `androidx.wear.compose.material3.Icon` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/CreditOwedCard.kt:58— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/CreditOwedCard.kt:58-66 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:116-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:360— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:360-368 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:405-413 — 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.
Duplicated block (9 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:156— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:156-164 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:151-159 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:97— app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:97-105 | app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearMessageListener.kt:91-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:97` 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.
DM11 · Constructible invalid state· Constructible in an invalid state · ×7
Constructible in an invalid state: ArchivedBudgetEntity app/src/main/java/com/serranoie/app/minus/data/local/entity/ArchivedBudgetEntity.kt:7— `ArchivedBudgetEntity`'s public constructor takes `totalBudget`, `spentAmount`, `currencyCode`, `periodType` 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 `ArchivedBudgetEntity` 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: BudgetSettingsEntity app/src/main/java/com/serranoie/app/minus/data/local/entity/BudgetSettingsEntity.kt:7— `BudgetSettingsEntity`'s public constructor takes `totalBudget`, `period`, `currencyCode`, `rollOverLimit`, … 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 `BudgetSettingsEntity` 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: CategoryEntity app/src/main/java/com/serranoie/app/minus/data/local/entity/CategoryEntity.kt:11— `CategoryEntity`'s public constructor takes `name`, `limitAmount`, `limitUnit` 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: PaidRecurrentOccurrenceEntity app/src/main/java/com/serranoie/app/minus/data/local/entity/PaidRecurrentOccurrenceEntity.kt:10— `PaidRecurrentOccurrenceEntity`'s public constructor takes `status` 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 `PaidRecurrentOccurrenceEntity` 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: QueuedTransactionEntity app/src/main/java/com/serranoie/app/minus/data/local/entity/QueuedTransactionEntity.kt:8— `QueuedTransactionEntity`'s public constructor takes `amount`, `comment`, `note` 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 `QueuedTransactionEntity` 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: SavingsPocketEntity app/src/main/java/com/serranoie/app/minus/data/local/entity/SavingsPocketEntity.kt:7— `SavingsPocketEntity`'s public constructor takes `name`, `targetAmount` 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 `SavingsPocketEntity` 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 app/src/main/java/com/serranoie/app/minus/data/local/entity/TransactionEntity.kt:17— `TransactionEntity`'s public constructor takes `amount`, `comment`, `note`, `clientGeneratedId`, … 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.
Duplicated block (14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryLimitCard.kt:256— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryLimitCard.kt:256-269 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/bugreport/BugReportForm.kt:408-421 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryLimitCard.kt:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/DueTodayCard.kt:48— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/DueTodayCard.kt:48-61 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/Subscriptions.kt:320-333 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:140— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:140-153 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:118-131 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:140` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: `Icon` names `androidx.compose.material3.Icon` in one and `androidx.wear.compose.material3.Icon` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:102— app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:102-115 | app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:137-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:102` 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 (14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:69— app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:69-82 | app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogItemCard.kt:121-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendBudgetCard.kt:312— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendBudgetCard.kt:312-325 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendBudgetCard.kt:330-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendBudgetCard.kt:312` 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.
TooManyMethods: SettingsRepositoryImpl app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:153— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. Most of these members implement repository.SettingsRepository (64 of 70 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: BudgetRepositoryImpl app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:44— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. Most of these members implement repository.BudgetRepository (44 of 49 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: SettingsViewModel app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/SettingsViewModel.kt:103— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BudgetViewModel app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:108— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AnalyticsViewModel app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:69— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: SettingsRepositoryImpl.kt ↔ SettingsViewModel.kt app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:1— `app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/SettingsViewModel.kt` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `6b747361` feat: enhance CSV folder sync with status reporting and non-destructi…; `e0c5f728` fix: enable marquee effect on projection label; `285b319e` feat: implement AMOLED dark theme option — run `git show` on any of them.
Change coupling: SettingsRepositoryImpl.kt ↔ MainActivity.kt app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt:1— `app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepositoryImpl.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/MainActivity.kt` change together 57% of the time (12 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `d609a396` fix(pockets): address PR review on savings pockets; `6f08a198` feat: support unresolved rollover surplus handling; `bd810a7d` Revert "feat: add daily surplus dialog and carry-forward support for … — run `git show` on any of them.
Change coupling: AppNavGraph.kt ↔ MainActivity.kt app/src/main/java/com/serranoie/app/minus/navigation/AppNavGraph.kt:1— `app/src/main/java/com/serranoie/app/minus/navigation/AppNavGraph.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/MainActivity.kt` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `b742edcf` feat: add launcher shortcuts for receipt scanner; `5b206317` feat: add automated CSV folder sync and guide screen; `285b319e` feat: implement AMOLED dark theme option — run `git show` on any of them.
Change coupling: MainScreen.kt ↔ NumpadButton.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt:1— `app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/NumpadButton.kt` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `76f6f5a6` fix: add API compatibility guards for font width variations and versi…; `a83812ac` fix: send the state for the budget split on main screen (#67); `ea10162b` feat: Overhaul Numpad interaction and refine keyboard animations — run `git show` on any of them.
Change coupling: AppDatabase.kt ↔ BudgetStateCalculator.kt app/src/main/java/com/serranoie/app/minus/data/local/AppDatabase.kt:1— `app/src/main/java/com/serranoie/app/minus/data/local/AppDatabase.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.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 `6f08a198` feat: support unresolved rollover surplus handling; `bd810a7d` Revert "feat: add daily surplus dialog and carry-forward support for …; `2b62273b` feat: add daily surplus dialog and carry-forward support for dynamic … — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×5
Edited copy of a member (20 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:376— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:376-398 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:406-425 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:223— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:223-242 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:444-478 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:210— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:210-232 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:236-255 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditToggleButton.kt:123— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditToggleButton.kt:123-142 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditToggleButton.kt:146-165 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:341— wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:341-360 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:376-396 — These two members are one piece of code written twice and then edited apart: 20 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.
Duplicated block (20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1223— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1223-1242 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1268-1287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1223` 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 (20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:155— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:155-174 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt:112-131 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:155` 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 (20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:80— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:80-99 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt:100-119 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:80` 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 (20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:330— app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:330-349 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:641-660 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:350` calls `Spacer`, `weight` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/MockDisplay.kt:661` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:870— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:870-889 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:896-915 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:870` 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 (17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:407— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:407-423 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:455-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:407` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:122— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:122-138 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:100-116 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `MaterialTheme` names `androidx.compose.material3.MaterialTheme` in one and `androidx.wear.compose.material3.MaterialTheme` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:184— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:184-200 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingDailyGraph.kt:181-197 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:893— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:893-909 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:948-964 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:893` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:176— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:176-192 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt:133-149 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:176` 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 (6 lines × 2) app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:84— app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:84-89 | app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt:124-129 — 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.
Duplicated block (6 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:391— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:391-396 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:668-673 — 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.
Duplicated block (6 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/split/CalculatedSplitCard.kt:39— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/split/CalculatedSplitCard.kt:39-44 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/split/SplitCalculations.kt:9-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/SectionUtils.kt:21— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/SectionUtils.kt:21-26 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/SavedCategoriesGrid.kt:51-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/SectionUtils.kt:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/hct/Cam16.java:376— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/hct/Cam16.java:376-381 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/hct/CamSolver.java:576-581 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:231— app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:231-248 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/bugreport/BugReportForm.kt:149-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:231` 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 (18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/CreditOwedCard.kt:72— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/CreditOwedCard.kt:72-89 | app/src/main/java/com/serranoie/app/minus/presentation/ui/tutorial/TutorialBox.kt:229-246 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:582— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:582-599 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:621-638 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:582` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:600` calls `plusDays` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:639` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:122— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:122-139 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:124-141 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:122` 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 (8 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:166— app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:166-173 | app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:388-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:166` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:204— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:204-211 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:275-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:329— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:329-339 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:163-170 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:329` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:172` calls `coerceAtMost`, `toPx` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:340` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:169— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:169-176 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:190-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:198` calls `previewCharge` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:177` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:370— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:370-374 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/PastPeriodsBottomSheet.kt:146-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:370` 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 (5 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:268— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:268-273 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:538-542 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:268` 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 (5 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:260— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:260-264 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/RolloverDialog.kt:89-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryToolbar.kt:216— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryToolbar.kt:216-220 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryToolbar.kt:245-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryToolbar.kt:216` 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.
ClassTooLong: BudgetViewModel app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:108— ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 179 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AnalyticsViewModel app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:69— ClassTooLong — 494 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 94 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PillFace app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:114— ClassTooLong — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 59 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:55— app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:55-84 | app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearMessageListener.kt:58-83 — 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) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:92— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:92-117 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:98-133 — 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) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryLimitCard.kt:322— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryLimitCard.kt:322-349 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryLimitCard.kt:353-378 — 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.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:130— app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:130-148 | app/src/main/java/com/serranoie/app/minus/presentation/widget/MonthHeatmapWidget.kt:104-122 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:86— app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:86-109 | app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearMessageListener.kt:85-103 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:520— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:520-538 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:542-564 — These two members are one piece of code written twice and then edited apart: 19 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.
Duplicated block (14 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:449— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:449-462 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:491-504 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:521-534 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:870— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:870-883 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:896-909 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:951-964 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:870` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/date/CalendarHeatmap.kt:541— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/date/CalendarHeatmap.kt:541-554 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/date/CalendarHeatmap.kt:559-572 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/date/CalendarHeatmap.kt:577-590 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:297— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:297-308 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:340-351 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:297` 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 (12 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:84— app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:84-95 | app/src/main/java/com/serranoie/app/minus/presentation/widget/MonthHeatmapWidget.kt:79-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/MinMaxSpentCard.kt:278— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/MinMaxSpentCard.kt:278-289 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/MinMaxSpentCard.kt:299-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/MinMaxSpentCard.kt:278` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1193— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1193-1203 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1366-1376 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/OnboardingScreen.kt:251— app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/OnboardingScreen.kt:251-261 | app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/OnboardingScreen.kt:275-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/OnboardingScreen.kt:251` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:154— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCategoryGraph.kt:154-164 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:429-439 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10–11 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1205— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1205-1215 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1377-1386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1204` calls `padding` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1376` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:188— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:188-198 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:385-394 — 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.
Duplicated block (10–11 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/util/ColorUtils.kt:116— app/src/main/java/com/serranoie/app/minus/presentation/util/ColorUtils.kt:116-125 | app/src/main/java/com/serranoie/app/minus/presentation/util/ColorUtils.kt:127-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/util/ColorUtils.kt:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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.
S05Pill.S05Pill (cyclomatic 36) promo/remotion-es/src/scenes/S05Pill.tsx:50— S05Pill.S05Pill has cyclomatic complexity 36 (threshold 15). Of this number, 35 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
S05Pill.S05Pill (cyclomatic 36) promo/remotion/src/scenes/S05Pill.tsx:50— S05Pill.S05Pill has cyclomatic complexity 36 (threshold 15). Of this number, 35 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Phone.EditorScreen (cyclomatic 26) promo/remotion-es/src/components/Phone.tsx:196— Phone.EditorScreen has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 273). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Phone.EditorScreen (cyclomatic 26) promo/remotion/src/components/Phone.tsx:196— Phone.EditorScreen has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 273). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
S09Subs.SubscriptionsScreen (cyclomatic 19) promo/remotion-es/src/scenes/S09Subs.tsx:74— S09Subs.SubscriptionsScreen has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 105, 93). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S09Subs.SubscriptionsScreen (cyclomatic 19) promo/remotion/src/scenes/S09Subs.tsx:74— S09Subs.SubscriptionsScreen has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 105, 93). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S10Analytics.Heatmap (cyclomatic 16) promo/remotion-es/src/scenes/S10Analytics.tsx:95— S10Analytics.Heatmap has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 111, 135). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S10Analytics.Heatmap (cyclomatic 16) promo/remotion/src/scenes/S10Analytics.tsx:95— S10Analytics.Heatmap has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 111, 135). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S05Pill.S05Pill (cognitive 55) promo/remotion-es/src/scenes/S05Pill.tsx:50— S05Pill.S05Pill has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 24 (44 pts), boolean chains 8, if/else 1 (2 pts), loops 1 (nesting depth added 21). Of this number, 54 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
S05Pill.S05Pill (cognitive 55) promo/remotion/src/scenes/S05Pill.tsx:50— S05Pill.S05Pill has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 24 (44 pts), boolean chains 8, if/else 1 (2 pts), loops 1 (nesting depth added 21). Of this number, 54 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
Phone.EditorScreen (cognitive 32) promo/remotion-es/src/components/Phone.tsx:196— Phone.EditorScreen has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 3, if/else 2 (nesting depth added 10). Of this number, 16 points are the body's own statements and 16 belong to one function literal inside it that branches. 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.
Phone.EditorScreen (cognitive 32) promo/remotion/src/components/Phone.tsx:196— Phone.EditorScreen has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 3, if/else 2 (nesting depth added 10). Of this number, 16 points are the body's own statements and 16 belong to one function literal inside it that branches. 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.
S09Subs.SubscriptionsScreen (cognitive 20) promo/remotion-es/src/scenes/S09Subs.tsx:74— S09Subs.SubscriptionsScreen has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 4 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 105, 93). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S09Subs.SubscriptionsScreen (cognitive 20) promo/remotion/src/scenes/S09Subs.tsx:74— S09Subs.SubscriptionsScreen has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 4 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 105, 93). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S10Analytics.Heatmap (cognitive 17) promo/remotion-es/src/scenes/S10Analytics.tsx:95— S10Analytics.Heatmap has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 111, 135). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
S10Analytics.Heatmap (cognitive 17) promo/remotion/src/scenes/S10Analytics.tsx:95— S10Analytics.Heatmap has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 111, 135). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FunctionTooLong: S05Pill.S05Pill promo/remotion-es/src/scenes/S05Pill.tsx:50— FunctionTooLong — S05Pill runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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.
FunctionTooLong: S05Pill.S05Pill promo/remotion/src/scenes/S05Pill.tsx:50— FunctionTooLong — S05Pill runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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.
Change-coupling hub: Editor.kt → EditableCategoryTag.kt, MainScreen.kt, MainScreenContent.kt app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt— `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt` changes together with 3 other files — `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: BudgetRepositoryImpl.kt → MidnightPeriodChecker.kt, BudgetStateCalculator.kt, BudgetTransactionHandler.kt app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt— `app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepositoryImpl.kt` changes together with 3 other files — `app/src/main/java/com/serranoie/app/minus/domain/time/MidnightPeriodChecker.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×2
Edited copy of a member (50 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:54— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:54-182 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:196-281 — These two members are one piece of code written twice and then edited apart: 50 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 (50 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/RecurringSummaryCard.kt:38— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/RecurringSummaryCard.kt:38-87 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendsCountCard.kt:41-98 — These two members are one piece of code written twice and then edited apart: 50 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 (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:146— app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:146-177 | app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:364-398 — These two members are one piece of code written twice and then edited apart: 32 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 (32 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:535— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:535-566 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:570-601 — These two members are one piece of code written twice and then edited apart: 32 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 (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:84— app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:84-115 | app/src/main/java/com/serranoie/app/minus/presentation/util/Utils.kt:121-150 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:394— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:394-423 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:201-233 — These two members are one piece of code written twice and then edited apart: 30 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 (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:60— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:60-81 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:61-84 — These two members are one piece of code written twice and then edited apart: 22 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 (22 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/ExpenseWidget.kt:239— app/src/main/java/com/serranoie/app/minus/presentation/widget/ExpenseWidget.kt:239-260 | app/src/main/java/com/serranoie/app/minus/presentation/widget/WidgetCommon.kt:38-59 — These two members are one piece of code written twice and then edited apart: 22 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 (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:27— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:27-42 | app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetWidgetUpdater.kt:152-174 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1300— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1300-1319 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1327-1342 — These two members are one piece of code written twice and then edited apart: 16 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) · ×2
Edited copy of a member (23 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:39— app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:39-61 | app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogItemCard.kt:55-77 — 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.
Edited copy of a member (23 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/ExpandableRow.kt:82— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/ExpandableRow.kt:82-104 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/ExpandableRow.kt:116-138 — 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 (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:117— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:117-128 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:275-286 — 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.
Edited copy of a member (12 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryViewModel.kt:215— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryViewModel.kt:215-229 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsViewModel.kt:133-144 — 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· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/dialogs/DeleteRecurrentExpenseDialog.kt:86— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/dialogs/DeleteRecurrentExpenseDialog.kt:86-100 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/dialogs/DeleteRecurrentExpenseDialog.kt:104-118 — These two members are one piece of code written twice and then edited apart: 15 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 (15 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:533— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:533-547 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:584-598 — These two members are one piece of code written twice and then edited apart: 15 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 (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:376— wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:376-395 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionDayDetailsSheet.kt:124-129 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1242— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:1242-1249 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormulaDialog.kt:565-570 — These two members are one piece of code written twice and then edited apart: 6 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 (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:192— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:192-202 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:250-261 — These two members are one piece of code written twice and then edited apart: 11 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 (11 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:206— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:206-216 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:280-291 — These two members are one piece of code written twice and then edited apart: 11 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.
Duplicated block (20–22 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:86— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:86-105 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:130-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:130` 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 (20–22 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:164— app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:164-183 | app/src/main/java/com/serranoie/app/minus/presentation/widget/MonthHeatmapWidget.kt:139-160 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:111— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:111-129 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:208-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:99— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:99-117 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:115-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:99` 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–18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/CategoryLimitsCard.kt:48— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/CategoryLimitsCard.kt:48-64 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:126-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/CategoryLimitsCard.kt:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17–18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:429— app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:429-445 | app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:502-519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:429` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:342— wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:342-357 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:377-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wear/src/main/java/com/serranoie/app/wear/minus/presentation/PeriodOverviewScreen.kt:342` 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 (16 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:356— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:356-371 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:403-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:356` 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) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1060— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1060-1074 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/CategoryToolbar.kt:255-269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:389— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:389-403 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:450-464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:389` 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 (12 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:149— app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:149-160 | app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:254-265 | app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:367-378 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:252` calls `recurrentNotificationId` and `app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationHelper.kt:365` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1232— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1232-1243 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1277-1288 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1323-1334 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1232` 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.
Complex function S05Pill (cyclomatic 35, cognitive 35) promo/remotion-es/src/scenes/S05Pill.tsx:50— S05Pill has cyclomatic complexity 35 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function S05Pill (cyclomatic 35, cognitive 35) promo/remotion/src/scenes/S05Pill.tsx:50— S05Pill has cyclomatic complexity 35 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 15) promo/remotion-es/src/components/Phone.tsx:273— (anonymous) has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 15) promo/remotion/src/components/Phone.tsx:273— (anonymous) has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function S04Question (cyclomatic 15, cognitive 23) promo/remotion-es/src/scenes/S04Question.tsx:13— S04Question has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function S04Question (cyclomatic 15, cognitive 23) promo/remotion/src/scenes/S04Question.tsx:12— S04Question has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) promo/remotion-es/src/scenes/S09Subs.tsx:105— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) promo/remotion/src/scenes/S09Subs.tsx:105— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 13) promo/remotion-es/src/scenes/S10Analytics.tsx:111— (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 13) promo/remotion/src/scenes/S10Analytics.tsx:111— (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function MinMaxCard (cyclomatic 12, cognitive 11) promo/remotion-es/src/scenes/S10Analytics.tsx:64— MinMaxCard has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function MinMaxCard (cyclomatic 12, cognitive 11) promo/remotion/src/scenes/S10Analytics.tsx:64— MinMaxCard has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 11, cognitive 10) promo/remotion-es/src/components/Phone.tsx:196— (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 11, cognitive 10) promo/remotion/src/components/Phone.tsx:196— (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Dead file (~18 LoC) promo/remotion-es/scripts/stills.mjs— no import path from any entry point (4 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~18 LoC) promo/remotion/scripts/stills.mjs— no import path from any entry point (4 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Stateful singleton: CensorManager app/src/main/java/com/serranoie/app/minus/presentation/util/CensorManager.kt:23— `CensorManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (wasNear; e.g. `wasNear` in `onSensorChanged` at line 49).
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption app/src/main/java/com/serranoie/app/minus/data/local/entity/BudgetSettingsEntity.kt:20— No encryption usage (javax.crypto's Cipher in ENCRYPT_MODE, Tink, Jasypt, Spring Security's Encryptors, Jetpack Security's EncryptedSharedPreferences or EncryptedFile, the Android Keystore, SQLCipher, pgcrypto) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
MainScreenContentKt.PhoneLayout (cyclomatic 77) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:628— MainScreenContentKt.PhoneLayout has cyclomatic complexity 77 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetPillKt.BudgetPill (cyclomatic 73) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:129— BudgetPillKt.BudgetPill has cyclomatic complexity 73 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AnalyticsKt.Analytics (cyclomatic 71) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:206— AnalyticsKt.Analytics has cyclomatic complexity 71 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TransactionEditScreenKt.TransactionEditScreen (cyclomatic 44) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:80— TransactionEditScreenKt.TransactionEditScreen has cyclomatic complexity 44 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TrendingGraphKt.BudgetGraph (cyclomatic 42) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:428— TrendingGraphKt.BudgetGraph has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EditorKt.EditingContent (cyclomatic 41) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:665— EditorKt.EditingContent has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HardwareKeyHandlerKt.handleHardwareNumpadKeyEvent (cyclomatic 40) app/src/main/java/com/serranoie/app/minus/presentation/util/HardwareKeyHandler.kt:11— HardwareKeyHandlerKt.handleHardwareNumpadKeyEvent has cyclomatic complexity 40 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SwatchColorsKt.getSwatchColors (cyclomatic 37) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/schemes/SwatchColors.kt:21— SwatchColorsKt.getSwatchColors has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ColorSchemesKt.getAppColorScheme (cyclomatic 36) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/schemes/ColorSchemes.kt:8— ColorSchemesKt.getAppColorScheme has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditableCategoryTagKt.EditableCategoryTag (cyclomatic 34) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt:98— EditableCategoryTagKt.EditableCategoryTag has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetPillMetricsKt.resolveExhaustedMessage (cyclomatic 34) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt:104— BudgetPillMetricsKt.resolveExhaustedMessage has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
SwipeActionsKt.SwipeActions (cyclomatic 33) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SwipeActions.kt:93— SwipeActionsKt.SwipeActions has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainScreenContentKt.MainScreenContent (cyclomatic 31) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:146— MainScreenContentKt.MainScreenContent has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetPillMetricsKt.calculateBudgetMetrics (cyclomatic 31) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt:29— BudgetPillMetricsKt.calculateBudgetMetrics has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BudgetPeriodManager.persistBudgetSettings (cyclomatic 30) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt:84— BudgetPeriodManager.persistBudgetSettings has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExpenseItemExpandedContentKt.ExpenseItemExpandedContent (cyclomatic 30) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt:46— ExpenseItemExpandedContentKt.ExpenseItemExpandedContent has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetPeriodSheetKt.EditBudgetContent (cyclomatic 29) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:659— BudgetPeriodSheetKt.EditBudgetContent has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainScreenKt.MainScreen (cyclomatic 25) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreen.kt:32— MainScreenKt.MainScreen has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BudgetFormulaKt.buildBudgetFormula (cyclomatic 25) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormula.kt:62— BudgetFormulaKt.buildBudgetFormula has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NumpadKt.Numpad (cyclomatic 25) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:93— NumpadKt.Numpad has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetTransactionHandler.applyTransaction (cyclomatic 24) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt:57— BudgetTransactionHandler.applyTransaction has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExpenseItemKt.ExpenseItem (cyclomatic 24) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:66— ExpenseItemKt.ExpenseItem has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditorKt.Editor (cyclomatic 23) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:157— EditorKt.Editor has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TotalBudgetCardKt.TotalBudgetCard (cyclomatic 23) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:70— TotalBudgetCardKt.TotalBudgetCard has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExpressionEvaluatorKt.evaluateExpression (cyclomatic 22) app/src/main/java/com/serranoie/app/minus/domain/calculator/ExpressionEvaluator.kt:9— ExpressionEvaluatorKt.evaluateExpression has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetPillStatusLabelKt.StatusLabel (cyclomatic 22) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillStatusLabel.kt:74— BudgetPillStatusLabelKt.StatusLabel has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainScreenContentKt.MainScreenNumpadSection (cyclomatic 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:1360— MainScreenContentKt.MainScreenNumpadSection has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UpcomingRecurrentItemRowKt.UpcomingRecurrentItemRow (cyclomatic 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:57— UpcomingRecurrentItemRowKt.UpcomingRecurrentItemRow has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NumpadButtonKt.NumpadButton (cyclomatic 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/NumpadButton.kt:62— NumpadButtonKt.NumpadButton has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BudgetStateCalculator.calculateBudgetState (cyclomatic 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:44— BudgetStateCalculator.calculateBudgetState has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ReceiptScannerKt.rememberReceiptScanner (cyclomatic 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/receipt/ReceiptScanner.kt:91— ReceiptScannerKt.rememberReceiptScanner has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ThemeKt.MinusTheme (cyclomatic 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/Theme.kt:275— ThemeKt.MinusTheme has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BudgetPillAmountTextKt.SegmentedAmountText (cyclomatic 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillAmountText.kt:45— BudgetPillAmountTextKt.SegmentedAmountText has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LeftoverChoiceListKt.LeftoverChoiceList (cyclomatic 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt:73— LeftoverChoiceListKt.LeftoverChoiceList has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TutorialBoxKt.TutorialBox (cyclomatic 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/tutorial/TutorialBox.kt:73— TutorialBoxKt.TutorialBox has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RecurrentExpenseDialogKt.RecurrentExpenseDialog (cyclomatic 19) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:77— RecurrentExpenseDialogKt.RecurrentExpenseDialog has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BudgetGraphChartDrawingKt.drawCoordinateSystem (cyclomatic 19) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:40— BudgetGraphChartDrawingKt.drawCoordinateSystem has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generate_audio.build_music (cyclomatic 19) promo/audio/generate_audio.py:275— generate_audio.build_music has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TopSheetKt.TopSheetLayout (cyclomatic 18) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TopSheet.kt:87— TopSheetKt.TopSheetLayout has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DetailedChartKt.DetailedChart (cyclomatic 18) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/DetailedChart.kt:66— DetailedChartKt.DetailedChart has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExpenseWidget.ExpenseWidgetContent (cyclomatic 18) app/src/main/java/com/serranoie/app/minus/presentation/widget/ExpenseWidget.kt:87— ExpenseWidget.ExpenseWidgetContent has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
NotificationScheduler.nextOccurrenceDateTime (cyclomatic 17) app/src/main/java/com/serranoie/app/minus/presentation/notification/NotificationScheduler.kt:342— NotificationScheduler.nextOccurrenceDateTime has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CategoryAnalyticsKt.CategoryAnalytics (cyclomatic 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/CategoryAnalytics.kt:62— CategoryAnalyticsKt.CategoryAnalytics has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HistoryCalculationsKt.calculateNextChargeDate (cyclomatic 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.kt:127— HistoryCalculationsKt.calculateNextChargeDate has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FinishDateSelectorKt.FinishDateSelector (cyclomatic 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/FinishDateSelector.kt:74— FinishDateSelectorKt.FinishDateSelector has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SwipeToDismissKt.SwipeToDismiss (cyclomatic 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SwipeToDismiss.kt:89— SwipeToDismissKt.SwipeToDismiss has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TextRowKt.TextRow (cyclomatic 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TextRow.kt:24— TextRowKt.TextRow has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TutorialBoxStateKt.markForTutorial (cyclomatic 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/tutorial/TutorialBoxState.kt:138— TutorialBoxStateKt.markForTutorial has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D12 · Dependency Hygiene· No Gemfile.lock committed by an application · ×1
No Gemfile.lock committed by an application — This repository declares 2 gem(s) across 1 Bundler manifest(s) and ships no application `.gemspec`, so it is an APPLICATION — but no `Gemfile.lock` is committed. Nothing records the versions a working build resolved to, so `bundle install` re-resolves against whatever rubygems.org serves today and two deploys of this commit are not guaranteed to be the same deploy. Run `bundle install` and commit the resulting `Gemfile.lock`. (A published GEM correctly omits its lock, which is why this is asked only of a repository that ships no .gemspec.)
BudgetPillKt.BudgetPill (cognitive 119) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:129— BudgetPillKt.BudgetPill has cognitive complexity 119 (threshold 15). Drivers by points: if/else 71 (91 pts), boolean chains 22, match/switch 2 (4 pts), loops 2 (nesting depth added 22). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AnalyticsKt.Analytics (cognitive 98) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:206— AnalyticsKt.Analytics has cognitive complexity 98 (threshold 15). Drivers by points: if/else 55 (77 pts), boolean chains 12, match/switch 4 (9 pts) (nesting depth added 27). 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.
EditorKt.EditingContent (cognitive 80) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:665— EditorKt.EditingContent has cognitive complexity 80 (threshold 15). Drivers by points: if/else 43 (65 pts), boolean chains 15 (nesting depth added 22). 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.
MainScreenContentKt.PhoneLayout (cognitive 71) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:628— MainScreenContentKt.PhoneLayout has cognitive complexity 71 (threshold 15). Drivers by points: if/else 40 (50 pts), boolean chains 16, loops 1 (3 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TransactionEditScreenKt.TransactionEditScreen (cognitive 64) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt:80— TransactionEditScreenKt.TransactionEditScreen has cognitive complexity 64 (threshold 15). Drivers by points: if/else 41 (52 pts), boolean chains 9, match/switch 2 (3 pts) (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TrendingGraphKt.BudgetGraph (cognitive 59) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingGraph.kt:428— TrendingGraphKt.BudgetGraph has cognitive complexity 59 (threshold 15). Drivers by points: if/else 38 (46 pts), boolean chains 12, match/switch 1 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EditableCategoryTagKt.EditableCategoryTag (cognitive 57) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt:98— EditableCategoryTagKt.EditableCategoryTag has cognitive complexity 57 (threshold 15). Drivers by points: if/else 37 (48 pts), boolean chains 9 (nesting depth added 11). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SwipeActionsKt.SwipeActions (cognitive 57) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SwipeActions.kt:93— SwipeActionsKt.SwipeActions has cognitive complexity 57 (threshold 15). Drivers by points: if/else 41 (51 pts), match/switch 4, boolean chains 2 (nesting depth added 10). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SwatchColorsKt.getSwatchColors (cognitive 55) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/schemes/SwatchColors.kt:21— SwatchColorsKt.getSwatchColors has cognitive complexity 55 (threshold 15). Drivers by points: if/else 36 (54 pts), match/switch 1 (nesting depth added 18). 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.
ColorSchemesKt.getAppColorScheme (cognitive 52) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/schemes/ColorSchemes.kt:8— ColorSchemesKt.getAppColorScheme has cognitive complexity 52 (threshold 15). Drivers by points: if/else 34 (51 pts), match/switch 1 (nesting depth added 17). 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.
EditorKt.Editor (cognitive 50) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:157— EditorKt.Editor has cognitive complexity 50 (threshold 15). Drivers by points: if/else 34 (49 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BudgetPeriodSheetKt.EditBudgetContent (cognitive 49) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:659— BudgetPeriodSheetKt.EditBudgetContent has cognitive complexity 49 (threshold 15). Drivers by points: if/else 28 (42 pts), boolean chains 5, match/switch 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExpenseItemKt.ExpenseItem (cognitive 46) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:66— ExpenseItemKt.ExpenseItem has cognitive complexity 46 (threshold 15). Drivers by points: if/else 24 (34 pts), boolean chains 6, match/switch 3 (6 pts) (nesting depth added 13). 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.
BudgetFormulaKt.buildBudgetFormula (cognitive 42) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/formula/BudgetFormula.kt:62— BudgetFormulaKt.buildBudgetFormula has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (37 pts), boolean chains 4, match/switch 1 (nesting depth added 16). 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.
BudgetPeriodManager.persistBudgetSettings (cognitive 39) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt:84— BudgetPeriodManager.persistBudgetSettings has cognitive complexity 39 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 11, match/switch 2 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UpcomingRecurrentItemRowKt.UpcomingRecurrentItemRow (cognitive 39) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:57— UpcomingRecurrentItemRowKt.UpcomingRecurrentItemRow has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 5, match/switch 2 (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.
BudgetPillMetricsKt.resolveExhaustedMessage (cognitive 37) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt:104— BudgetPillMetricsKt.resolveExhaustedMessage has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 9, match/switch 4 (7 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TotalBudgetCardKt.TotalBudgetCard (cognitive 35) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/TotalBudgetCard.kt:70— TotalBudgetCardKt.TotalBudgetCard has cognitive complexity 35 (threshold 15). Drivers by points: if/else 25 (28 pts), boolean chains 4, match/switch 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ExpenseItemExpandedContentKt.ExpenseItemExpandedContent (cognitive 34) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt:46— ExpenseItemExpandedContentKt.ExpenseItemExpandedContent has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23 (25 pts), boolean chains 7, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BudgetGraphChartDrawingKt.drawCoordinateSystem (cognitive 33) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/BudgetGraphChartDrawing.kt:40— BudgetGraphChartDrawingKt.drawCoordinateSystem has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 6, loops 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TutorialBoxKt.TutorialBox (cognitive 33) app/src/main/java/com/serranoie/app/minus/presentation/ui/tutorial/TutorialBox.kt:73— TutorialBoxKt.TutorialBox has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 7 (nesting depth added 13). 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.
generate_audio.build_music (cognitive 33) promo/audio/generate_audio.py:275— generate_audio.build_music has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 8 (11 pts), ternaries 4 (9 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecurrentExpenseDialogKt.RecurrentExpenseDialog (cognitive 32) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:77— RecurrentExpenseDialogKt.RecurrentExpenseDialog has cognitive complexity 32 (threshold 15). Drivers by points: if/else 28 (30 pts), boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NumpadKt.Numpad (cognitive 32) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:93— NumpadKt.Numpad has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 9, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ExpressionEvaluatorKt.evaluateExpression (cognitive 31) app/src/main/java/com/serranoie/app/minus/domain/calculator/ExpressionEvaluator.kt:9— ExpressionEvaluatorKt.evaluateExpression has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (21 pts), match/switch 2 (4 pts), boolean chains 3, loops 2, error handling 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BudgetStateCalculator.calculateBudgetState (cognitive 31) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:44— BudgetStateCalculator.calculateBudgetState has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (26 pts), boolean chains 4, match/switch 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BudgetTransactionHandler.applyTransaction (cognitive 30) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt:57— BudgetTransactionHandler.applyTransaction has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (17 pts), error handling 5 (7 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MainScreenContentKt.MainScreenNumpadSection (cognitive 29) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:1360— MainScreenContentKt.MainScreenNumpadSection has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 8, 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.
TutorialBoxStateKt.markForTutorial (cognitive 28) app/src/main/java/com/serranoie/app/minus/presentation/ui/tutorial/TutorialBoxState.kt:138— TutorialBoxStateKt.markForTutorial has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 4, loops 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ReceiptScannerKt.rememberReceiptScanner (cognitive 27) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/receipt/ReceiptScanner.kt:91— ReceiptScannerKt.rememberReceiptScanner has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23 (26 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MainScreenContentKt.MainScreenContent (cognitive 27) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:146— MainScreenContentKt.MainScreenContent has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16, boolean chains 7, match/switch 3 (4 pts) (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.
BudgetPillStatusLabelKt.StatusLabel (cognitive 27) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillStatusLabel.kt:74— BudgetPillStatusLabelKt.StatusLabel has cognitive complexity 27 (threshold 15). Drivers by points: if/else 19, boolean chains 5, match/switch 2 (3 pts) (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.
TextRowKt.TextRow (cognitive 26) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TextRow.kt:24— TextRowKt.TextRow has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LeftoverChoiceListKt.LeftoverChoiceList (cognitive 25) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/LeftoverChoiceList.kt:73— LeftoverChoiceListKt.LeftoverChoiceList has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (17 pts), match/switch 4 (5 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
FinishDateSelectorKt.FinishDateSelector (cognitive 23) app/src/main/java/com/serranoie/app/minus/presentation/ui/onboarding/FinishDateSelector.kt:74— FinishDateSelectorKt.FinishDateSelector has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 5 (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.
SettingsKt.Settings (cognitive 23) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/Settings.kt:147— SettingsKt.Settings has cognitive complexity 23 (threshold 15). Drivers by points: if/else 23. 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.
BudgetPillAmountTextKt.SegmentedAmountText (cognitive 23) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillAmountText.kt:45— BudgetPillAmountTextKt.SegmentedAmountText has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15, boolean chains 6, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HistoryCalculationsKt.calculateNextChargeDate (cognitive 22) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.kt:127— HistoryCalculationsKt.calculateNextChargeDate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, loops 2 (4 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TopSheetKt.TopSheetLayout (cognitive 22) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TopSheet.kt:87— TopSheetKt.TopSheetLayout has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3, loops 1 (2 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CategoriesChartCardKt.CategoriesChartCard (cognitive 22) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/CategoriesChartCard.kt:97— CategoriesChartCardKt.CategoriesChartCard has cognitive complexity 22 (threshold 15). Drivers by points: if/else 19, boolean chains 2, error handling 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CategoryAnalyticsKt.CategoryAnalytics (cognitive 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/CategoryAnalytics.kt:62— CategoryAnalyticsKt.CategoryAnalytics has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NewCategoryTagKt.NewCategoryTag (cognitive 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/NewCategoryTag.kt:63— NewCategoryTagKt.NewCategoryTag has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (20 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MinMaxSpentCardKt.MinMaxSpentCard (cognitive 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/MinMaxSpentCard.kt:70— MinMaxSpentCardKt.MinMaxSpentCard has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DetailedChartKt.DetailedChart (cognitive 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/DetailedChart.kt:66— DetailedChartKt.DetailedChart has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13, boolean chains 3, loops 2 (3 pts), match/switch 2 (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.
CalendarHeatmapKt.DayCell (cognitive 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/date/CalendarHeatmap.kt:338— CalendarHeatmapKt.DayCell has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15, boolean chains 4, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CamSolver.bisectToLimit (cognitive 21) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/hct/CamSolver.java:500— CamSolver.bisectToLimit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiCategoryChartKt.MultiCategoryChart (cognitive 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:193— MultiCategoryChartKt.MultiCategoryChart has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BudgetPillMetricsKt.calculateBudgetMetrics (cognitive 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPillMetrics.kt:29— BudgetPillMetricsKt.calculateBudgetMetrics has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8, match/switch 6 (7 pts), boolean chains 5 (nesting depth added 1). 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.
DonutChartKt.DonutChart (cognitive 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/DonutChart.kt:34— DonutChartKt.DonutChart has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NumpadKt.ActionButtonsColumn (cognitive 20) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:631— NumpadKt.ActionButtonsColumn has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ThemeKt.MinusTheme (cognitive 19) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/Theme.kt:275— ThemeKt.MinusTheme has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 4 (6 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HistoryScreenKt.History (cognitive 18) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:125— HistoryScreenKt.History has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HistoryScreenKt.HistoryListContent (cognitive 18) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:322— HistoryScreenKt.HistoryListContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 4 (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.
SpendsChartKt.SpendsChart (cognitive 18) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:47— SpendsChartKt.SpendsChart has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15 (17 pts), match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BudgetViewModel.triggerTestNotifications (cognitive 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:416— BudgetViewModel.triggerTestNotifications has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), error handling 4, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BudgetPeriodSheetKt.BudgetPeriodSheet (cognitive 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:159— BudgetPeriodSheetKt.BudgetPeriodSheet has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 2 (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.
BudgetPeriodSheetKt.ViewBudgetContent (cognitive 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:341— BudgetPeriodSheetKt.ViewBudgetContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NumpadKt.CompactHardwareLayout (cognitive 17) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/numpad/Numpad.kt:322— NumpadKt.CompactHardwareLayout has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HapticUtil.performCustomHaptic (cognitive 17) app/src/main/java/com/serranoie/app/minus/presentation/util/haptic/HapticUtils.kt:87— HapticUtil.performCustomHaptic has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 1 (2 pts) (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.
generate_audio.render_cue (cognitive 17) promo/audio/generate_audio.py:203— generate_audio.render_cue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BugReportFormKt.BugReportForm (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/bugreport/BugReportForm.kt:118— BugReportFormKt.BugReportForm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SavingsPreferencesEditorKt.SavingsPreferencesEditor (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/savings/SavingsPreferencesEditor.kt:82— SavingsPreferencesEditorKt.SavingsPreferencesEditor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SubscriptionsWeeklyCalendarKt.SubscriptionsWeeklyDayPill (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:289— SubscriptionsWeeklyCalendarKt.SubscriptionsWeeklyDayPill has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AverageSpendCardKt.AverageSpendCard (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/AverageSpendCard.kt:33— AverageSpendCardKt.AverageSpendCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SpendBudgetCardKt.drawWavyPattern (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/SpendBudgetCard.kt:62— SpendBudgetCardKt.drawWavyPattern has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateFormattingKt.prettyDate (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/util/font/format/DateFormatting.kt:139— DateFormattingKt.prettyDate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 5 (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.
CamSolver.findResultByJ (cognitive 16) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/hct/CamSolver.java:553— CamSolver.findResultByJ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (79 shared lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1073— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1073-1233 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1247-1402 — These two members are variants of one another: 79 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:56— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:56-126 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/FutureRecurrentSection.kt:60-141 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:57-155 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt:76-182 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (94 corresponding lines) · ×1
Edited copy of a member (94 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/Type.kt:167— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/Type.kt:167-260 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/Type.kt:263-356 — These two members are one piece of code written twice and then edited apart: 94 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 (73 corresponding lines) · ×1
Edited copy of a member (73 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:52— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:52-153 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:172-244 — These two members are one piece of code written twice and then edited apart: 73 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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:142— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:142-207 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:298-363 — These two members are one piece of code written twice and then edited apart: 66 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) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:445— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:445-482 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/SavingsPocketsCard.kt:489-531 — 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1222— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1222-1263 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1313-1358 — These two members are one piece of code written twice and then edited apart: 42 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 (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:121— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:121-163 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:99-141 — These two members are one piece of code written twice and then edited apart: 43 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 (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:511— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:511-559 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:288-331 — These two members are one piece of code written twice and then edited apart: 44 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:111— app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:111-138 | app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearMessageListener.kt:105-125 — These two members are one piece of code written twice and then edited apart: 21 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:190— app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:190-226 | app/src/main/java/com/serranoie/app/minus/presentation/widget/MonthHeatmapWidget.kt:171-216 — These two members are one piece of code written twice and then edited apart: 37 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) · ×1
Edited copy of a member (27 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:990— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:990-1016 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsEmptyState.kt:27-53 — 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 (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:151— app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:151-183 | app/src/main/java/com/serranoie/app/minus/presentation/widget/MonthHeatmapWidget.kt:125-160 — These two members are one piece of code written twice and then edited apart: 33 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:356— app/src/main/java/com/serranoie/app/minus/presentation/widget/HeatmapWidget.kt:356-393 | app/src/main/java/com/serranoie/app/minus/presentation/widget/MonthHeatmapWidget.kt:321-354 — These two members are one piece of code written twice and then edited apart: 34 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 (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:225— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:225-241 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:301-317 — These two members are one piece of code written twice and then edited apart: 17 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) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:383— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:383-407 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SavingsRecommendationCard.kt:444-475 — 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 copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1031— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1031-1059 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/RolloverDialog.kt:107-137 — These two members are one piece of code written twice and then edited apart: 29 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, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) wear/src/main/java/com/serranoie/app/wear/minus/sync/WearSyncManager.kt:25— wear/src/main/java/com/serranoie/app/wear/minus/sync/WearSyncManager.kt:25-52 | wear/src/main/java/com/serranoie/app/wear/minus/sync/WearSyncManager.kt:54-76 | wear/src/main/java/com/serranoie/app/wear/minus/sync/WearSyncManager.kt:78-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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 copies of one member (4 members, 23+ corresponding lines) · ×1
Edited copies of one member (4 members, 23+ corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:226— app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:226-248 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/CsvSyncGuideScreen.kt:269-291 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/FeatureLabScreen.kt:244-266 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/NotificationScanScreen.kt:214-236 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:253— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:253-276 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:352-377 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:235-258 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:263-286 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 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 4 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) app/src/main/java/com/serranoie/app/minus/presentation/widget/DaysCountdownWidget.kt:108— app/src/main/java/com/serranoie/app/minus/presentation/widget/DaysCountdownWidget.kt:108-120 | app/src/main/java/com/serranoie/app/minus/presentation/widget/ExpenseWidget.kt:279-291 — 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 copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:296— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:296-315 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:319-337 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt:269-287 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 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 (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TopSheet.kt:62— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TopSheet.kt:62-68 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/TopSheet.kt:71-77 — These two members are one piece of code written twice and then edited apart: 7 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 (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/util/ColorUtils.java:159— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/util/ColorUtils.java:159-168 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/harmonize/hct/CamSolver.java:333-342 — These two members are one piece of code written twice and then edited apart: 10 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 (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:42— app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:42-53 | app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearMessageListener.kt:48-56 — These two members are one piece of code written twice and then edited apart: 9 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 (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:781— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:781-784 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/SettingsViewModel.kt:430-433 — These two members are one piece of code written twice and then edited apart: 4 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 (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) app/src/main/java/com/serranoie/app/minus/domain/time/MidnightPeriodChecker.kt:394— app/src/main/java/com/serranoie/app/minus/domain/time/MidnightPeriodChecker.kt:394-400 | app/src/main/java/com/serranoie/app/minus/presentation/notification/MidnightPeriodTransitionReceiver.kt:104-108 — These two members are one piece of code written twice and then edited apart: 5 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.
Duplicated block (61 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:126— app/src/main/java/com/serranoie/app/minus/presentation/widget/BudgetOverviewWidget.kt:126-186 | app/src/main/java/com/serranoie/app/minus/presentation/widget/CompleteBudgetWidget.kt:185-245 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (50 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:77— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:77-126 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/FutureRecurrentSection.kt:92-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:77` 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 (3–50 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/DetailedChart.kt:99— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/DetailedChart.kt:99-101 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:75-124 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:201-250 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/SpendsChart.kt:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (48 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:374— app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:374-421 | app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:447-494 — 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.
Duplicated block (37–43 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:600— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:600-642 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:402-438 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Icon` names `androidx.compose.material3.Icon` in one and `androidx.wear.compose.material3.Icon` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:644` calls `HorizontalDivider`, `padding` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:440` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (33 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:88— app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:88-120 | app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogItemCard.kt:140-172 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/changelog/components/ChangelogBugFixItemCard.kt:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:989— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:989-1019 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:1035-1065 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:989` 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 (29 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:203— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:203-231 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:234-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryHourChart.kt:203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27–28 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:736— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:736-762 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:764-791 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:764` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:182— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:182-209 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt:160-187 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–27 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:250— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:250-274 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:307-333 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:250` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:55— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:55-78 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:175-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1109— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1109-1131 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1285-1307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:735— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:735-756 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:786-807 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:811-832 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:735` 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 (21–22 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:228— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:228-248 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:285-306 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (21 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1161— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1161-1181 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1313-1333 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1160` calls `padding` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1312` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–21 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:477— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:477-491 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:556-576 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryScreen.kt:477` 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 (20–21 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:179— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:179-198 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.kt:334-354 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:764— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:764-782 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:791-810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:791` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–20 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/CategoriesChartCard.kt:153— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/CategoriesChartCard.kt:153-172 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/RecurringItemVisuals.kt:47-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/CategoriesChartCard.kt:153` 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 (19 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:378— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:378-396 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:425-443 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:473-491 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:378` 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 (18 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/CsvSyncGuideScreen.kt:274— app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/CsvSyncGuideScreen.kt:274-291 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/FeatureLabScreen.kt:249-266 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/NotificationScanScreen.kt:219-236 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/features/CsvSyncGuideScreen.kt:274` 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 (16–18 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:544— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:544-559 | wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt:314-331 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt` and `wear/src/main/java/com/serranoie/app/wear/minus/presentation/theme/component/SettingsGroup.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:544` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:265— app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:265-281 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:318-334 | app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:495-511 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/appearance/AppearanceOptionsScreen.kt:265` 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 (11–17 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:566— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SettingsGroup.kt:566-576 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:61-77 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:181-197 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/PastPeriodsBottomSheet.kt:222— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/PastPeriodsBottomSheet.kt:222-237 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/PastPeriodsBottomSheet.kt:260-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/dialogs/PastPeriodsBottomSheet.kt:222` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–17 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingDailyGraph.kt:115— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingDailyGraph.kt:115-129 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/charts/DetailedChart.kt:180-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingDailyGraph.kt:115` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1248— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1248-1263 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1294-1309 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1343-1358 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1248` 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 (14–16 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1137— app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1137-1152 | app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1339-1352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:1137` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–16 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:362— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:362-377 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt:341-353 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–16 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/GraphCanvas.kt:62— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/GraphCanvas.kt:62-77 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/TrendingDailyGraph.kt:96-107 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12–15 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:31— app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:31-42 | app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetWidgetUpdater.kt:160-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.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.
Duplicated block (14–15 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt:218— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt:218-231 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/note/EditableNoteTag.kt:135-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/category/EditableCategoryTag.kt:218` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetBehaviourContent.kt:245— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetBehaviourContent.kt:245-257 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetPeriodSheet.kt:499-512 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/sheets/BudgetBehaviourContent.kt:245` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1279— app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1279-1291 | app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1325-1336 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.kt:1279` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 4) app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:74— app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:74-85 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/FutureRecurrentSection.kt:89-100 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:77-88 | app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt:97-108 — before extracting anything, compare `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt` and `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/CurrentPeriodRecurrentSection.kt:74` 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 (9–12 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:295— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:295-306 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:316-328 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:337-345 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.kt:295` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:123— app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:123-134 | app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearMessageListener.kt:113-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/wear/java/com/serranoie/app/minus/wearsync/PhoneWearListenerService.kt:123` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:734— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:734-744 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:759-769 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:785-795 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/pill/BudgetPill.kt:734` 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 (7–8 lines × 3) app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/Subscriptions.kt:223— app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/Subscriptions.kt:223-229 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/Subscriptions.kt:235-242 | app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/Subscriptions.kt:258-265 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/Subscriptions.kt:223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/GraphCanvas.kt:61— app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/GraphCanvas.kt:61-70 | app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/graphs/MultiCategoryChart.kt:207-213 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Off the main sequence: :island-sdk — :island-sdk: abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Duplication concentrated across 2 sibling directories (25 clone groups) promo/remotion-es/src/components/Phone.tsx:1— 25 of the duplicated blocks reported below have copies in at least two of the sibling directories remotion, remotion-es under promo/. That concentration is one structural fact, not 25 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 25 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (260 identical lines × 2 files) promo/remotion-es/src/components/Phone.tsx:1— promo/remotion-es/src/components/Phone.tsx:1 · promo/remotion/src/components/Phone.tsx:1 — these 2 files are line-for-line copies of one another — 260 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (177 identical lines × 2 files) promo/remotion-es/src/scenes/S05Pill.tsx:1— promo/remotion-es/src/scenes/S05Pill.tsx:1 · promo/remotion/src/scenes/S05Pill.tsx:1 — these 2 files are line-for-line copies of one another — 177 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (167 identical lines × 2 files) promo/remotion-es/src/scenes/S09Subs.tsx:1— promo/remotion-es/src/scenes/S09Subs.tsx:1 · promo/remotion/src/scenes/S09Subs.tsx:1 — these 2 files are line-for-line copies of one another — 167 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (147 identical lines × 2 files) promo/remotion-es/src/scenes/S06Sheet.tsx:1— promo/remotion-es/src/scenes/S06Sheet.tsx:1 · promo/remotion/src/scenes/S06Sheet.tsx:1 — these 2 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (144 identical lines × 2 files) promo/remotion-es/src/scenes/S10Analytics.tsx:1— promo/remotion-es/src/scenes/S10Analytics.tsx:1 · promo/remotion/src/scenes/S10Analytics.tsx:1 — these 2 files are line-for-line copies of one another — 144 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (103 identical lines × 2 files) promo/remotion-es/src/scenes/S07Split.tsx:1— promo/remotion-es/src/scenes/S07Split.tsx:1 · promo/remotion/src/scenes/S07Split.tsx:1 — these 2 files are line-for-line copies of one another — 103 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (86 identical lines × 2 files) promo/remotion-es/src/scenes/S04Question.tsx:1— promo/remotion-es/src/scenes/S04Question.tsx:1 · promo/remotion/src/scenes/S04Question.tsx:1 — these 2 files are line-for-line copies of one another — 86 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (83 identical lines × 2 files) promo/remotion-es/src/components/Icons.tsx:1— promo/remotion-es/src/components/Icons.tsx:1 · promo/remotion/src/components/Icons.tsx:1 — these 2 files are line-for-line copies of one another — 83 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (79 identical lines × 2 files) promo/remotion-es/src/scenes/S08Choice.tsx:1— promo/remotion-es/src/scenes/S08Choice.tsx:1 · promo/remotion/src/scenes/S08Choice.tsx:1 — these 2 files are line-for-line copies of one another — 79 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (75 identical lines × 2 files) promo/remotion-es/src/theme.ts:1— promo/remotion-es/src/theme.ts:1 · promo/remotion/src/theme.ts:1 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (64 identical lines × 2 files) promo/remotion-es/src/Promo.tsx:1— promo/remotion-es/src/Promo.tsx:1 · promo/remotion/src/Promo.tsx:1 — these 2 files are line-for-line copies of one another — 64 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (59 lines × 2 locations) promo/remotion-es/src/components/Logo.tsx:4— promo/remotion-es/src/components/Logo.tsx:4 · promo/remotion/src/components/Logo.tsx:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Wholesale file copy (58 identical lines × 2 files) promo/remotion-es/src/components/Cursor.tsx:1— promo/remotion-es/src/components/Cursor.tsx:1 · promo/remotion/src/components/Cursor.tsx:1 — these 2 files are line-for-line copies of one another — 58 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (56 identical lines × 2 files) promo/remotion-es/src/components/Kinetic.tsx:1— promo/remotion-es/src/components/Kinetic.tsx:1 · promo/remotion/src/components/Kinetic.tsx:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (54 identical lines × 2 files) promo/remotion-es/src/components/Pill.tsx:1— promo/remotion-es/src/components/Pill.tsx:1 · promo/remotion/src/components/Pill.tsx:1 — these 2 files are line-for-line copies of one another — 54 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (53 identical lines × 2 files) promo/remotion-es/src/components/Backgrounds.tsx:1— promo/remotion-es/src/components/Backgrounds.tsx:1 · promo/remotion/src/components/Backgrounds.tsx:1 — these 2 files are line-for-line copies of one another — 53 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (52 identical lines × 2 files) promo/remotion-es/src/anim.ts:1— promo/remotion-es/src/anim.ts:1 · promo/remotion/src/anim.ts:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (50 identical lines × 2 files) promo/remotion-es/src/scenes/S03Splash.tsx:1— promo/remotion-es/src/scenes/S03Splash.tsx:1 · promo/remotion/src/scenes/S03Splash.tsx:1 — these 2 files are line-for-line copies of one another — 50 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (35 lines × 2 locations) promo/remotion-es/src/scenes/S02Wordmark.tsx:13— promo/remotion-es/src/scenes/S02Wordmark.tsx:13 · promo/remotion/src/scenes/S02Wordmark.tsx:13 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (29 lines × 2 locations) promo/remotion-es/src/scenes/S11Outro.tsx:10— promo/remotion-es/src/scenes/S11Outro.tsx:10 · promo/remotion/src/scenes/S11Outro.tsx:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (22 lines × 2 locations) promo/remotion-es/src/components/SplashLogo.tsx:4— promo/remotion-es/src/components/SplashLogo.tsx:4 · promo/remotion/src/components/SplashLogo.tsx:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (17 lines × 2 locations) promo/remotion-es/src/scenes/S11Outro.tsx:44— promo/remotion-es/src/scenes/S11Outro.tsx:44 · promo/remotion/src/scenes/S11Outro.tsx:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (12 lines × 2 locations) promo/remotion-es/scripts/mux.mjs:5— promo/remotion-es/scripts/mux.mjs:5 · promo/remotion/scripts/mux.mjs:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (11 lines × 2 locations) promo/remotion-es/scripts/stills.mjs:5— promo/remotion-es/scripts/stills.mjs:5 · promo/remotion/scripts/stills.mjs:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (10 lines × 2 locations) promo/remotion-es/remotion.config.ts:3— promo/remotion-es/remotion.config.ts:3 · promo/remotion/remotion.config.ts:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
No test script — test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Swallowed exception (empty catch) island-sdk/src/main/java/com/sameerasw/island/sdk/compose/IslandSnapshot.kt:24— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Duplicated predicate promo/remotion-es/src/scenes/S05Pill.tsx:125— `Math.floor(f / 14) % 2 === 0 || typed < WORD.length` appears character-identically in 2 files — promo/remotion-es/src/scenes/S05Pill.tsx, promo/remotion/src/scenes/S05Pill.tsx. 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.
Duplicated predicate promo/remotion-es/src/scenes/S05Pill.tsx:129— `f >= m.type && f < m.type + WORD.length * 4` appears character-identically in 2 files — promo/remotion-es/src/scenes/S05Pill.tsx, promo/remotion/src/scenes/S05Pill.tsx. 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.
Duplicated predicate promo/remotion-es/src/components/Phone.tsx:276— `k === 'div' || k === 'mul' || k === 'plus' || k === 'minus'` appears character-identically in 2 files — promo/remotion-es/src/components/Phone.tsx, promo/remotion/src/components/Phone.tsx. 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.
Duplicated predicate promo/remotion-es/src/components/Phone.tsx:104— `k === 'dot' || k === 'eq' || k === 'div' || k === 'mul' || k === 'plus' || k === 'minus'` appears character-identically in 2 files — promo/remotion-es/src/components/Phone.tsx, promo/remotion/src/components/Phone.tsx. 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.
Duplicated predicate promo/remotion-es/src/scenes/S05Pill.tsx:179— `tagFor(m.clear1, m.cleared1) || tagFor(m.clear2, m.cleared2)` appears character-identically in 2 files — promo/remotion-es/src/scenes/S05Pill.tsx, promo/remotion/src/scenes/S05Pill.tsx. 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.
Duplicated predicate promo/remotion-es/src/scenes/S05Pill.tsx:179— `tagFor(m.swipe, m.calcOn) || tagFor(m.swipe2, m.calcOn2) || tagFor(m.swipe3, m.calcOn3)` appears character-identically in 2 files — promo/remotion-es/src/scenes/S05Pill.tsx, promo/remotion/src/scenes/S05Pill.tsx. 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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:69— `!endOfWeek.isBefore(periodStart) && !week.startDate.isAfter(periodEnd)` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:30— `currentPeriodId > 0L && transaction.periodId > 0L` appears character-identically in 3 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetWidgetUpdater.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt:110— `date.isAfter(today) && !date.isAfter(maxSelectableDate)` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/dialogs/RecurrentExpenseDialog.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/RecurrenceConfigSheet.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt:94— `day.isBefore(periodStart) || day.isAfter(periodEnd)` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsCalendarSection.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/subscriptions/SubscriptionsWeeklyCalendar.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/domain/calculator/RecurringExpenseCalculator.kt:41— `endDate != null && today.isAfter(endDate)` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/domain/calculator/RecurringExpenseCalculator.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryCalculations.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt:122— `index < transactions.size - 1 && transaction.id !in deletingTransactionIds` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/PastTransactionDateSections.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/history/sections/TransactionDateSections.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt:119— `input.startsWith("+") || input.startsWith("-")` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetTransactionHandler.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/editor/Editor.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:288— `it.amount > BigDecimal.ZERO && !it.isAdjustment` appears character-identically in 3 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/budget/MinMaxSpentCard.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:429— `it.amount > BigDecimal.ZERO && it.isAdjustment` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:528— `it.isCredit && !it.isDeleted && !it.isCreditPaid` appears character-identically in 3 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/history/HistoryViewModel.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/domain/time/MidnightPeriodChecker.kt:230— `it.periodId == periodId && !it.isDeleted` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/domain/time/MidnightPeriodChecker.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:94— `sharedTransitionScope != null && animatedVisibilityScope != null` appears character-identically in 3 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:140— `transaction.amount > java.math.BigDecimal.ZERO && transaction.isAdjustment` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/SwipeableExpenseItem.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt:214— `transaction.isCredit && creditCardCutoffDay != null` appears character-identically in 3 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItem.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/ExpenseItemExpandedContent.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/expense/UpcomingRecurrentItemRow.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:34— `txDate.isBefore(settings.startDate) || txDate.isAfter(periodEnd)` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetWidgetUpdater.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.
Duplicated predicate app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt:37— `txDate.isEqual(settings.startDate) && currentPeriodStartedAtMillis > 0L` appears character-identically in 2 files — app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetStateCalculator.kt, app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetWidgetUpdater.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.
Fat interface: TransactionDao (24 abstract methods) app/src/main/java/com/serranoie/app/minus/data/local/dao/TransactionDao.kt:13— `TransactionDao` declares 24 abstract methods: `getAllTransactions`, `getTransactionsForDateRange`, `getTransactionsForDay`, `getTotalSpentForDay`, `getTotalSpentForPeriod`, `insert`, `insertOrReplace`, `insertIgnore`, `insertAllOrReplace`, `update`, `delete`, `deleteById`, `deleteAll`, `getByPocketId`, `deleteOneTimeByPeriodId`, `getTransactionById`, `countDistinctPeriods`, `hasTransactionsInPeriod`, `existsByClientGeneratedId`, `getByClientGeneratedId`, `getRecentTransactions`, `markCreditAsPaidInRange`, `markAllCreditAsPaid`, `markTransactionAsPaid`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: BudgetRepository (44 abstract methods) app/src/main/java/com/serranoie/app/minus/data/repository/BudgetRepository.kt:15— `BudgetRepository` declares 44 abstract methods: `getTransactions`, `getQueuedTransactions`, `getTransactionsForPeriod`, `addTransaction`, `addTransactions`, `addQueuedTransaction`, `addTransactionIfAbsent`, `addPocketWithdrawal`, `addPocketDeposit`, `updateTransaction`, `assignQueuedTransactionsToPeriod`, `upsertTransactions`, `replaceAllTransactions`, `existsTransactionByClientGeneratedId`, `getRecentTransactions`, `deleteTransaction`, `getSpentForDate`, `getSpentForPeriod`, `getBudgetSettings`, `saveBudgetSettings`, `getBudgetSettingsSync`, `getTransactionById`, `getActiveCategories`, `getAllCategories`, `findOrCreateCategory`, `createCategory`, `hideCategory`, `incrementCategoryUsage`, `setCategoryLimit`, `getPeriodCount`, `markCreditTransactionsAsPaid`, `markAllCreditTransactionsAsPaid`, `markTransactionAsPaid`, `getPaidRecurrentOccurrences`, `markRecurrentOccurrencePaid`, `getPaidOccurrenceDatesFor`, `getArchivedBudgets`, `upsertArchivedBudgets`, `replaceAllArchivedBudgets`, `archiveCurrentPeriod`, and 4 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: SettingsRepository (64 abstract methods) app/src/main/java/com/serranoie/app/minus/data/repository/SettingsRepository.kt:18— `SettingsRepository` declares 64 abstract methods: `observeSettings`, `observeCurrentPeriodRollover`, `observeCurrentPeriodBoundary`, `getCurrentPeriodId`, `getSettings`, `setOnboardingCompleted`, `setEarlyFinishActive`, `setPeriodEndAlreadyHandled`, `setCurrentPeriod`, `setCurrentPeriodRollover`, `setPendingRollover`, `clearPendingRollover`, `setNotificationTime`, `setRecurrentNotificationTime`, `setThemeMode`, `setTypographyMode`, `setContrastMode`, `setAppColorScheme`, `setLanguage`, `setDynamicColorEnabled`, `setRoundedFontEnabled`, `setAmoledEnabled`, `setCreditQuickToggleEnabled`, `setShowPastTransactions`, `setCategoryPickerDirectPopupEnabled`, `setCategoryGridModeEnabled`, `setExtraNoteEnabled`, `setReserveUpcomingChargesEnabled`, `setNewCategoryTagEnabled`, `setNotificationScanEnabled`, `setNotificationScanPackages`, `toggleNotificationScanPackage`, `setTutorialBoxCompleted`, `setAnalyticsTutorialCompleted`, `setHistoryTutorialCompleted`, `setReceiptScanHintShown`, `setSavingsReminderEnabled`, `setAnalyticsSpendsTutorialCompleted`, `setPeriodMappingMode`, `setFirstLaunchTutorialStage`, and 24 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Silent fallback default in catch app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt:1045— `PhoneLayout` swallows every exception into `0f` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/serranoie/app/minus/presentation/ui/theme/component/SwipeActions.kt:143— `SwipeActions` swallows every exception into `0f` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/wear/java/com/serranoie/app/minus/wearsync/WearExpenseIngestor.kt:101— `readLedger` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
M2 · Architecture documentation· Architecture diagram out of date · ×2
Architecture diagram out of date PROJECT_OVERVIEW.md:31— `PROJECT_OVERVIEW.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `island-sdk`, `sync-contract`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Architecture diagram out of date fastlane/CHANGELOG_GENERATION.md:15— `fastlane/CHANGELOG_GENERATION.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `island-sdk`, `sync-contract`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
No ADRs found wear/build.gradle.kts:5— 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 `wear/build.gradle.kts` makes this repository a deployable product (line 5).
D21 · Naming Consistency· `onExportCSV` spells `CSV` where 12 names in the project spell it `Csv` · ×1
`onExportCSV` spells `CSV` where 12 names in the project spell it `Csv` app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/Analytics.kt:186— 12 of 13 names in project app spell the token `Csv` (12 of 13; unit: names in project app containing `Csv`). Peers: com.serranoie.app.minus.data.csv.MinusCsvContract (app/src/main/java/com/serranoie/app/minus/data/csv/MinusCsvContract.kt:3); com.serranoie.app.minus.data.csv.MinusCsvExporter (app/src/main/java/com/serranoie/app/minus/data/csv/MinusCsvExporter.kt:15); com.serranoie.app.minus.data.csv.MinusCsvParser (app/src/main/java/com/serranoie/app/minus/data/csv/MinusCsvParser.kt:21); com.serranoie.app.minus.data.csv.MinusCsvService (app/src/main/java/com/serranoie/app/minus/data/csv/MinusCsvService.kt:13); SettingsKt.Settings(onExportCsv) (app/src/main/java/com/serranoie/app/minus/presentation/ui/settings/Settings.kt:147). Rename to `onExportCsv`. [rule N6]
D21 · Naming Consistency· `performUIHaptic` spells `UI` where 40 names in the project spell it `Ui` · ×1
`performUIHaptic` spells `UI` where 40 names in the project spell it `Ui` app/src/main/java/com/serranoie/app/minus/presentation/util/haptic/HapticUtils.kt:19— 40 of 41 names in project app spell the token `Ui` (40 of 41; unit: names in project app containing `Ui`). Peers: com.serranoie.app.minus.presentation.ui.analytics.AnalyticsUiState (app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:45); com.serranoie.app.minus.presentation.ui.analytics.AnalyticsUiEffect (app/src/main/java/com/serranoie/app/minus/presentation/ui/analytics/AnalyticsViewModel.kt:62); com.serranoie.app.minus.presentation.ui.budget.BudgetUiState (app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetUiState.kt:15); BudgetViewModel.observeBudgetUiState (app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:157); BudgetViewModelKt.toBudgetUiError (app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetViewModel.kt:997). Rename to `performUiHaptic`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion app/build.gradle.kts:1— `app` (70503 LoC, 951 module-visible types across 85 directories) overshoots its size bounds. 1 of 7 build unit(s) (Gradle, npm) overshoot their size bounds, lowering Project Cohesion to 7.1/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.
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.
No SAST REDACTED:4— 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 5 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.
No dependency-update automation promo/remotion-es/package.json:14— `promo/remotion-es/package.json` 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`.
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.)
Off the main sequence: :sync-contract — :sync-contract: abstractness 0.00, instability 0.00, distance 1.00 — 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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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) — `app/src/main/java/com/serranoie/app/minus/domain/receipt/ReceiptVocabulary.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/budget/BudgetPeriodManager.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/history/edit/TransactionEditScreen.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/ui/home/MainScreenContent.kt`, `app/src/main/java/com/serranoie/app/minus/presentation/util/font/format/DateFormatting.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
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.
Run 01a1ea2e-72e4-749d-b264-9c9742756c2d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 27 · Warnings: 484 · Recommendations: 55 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 15:44 UTC.
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.