Public report of BeamMW/android-wallet, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 16 November 2026, 21:06 UTC · Survey ID cd_7ec0897c7f4442de8db5d47e7f966281
BeamMW/android-wallet
Measured 16 November 2026, 21:05 UTC, at code version 4a8d927
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: 34,261 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 24.9
Findings by how serious they are
19 critical247 serious158 minor
12 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
16 November 2026, 21:05 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 ▸
41of 41 dimensions measured by tools.
413of 424 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.
41dimensions across 5 lenses, read from 34,261 lines of product code in 2 projects.
BeamMW/android-wallet falls short of our standard for production because the project has no automated tests and ten passwords or keys sit in the current code. It scores 40.9 out of 100 and is rated Weak, and 18 of its 19 critical findings are security problems.
Production Readiness, at 24.9, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 10.2 points. Replacing the ten exposed passwords or keys and switching the old ones off would lift Production Readiness itself, worth about 14.5 points. Raising Production Readiness to 70 would lift the score to about 55.0.
Ten passwords or keys in the code and five in the code's history are open to anyone who can read the repository. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key and pinning each tool to an exact version would close both risks. The project with no automated tests needs automated tests, starting with the business logic.
The product code is 34,261 lines, about €29,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 Production Readiness rose from 24.9 to 70, the lowest score rated Strong, the score would rise from 40.9 to about 55.0.
Code composition: what the lines of code are
Product code 100%
Rebuild cost: about €29,000 · Estimate
Cost to rebuild
€9,700 to €49,000, for 161 to 512 hours of work, about 0.2 person-years for one engineer
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 41. 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: 34,261 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
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.
Raises the score by about 10.2 points · Low effort · ADR Quality
2
Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (3), REDACTED.
Raises the score by about 14.5 points · Medium effort · REDACTED Scanning
3
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 16.3 points · High effort · Code Coverage
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €29,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 24.9 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 10.2 points for low effort, because it clears the 1 ADR Quality findings. 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 6.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 3,061 lines over the last 90 days, which is about 12,414 lines a year. At that pace, the extra work comes to an estimated 1 to 6.2 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: 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.
203 modules, with 385 dependencies between them. 9 loops run through 30 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 163 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.
core.entities.dto uses core.entities, so a change to core.entities can break core.entities.dto, while a change to core.entities.dto can't break core.entities.
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.
5→8 core.helpers.TrashManager uses core.entitiespart of a loop✕
Connections
2 pairs of types, where a type in core.helpers.TrashManager uses a type in core.entities.
core.helpers.TrashManager uses core.entities, so a change to core.entities can break core.helpers.TrashManager, while a change to core.helpers.TrashManager can't break core.entities.
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.
6→13 screens.confirm uses base_screenpart of a loop✕
Connections
12 pairs of types, where a type in screens.confirm uses a type in base_screen.
core.helpers uses core.helpers.LocaleHelper, so a change to core.helpers.LocaleHelper can break core.helpers, while a change to core.helpers can't break core.helpers.LocaleHelper.
Position
Below the diagonal: core.helpers uses a module listed above it, which is the healthy direction.
core.helpers uses core.helpers.TrashManager, so a change to core.helpers.TrashManager can break core.helpers, while a change to core.helpers can't break core.helpers.TrashManager.
Position
Below the diagonal: core.helpers uses a module listed above it, which is the healthy direction.
7→8 core.helpers uses core.entitiespart of a loop✕
Connections
4 pairs of types, where a type in core.helpers uses a type in core.entities.
core.entities uses core.entities.dto, so a change to core.entities.dto can break core.entities, while a change to core.entities can't break core.entities.dto.
Position
Below the diagonal: core.entities uses a module listed above it, which is the healthy direction.
screens.settings.SettingsContract uses core.helpers.LocaleHelper, so a change to core.helpers.LocaleHelper can break screens.settings.SettingsContract, while a change to screens.settings.SettingsContract can't break core.helpers.LocaleHelper.
Position
Below the diagonal: screens.settings.SettingsContract uses a module listed above it, which is the healthy direction.
screens.settings.SettingsContract uses core.entities, so a change to core.entities can break screens.settings.SettingsContract, while a change to screens.settings.SettingsContract can't break core.entities.
Position
Below the diagonal: screens.settings.SettingsContract uses a module listed above it, which is the healthy direction.
9→11 screens.settings.SettingsContract uses screens.settingspart of a loop✕
Connections
1 pair of types, where a type in screens.settings.SettingsContract uses a type in screens.settings.
screens.settings.SettingsContract uses screens.settings, so a change to screens.settings can break screens.settings.SettingsContract, while a change to screens.settings.SettingsContract can't break screens.settings.
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.
9→13 screens.settings.SettingsContract uses base_screenpart of a loop✕
Connections
3 pairs of types, where a type in screens.settings.SettingsContract uses a type in base_screen.
screens.settings.SettingsContract uses base_screen, so a change to base_screen can break screens.settings.SettingsContract, while a change to screens.settings.SettingsContract can't break base_screen.
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.
screens.settings uses core.helpers.LocaleHelper, so a change to core.helpers.LocaleHelper can break screens.settings, while a change to screens.settings can't break core.helpers.LocaleHelper.
Position
Below the diagonal: screens.settings uses a module listed above it, which is the healthy direction.
screens.settings uses core.entities, so a change to core.entities can break screens.settings, while a change to screens.settings can't break core.entities.
Position
Below the diagonal: screens.settings uses a module listed above it, which is the healthy direction.
screens.settings uses screens.settings.SettingsContract, so a change to screens.settings.SettingsContract can break screens.settings, while a change to screens.settings can't break screens.settings.SettingsContract.
Position
Below the diagonal: screens.settings uses a module listed above it, which is the healthy direction.
11→13 screens.settings uses base_screenpart of a loop✕
Connections
6 pairs of types, where a type in screens.settings uses a type in base_screen.
core.views uses core.views.PasswordStrengthView, so a change to core.views.PasswordStrengthView can break core.views, while a change to core.views can't break core.views.PasswordStrengthView.
Position
Below the diagonal: core.views uses a module listed above it, which is the healthy direction.
screens.address_details uses core.entities, so a change to core.entities can break screens.address_details, while a change to screens.address_details can't break core.entities.
Position
Below the diagonal: screens.address_details uses a module listed above it, which is the healthy direction.
screens.address_details uses screens.wallet, so a change to screens.wallet can break screens.address_details, while a change to screens.address_details can't break screens.wallet.
Position
Below the diagonal: screens.address_details uses a module listed above it, which is the healthy direction.
screens.address_details uses base_screen, so a change to base_screen can break screens.address_details, while a change to screens.address_details can't break base_screen.
Position
Below the diagonal: screens.address_details uses a module listed above it, which is the healthy direction.
screens.address_edit.EditAddressContract uses core.helpers, so a change to core.helpers can break screens.address_edit.EditAddressContract, while a change to screens.address_edit.EditAddressContract can't break core.helpers.
Position
Below the diagonal: screens.address_edit.EditAddressContract uses a module listed above it, which is the healthy direction.
screens.address_edit.EditAddressContract uses core.entities, so a change to core.entities can break screens.address_edit.EditAddressContract, while a change to screens.address_edit.EditAddressContract can't break core.entities.
Position
Below the diagonal: screens.address_edit.EditAddressContract uses a module listed above it, which is the healthy direction.
screens.address_edit.EditAddressContract uses base_screen, so a change to base_screen can break screens.address_edit.EditAddressContract, while a change to screens.address_edit.EditAddressContract can't break base_screen.
Position
Below the diagonal: screens.address_edit.EditAddressContract uses a module listed above it, which is the healthy direction.
screens.addresses.AddressesContract uses core.entities, so a change to core.entities can break screens.addresses.AddressesContract, while a change to screens.addresses.AddressesContract can't break core.entities.
Position
Below the diagonal: screens.addresses.AddressesContract uses a module listed above it, which is the healthy direction.
screens.addresses.AddressesContract uses base_screen, so a change to base_screen can break screens.addresses.AddressesContract, while a change to screens.addresses.AddressesContract can't break base_screen.
Position
Below the diagonal: screens.addresses.AddressesContract uses a module listed above it, which is the healthy direction.
17→35 screens.addresses.AddressesContract uses screens.addressespart of a loop✕
Connections
1 pair of types, where a type in screens.addresses.AddressesContract uses a type in screens.addresses.
screens.addresses.AddressesContract uses screens.addresses, so a change to screens.addresses can break screens.addresses.AddressesContract, while a change to screens.addresses.AddressesContract can't break screens.addresses.
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.
screens.app_activity uses core.entities, so a change to core.entities can break screens.app_activity, while a change to screens.app_activity can't break core.entities.
Position
Below the diagonal: screens.app_activity uses a module listed above it, which is the healthy direction.
screens.app_activity uses screens.wallet, so a change to screens.wallet can break screens.app_activity, while a change to screens.app_activity can't break screens.wallet.
Position
Below the diagonal: screens.app_activity uses a module listed above it, which is the healthy direction.
screens.app_activity uses base_screen, so a change to base_screen can break screens.app_activity, while a change to screens.app_activity can't break base_screen.
Position
Below the diagonal: screens.app_activity uses a module listed above it, which is the healthy direction.
screens.apps.confirm uses core.entities.dto, so a change to core.entities.dto can break screens.apps.confirm, while a change to screens.apps.confirm can't break core.entities.dto.
Position
Below the diagonal: screens.apps.confirm uses a module listed above it, which is the healthy direction.
screens.apps.confirm uses core.entities, so a change to core.entities can break screens.apps.confirm, while a change to screens.apps.confirm can't break core.entities.
Position
Below the diagonal: screens.apps.confirm uses a module listed above it, which is the healthy direction.
screens.apps.confirm uses base_screen, so a change to base_screen can break screens.apps.confirm, while a change to screens.apps.confirm can't break base_screen.
Position
Below the diagonal: screens.apps.confirm uses a module listed above it, which is the healthy direction.
screens.apps.detail.AppDetailContract uses core.entities.dto, so a change to core.entities.dto can break screens.apps.detail.AppDetailContract, while a change to screens.apps.detail.AppDetailContract can't break core.entities.dto.
Position
Below the diagonal: screens.apps.detail.AppDetailContract uses a module listed above it, which is the healthy direction.
screens.apps.detail.AppDetailContract uses core.entities, so a change to core.entities can break screens.apps.detail.AppDetailContract, while a change to screens.apps.detail.AppDetailContract can't break core.entities.
Position
Below the diagonal: screens.apps.detail.AppDetailContract uses a module listed above it, which is the healthy direction.
screens.apps.detail.AppDetailContract uses base_screen, so a change to base_screen can break screens.apps.detail.AppDetailContract, while a change to screens.apps.detail.AppDetailContract can't break base_screen.
Position
Below the diagonal: screens.apps.detail.AppDetailContract uses a module listed above it, which is the healthy direction.
screens.asset_detail uses core.entities, so a change to core.entities can break screens.asset_detail, while a change to screens.asset_detail can't break core.entities.
Position
Below the diagonal: screens.asset_detail uses a module listed above it, which is the healthy direction.
screens.asset_detail uses screens.wallet, so a change to screens.wallet can break screens.asset_detail, while a change to screens.asset_detail can't break screens.wallet.
Position
Below the diagonal: screens.asset_detail uses a module listed above it, which is the healthy direction.
screens.asset_detail uses base_screen, so a change to base_screen can break screens.asset_detail, while a change to screens.asset_detail can't break base_screen.
Position
Below the diagonal: screens.asset_detail uses a module listed above it, which is the healthy direction.
screens.asset_info uses core.entities, so a change to core.entities can break screens.asset_info, while a change to screens.asset_info can't break core.entities.
Position
Below the diagonal: screens.asset_info uses a module listed above it, which is the healthy direction.
screens.asset_info uses base_screen, so a change to base_screen can break screens.asset_info, while a change to screens.asset_info can't break base_screen.
Position
Below the diagonal: screens.asset_info uses a module listed above it, which is the healthy direction.
screens.assets_list.AssetsListContract uses core.entities, so a change to core.entities can break screens.assets_list.AssetsListContract, while a change to screens.assets_list.AssetsListContract can't break core.entities.
Position
Below the diagonal: screens.assets_list.AssetsListContract uses a module listed above it, which is the healthy direction.
screens.assets_list.AssetsListContract uses base_screen, so a change to base_screen can break screens.assets_list.AssetsListContract, while a change to screens.assets_list.AssetsListContract can't break base_screen.
Position
Below the diagonal: screens.assets_list.AssetsListContract uses a module listed above it, which is the healthy direction.
23→37 screens.assets_list.AssetsListContract uses screens.assets_listpart of a loop✕
Connections
1 pair of types, where a type in screens.assets_list.AssetsListContract uses a type in screens.assets_list.
screens.assets_list.AssetsListContract uses screens.assets_list, so a change to screens.assets_list can break screens.assets_list.AssetsListContract, while a change to screens.assets_list.AssetsListContract can't break screens.assets_list.
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.
screens.change_address.ChangeAddressContract uses core.helpers.TrashManager, so a change to core.helpers.TrashManager can break screens.change_address.ChangeAddressContract, while a change to screens.change_address.ChangeAddressContract can't break core.helpers.TrashManager.
Position
Below the diagonal: screens.change_address.ChangeAddressContract uses a module listed above it, which is the healthy direction.
screens.change_address.ChangeAddressContract uses core.entities, so a change to core.entities can break screens.change_address.ChangeAddressContract, while a change to screens.change_address.ChangeAddressContract can't break core.entities.
Position
Below the diagonal: screens.change_address.ChangeAddressContract uses a module listed above it, which is the healthy direction.
screens.change_address.ChangeAddressContract uses base_screen, so a change to base_screen can break screens.change_address.ChangeAddressContract, while a change to screens.change_address.ChangeAddressContract can't break base_screen.
Position
Below the diagonal: screens.change_address.ChangeAddressContract uses a module listed above it, which is the healthy direction.
screens.choose_currency uses core.entities, so a change to core.entities can break screens.choose_currency, while a change to screens.choose_currency can't break core.entities.
Position
Below the diagonal: screens.choose_currency uses a module listed above it, which is the healthy direction.
screens.choose_currency uses base_screen, so a change to base_screen can break screens.choose_currency, while a change to screens.choose_currency can't break base_screen.
Position
Below the diagonal: screens.choose_currency uses a module listed above it, which is the healthy direction.
screens.create_password uses core.views.PasswordStrengthView, so a change to core.views.PasswordStrengthView can break screens.create_password, while a change to screens.create_password can't break core.views.PasswordStrengthView.
Position
Below the diagonal: screens.create_password uses a module listed above it, which is the healthy direction.
screens.create_password uses core.helpers, so a change to core.helpers can break screens.create_password, while a change to screens.create_password can't break core.helpers.
Position
Below the diagonal: screens.create_password uses a module listed above it, which is the healthy direction.
screens.create_password uses base_screen, so a change to base_screen can break screens.create_password, while a change to screens.create_password can't break base_screen.
Position
Below the diagonal: screens.create_password uses a module listed above it, which is the healthy direction.
screens.max_privacy_details uses core.entities, so a change to core.entities can break screens.max_privacy_details, while a change to screens.max_privacy_details can't break core.entities.
Position
Below the diagonal: screens.max_privacy_details uses a module listed above it, which is the healthy direction.
screens.max_privacy_details uses base_screen, so a change to base_screen can break screens.max_privacy_details, while a change to screens.max_privacy_details can't break base_screen.
Position
Below the diagonal: screens.max_privacy_details uses a module listed above it, which is the healthy direction.
screens.notifications uses core.entities, so a change to core.entities can break screens.notifications, while a change to screens.notifications can't break core.entities.
Position
Below the diagonal: screens.notifications uses a module listed above it, which is the healthy direction.
screens.notifications uses base_screen, so a change to base_screen can break screens.notifications, while a change to screens.notifications can't break base_screen.
Position
Below the diagonal: screens.notifications uses a module listed above it, which is the healthy direction.
screens.receive uses core.watchers, so a change to core.watchers can break screens.receive, while a change to screens.receive can't break core.watchers.
Position
Below the diagonal: screens.receive uses a module listed above it, which is the healthy direction.
screens.receive uses core.entities, so a change to core.entities can break screens.receive, while a change to screens.receive can't break core.entities.
Position
Below the diagonal: screens.receive uses a module listed above it, which is the healthy direction.
screens.transaction_details uses core.entities, so a change to core.entities can break screens.transaction_details, while a change to screens.transaction_details can't break core.entities.
Position
Below the diagonal: screens.transaction_details uses a module listed above it, which is the healthy direction.
screens.transaction_details uses base_screen, so a change to base_screen can break screens.transaction_details, while a change to screens.transaction_details can't break base_screen.
Position
Below the diagonal: screens.transaction_details uses a module listed above it, which is the healthy direction.
screens.transactions uses core.entities, so a change to core.entities can break screens.transactions, while a change to screens.transactions can't break core.entities.
Position
Below the diagonal: screens.transactions uses a module listed above it, which is the healthy direction.
screens.transactions uses screens.wallet, so a change to screens.wallet can break screens.transactions, while a change to screens.transactions can't break screens.wallet.
Position
Below the diagonal: screens.transactions uses a module listed above it, which is the healthy direction.
screens.transactions uses base_screen, so a change to base_screen can break screens.transactions, while a change to screens.transactions can't break base_screen.
Position
Below the diagonal: screens.transactions uses a module listed above it, which is the healthy direction.
screens.welcome_screen.welcome_progress.WelcomeProgressContract uses core.helpers, so a change to core.helpers can break screens.welcome_screen.welcome_progress.WelcomeProgressContract, while a change to screens.welcome_screen.welcome_progress.WelcomeProgressContract can't break core.helpers.
Position
Below the diagonal: screens.welcome_screen.welcome_progress.WelcomeProgressContract uses a module listed above it, which is the healthy direction.
screens.welcome_screen.welcome_progress.WelcomeProgressContract uses core.entities, so a change to core.entities can break screens.welcome_screen.welcome_progress.WelcomeProgressContract, while a change to screens.welcome_screen.welcome_progress.WelcomeProgressContract can't break core.entities.
Position
Below the diagonal: screens.welcome_screen.welcome_progress.WelcomeProgressContract uses a module listed above it, which is the healthy direction.
screens.welcome_screen.welcome_progress.WelcomeProgressContract uses base_screen, so a change to base_screen can break screens.welcome_screen.welcome_progress.WelcomeProgressContract, while a change to screens.welcome_screen.welcome_progress.WelcomeProgressContract can't break base_screen.
Position
Below the diagonal: screens.welcome_screen.welcome_progress.WelcomeProgressContract uses a module listed above it, which is the healthy direction.
33→38 screens.welcome_screen.welcome_progress.WelcomeProgressContract uses screens.welcome_screen.welcome_progresspart of a loop✕
Connections
1 pair of types, where a type in screens.welcome_screen.welcome_progress.WelcomeProgressContract uses a type in screens.welcome_screen.welcome_progress.
screens.welcome_screen.welcome_progress.WelcomeProgressContract uses screens.welcome_screen.welcome_progress, so a change to screens.welcome_screen.welcome_progress can break screens.welcome_screen.welcome_progress.WelcomeProgressContract, while a change to screens.welcome_screen.welcome_progress.WelcomeProgressContract can't break screens.welcome_screen.welcome_progress.
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.
screens.address_edit uses core.helpers, so a change to core.helpers can break screens.address_edit, while a change to screens.address_edit can't break core.helpers.
Position
Below the diagonal: screens.address_edit uses a module listed above it, which is the healthy direction.
screens.address_edit uses core.entities, so a change to core.entities can break screens.address_edit, while a change to screens.address_edit can't break core.entities.
Position
Below the diagonal: screens.address_edit uses a module listed above it, which is the healthy direction.
screens.address_edit uses base_screen, so a change to base_screen can break screens.address_edit, while a change to screens.address_edit can't break base_screen.
Position
Below the diagonal: screens.address_edit uses a module listed above it, which is the healthy direction.
screens.address_edit uses screens.address_edit.EditAddressContract, so a change to screens.address_edit.EditAddressContract can break screens.address_edit, while a change to screens.address_edit can't break screens.address_edit.EditAddressContract.
Position
Below the diagonal: screens.address_edit uses a module listed above it, which is the healthy direction.
screens.addresses uses core.entities, so a change to core.entities can break screens.addresses, while a change to screens.addresses can't break core.entities.
Position
Below the diagonal: screens.addresses uses a module listed above it, which is the healthy direction.
screens.addresses uses base_screen, so a change to base_screen can break screens.addresses, while a change to screens.addresses can't break base_screen.
Position
Below the diagonal: screens.addresses uses a module listed above it, which is the healthy direction.
screens.addresses uses screens.addresses.AddressesContract, so a change to screens.addresses.AddressesContract can break screens.addresses, while a change to screens.addresses can't break screens.addresses.AddressesContract.
Position
Below the diagonal: screens.addresses uses a module listed above it, which is the healthy direction.
screens.apps.detail uses core.entities.dto, so a change to core.entities.dto can break screens.apps.detail, while a change to screens.apps.detail can't break core.entities.dto.
Position
Below the diagonal: screens.apps.detail uses a module listed above it, which is the healthy direction.
screens.apps.detail uses core.entities, so a change to core.entities can break screens.apps.detail, while a change to screens.apps.detail can't break core.entities.
Position
Below the diagonal: screens.apps.detail uses a module listed above it, which is the healthy direction.
screens.apps.detail uses base_screen, so a change to base_screen can break screens.apps.detail, while a change to screens.apps.detail can't break base_screen.
Position
Below the diagonal: screens.apps.detail uses a module listed above it, which is the healthy direction.
screens.apps.detail uses screens.apps.detail.AppDetailContract, so a change to screens.apps.detail.AppDetailContract can break screens.apps.detail, while a change to screens.apps.detail can't break screens.apps.detail.AppDetailContract.
Position
Below the diagonal: screens.apps.detail uses a module listed above it, which is the healthy direction.
screens.assets_list uses core.entities, so a change to core.entities can break screens.assets_list, while a change to screens.assets_list can't break core.entities.
Position
Below the diagonal: screens.assets_list uses a module listed above it, which is the healthy direction.
screens.assets_list uses screens.wallet, so a change to screens.wallet can break screens.assets_list, while a change to screens.assets_list can't break screens.wallet.
Position
Below the diagonal: screens.assets_list uses a module listed above it, which is the healthy direction.
screens.assets_list uses base_screen, so a change to base_screen can break screens.assets_list, while a change to screens.assets_list can't break base_screen.
Position
Below the diagonal: screens.assets_list uses a module listed above it, which is the healthy direction.
screens.assets_list uses screens.assets_list.AssetsListContract, so a change to screens.assets_list.AssetsListContract can break screens.assets_list, while a change to screens.assets_list can't break screens.assets_list.AssetsListContract.
Position
Below the diagonal: screens.assets_list uses a module listed above it, which is the healthy direction.
screens.welcome_screen.welcome_progress uses core.helpers, so a change to core.helpers can break screens.welcome_screen.welcome_progress, while a change to screens.welcome_screen.welcome_progress can't break core.helpers.
Position
Below the diagonal: screens.welcome_screen.welcome_progress uses a module listed above it, which is the healthy direction.
screens.welcome_screen.welcome_progress uses core.entities, so a change to core.entities can break screens.welcome_screen.welcome_progress, while a change to screens.welcome_screen.welcome_progress can't break core.entities.
Position
Below the diagonal: screens.welcome_screen.welcome_progress uses a module listed above it, which is the healthy direction.
screens.welcome_screen.welcome_progress uses base_screen, so a change to base_screen can break screens.welcome_screen.welcome_progress, while a change to screens.welcome_screen.welcome_progress can't break base_screen.
Position
Below the diagonal: screens.welcome_screen.welcome_progress uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in screens.welcome_screen.welcome_progress uses a type in screens.welcome_screen.welcome_progress.WelcomeProgressContract.
screens.welcome_screen.welcome_progress uses screens.welcome_screen.welcome_progress.WelcomeProgressContract, so a change to screens.welcome_screen.welcome_progress.WelcomeProgressContract can break screens.welcome_screen.welcome_progress, while a change to screens.welcome_screen.welcome_progress can't break screens.welcome_screen.welcome_progress.WelcomeProgressContract.
Position
Below the diagonal: screens.welcome_screen.welcome_progress uses a module listed above it, which is the healthy direction.
screens.change_address uses core.helpers.TrashManager, so a change to core.helpers.TrashManager can break screens.change_address, while a change to screens.change_address can't break core.helpers.TrashManager.
Position
Below the diagonal: screens.change_address uses a module listed above it, which is the healthy direction.
screens.change_address uses core.entities, so a change to core.entities can break screens.change_address, while a change to screens.change_address can't break core.entities.
Position
Below the diagonal: screens.change_address uses a module listed above it, which is the healthy direction.
screens.change_address uses base_screen, so a change to base_screen can break screens.change_address, while a change to screens.change_address can't break base_screen.
Position
Below the diagonal: screens.change_address uses a module listed above it, which is the healthy direction.
screens.change_address uses screens.change_address.ChangeAddressContract, so a change to screens.change_address.ChangeAddressContract can break screens.change_address, while a change to screens.change_address can't break screens.change_address.ChangeAddressContract.
Position
Below the diagonal: screens.change_address uses a module listed above it, which is the healthy direction.
screens.change_address uses screens.addresses, so a change to screens.addresses can break screens.change_address, while a change to screens.change_address can't break screens.addresses.
Position
Below the diagonal: screens.change_address uses a module listed above it, which is the healthy direction.
screens.send uses screens.addresses, so a change to screens.addresses can break screens.send, while a change to screens.send can't break screens.addresses.
Position
Below the diagonal: screens.send uses a module listed above it, which is the healthy direction.
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
A07:2025 — Authentication Failures
16
High / Critical
A05:2025 — Injection
5
High / Critical
A03:2025 — Software Supply Chain Failures
5
Medium
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (3), REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.
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.
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.
Code Duplication: Edited copy of a member (18 corresponding lines)
REDACTED
6.4
Mixed
Static Analysis (SAST): Medium: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 19
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 — 247
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 — 158
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
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 41 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 — 41 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, 413 of 424 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.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 213 artifact(s) across its subprojects (75 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D19 Documentation Quality — 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 ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D26 Project Cohesion — 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` (34261 LoC, 848 module-visible types across 62 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
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/mw/beam/beamwallet/base_screen/BaseRepository.kt`, `app/src/main/java/com/mw/beam/beamwallet/core/helpers/LocaleHelper.kt`, `app/src/main/java/com/mw/beam/beamwallet/core/watchers/InputFilterMinMax.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: lugin.VMPluginFactory.createPlugin(VMPluginFactory.java:57)
at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:39)
... 140 more
FAILURE: Build failed with an exception.…; runtime evidence skipped (launch chosen because app/build.gradle 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.
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 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 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.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
+ 14 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with AppManager.subscribeToUpdates (cyclomatic 73). — Refactoring it lifts Cyclomatic Complexity from 6.8 to about 7.0/10.
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.
+ 42 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 NotificationItem.<init> (cognitive 128), AppManager.subscribeToUpdates (cognitive 127), SettingsFragment.addItems (cognitive 102). — 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 5.8 to about 6.5/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.9 / 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 13 TooManyMethods finding(s) in God Classes — start with SendFragment.kt, SettingsFragment.kt, AppManager.kt. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 6 MethodTooLong finding(s) in God Classes — start with AppManager.kt, SettingsFragment.kt, NotificationItem.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 ClassTooLong finding(s) in God Classes — start with SettingsFragment.kt, SendFragment.kt, AppManager.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.
69 duplicated block group(s) detected. 7.4 % of the production lines (2,546 of 34,261) are in a reported copy. A further 41 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 57 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SettingsFragment.kt (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 7 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with BaseRepository.kt, AddressFragment.kt, AssetDetailFragment.kt. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with NodeFragment.kt, ReceiveFragment.kt, WelcomeProgressFragment.kt. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
2 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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.
Resolve the 19 Low cohesion finding(s) in Cohesion (LCOM4) — start with SettingsFragment.kt, SendFragment.kt, SettingsPresenter.kt. — One of this dimension's main actionable groups (19 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
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.
Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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 19 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 25 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with SettingsFragment.kt, TransactionDetailsFragment.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.4 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt. Counted over 80 of the 372 production source files in this repository: 226 are under the ~2,400-byte size floor this dimension measures over, and the remaining 66 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
6 deducted task-comment markers across 34261 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.
Resolve the 6 TodoComment finding(s) in Explicit Debt — start with WelcomeProgressFragment.kt, SendPresenter.kt, ReceivePresenter.kt. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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. — 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: 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.
45 % of calls cross a namespace and 5 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. 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: REDACTED 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.
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
5 finding(s): 0 critical, 3 high, 2 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (lines 160–161, line 162, line 163, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
No action in Static Analysis (SAST) — all 3 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 (3 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 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.
121 of 146 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/java/com/mw/beam/beamwallet/core/listeners/WalletListener.kt. Counted over 146 of the 372 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×2app/src/main/java/com/mw/beam/beamwallet/core/listeners/WalletListener.kt:1
Concentrated knowledge decay
What to do
Resolve the 119 Orphaned file finding(s) in Knowledge Freshness — start with TransactionsFragment.kt, TransactionsAdapter.kt, REDACTED. — One of this dimension's main actionable groups (119 recommendation-level).
Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with WalletListener.kt, NodeFragment.kt. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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 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 1 platform declaration(s) and 46 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 · 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 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.
`MvpView` declares 22 abstract methods: `showKeyboard`, `hideKeyboard`, `showSnackBar`, `showAlert`, `dismissAlert`, `copyToClipboard`, `showToast`, `initPresenter`, `initToolbar`, `configStatus`, `getToolbarTitle`, `shareText`, `addListeners`, `clearListeners`, `onHideKeyboard`, `onShowKeyboard`, `openExternalLink`, `registerKeyboardStateListener`, `unregisterKeyboardStateListener`, `vibrate`, `logOut`, `dismissSnackBar`. 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/mw/beam/beamwallet/base_screen/MvpView.kt:28
`View` declares 21 abstract methods: `init`, `initAddress`, `getComment`, `showQR`, `shareToken`, `copyToken`, `close`, `getAssetId`, `getAmountFromArguments`, `getAmount`, `getTxComment`, `setAmount`, `handleExpandAmount`, `handleExpandComment`, `handleExpandAdvanced`, `getLifecycleOwner`, `getWalletAddressFromArguments`, `showSaveAddressDialog`, `showSaveChangesDialog`, `showShowToken`, `updateTokens`. 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/mw/beam/beamwallet/screens/receive/ReceiveContract.kt:27
`View` declares 52 abstract methods: `getAmountText`, `getAmount`, `getFee`, `isOffline`, `getComment`, `getToken`, `updateUI`, `hasErrors`, `hasAmountError`, `configOutgoingAddress`, `clearErrors`, `clearToken`, `init`, `updateMaxPrivacyCount`, `refreshAddressType`, `clearAddressError`, `showCantSendToExpiredError`, `showCantPasteError`, `showNotBeamAddressError`, `setAddress`, `setAmount`, `setComment`, `setFee`, `scanQR`, `updateAvailable`, `isAmountErrorShown`, `isPermissionGranted`, `showPermissionRequiredAlert`, `showActivatePrivacyModeDialog`, `configPrivacyStatus`, `createOptionsMenu`, `showConfirmTransaction`, `getAddressFromArguments`, `getAmountFromArguments`, `showChangeAddressFragment`, `updateFeeTransactionVisibility`, `getLifecycleOwner`, `getCommentOutgoingAddress`, `handleExpandEditAddress`, `handleExpandAdvanced`, and 12 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/mw/beam/beamwallet/screens/send/SendContract.kt:35
`Presenter` declares 26 abstract methods: `onNext`, `onMaxPrivacy`, `onTokenChanged`, `onAmountChanged`, `onFeeChanged`, `requestFee`, `onAmountUnfocused`, `onScannedQR`, `onScanQrPressed`, `onRequestPermissionsResult`, `onChangePrivacyModePressed`, `showTokenFragmentPressed`, `onPrivacyModeActivated`, `onCreateOptionsMenu`, `onCancelDialog`, `onSendAllPressed`, `onAdvancedPressed`, `onEditAddressPressed`, `onChangeAddressPressed`, `onExpirePeriodChanged`, `onLabelAddressChanged`, `onAddressChanged`, `onLongPressFee`, `onEnterFee`, `onSelectAddress`, `onPaste`. 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/mw/beam/beamwallet/screens/send/SendContract.kt:91
`View` declares 19 abstract methods: `getAddress`, `getOutgoingAddress`, `getAmount`, `getFee`, `getChange`, `getShieldedInputsFee`, `getComment`, `getAddressType`, `getRemaining`, `getIsOffline`, `getAssetId`, `init`, `configureContact`, `configureOutAddress`, `configUtxoInfo`, `showSaveAddressFragment`, `delaySend`, `showWallet`, `showConfirmDialog`. 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/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationContract.kt:27
`View` declares 52 abstract methods: `onNeedAddedViews`, `mode`, `setRunOnRandomNode`, `setMobileNodeEnabled`, `setRunOnBackground`, `sendMailWithLogs`, `setLanguage`, `setConfirmations`, `changePass`, `showLockScreenSettingsDialog`, `showConfirmationsSettingsDialog`, `showFingerprintSettings`, `getContext`, `closeDialog`, `showMaxPrivacySettingsDialog`, `updateLockScreenValue`, `updateMaxPrivacyValue`, `updateConfirmTransactionValue`, `showConfirmPasswordDialog`, `showNodeAddressDialog`, `showInvalidNodeAddressError`, `clearInvalidNodeAddressError`, `showClearDataDialog`, `setAllowOpenExternalLinkValue`, `navigateToLanguage`, `navigateToCurrency`, `navigateToOwnerKeyVerification`, `navigateToPaymentProof`, `showClearDataAlert`, `setLogSettings`, `setCurrencySettings`, `showLogsDialog`, `navigateToSeed`, `navigateToSeedVerification`, `showReceiveFaucet`, `showExportDialog`, `showExportSaveDialog`, `exportSave`, `exportShare`, `showImportDialog`, and 12 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/mw/beam/beamwallet/screens/settings/SettingsContract.kt:33
`Presenter` declares 42 abstract methods: `onReportProblem`, `onChangePass`, `onShowLockScreenSettings`, `onChangeLockSettings`, `onDialogClosePressed`, `onChangeConfirmTransactionSettings`, `onChangeFingerprintSettings`, `onChangeRunOnRandomNode`, `onChangeRunOnBackground`, `onChangeAllowOpenExternalLink`, `onNodeAddressPressed`, `onChangeNodeAddress`, `onClearDataPressed`, `onDialogClearDataPressed`, `onConfirmClearDataPressed`, `onSaveNodeAddress`, `onLanguagePressed`, `onShowOwnerKey`, `onChangeLogSettings`, `onLogsPressed`, `onSeedPressed`, `onShowMaxPrivacySettings`, `onSeedVerificationPressed`, `onReceiveFaucet`, `onProofPressed`, `onExportPressed`, `onExportWithExclude`, `onExportSave`, `onRescanPressed`, `onExportShare`, `omImportPressed`, `onRemoveWalletPressed`, `onConfirmRemoveWallet`, `onCurrencyPressed`, `onChangeAllowNews`, `onChangeAllowTransactionStatus`, `onChangeAllowWalletUpdates`, `onChangeAllowAddressExpiration`, `onChangeMaxPrivacySettings`, `onEnableMobileNode`, and 2 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/mw/beam/beamwallet/screens/settings/SettingsContract.kt:88
`Repository` declares 32 abstract methods: `getLockScreenValue`, `saveLockSettings`, `saveConfirmTransactionSettings`, `saveEnableFingerprintSettings`, `shouldConfirmTransaction`, `isFingerPrintEnabled`, `isAllowOpenExternalLink`, `isAllowBackgroundMode`, `setAllowOpenExternalLink`, `setCurrencySettings`, `setNodeAddress`, `getSavedNodeAddress`, `setRunOnRandomNode`, `setRunOnBackground`, `getCurrentNodeAddress`, `deleteAddress`, `deleteTransaction`, `getCurrentLanguage`, `saveLogSettings`, `getLogSettings`, `getDataFile`, `getCurrencySettings`, `isAllowWalletUpdates`, `isAllowTransactions`, `isAllowNews`, `isAllowAddressExpiration`, `setAllowWalletUpdates`, `setAllowTransactions`, `setAllowNews`, `setAllowAddressExpiration`, `setMobileNodeEnabled`, `getConfirmations`. 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/mw/beam/beamwallet/screens/settings/SettingsContract.kt:133
`View` declares 23 abstract methods: `getTransactionId`, `init`, `updateAddresses`, `updatePaymentProof`, `configMenuItems`, `finishScreen`, `updateUtxos`, `showCopiedAlert`, `showPaymentProof`, `showOpenLinkAlert`, `showSendFragment`, `showSaveContact`, `showReceiveFragment`, `showDeleteSnackBar`, `convertViewIntoBitmap`, `shareTransactionDetails`, `handleExpandDetails`, `handleExpandUtxos`, `handleExpandProof`, `showCancelAlert`, `showDeleteAlert`, `copyDetails`, `showOpenAssetIdLinkAlert`. 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/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsContract.kt:34
`Presenter` declares 17 abstract methods: `onMenuCreate`, `onCancelTransaction`, `onDeleteTransaction`, `onShowPaymentProof`, `onCopyPaymentProof`, `onOpenInBlockExplorerPressed`, `onOpenLinkPressed`, `onRepeatTransaction`, `onSharePressed`, `onExpandDetailedPressed`, `onExpandUtxosPressed`, `onExpandProofPressed`, `onSaveContact`, `onCancelTransactionConfirm`, `onDeleteTransactionsPressed`, `onCopyDetailsPressed`, `onOpenAssetIdPressed`. 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/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsContract.kt:60
`View` declares 18 abstract methods: `init`, `configWalletStatus`, `configTransactions`, `showTransactionDetails`, `showReceiveScreen`, `showSendScreen`, `showActivatePrivacyModeDialog`, `configPrivacyStatus`, `createOptionsMenu`, `closeDrawer`, `clearAllNotification`, `showAllTransactions`, `showAllAssets`, `selectWalletMenu`, `showFaucet`, `showSecure`, `showReceiveFaucet`, `showSeedScreen`. 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/mw/beam/beamwallet/screens/wallet/WalletContract.kt:36
`View` declares 17 abstract methods: `init`, `updateProgress`, `getMode`, `getIsTrustedRestore`, `getPassword`, `getSeed`, `showWallet`, `showNoInternetMessage`, `showIncorrectNodeMessage`, `showCancelRestoreAlert`, `showCancelCreateAlert`, `showFailedRestoreAlert`, `showFailedDownloadRestoreFileAlert`, `getLifecycleOwner`, `navigateToCreateFragment`, `changeCancelButtonVisibility`, `close`. 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/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressContract.kt:35
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.
The root README is 59 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
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.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record 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.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
`build.gradle` 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`. — build.gradle:39
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 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.
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 method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. 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 (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?
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 (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. (×9) — app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsPresenter.kt:327, app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:238, app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:120, …
`catch (ex: 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/mw/beam/beamwallet/screens/send/SendFragment.kt:231
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. — app/src/main/java/com/mw/beam/beamwallet/core/helpers/FingerprintManager.kt:133
`catch (e: java.lang.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/mw/beam/beamwallet/base_screen/BaseRepository.kt:89
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
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 — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
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: lugin.VMPluginFactory.createPlugin(VMPluginFactory.java:57)
at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:39)
... 140 more
FAILURE: Build failed with an exception.…; runtime evidence skipped (launch chosen because app/build.gradle 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.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Not scored — a Gradle build resolved 213 artifact(s) across its subprojects (75 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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.
D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 2 folder(s) declared by build.gradle were not judged for an overview, an example or the map.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 4 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (12 value object(s))
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
M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's JVM source (1 module(s), 369 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (JUnit (with Kotest or MockK on Kotlin)), and run it in CI so the gap cannot reopen.
Low cohesion: SettingsFragment (LCOM4 36) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:95— SettingsFragment's methods fall into 36 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 36 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SendFragment (LCOM4 15) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:86— SendFragment's methods fall into 15 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 15 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SettingsPresenter (LCOM4 13) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsPresenter.kt:36— SettingsPresenter's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ScreenDelegate (LCOM4 10) app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:50— ScreenDelegate's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ReceiveFragment (LCOM4 10) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:62— ReceiveFragment's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WelcomeConfirmFragment (LCOM4 9) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_confirm/WelcomeConfirmFragment.kt:48— WelcomeConfirmFragment's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DoubleAuthorizationFragment (LCOM4 8) REDACTED:40— DoubleAuthorizationFragment's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ScanQrActivity (LCOM4 8) app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrActivity.kt:53— ScanQrActivity's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WelcomeOpenFragment (LCOM4 8) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenFragment.kt:54— WelcomeOpenFragment's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WelcomeProgressFragment (LCOM4 8) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:53— WelcomeProgressFragment's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WalletFragment (LCOM4 7) app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:46— WalletFragment's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BaseFragment (LCOM4 6) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseFragment.kt:51— BaseFragment's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NotificationsFragment (LCOM4 6) app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:39— NotificationsFragment's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BaseActivity (LCOM4 5) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:50— BaseActivity's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PasswordConfirmDialog (LCOM4 5) app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmDialog.kt:25— PasswordConfirmDialog's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BaseRepository (LCOM4 4) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt:34— BaseRepository's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: App (LCOM4 4) app/src/main/java/com/mw/beam/beamwallet/core/App.kt:60— App's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MaxPrivacyDetailFragment (LCOM4 4) app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailFragment.kt:61— MaxPrivacyDetailFragment's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RestoreTrustedNodeFragment (LCOM4 4) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/restore_trusted_node/RestoreTrustedNodeFragment.kt:18— RestoreTrustedNodeFragment's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
TooManyMethods: SendFragment app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:86— TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SettingsFragment app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:95— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. Most of these members implement SettingsContract.View (51 of 73 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: AppManager app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:27— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SettingsPresenter app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsPresenter.kt:36— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. Most of these members implement SettingsContract.Presenter (42 of 53 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: WalletListener app/src/main/java/com/mw/beam/beamwallet/core/listeners/WalletListener.kt:41— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SendPresenter app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:41— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: AppActivity app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:74— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BaseActivity app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:50— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: TransactionDetailsFragment app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:55— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: BaseFragment app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseFragment.kt:51— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ReceiveFragment app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:62— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WelcomeProgressFragment app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:53— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SettingsRepository app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsRepository.kt:33— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. Most of these members implement SettingsContract.Repository (32 of 32 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.
Swallowed exception (caught, then discarded) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsPresenter.kt:327— `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/mw/beam/beamwallet/screens/send/SendFragment.kt:231— `catch (ex: 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/mw/beam/beamwallet/screens/send/SendFragment.kt:238— `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/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:120— `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/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:147— `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/mw/beam/beamwallet/screens/qr/ScanQrActivity.kt:133— `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/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressFragment.kt:74— `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/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:380— `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/mw/beam/beamwallet/core/helpers/LocaleHelper.kt:130— `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/mw/beam/beamwallet/base_screen/BaseRepository.kt:72— `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/mw/beam/beamwallet/base_screen/BaseRepository.kt:89— `catch (e: java.lang.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.
Duplicated block (8 lines × 2) REDACTED:361— REDACTED:361-368 | REDACTED:290-297 — 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 `REDACTED:361` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) REDACTED:184— REDACTED:184-191 | REDACTED:244-251 — 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 `REDACTED:184` 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) REDACTED:202— REDACTED:202-209 | REDACTED:258-265 — 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 `REDACTED:202` 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/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:80— app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:80-87 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:180-187 — 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 (8 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1182— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1182-1189 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1210-1217 — 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/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1182` 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 (8 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:265— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:265-272 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:349-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.
Duplicated block (8 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:592— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:592-599 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1024-1031 — 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/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:54— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:54-61 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxosPagerAdapter.kt:44-51 — 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 (8 lines × 2) REDACTED:225— REDACTED:225-233 | app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmDialog.kt:232-239 — 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 lines × 2) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt:126— app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt:126-137 | app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt:140-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. 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/mw/beam/beamwallet/screens/address_details/AddressFragment.kt:196— app/src/main/java/com/mw/beam/beamwallet/screens/address_details/AddressFragment.kt:196-207 | app/src/main/java/com/mw/beam/beamwallet/screens/address_edit/EditAddressFragment.kt:204-215 — 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/mw/beam/beamwallet/screens/address_details/AddressFragment.kt:196` 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 (12 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:59— app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:59-70 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:60-71 — before extracting anything, compare `app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt` and `app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:59` 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/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:169— app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:169-180 | app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailFragment.kt:133-144 — 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/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:169` 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 (12 lines × 2) REDACTED:247— REDACTED:247-258 | REDACTED:261-272 — 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 `REDACTED:247` 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 (12 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:503— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:503-514 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:520-531 — 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/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:503` 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 (12 lines × 2) REDACTED:109— REDACTED:109-120 | REDACTED:141-152 — 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 `REDACTED:109` 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.
TodoComment app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:412— //TODO decide what should be by default (arguments == null), when all modes will be available — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:522— // view?.requestFocusToAmount() TODO: ?? CHECK — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:298— // TODO: replace with generateToken(type, amount, assetId, newAddress) + deleteAddressByToken() — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:125— //TODO: token! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/java/com/mw/beam/beamwallet/screens/create_password/PasswordRepository.kt:53— //TODO move synchronization to progress screen (already done) when progress for create flow will be needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/src/main/java/com/mw/beam/beamwallet/core/helpers/PreferencesManager.kt:33— //TODO should we throw some custom exception here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: AppManager.subscribeToUpdates app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:941— MethodTooLong — subscribeToUpdates runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× 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: SettingsFragment.addItems app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:449— MethodTooLong — addItems runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: NotificationItem.<init> app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:38— MethodTooLong — <init> runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: TransactionsAdapter.onBindViewHolder app/src/main/java/com/mw/beam/beamwallet/screens/wallet/TransactionsAdapter.kt:128— MethodTooLong — onBindViewHolder runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: TransactionDetailsFragment.configGeneralTransactionInfo app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:217— MethodTooLong — configGeneralTransactionInfo runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: SendFragment.addListeners app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:460— MethodTooLong — addListeners 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.
ClassTooLong: SettingsFragment app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:95— ClassTooLong — 943 significant lines (blank, comment-only and punctuation-only lines excluded), 73 methods. The bar is 400 significant lines; this is 543 over it, 2.36× 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: SendFragment app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:86— ClassTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 516 over it, 2.29× 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: AppManager app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:27— ClassTooLong — 750 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 400 significant lines; this is 350 over it, 1.88× 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: AppActivity app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:74— ClassTooLong — 447 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 47 over it, 1.12× 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: SendPresenter app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:41— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 20 over it, 1.05× 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.
Duplicated block (9 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:330— app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:330-338 | app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:341-349 — 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/mw/beam/beamwallet/screens/node/NodeFragment.kt:330` 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/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:243— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:243-251 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:672-680 — 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/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:243` 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/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:258— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:258-266 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:273-281 — 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/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:286— app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:286-294 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:546-554 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1524— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1524-1532 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:258-266 — 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.
FileTooLong: settings/SettingsFragment.kt app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt— FileTooLong — 1014 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: SettingsFragment (95-1607). The bar is 500 significant lines; this is 514 over it, 2.03× 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: send/SendFragment.kt app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt— FileTooLong — 977 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: SendFragment (86-1563). The bar is 500 significant lines; this is 477 over it, 1.95× 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: core/AppManager.kt app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt— FileTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: AppManager (27-1342). The bar is 500 significant lines; this is 273 over it, 1.55× 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: app_activity/AppActivity.kt app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt— FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: AppActivity (74-793). The bar is 500 significant lines; this is 1 over it, 1.00× 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.
Duplicated block (6 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesAdapter.kt:99— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesAdapter.kt:99-104 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxosAdapter.kt:94-99 — 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 (6 lines × 2) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseBottomSheetDialogFragment.kt:117— app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseBottomSheetDialogFragment.kt:117-122 | app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseDialogFragment.kt:147-152 — 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/mw/beam/beamwallet/screens/language/LanguageFragment.kt:42— app/src/main/java/com/mw/beam/beamwallet/screens/language/LanguageFragment.kt:42-47 | app/src/main/java/com/mw/beam/beamwallet/screens/notifications/newversion/NewVersionFragment.kt:39-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:405— app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:405-410 | app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:609-614 — 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/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:405` 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/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:212— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:212-216 | app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:162-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/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:212` 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/mw/beam/beamwallet/screens/address_details/AddressFragment.kt:168— app/src/main/java/com/mw/beam/beamwallet/screens/address_details/AddressFragment.kt:168-172 | app/src/main/java/com/mw/beam/beamwallet/screens/address_edit/EditAddressFragment.kt:188-192 — 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 (5 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:180— app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:180-184 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:143-147 — before extracting anything, compare `app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt` and `app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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.
Duplicated block (5 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_create/WelcomeCreateFragment.kt:65— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_create/WelcomeCreateFragment.kt:65-69 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:311-315 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:872— app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:872-893 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:368-383 — 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/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:499— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:499-514 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:516-531 — 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/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:127— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:127-142 | app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:167-182 — 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 (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:690— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:690-701 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/TransactionsAdapter.kt:391-400 — 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.
Edited copy of a member (10 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:131— app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:131-140 | app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:151-160 — 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.
Edited copy of a member (10 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:85— app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:85-97 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:104-113 — 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 (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) REDACTED:384— REDACTED:384-390 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_confirm/WelcomeConfirmFragment.kt:262-268 — 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.
Edited copy of a member (7 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrActivity.kt:97— app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrActivity.kt:97-103 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:864-870 — 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.
Edited copy of a member (7 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/address_details/AddressPresenter.kt:90— app/src/main/java/com/mw/beam/beamwallet/screens/address_details/AddressPresenter.kt:90-96 | app/src/main/java/com/mw/beam/beamwallet/screens/address_edit/EditAddressPresenter.kt:72-78 — 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.
Duplicated block (10 lines × 2) app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:84— app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:84-93 | app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:96-105 — 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/mw/beam/beamwallet/core/entities/NotificationItem.kt:84` 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/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:68— app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:68-77 | app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:95-104 — 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/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:68` 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/mw/beam/beamwallet/screens/save_address/SaveAddressFragment.kt:75— app/src/main/java/com/mw/beam/beamwallet/screens/save_address/SaveAddressFragment.kt:75-84 | app/src/main/java/com/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationFragment.kt:127-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 3) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:279— app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:279-287 | app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:290-298 | app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:301-309 — 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/mw/beam/beamwallet/screens/node/NodeFragment.kt:279` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:289` calls `showAlert`, `getString` and `app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:311` 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 × 3) app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt:33— app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt:33-41 | app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogRepository.kt:31-39 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsRepository.kt:81-89 — before extracting anything, compare `app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt` and `app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogRepository.kt` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt:33` 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 × 3) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:255— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:255-263 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:270-278 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:291-299 — 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 (7 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/wallet/AssetsAdapter.kt:85— app/src/main/java/com/mw/beam/beamwallet/screens/wallet/AssetsAdapter.kt:85-91 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/AssetsAdapter.kt:96-102 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/wallet/AssetsAdapter.kt:84` calls `lockedSum` and `app/src/main/java/com/mw/beam/beamwallet/screens/wallet/AssetsAdapter.kt:95` 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 (7 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/add_contact/AddContactFragment.kt:108— app/src/main/java/com/mw/beam/beamwallet/screens/add_contact/AddContactFragment.kt:108-114 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:957-963 — 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 (7 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesLockableTabLayout.kt:13— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesLockableTabLayout.kt:13-19 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsLockableTabLayout.kt:12-18 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `mode` to `AddressesFragment.Mode` in one and `TransactionsFragment.Mode` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Hotspot: app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:449— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in SettingsFragment.addItems at line 449. 2 of those changes were fix/bug commits, 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-06-05..2026-09-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-05 15:20:43 +02:00' --until='2026-09-03 15:20:43 +02:00' --full-history --no-merges -- app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:217— app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TransactionDetailsFragment.configGeneralTransactionInfo at line 217. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-05..2026-09-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-05 15:20:43 +02:00' --until='2026-09-03 15:20:43 +02:00' --full-history --no-merges -- app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×2
Edited copy of a member (43 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1476— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1476-1521 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:213-255 — 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.
Edited copy of a member (43 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:322— app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:322-364 | app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:375-423 — 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 (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:425— app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:425-445 | app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:463-480 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrActivity.kt:148— app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrActivity.kt:148-166 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:845-862 — These two members are one piece of code written twice and then edited apart: 18 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) · ×2
Edited copy of a member (17 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:162— app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:162-178 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:125-141 — 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.
Edited copy of a member (17 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenPresenter.kt:62— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenPresenter.kt:62-78 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenPresenter.kt:123-139 — 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 (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailPresenter.kt:72— app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailPresenter.kt:72-81 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListPresenter.kt:95-103 — 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.
Edited copy of a member (9 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrPresenter.kt:34— app/src/main/java/com/mw/beam/beamwallet/screens/qr/ScanQrPresenter.kt:34-42 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:487-497 — 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) · ×2
Edited copy of a member (4 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationFragment.kt:164— app/src/main/java/com/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationFragment.kt:164-171 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1397-1400 — 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.
Edited copy of a member (4 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:74— app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:74-77 | app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseFragment.kt:99-102 — 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.
Duplicated block (20 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt:31— app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt:31-50 | app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogRepository.kt:29-48 — before extracting anything, compare `app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressRepository.kt` and `app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogRepository.kt` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1502— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1502-1521 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:236-255 — 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/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1502` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1498` calls `showSnackBar`, `getString` and `app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:232` 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 (16 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailPresenter.kt:32— app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailPresenter.kt:32-47 | app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailPresenter.kt:57-72 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailPresenter.kt:74` calls `when` and `app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailPresenter.kt:49` 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 (16 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/payment_proof_details/PaymentProofDetailsFragment.kt:57— app/src/main/java/com/mw/beam/beamwallet/screens/payment_proof_details/PaymentProofDetailsFragment.kt:57-72 | app/src/main/java/com/mw/beam/beamwallet/screens/proof_verification/ProofVerificationFragment.kt:163-178 — 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/mw/beam/beamwallet/screens/payment_proof_details/PaymentProofDetailsFragment.kt:57` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 3) app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:103— app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:103-117 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:93-107 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:226-240 — before extracting anything, compare `app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt` and `app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:103` 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 (15 lines × 3) app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:105— app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:105-119 | app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:144-158 | app/src/main/java/com/mw/beam/beamwallet/screens/asset_info/AssetDescriptionFragment.kt:122-136 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `message` to `SpannableString` in one and `String` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:103` calls `dismiss` and `app/src/main/java/com/mw/beam/beamwallet/screens/asset_info/AssetDescriptionFragment.kt:120` 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 (14 lines × 3) app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:128— app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:128-141 | app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:175-188 | app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:217-230 — 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/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 3) app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:185— app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:185-198 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:567-580 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1412-1425 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:185` 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/mw/beam/beamwallet/screens/welcome_screen/welcome_restore/WelcomeRestoreFragment.kt:188— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_restore/WelcomeRestoreFragment.kt:188-200 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_seed/WelcomeSeedFragment.kt:155-167 — 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/mw/beam/beamwallet/service/BackgroundService.kt:114— app/src/main/java/com/mw/beam/beamwallet/service/BackgroundService.kt:114-126 | app/src/main/java/com/mw/beam/beamwallet/service/BackgroundService.kt:224-236 — 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/mw/beam/beamwallet/service/BackgroundService.kt:114` 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/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:141— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:141-151 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:169-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:141` 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/mw/beam/beamwallet/core/views/NotificationBanner.java:94— app/src/main/java/com/mw/beam/beamwallet/core/views/NotificationBanner.java:94-104 | app/src/main/java/com/mw/beam/beamwallet/core/views/NotificationBanner.java:146-156 — 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 × 3) app/src/main/java/com/mw/beam/beamwallet/screens/save_address/SaveAddressFragment.kt:86— app/src/main/java/com/mw/beam/beamwallet/screens/save_address/SaveAddressFragment.kt:86-93 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:420-427 | app/src/main/java/com/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationFragment.kt:144-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (8 lines × 3) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:247— app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:247-254 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoPresenter.kt:62-69 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletPresenter.kt:83-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:244` calls `updateAvailable`, `getAvailable` and `app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoPresenter.kt:59` 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.
AppManager.subscribeToUpdates (cyclomatic 73) app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:941— AppManager.subscribeToUpdates has cyclomatic complexity 73 (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.
SettingsFragment.addItems (cyclomatic 60) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:449— SettingsFragment.addItems has cyclomatic complexity 60 (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.
TxDescription.statusImage (cyclomatic 48) app/src/main/java/com/mw/beam/beamwallet/core/entities/TxDescription.kt:287— TxDescription.statusImage has cyclomatic complexity 48 (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.
TransactionsAdapter.onBindViewHolder (cyclomatic 48) app/src/main/java/com/mw/beam/beamwallet/screens/wallet/TransactionsAdapter.kt:128— TransactionsAdapter.onBindViewHolder has cyclomatic complexity 48 (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.
NotificationItem.<init> (cyclomatic 42) app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:38— NotificationItem.<init> has cyclomatic complexity 42 (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.
UtxoDetailsFragment.configUtxoInfo (cyclomatic 37) app/src/main/java/com/mw/beam/beamwallet/screens/utxo_details/UtxoDetailsFragment.kt:75— UtxoDetailsFragment.configUtxoInfo has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
UtxosAdapter.onBindViewHolder (cyclomatic 34) app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxosAdapter.kt:68— UtxosAdapter.onBindViewHolder has cyclomatic complexity 34 (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.
WelcomeProgressPresenter.onProgress (cyclomatic 31) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressPresenter.kt:435— WelcomeProgressPresenter.onProgress has cyclomatic complexity 31 (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.
TransactionDetailsFragment.configGeneralTransactionInfo (cyclomatic 28) app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:217— TransactionDetailsFragment.configGeneralTransactionInfo has cyclomatic complexity 28 (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.
TxDescription.getStatusString (cyclomatic 23) app/src/main/java/com/mw/beam/beamwallet/core/entities/TxDescription.kt:186— TxDescription.getStatusString has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WelcomeProgressFragment.init (cyclomatic 23) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:97— WelcomeProgressFragment.init 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.
SendFragment.hasAmountError (cyclomatic 21) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:1043— SendFragment.hasAmountError has cyclomatic complexity 21 (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.
BeamToolbar.handleStatus (cyclomatic 20) app/src/main/java/com/mw/beam/beamwallet/core/views/BeamToolbar.kt:237— BeamToolbar.handleStatus 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.
WelcomeProgressPresenter.initSubscriptions (cyclomatic 19) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressPresenter.kt:263— WelcomeProgressPresenter.initSubscriptions 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.
ShowTokenFragment.init (cyclomatic 18) app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:84— ShowTokenFragment.init has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SendPresenter.onScannedQR (cyclomatic 17) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:404— SendPresenter.onScannedQR 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.
WalletListener.onReceiveRates (cyclomatic 16) app/src/main/java/com/mw/beam/beamwallet/core/listeners/WalletListener.kt:398— WalletListener.onReceiveRates has cyclomatic complexity 16 (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.
AddressesPagerAdapter.instantiateItem (cyclomatic 16) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:53— AddressesPagerAdapter.instantiateItem has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PasswordConfirmDialog.init (cyclomatic 16) app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmDialog.kt:59— PasswordConfirmDialog.init 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.
NotificationItem.<init> (cognitive 128) app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:38— NotificationItem.<init> has cognitive complexity 128 (threshold 15). Drivers by points: if/else 43 (117 pts), boolean chains 11 (nesting depth added 74). 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.
AppManager.subscribeToUpdates (cognitive 127) app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:941— AppManager.subscribeToUpdates has cognitive complexity 127 (threshold 15). Drivers by points: if/else 56 (104 pts), boolean chains 23 (nesting depth added 48). 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.
SettingsFragment.addItems (cognitive 102) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:449— SettingsFragment.addItems has cognitive complexity 102 (threshold 15). Drivers by points: if/else 57 (90 pts), boolean chains 5, error handling 1 (4 pts), loops 2 (3 pts) (nesting depth added 37). 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.
TransactionsAdapter.onBindViewHolder (cognitive 102) app/src/main/java/com/mw/beam/beamwallet/screens/wallet/TransactionsAdapter.kt:128— TransactionsAdapter.onBindViewHolder has cognitive complexity 102 (threshold 15). Drivers by points: if/else 47 (87 pts), boolean chains 9, match/switch 3 (6 pts) (nesting depth added 43). 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.
TxDescription.statusImage (cognitive 95) app/src/main/java/com/mw/beam/beamwallet/core/entities/TxDescription.kt:287— TxDescription.statusImage has cognitive complexity 95 (threshold 15). Drivers by points: if/else 27 (48 pts), match/switch 12 (44 pts), boolean chains 3 (nesting depth added 53). 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.
BeamToolbar.handleStatus (cognitive 55) app/src/main/java/com/mw/beam/beamwallet/core/views/BeamToolbar.kt:237— BeamToolbar.handleStatus has cognitive complexity 55 (threshold 15). Drivers by points: if/else 22 (46 pts), match/switch 3 (8 pts), boolean chains 1 (nesting depth added 29). 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.
WelcomeProgressPresenter.onProgress (cognitive 47) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressPresenter.kt:435— WelcomeProgressPresenter.onProgress has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (35 pts), boolean chains 12 (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.
ShowTokenFragment.init (cognitive 39) app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:84— ShowTokenFragment.init has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (34 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransactionDetailsFragment.configGeneralTransactionInfo (cognitive 39) app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:217— TransactionDetailsFragment.configGeneralTransactionInfo has cognitive complexity 39 (threshold 15). Drivers by points: if/else 32, boolean chains 7. 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.
SendPresenter.onScannedQR (cognitive 36) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:404— SendPresenter.onScannedQR has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (32 pts), boolean chains 4 (nesting depth added 17). 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.
AddressesFragment.showDeleteAddressesDialog (cognitive 34) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:349— AddressesFragment.showDeleteAddressesDialog has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 6 (16 pts) (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.
NotificationsAdapter.onBindViewHolder (cognitive 33) app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsAdapter.kt:100— NotificationsAdapter.onBindViewHolder has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (33 pts) (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.
WelcomeProgressPresenter.initSubscriptions (cognitive 33) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressPresenter.kt:263— WelcomeProgressPresenter.initSubscriptions has cognitive complexity 33 (threshold 15). Drivers by points: if/else 20 (27 pts), match/switch 3 (5 pts), boolean chains 1 (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.
QrDialogFragment.init (cognitive 32) app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:62— QrDialogFragment.init has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (27 pts), error handling 2 (4 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.
SendPresenter.initSubscriptions (cognitive 32) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:640— SendPresenter.initSubscriptions has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (28 pts), error handling 1 (4 pts) (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.
BeamPhraseInput.init (cognitive 29) app/src/main/java/com/mw/beam/beamwallet/core/views/BeamPhraseInput.kt:83— BeamPhraseInput.init has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (27 pts), match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppActivity.openNotification (cognitive 25) app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:688— AppActivity.openNotification has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5 (nesting depth added 11). 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.
PasswordConfirmDialog.init (cognitive 25) app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmDialog.kt:59— PasswordConfirmDialog.init has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SendFragment.addListeners (cognitive 25) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:460— SendFragment.addListeners has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (24 pts), match/switch 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.
TxDescription.getStatusString (cognitive 24) app/src/main/java/com/mw/beam/beamwallet/core/entities/TxDescription.kt:186— TxDescription.getStatusString has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 6 (11 pts), boolean chains 1 (nesting depth added 9). 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.
AddressesPagerAdapter.instantiateItem (cognitive 23) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:53— AddressesPagerAdapter.instantiateItem has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 11 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AddressesAdapter.onBindViewHolder (cognitive 22) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesAdapter.kt:82— AddressesAdapter.onBindViewHolder has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), match/switch 2 (4 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.
NavItemsAdapter.onBindViewHolder (cognitive 22) app/src/main/java/com/mw/beam/beamwallet/screens/wallet/NavItemsAdapter.kt:43— NavItemsAdapter.onBindViewHolder has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (22 pts) (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.
WelcomeProgressFragment.init (cognitive 22) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:97— WelcomeProgressFragment.init has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8, match/switch 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.
AppActivity.setupMenu (cognitive 21) app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:397— AppActivity.setupMenu has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransactionsPageAdapter.changeSelectedItems (cognitive 21) app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsPageAdapter.kt:146— TransactionsPageAdapter.changeSelectedItems has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (8 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.
BeamToolbar.configureStatus (cognitive 20) app/src/main/java/com/mw/beam/beamwallet/core/views/BeamToolbar.kt:157— BeamToolbar.configureStatus has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 3 (7 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.
SendFragment.setAddressType (cognitive 20) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:1511— SendFragment.setAddressType has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WelcomeProgressFragment.updateProgress (cognitive 20) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:227— WelcomeProgressFragment.updateProgress has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (nesting depth added 8). 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.
CurrenciesHelperKt.convertToCurrencyGrothString (cognitive 19) app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:143— CurrenciesHelperKt.convertToCurrencyGrothString has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PasswordPresenter.onProceed (cognitive 19) app/src/main/java/com/mw/beam/beamwallet/screens/create_password/PasswordPresenter.kt:68— PasswordPresenter.onProceed has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseRepository.openWallet (cognitive 18) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt:49— BaseRepository.openWallet has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 3 (5 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.
ReceivePresenter.onViewCreated (cognitive 18) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:55— ReceivePresenter.onViewCreated has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 1 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SendFragment.hasAmountError (cognitive 18) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:1043— SendFragment.hasAmountError has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), error handling 1, match/switch 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SendPresenter.onNext (cognitive 18) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt:310— SendPresenter.onNext has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3 (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ShareTransactionDetailsView.configGeneralTransactionInfo (cognitive 18) app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/ShareTransactionDetailsView.kt:31— ShareTransactionDetailsView.configGeneralTransactionInfo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 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.
WalletListener.onReceiveRates (cognitive 17) app/src/main/java/com/mw/beam/beamwallet/core/listeners/WalletListener.kt:398— WalletListener.onReceiveRates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 7 (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.
AppManager.setNetworkStatus (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:898— AppManager.setNetworkStatus has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddressesPagerAdapter.changeSelectedItems (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:222— AddressesPagerAdapter.changeSelectedItems has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppConfirmDialog.checkAmount (cognitive 16) REDACTED:227— AppConfirmDialog.checkAmount has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 1 (3 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.
NodeFragment.onNext (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:247— NodeFragment.onNext has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 1 (4 pts) (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.
ReceiveFragment.addListeners (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:269— ReceiveFragment.addListeners has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (16 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.
SendFragment.configAmountErrorMessage (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:1103— SendFragment.configAmountErrorMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransactionDetailsFragment.onContextItemSelected (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:510— TransactionDetailsFragment.onContextItemSelected has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UtxosAdapter.onBindViewHolder (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxosAdapter.kt:68— UtxosAdapter.onBindViewHolder has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 3, 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.
WelcomeProgressFragment.showWallet (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:422— WelcomeProgressFragment.showWallet has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 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.
BackgroundService.receiveOnTxData (cognitive 16) app/src/main/java/com/mw/beam/beamwallet/service/BackgroundService.kt:75— BackgroundService.receiveOnTxData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5 (nesting depth added 6). 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.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:75— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:75-90 | app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:58-90 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:59-85 | app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:64-79 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoFragment.kt:49-63 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:115-153 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· 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/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:237— app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:237-257 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:920-929 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoFragment.kt:84-93 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:251-260 — 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 (78 corresponding lines) · ×1
Edited copy of a member (78 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:182— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:182-286 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:288-365 — These two members are one piece of code written twice and then edited apart: 78 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) REDACTED:183— REDACTED:183-225 | REDACTED:243-278 — These two members are one piece of code written twice and then edited apart: 36 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 (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:111— app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:111-141 | app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:143-188 — These two members are one piece of code written twice and then edited apart: 31 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/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:258— app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:258-284 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:510-544 — 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:102— app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:102-138 | app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:141-177 — 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsPageAdapter.kt:48— app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsPageAdapter.kt:48-79 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxosPagerAdapter.kt:43-79 — 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:51— app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:51-80 | app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:82-109 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 26+ corresponding lines) · ×1
Edited copies of one member (4 members, 26+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:154— app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:154-180 | app/src/main/java/com/mw/beam/beamwallet/screens/max_privacy_details/MaxPrivacyDetailFragment.kt:117-144 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1164-1189 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1192-1217 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 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 (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesAdapter.kt:57— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesAdapter.kt:57-79 | app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsAdapter.kt:59-79 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/TransactionsAdapter.kt:96-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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 (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:208— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:208-227 | app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:158-177 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:396-416 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_restore/WelcomeRestoreFragment.kt:155— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_restore/WelcomeRestoreFragment.kt:155-177 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_seed/WelcomeSeedFragment.kt:102-122 — 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 (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:809— app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:809-832 | app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt:834-857 — These two members are one piece of code written twice and then edited apart: 24 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 (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:184— app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:184-203 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:566-585 — 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.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:215— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:215-226 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:240-251 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:669-680 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:184— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:184-196 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:213-225 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:227-239 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceivePresenter.kt:312-324 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:735— app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:735-750 | app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:752-766 — 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 (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesLockableViewPager.kt:27— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesLockableViewPager.kt:27-39 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsLockableViewPager.kt:27-39 — 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 (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:286— app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:286-288 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:931-933 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoFragment.kt:95-97 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:262-264 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 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 (5 members, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressFragment.kt:86— app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressFragment.kt:86-98 | app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:164-177 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1523-1535 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:601-617 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:257-269 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) REDACTED:210— REDACTED:210-221 | app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmDialog.kt:179-190 — 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.
Duplicated block (30 lines × 2) app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:109— app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:109-138 | app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:148-177 — 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/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `message` to `SpannableString` in one and `String` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenFragment.kt:274— app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenFragment.kt:274-295 | app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt:468-489 — 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 (17–18 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:76— app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:76-93 | app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1234-1250 — 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/mw/beam/beamwallet/screens/node/NodeFragment.kt:76` 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 (18 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1368— app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1368-1385 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:305-322 — 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/mw/beam/beamwallet/screens/settings/SettingsFragment.kt:1368` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:187— app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:187-203 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:569-585 — 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/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:187` 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) REDACTED:187— REDACTED:187-202 | REDACTED:205-218 — 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 `REDACTED:187` 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 (15 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:242— app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:242-256 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:494-508 — 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. 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–13 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/address_edit/EditAddressFragment.kt:251— app/src/main/java/com/mw/beam/beamwallet/screens/address_edit/EditAddressFragment.kt:251-263 | app/src/main/java/com/mw/beam/beamwallet/screens/address_edit/EditAddressFragment.kt:279-290 — 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 (11 lines × 6) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:79— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:79-89 | app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt:65-75 | app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:66-76 | app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:68-78 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoFragment.kt:52-62 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:122-132 — before extracting anything, compare `app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailFragment.kt` and `app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:77` calls `requireActivity`, `addCallback` and `app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoFragment.kt:50` 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 (11 lines × 3) app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressFragment.kt:87— app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressFragment.kt:87-97 | app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:165-175 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:603-613 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `file` to `File` in one and `File?` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/qr_dialog/QrDialogFragment.kt:176` calls `findNavController`, `popBackStack` and `app/src/main/java/com/mw/beam/beamwallet/screens/public_offline_address/PublicOfflineAddressFragment.kt:98` 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 (8–9 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:251— app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:251-259 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:283-290 — 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/mw/beam/beamwallet/screens/addresses/AddressesFragment.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:292` calls `inflate` and `app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesFragment.kt:260` 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 (14–15 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:367— app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:367-381 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:599-612 — 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/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:367` 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 × 4) app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:240— app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:240-247 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:922-929 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoFragment.kt:86-93 | app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletFragment.kt:253-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:240` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:452— app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:452-459 | app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:469-475 — 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/mw/beam/beamwallet/screens/node/NodeFragment.kt:452` 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 (7 lines × 3) app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:246— app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:246-252 | app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt:498-504 | app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:373-379 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 5) app/src/main/java/com/mw/beam/beamwallet/screens/asset_info/AssetBalanceFragment.kt:137— app/src/main/java/com/mw/beam/beamwallet/screens/asset_info/AssetBalanceFragment.kt:137-143 | app/src/main/java/com/mw/beam/beamwallet/screens/proof_verification/ProofVerificationFragment.kt:227-233 | app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt:253-259 | app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:1202-1208 | app/src/main/java/com/mw/beam/beamwallet/screens/utxo_details/UtxoDetailsFragment.kt:249-255 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (12 lines × 3) app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:259— app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:259-271 | app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:768-779 | app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:781-792 — 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.
Swallowed exception (empty catch) app/src/main/java/com/mw/beam/beamwallet/core/helpers/FingerprintManager.kt:133— 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.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/transactions/TransactionsFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/wallet/TransactionsAdapter.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/core/views/BeamToolbar.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/core/entities/NotificationItem.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/show_token/ShowTokenFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/utxo_details/UtxoDetailsFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/service/BackgroundService.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseActivity.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/core/App.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/core/views/NotificationBanner.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_confirm/WelcomeConfirmFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_restore/WelcomeRestoreFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/addresses/AddressesPagerAdapter.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/core/helpers/CurrenciesHelper.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/address_details/AddressFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/proof_verification/ProofVerificationFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmDialog.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/base_screen/ScreenDelegate.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListFragment.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Fat interface: MvpView (22 abstract methods) app/src/main/java/com/mw/beam/beamwallet/base_screen/MvpView.kt:28— `MvpView` declares 22 abstract methods: `showKeyboard`, `hideKeyboard`, `showSnackBar`, `showAlert`, `dismissAlert`, `copyToClipboard`, `showToast`, `initPresenter`, `initToolbar`, `configStatus`, `getToolbarTitle`, `shareText`, `addListeners`, `clearListeners`, `onHideKeyboard`, `onShowKeyboard`, `openExternalLink`, `registerKeyboardStateListener`, `unregisterKeyboardStateListener`, `vibrate`, `logOut`, `dismissSnackBar`. 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: View (21 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveContract.kt:27— `View` declares 21 abstract methods: `init`, `initAddress`, `getComment`, `showQR`, `shareToken`, `copyToken`, `close`, `getAssetId`, `getAmountFromArguments`, `getAmount`, `getTxComment`, `setAmount`, `handleExpandAmount`, `handleExpandComment`, `handleExpandAdvanced`, `getLifecycleOwner`, `getWalletAddressFromArguments`, `showSaveAddressDialog`, `showSaveChangesDialog`, `showShowToken`, `updateTokens`. 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: View (52 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendContract.kt:35— `View` declares 52 abstract methods: `getAmountText`, `getAmount`, `getFee`, `isOffline`, `getComment`, `getToken`, `updateUI`, `hasErrors`, `hasAmountError`, `configOutgoingAddress`, `clearErrors`, `clearToken`, `init`, `updateMaxPrivacyCount`, `refreshAddressType`, `clearAddressError`, `showCantSendToExpiredError`, `showCantPasteError`, `showNotBeamAddressError`, `setAddress`, `setAmount`, `setComment`, `setFee`, `scanQR`, `updateAvailable`, `isAmountErrorShown`, `isPermissionGranted`, `showPermissionRequiredAlert`, `showActivatePrivacyModeDialog`, `configPrivacyStatus`, `createOptionsMenu`, `showConfirmTransaction`, `getAddressFromArguments`, `getAmountFromArguments`, `showChangeAddressFragment`, `updateFeeTransactionVisibility`, `getLifecycleOwner`, `getCommentOutgoingAddress`, `handleExpandEditAddress`, `handleExpandAdvanced`, and 12 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: Presenter (26 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/send/SendContract.kt:91— `Presenter` declares 26 abstract methods: `onNext`, `onMaxPrivacy`, `onTokenChanged`, `onAmountChanged`, `onFeeChanged`, `requestFee`, `onAmountUnfocused`, `onScannedQR`, `onScanQrPressed`, `onRequestPermissionsResult`, `onChangePrivacyModePressed`, `showTokenFragmentPressed`, `onPrivacyModeActivated`, `onCreateOptionsMenu`, `onCancelDialog`, `onSendAllPressed`, `onAdvancedPressed`, `onEditAddressPressed`, `onChangeAddressPressed`, `onExpirePeriodChanged`, `onLabelAddressChanged`, `onAddressChanged`, `onLongPressFee`, `onEnterFee`, `onSelectAddress`, `onPaste`. 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: View (19 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/send_confirmation/SendConfirmationContract.kt:27— `View` declares 19 abstract methods: `getAddress`, `getOutgoingAddress`, `getAmount`, `getFee`, `getChange`, `getShieldedInputsFee`, `getComment`, `getAddressType`, `getRemaining`, `getIsOffline`, `getAssetId`, `init`, `configureContact`, `configureOutAddress`, `configUtxoInfo`, `showSaveAddressFragment`, `delaySend`, `showWallet`, `showConfirmDialog`. 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: View (52 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsContract.kt:33— `View` declares 52 abstract methods: `onNeedAddedViews`, `mode`, `setRunOnRandomNode`, `setMobileNodeEnabled`, `setRunOnBackground`, `sendMailWithLogs`, `setLanguage`, `setConfirmations`, `changePass`, `showLockScreenSettingsDialog`, `showConfirmationsSettingsDialog`, `showFingerprintSettings`, `getContext`, `closeDialog`, `showMaxPrivacySettingsDialog`, `updateLockScreenValue`, `updateMaxPrivacyValue`, `updateConfirmTransactionValue`, `showConfirmPasswordDialog`, `showNodeAddressDialog`, `showInvalidNodeAddressError`, `clearInvalidNodeAddressError`, `showClearDataDialog`, `setAllowOpenExternalLinkValue`, `navigateToLanguage`, `navigateToCurrency`, `navigateToOwnerKeyVerification`, `navigateToPaymentProof`, `showClearDataAlert`, `setLogSettings`, `setCurrencySettings`, `showLogsDialog`, `navigateToSeed`, `navigateToSeedVerification`, `showReceiveFaucet`, `showExportDialog`, `showExportSaveDialog`, `exportSave`, `exportShare`, `showImportDialog`, and 12 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: Presenter (42 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsContract.kt:88— `Presenter` declares 42 abstract methods: `onReportProblem`, `onChangePass`, `onShowLockScreenSettings`, `onChangeLockSettings`, `onDialogClosePressed`, `onChangeConfirmTransactionSettings`, `onChangeFingerprintSettings`, `onChangeRunOnRandomNode`, `onChangeRunOnBackground`, `onChangeAllowOpenExternalLink`, `onNodeAddressPressed`, `onChangeNodeAddress`, `onClearDataPressed`, `onDialogClearDataPressed`, `onConfirmClearDataPressed`, `onSaveNodeAddress`, `onLanguagePressed`, `onShowOwnerKey`, `onChangeLogSettings`, `onLogsPressed`, `onSeedPressed`, `onShowMaxPrivacySettings`, `onSeedVerificationPressed`, `onReceiveFaucet`, `onProofPressed`, `onExportPressed`, `onExportWithExclude`, `onExportSave`, `onRescanPressed`, `onExportShare`, `omImportPressed`, `onRemoveWalletPressed`, `onConfirmRemoveWallet`, `onCurrencyPressed`, `onChangeAllowNews`, `onChangeAllowTransactionStatus`, `onChangeAllowWalletUpdates`, `onChangeAllowAddressExpiration`, `onChangeMaxPrivacySettings`, `onEnableMobileNode`, and 2 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: Repository (32 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsContract.kt:133— `Repository` declares 32 abstract methods: `getLockScreenValue`, `saveLockSettings`, `saveConfirmTransactionSettings`, `saveEnableFingerprintSettings`, `shouldConfirmTransaction`, `isFingerPrintEnabled`, `isAllowOpenExternalLink`, `isAllowBackgroundMode`, `setAllowOpenExternalLink`, `setCurrencySettings`, `setNodeAddress`, `getSavedNodeAddress`, `setRunOnRandomNode`, `setRunOnBackground`, `getCurrentNodeAddress`, `deleteAddress`, `deleteTransaction`, `getCurrentLanguage`, `saveLogSettings`, `getLogSettings`, `getDataFile`, `getCurrencySettings`, `isAllowWalletUpdates`, `isAllowTransactions`, `isAllowNews`, `isAllowAddressExpiration`, `setAllowWalletUpdates`, `setAllowTransactions`, `setAllowNews`, `setAllowAddressExpiration`, `setMobileNodeEnabled`, `getConfirmations`. 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: View (23 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsContract.kt:34— `View` declares 23 abstract methods: `getTransactionId`, `init`, `updateAddresses`, `updatePaymentProof`, `configMenuItems`, `finishScreen`, `updateUtxos`, `showCopiedAlert`, `showPaymentProof`, `showOpenLinkAlert`, `showSendFragment`, `showSaveContact`, `showReceiveFragment`, `showDeleteSnackBar`, `convertViewIntoBitmap`, `shareTransactionDetails`, `handleExpandDetails`, `handleExpandUtxos`, `handleExpandProof`, `showCancelAlert`, `showDeleteAlert`, `copyDetails`, `showOpenAssetIdLinkAlert`. 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: Presenter (17 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsContract.kt:60— `Presenter` declares 17 abstract methods: `onMenuCreate`, `onCancelTransaction`, `onDeleteTransaction`, `onShowPaymentProof`, `onCopyPaymentProof`, `onOpenInBlockExplorerPressed`, `onOpenLinkPressed`, `onRepeatTransaction`, `onSharePressed`, `onExpandDetailedPressed`, `onExpandUtxosPressed`, `onExpandProofPressed`, `onSaveContact`, `onCancelTransactionConfirm`, `onDeleteTransactionsPressed`, `onCopyDetailsPressed`, `onOpenAssetIdPressed`. 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: View (18 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletContract.kt:36— `View` declares 18 abstract methods: `init`, `configWalletStatus`, `configTransactions`, `showTransactionDetails`, `showReceiveScreen`, `showSendScreen`, `showActivatePrivacyModeDialog`, `configPrivacyStatus`, `createOptionsMenu`, `closeDrawer`, `clearAllNotification`, `showAllTransactions`, `showAllAssets`, `selectWalletMenu`, `showFaucet`, `showSecure`, `showReceiveFaucet`, `showSeedScreen`. 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: View (17 abstract methods) app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressContract.kt:35— `View` declares 17 abstract methods: `init`, `updateProgress`, `getMode`, `getIsTrustedRestore`, `getPassword`, `getSeed`, `showWallet`, `showNoInternetMessage`, `showIncorrectNodeMessage`, `showCancelRestoreAlert`, `showCancelCreateAlert`, `showFailedRestoreAlert`, `showFailedDownloadRestoreFileAlert`, `getLifecycleOwner`, `navigateToCreateFragment`, `changeCancelButtonVisibility`, `close`. 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.
Duplicated predicate app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailPresenter.kt:73— `!ExchangeManager.instance.isPrivacyMode && repository.isNeedConfirmEnablePrivacyMode()` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/screens/asset_detail/AssetDetailPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/assets_list/AssetsListPresenter.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/mw/beam/beamwallet/base_screen/BaseRepository.kt:55— `!isEnabledConnectToRandomNode() && !nodeAddress.isNullOrBlank()` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt, app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressRepository.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/mw/beam/beamwallet/screens/notifications/NotificationsPresenter.kt:85— `!state.privacyMode && repository.isNeedConfirmEnablePrivacyMode()` appears character-identically in 4 files — app/src/main/java/com/mw/beam/beamwallet/screens/notifications/NotificationsPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/utxo/UtxoPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/wallet/WalletPresenter.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/mw/beam/beamwallet/screens/confirm/DoubleAuthorizationPresenter.kt:66— `PreferencesManager.getBoolean(PreferencesManager.KEY_IS_FINGERPRINT_ENABLED) && FaceIDManager.isManagerAvailable()` appears character-identically in 5 files — app/src/main/java/com/mw/beam/beamwallet/screens/confirm/DoubleAuthorizationPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/confirm/DoubleAuthorizationRepository.kt, app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmRepository.kt, app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.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/mw/beam/beamwallet/screens/confirm/DoubleAuthorizationPresenter.kt:61— `PreferencesManager.getBoolean(PreferencesManager.KEY_IS_FINGERPRINT_ENABLED) && FingerprintManager.isManagerAvailable()` appears character-identically in 4 files — app/src/main/java/com/mw/beam/beamwallet/screens/confirm/DoubleAuthorizationPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/confirm/DoubleAuthorizationRepository.kt, app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmRepository.kt, app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenRepository.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/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:643— `count == 1 && AppManager.instance.allUnsentIsAddresses()` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt, app/src/main/java/com/mw/beam/beamwallet/service/BackgroundService.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/mw/beam/beamwallet/screens/app_activity/AppActivity.kt:634— `count > 1 && AppManager.instance.allUnsentIsAddresses()` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt, app/src/main/java/com/mw/beam/beamwallet/service/BackgroundService.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/mw/beam/beamwallet/screens/welcome_screen/welcome_confirm/WelcomeConfirmFragment.kt:227— `hasFocus && field?.isStateError == false` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_confirm/WelcomeConfirmFragment.kt, app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_restore/WelcomeRestoreFragment.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/mw/beam/beamwallet/screens/payment_proof_details/PaymentProofDetailsFragment.kt:65— `receiver !=null && !receiver.label.isNullOrEmpty()` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/screens/payment_proof_details/PaymentProofDetailsFragment.kt, app/src/main/java/com/mw/beam/beamwallet/screens/proof_verification/ProofVerificationFragment.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/mw/beam/beamwallet/screens/confirm/PasswordConfirmPresenter.kt:13— `repository.isFingerPrintEnabled() || repository.isFaceIDEnabled()` appears character-identically in 2 files — app/src/main/java/com/mw/beam/beamwallet/screens/confirm/PasswordConfirmPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_open/WelcomeOpenPresenter.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.
D34 · Knowledge Freshness· Most significant orphaned file · ×2
Most significant orphaned file app/src/main/java/com/mw/beam/beamwallet/core/listeners/WalletListener.kt:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file app/src/main/java/com/mw/beam/beamwallet/screens/node/NodeFragment.kt:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Silent fallback default in catch app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt:231— `getAmount` swallows every exception into `0.0` — 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/mw/beam/beamwallet/screens/send/SendFragment.kt:238— `getRealAmount` swallows every exception into `0.0` — 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 21 significant file(s) lose their only recent owner: app/src/main/java/com/mw/beam/beamwallet/screens/settings/SettingsFragment.kt, app/src/main/java/com/mw/beam/beamwallet/screens/send/SendFragment.kt, app/src/main/java/com/mw/beam/beamwallet/core/AppManager.kt, app/src/main/java/com/mw/beam/beamwallet/screens/app_activity/AppActivity.kt, app/src/main/java/com/mw/beam/beamwallet/screens/transaction_details/TransactionDetailsFragment.kt, app/src/main/java/com/mw/beam/beamwallet/screens/send/SendPresenter.kt, app/src/main/java/com/mw/beam/beamwallet/screens/receive/ReceiveFragment.kt, app/src/main/java/com/mw/beam/beamwallet/screens/welcome_screen/welcome_progress/WelcomeProgressFragment.kt (+13 more). Pair on, review, or document these before any departure.
No ADRs found app/build.gradle:1— 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 `app/build.gradle` makes this repository a deployable product (line 1).
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Concentrated knowledge decay — 121 of 146 significant files have no living knowledge, while the repository is still being changed at a low rate (4 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 121 separate risks. Counted over 146 of the 372 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
Thin README README.md:1— The root README is 59 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST REDACTED:6— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation build.gradle:39— `build.gradle` 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.)
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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 3 file(s) — `app/src/main/java/com/mw/beam/beamwallet/base_screen/BaseRepository.kt`, `app/src/main/java/com/mw/beam/beamwallet/core/helpers/LocaleHelper.kt`, `app/src/main/java/com/mw/beam/beamwallet/core/watchers/InputFilterMinMax.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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
0
—
Run 01a1e62d-c72a-7769-83a5-1b9df42ae6de · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 19 · Warnings: 247 · Recommendations: 158 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 21:05 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.