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

novasamatech/nova-wallet-android

Measured 16 November 2026, 23:10 UTC, at code version f1b3595

First survey, so nothing to compare with yet Test reliability: not measured

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

CAI score 48.2out of 100 Weak
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 large codebase: 304,613 lines of product code in 70 projects, tests not counted · Estimated rebuild effort: about 3.4 person-years · Weakest lens: Production Readiness, 39.3

Findings by how serious they are

96 critical 744 serious 1058 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 23:10 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 ▸

61of 61 dimensions measured by tools.
1858of 1898 findings point to an exact file and line, so you can open each one in the code. The other 40 concern the repository as a whole, such as missing documentation.
61dimensions across 7 lenses, read from 304,613 lines of product code in 70 projects.
Chapters

Executive summary

novasamatech/nova-wallet-android falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 48.2 out of 100 and is rated Weak, and 71 of its 96 critical findings are security problems.

Production Readiness, at 39.3, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 6.7 points. Adding automated security scanning would lift Production Readiness itself, worth about 6.2 points. Raising Production Readiness to 70 would lift the score to about 55.3.

Forty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twelve secrets can leak from the build pipeline, and eight pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code. The 12 sets of files in separate parts that keep changing together need that dependency made explicit.

The product code is 304,613 lines, about €490,000 to rebuild.

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

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

If Production Readiness rose from 39.3 to 70, the lowest score rated Strong, the score would rise from 48.2 to about 55.3.

Code composition: what the lines of code are
Product code 89%Tests 11%
Rebuild cost: about €490,000 · Estimate
Cost to rebuild€160,000 to €810,000, for 2,704 to 8,578 hours of work, about 3.4 person-years for 2 to 7 engineers
Difficulty of the problemHigh, 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 48. 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.
SizeLarge: 304,613 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 6.7 points · Low effort · Secret Scanning
2
Resolve the 1 Banned license finding(s) in License Compliance.
Raises the score by about 4.5 points · Low effort · License Compliance
3
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 6.2 points · Medium effort · Security & performance tooling

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 €490,000 to build again, about 3.4 person-years of work. Its weakest lens is Production Readiness, at 39.3 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 83 Domain Modelling findings · Common cause
83 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (3 findings) · Rich vs anemic model (40 findings) · Strongly-typed ids (40 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6.7 points for low effort, because it clears the 1 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch :analytics :analytics :common :common :analytics->:common :core-db :core-db :analytics->:core-db :app :app :app->:analytics :app->:common :app->:core-db :feature-account-api :feature-account-api :app->:feature-account-api :feature-account-impl :feature-account-impl :app->:feature-account-impl :feature-assets :feature-assets :app->:feature-assets :feature-cloud-backup-api :feature-cloud-backup-api :app->:feature-cloud-backup-api :feature-currency-api :feature-currency-api :app->:feature-currency-api :feature-dapp-impl :feature-dapp-impl :app->:feature-dapp-impl :feature-deep-linking :feature-deep-linking :app->:feature-deep-linking :feature-governance-impl :feature-governance-impl :app->:feature-governance-impl :feature-push-notifications :feature-push-notifications :app->:feature-push-notifications :feature-settings-impl :feature-settings-impl :app->:feature-settings-impl :feature-staking-impl :feature-staking-impl :app->:feature-staking-impl :feature-swap-impl :feature-swap-impl :app->:feature-swap-impl :feature-wallet-api :feature-wallet-api :app->:feature-wallet-api :feature-wallet-connect-impl :feature-wallet-connect-impl :app->:feature-wallet-connect-impl :runtime :runtime :app->:runtime :core-api :core-api :common->:core-api :core-db->:common :feature-account-api->:common :feature-account-api->:core-api :feature-account-api->:feature-cloud-backup-api :feature-account-api->:feature-currency-api :feature-account-api->:feature-deep-linking :feature-account-api->:runtime :feature-account-impl->:analytics :feature-account-impl->:common :feature-account-impl->:core-db :feature-account-impl->:feature-account-api :feature-account-impl->:feature-cloud-backup-api :feature-account-impl->:feature-currency-api :feature-account-impl->:feature-deep-linking :feature-account-impl->:runtime :feature-assets->:analytics :feature-assets->:common :feature-assets->:core-db :feature-assets->:feature-account-api :feature-assets->:feature-currency-api :feature-assets->:feature-deep-linking :feature-assets->:feature-wallet-api :feature-assets->:runtime :feature-cloud-backup-api->:common :feature-cloud-backup-api->:core-api :feature-cloud-backup-api->:core-db :feature-cloud-backup-api->:runtime :feature-currency-api->:common :feature-currency-api->:core-api :feature-currency-api->:core-db :feature-currency-api->:runtime :feature-dapp-impl->:analytics :feature-dapp-impl->:common :feature-dapp-impl->:core-db :feature-dapp-impl->:feature-account-api :feature-dapp-impl->:feature-currency-api :feature-dapp-impl->:feature-deep-linking :feature-dapp-impl->:feature-wallet-api :feature-dapp-impl->:runtime :feature-deep-linking->:common :feature-governance-impl->:analytics :feature-governance-impl->:common :feature-governance-impl->:core-db :feature-governance-impl->:feature-account-api :feature-governance-impl->:feature-deep-linking :feature-governance-impl->:feature-wallet-api :feature-governance-impl->:runtime :feature-push-notifications->:common :feature-push-notifications->:feature-account-api :feature-push-notifications->:feature-assets :feature-push-notifications->:feature-currency-api :feature-push-notifications->:feature-deep-linking :feature-push-notifications->:runtime :feature-settings-impl->:analytics :feature-settings-impl->:common :feature-settings-impl->:feature-account-api :feature-settings-impl->:feature-assets :feature-settings-impl->:feature-cloud-backup-api :feature-settings-impl->:feature-currency-api :feature-settings-impl->:feature-push-notifications :feature-settings-impl->:feature-wallet-api :feature-settings-impl->:runtime :feature-staking-impl->:analytics :feature-staking-impl->:common :feature-staking-impl->:core-db :feature-staking-impl->:feature-account-api :feature-staking-impl->:feature-currency-api :feature-staking-impl->:feature-deep-linking :feature-staking-impl->:feature-wallet-api :feature-staking-impl->:runtime :feature-swap-impl->:analytics :feature-swap-impl->:common :feature-swap-impl->:core-db :feature-swap-impl->:feature-account-api :feature-swap-impl->:feature-currency-api :feature-swap-impl->:feature-wallet-api :feature-swap-impl->:runtime :feature-wallet-api->:common :feature-wallet-api->:core-api :feature-wallet-api->:core-db :feature-wallet-api->:feature-account-api :feature-wallet-api->:feature-currency-api :feature-wallet-api->:runtime :feature-wallet-connect-impl->:analytics :feature-wallet-connect-impl->:common :feature-wallet-connect-impl->:core-db :feature-wallet-connect-impl->:feature-account-api :feature-wallet-connect-impl->:feature-currency-api :feature-wallet-connect-impl->:feature-deep-linking :feature-wallet-connect-impl->:feature-wallet-api :feature-wallet-connect-impl->:runtime :runtime->:common :runtime->:core-api :runtime->:core-db __more__ +50 more projects

Architecture: which parts of the code depend on which

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

4439 modules, with 20667 dependencies between them. 161 loops run through 533 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 analytics2 common.mixin.actionAwaitable.ActionAwaitableMixin3 common.resources4 core_db.dao5 feature_account_impl.presentation6 common.address7 common.presentation8 common.utils9 common.mixin.api10 runtime.multiNetwork.chain.model.Chain11 common.validation12 feature_account_api.data.model13 feature_governance_api.data.network.blockhain.model14 runtime.multiNetwork.chain.model15 common.base16 feature_account_api.data.extrinsic17 feature_account_api.domain.model18 feature_account_api.presenatation.actions.ExternalActions19 runtime.multiNetwork20 common.data.network21 feature_account_api.presenatation.account.wallet22 runtime.repository23 runtime.state.SelectedAssetOptionSharedState24 common.di25 feature_account_api.domain.interfaces26 feature_staking_impl.data27 feature_account_impl.di28 feature_wallet_api.domain.interfaces29 feature_wallet_api.domain.model30 feature_wallet_api.data.repository31 feature_wallet_api.presentation.mixin.fee.v2.FeeLoaderMixinV232 feature_wallet_api.presentation.model33 feature_staking_impl.domain.bittensor34 feature_wallet_api.domain35 feature_wallet_api.presentation.formatters.amount36 feature_assets.di37 feature_governance_impl.di38 feature_staking_impl.presentation.bittensor.subnet39 feature_staking_impl.presentation40 feature_staking_impl.di
1 analytics
2 common.mixin.actionAwaitable.ActionAwaitableMixin
3 common.resources
4 core_db.dao
5 feature_account_impl.presentation
6 common.address1
7 common.presentation1
8 common.utils52
9 common.mixin.api15
10 runtime.multiNetwork.chain.model.Chain5
11 common.validation1
12 feature_account_api.data.model63
13 feature_governance_api.data.network.blockhain.model1
14 runtime.multiNetwork.chain.model211
15 common.base43
16 feature_account_api.data.extrinsic13
17 feature_account_api.domain.model214
18 feature_account_api.presenatation.actions.ExternalActions12
19 runtime.multiNetwork1146
20 common.data.network11
21 feature_account_api.presenatation.account.wallet111
22 runtime.repository2273
23 runtime.state.SelectedAssetOptionSharedState1
24 common.di15115113
25 feature_account_api.domain.interfaces517141
26 feature_staking_impl.data3313
27 feature_account_impl.di1199223121331226
28 feature_wallet_api.domain.interfaces5171125
29 feature_wallet_api.domain.model310541
30 feature_wallet_api.data.repository4316
31 feature_wallet_api.presentation.mixin.fee.v2.FeeLoaderMixinV211
32 feature_wallet_api.presentation.model1111
33 feature_staking_impl.domain.bittensor245821619577125
34 feature_wallet_api.domain61312112111
35 feature_wallet_api.presentation.formatters.amount14154
36 feature_assets.di1234121111231226127124
37 feature_governance_impl.di1122221112113222213
38 feature_staking_impl.presentation.bittensor.subnet116951241212212114436376
39 feature_staking_impl.presentation15
40 feature_staking_impl.di11512222313616252851233516
Uses a module listed above itPart of a loopThe module itself
1 analytics2 common.mixin.actionAwaitable.ActionAwaitableMixin3 common.resources4 core_db.dao5 feature_account_impl.presentation6 common.address7 common.presentation8 common.utils9 common.mixin.api10 runtime.multiNetwork.chain.model.Chain11 common.validation12 feature_account_api.data.model13 feature_governance_api.data.network.blockhain.model14 runtime.multiNetwork.chain.model15 common.base16 feature_account_api.data.extrinsic17 feature_account_api.domain.model18 feature_account_api.presenatation.actions.ExternalActions19 runtime.multiNetwork20 common.data.network21 feature_account_api.presenatation.account.wallet22 runtime.repository23 runtime.state.SelectedAssetOptionSharedState24 common.di25 feature_account_api.domain.interfaces26 feature_staking_impl.data27 feature_account_impl.di28 feature_wallet_api.domain.interfaces29 feature_wallet_api.domain.model30 feature_wallet_api.data.repository31 feature_wallet_api.presentation.mixin.fee.v2.FeeLoaderMixinV232 feature_wallet_api.presentation.model33 feature_staking_impl.domain.bittensor34 feature_wallet_api.domain35 feature_wallet_api.presentation.formatters.amount36 feature_assets.di37 feature_governance_impl.di38 feature_staking_impl.presentation.bittensor.subnet39 feature_staking_impl.presentation40 feature_staking_impl.dianalytics1common.mixin.actionAwaitable.ActionAwaitableMixin2common.resources3core_db.dao4feature_account_impl.presentation5common.address6common.presentation7common.utils8common.mixin.api9runtime.multiNetwork.chain.model.Chain10common.validation11feature_account_api.data.model12feature_governance_api.data.network.blockhain.model13runtime.multiNetwork.chain.model14common.base15feature_account_api.data.extrinsic16feature_account_api.domain.model17feature_account_api.presenatation.actions.ExternalActions18runtime.multiNetwork19common.data.network20feature_account_api.presenatation.account.wallet21runtime.repository22runtime.state.SelectedAssetOptionSharedState23common.di24feature_account_api.domain.interfaces25feature_staking_impl.data26feature_account_impl.di27feature_wallet_api.domain.interfaces28feature_wallet_api.domain.model29feature_wallet_api.data.repository30feature_wallet_api.presentation.mixin.fee.v2.FeeLoaderMixinV231feature_wallet_api.presentation.model32feature_staking_impl.domain.bittensor33feature_wallet_api.domain34feature_wallet_api.presentation.formatters.amount35feature_assets.di36feature_governance_impl.di37feature_staking_impl.presentation.bittensor.subnet38feature_staking_impl.presentation39feature_staking_impl.di4011521551631211431321412114611111227311511511351714133131199223121331226517112531054143161111112458216195771256131211211114154123412111123122612712411222211121132222131169512412122121144363761511512222313616252851233516+4399 more modules (most-connected shown)

At a glance — Code Health · 84.5 · Strong ·

At a glance — Architecture · 68.7 · Adequate · gated by AX2 ·

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

At a glance — Readiness · 39.3 · Weak · gated by P3, P7 ·

At a glance — Security · 53.8 · Adequate · gated by D29, D36 ·

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

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection73High / Critical
A03:2025 — Software Supply Chain Failures28Medium
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; 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; Resolve the 1 Banned license finding(s) in License Compliance.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+6.7 ptsLowSecret Scanning
Resolve the 1 Banned license finding(s) in License Compliance.+4.5 ptsLowLicense Compliance
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+6.2 ptsMediumSecurity & performance tooling
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).+4.4 ptsMediumOutbound HTTP resilience
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).+3.4 ptsMediumDR & Backup
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.+1.7 ptsMediumStrongly-typed ids
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.+1.6 ptsMediumRich vs anemic model
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.+1.6 ptsMediumConstructible invalid state

File quality

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

FileScoreBandWorst signal
REDACTED0.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt5.1MixedGod Classes: TooManyMethods: SwapMainSettingsViewModel
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedDependency Vulnerabilities: Medium advisory (unsound): 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 — 96

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

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

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 61 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 — 61 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D16D17D19D21D26D27D28D29D30D34D35D36D43D44AX10AX2AX3AX4AX5AX6AX9DM1DM10DM11DM12DM2DM4DM5DM6DM7DM9M1M2M3P1P3P4P5P6P7PF3X1X12X16X18X19X21X25X27X3X30X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1e6a0-b9e0-7916-a6f5-9cb68c6ce606.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .rs, .kt, and our analyzer cannot run the .kt test suite(s) — so no coverage was collected for the repository as a whole. The Rust half did build and run, and its own line coverage came back at 14.6% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • 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 — 68 Maven/Gradle manifest(s) were read, stating a version for 6 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (feature-account-migration/build.gradle), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `analytics/src/main/java/io/novafoundation/nova/analytics/transport/AnalyticsUploader.kt`, `app/src/main/java/io/novafoundation/nova/app/root/domain/RootInteractor.kt`, `common/src/main/java/io/novafoundation/nova/common/address/format/AddressFormat.kt`, `common/src/main/java/io/novafoundation/nova/common/data/memory/ComputationalScope.kt`, `common/src/main/java/io/novafoundation/nova/common/data/memory/SharedComputation.kt`, … (+192 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (web3names/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • DM11 Constructible invalid state — 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
  • DM2 Strongly-typed ids — 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. 38 further occurrence(s) are not listed individually; the score already reflects all 78.
  • DM4 Rich vs anemic model — 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. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
  • DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The frontend declares that it computes whether a construction is produced or passed, yet 7710 of 7714 constructions arrived without the answer. Arm two skipped them; it did not clear them.
  • ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
  • 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.
  • 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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity8.4 / 10Strong✓ Tool-verified

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

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

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

8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BittensorSubmissionExecutor.execute at 37. A further 7 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FeatureNavigationTracker.featureFor at 23 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/io/novafoundation/nova/app/root/analytics/FeatureNavigationTracker.kt (FeatureNavigationTracker.featureFor at 23), feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/track/TrackFormatter.kt (RealTrackFormatter.formatTrack at 17), feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorExitValidationUi.kt (BittensorExitValidationUiKt.titleAndMessage at 17), feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorStakeValidationUi.kt (BittensorStakeValidationUiKt.titleAndMessage at 17), feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt (SwapValidationFailureUiKt.mapSwapValidationFailureToUI at 17), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

BittensorSubmissionExecutor.execute (cyclomatic 37)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt:77
ResponseCache.observe (cyclomatic 24)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt:148
AddFragmentNavigator.navigate (cyclomatic 23)app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/AddFragmentNavigator.java:130
BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics (cyclomatic 18)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorOperationAnalyticsMapping.kt:22
BittensorExitReviewViewModel.confirmClicked (cyclomatic 18)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:651

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

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with BittensorSubmissionExecutor.execute (cyclomatic 37). — Refactoring it lifts Cyclomatic Complexity from 8.4 to about 8.6/10.

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

D2 · Cognitive Complexity7.7 / 10Strong✓ Tool-verified

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

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

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

14 method(s) exceeded the cognitive complexity threshold of 15; the worst was BittensorSubmissionExecutor.execute at 45.

BittensorSubmissionExecutor.execute (cognitive 45)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt:77
ResponseCache.observe (cognitive 41)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt:148
AddFragmentNavigator.navigate (cognitive 34)app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/AddFragmentNavigator.java:130
StackBlur.blur (cognitive 30)common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:8
BittensorMevTracker.scan (cognitive 28)feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/mev/BittensorMevTracker.kt:84

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

What to do

  1. Bring the 14 bodies over 15 down to 15 or less in Cognitive Complexity — start with BittensorSubmissionExecutor.execute (cognitive 45), ResponseCache.observe (cognitive 41), AddFragmentNavigator.navigate (cognitive 34). — 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 14 together lifts Cognitive Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes9.5 / 10Stronggated by 44 serious findings✓ Tool-verified

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

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

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

44 god class(es) detected.

TooManyMethods: Navigator · ×21app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:115
FileTooLong: subnet/BittensorSubnetAmountViewModel.kt · ×11feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt
ClassTooLong: BittensorSubnetAmountViewModel · ×10feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:123
MethodTooLong: StackBlur.blur · ×2common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:8

What to do

  1. Resolve the 21 TooManyMethods finding(s) in God Classes — start with Navigator.kt, BittensorModule.kt, CommonModule.kt. — One of this dimension's main actionable groups (21 warning-level).
  2. Resolve the 11 FileTooLong finding(s) in God Classes — start with BittensorSubnetAmountViewModel.kt, AccountFeatureModule.kt, lib.rs. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 10 ClassTooLong finding(s) in God Classes — start with BittensorSubnetAmountViewModel.kt, RealSwapService.kt, SwapMainSettingsViewModel.kt. — One of this dimension's main actionable groups (10 warning-level).

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

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

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

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

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

138 duplicated block group(s) detected. 3.5 % of the production lines (10,634 of 304,613) are in a reported copy. A further 274 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (7 lines × 2) · ×26feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:119
Edited copy of a member (13 corresponding lines) · ×21feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:19
Edited copy of a member (12 corresponding lines) · ×20feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:86
Edited copy of a member (16 corresponding lines) · ×17feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:107
Edited copy of a member (9 corresponding lines) · ×17feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/LegacyDelegationScheduledRequestExecutor.kt:30

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

What to do

  1. Resolve the 26 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ByNetworkAssetSearchInteractor.kt, CloudBackup.kt, GovernanceUnlockInteractor.kt. — One of this dimension's main actionable groups (26 warning-level).
  2. Resolve the 21 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with StakingTypeMappers.kt (2), ByNetworkAssetSearchInteractor.kt, MainFlowMoonbeamCustomization.kt. — One of this dimension's main actionable groups (21 warning-level).
  3. Resolve the 20 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with UpdateNotificationsAdapter.kt, GiftAnimationFactory.kt, SwitchersSetup.kt. — One of this dimension's main actionable groups (20 warning-level).

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

D5 · Coupling6.8 / 10Adequate✓ Tool-verified

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

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

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

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

70 production modules (Gradle+Cargo), 0 dependency cycle(s), 19 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; 5 module(s) off the main sequence.

Unstable project :feature-account-impl · ×19
Off the main sequence: :bindings:metadata_shortener · ×4
Off the main sequence: :common

What to do

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

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

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

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

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

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

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

16 of 1378 classes have LCOM4 above 3.

Low cohesion: RootActivity (LCOM4 8) · ×16app/src/main/java/io/novafoundation/nova/app/root/presentation/RootActivity.kt:28

What to do

  1. Resolve the 16 Low cohesion finding(s) in Cohesion (LCOM4) — start with RootActivity.kt, BalanceListViewModel.kt, MythosSharedComputation.kt. — One of this dimension's main actionable groups (16 warning-level).

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D14 · License Compliance8.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

1 of 297 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 13 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

Banned license: array-bytes

What to do

  1. Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).

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

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

Top hotspots: feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt (7×37=259); feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt (6×18=108); feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt (2×24=48)

Hotspot: feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt · ×3feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt:77

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with BittensorSubmissionExecutor.kt, BittensorExitReviewViewModel.kt, ResponseCache.kt. — One of this dimension's main actionable groups (3 warning-level).

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

D16 · Bus Factor9.8 / 10Exemplary✓ Tool-verified

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

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

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

43 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt. Counted over 1976 of the 6239 production source files in this repository: 4258 are under the ~2,400-byte size floor this dimension measures over, and the remaining 5 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt10.0 / 10Stronggated by 67 serious findings✓ Tool-verified

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

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

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

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

TodoComment · ×66runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/RemoteStorageQueryContext.kt:66
FixmeCommentruntime/src/test/java/io/novafoundation/nova/runtime/multiNetwork/runtime/RuntimeProviderTest.kt:26

What to do

  1. Resolve the 66 TodoComment finding(s) in Explicit Debt — start with Asset.kt (4), WalletRepositoryImpl.kt (2), NovaCardViewModel.kt (2). — One of this dimension's main actionable groups (66 warning-level).
  2. Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with RuntimeProviderTest.kt. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

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

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

1 of 1 documentation facets pass in full. 17 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D21 · Naming Consistency6.2 / 10Adequate✓ Tool-verified

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

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

12 naming inconsistencies among 317 declarations measured against a convention their peers follow.

`sufficientBalanceToStayAboveEd` spells `Ed` where 46 names in the project spell it `ED` · ×2feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/add/Declarations.kt:32
`EmptyGroupRVItem` spells `RV` where 12 names in the project spell it `Rv`feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/wallets/ManualBackupWalletsAdapter.kt:23
`CloudBackupChangingWarningMixinUIKt` spells `UI` where 14 names in the project spell it `Ui`feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/mixin/CloudBackupChangingWarningMixinUI.kt:1
`ShareReferendumUIKt` spells `UI` where 67 names in the project spell it `Ui`feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/share/ShareReferendumUI.kt:1
`RewardDestinationUIKt` spells `UI` where 153 names in the project spell it `Ui`feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/common/rewardDestination/RewardDestinationUI.kt:1

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

What to do

  1. Resolve the 2 `sufficientBalanceToStayAboveEd` spells `Ed` where 46 names in the… finding(s) in Naming Consistency — start with Declarations.kt (2). — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 `EmptyGroupRVItem` spells `RV` where 12 names in the project spell it… finding(s) in Naming Consistency — start with ManualBackupWalletsAdapter.kt. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `CloudBackupChangingWarningMixinUIKt` spells `UI` where 14 names in the… finding(s) in Naming Consistency — start with CloudBackupChangingWarningMixinUI.kt. — One of this dimension's main actionable groups (1 recommendation-level).

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

D26 · Project Cohesion5.0 / 10Adequate✓ Tool-verified

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

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

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

17 of 68 build units (Cargo, Gradle) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×17feature-staking-impl/build.gradle:1

What to do

  1. Resolve the 17 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle (17). — One of this dimension's main actionable groups (17 recommendation-level).

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

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

72 % of calls cross a namespace and 6 % 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.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

  1. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

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

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

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

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

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

73 finding(s): 0 critical, 69 high, 4 medium, 0 low. 36 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 3 file(s) — `feature-dapp-impl/src/main/res/raw/metamask_min.js`, `feature-dapp-impl/src/main/res/raw/polkadotjs_min.js`, `gradlew` (line 74, line 181) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 8 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 11 REDACTED finding(s) charged to Static Analysis (SAST) — the other 36 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (47 issue-level, 11 of them charged here).
  2. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  3. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).

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

D30 · Dependency Vulnerabilities8.1 / 10Strong✓ Tool-verified

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

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

10 finding(s): 0 critical, 0 high, 10 medium, 0 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness5.3 / 10Adequate✓ Tool-verified

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

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

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

933 of 1981 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is bindings/hydra-dx-math/rust/src/lib.rs. Counted over 1981 of the 6239 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×7bindings/hydra-dx-math/rust/src/lib.rs:1
Orphaned file · ×926feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/extrinsic/RealExtrinsicService.kt:1
Further orphaned files (smaller)

What to do

  1. Resolve the 926 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (6), ExtrinsicBuilderExt.kt (4), Declarations.kt (3). — One of this dimension's main actionable groups (926 recommendation-level).
  2. Resolve the 7 Orphaned knowledge finding(s) in Knowledge Freshness — start with lib.rs, RealLocalAccountsCloudBackupFacade.kt, PayoutRepository.kt. — One of this dimension's main actionable groups (7 issue-level).
  3. Resolve the 1 Further orphaned files (smaller) 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.

D35 · Change Coupling9.9 / 10Adequategated by 12 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: UnsupportedDelegationsRepository.kt↔Gov2DelegationsRepository.kt 100%; SwapService.kt↔AssetConversionExchange.kt 94%; SwapConfirmationFragment.kt↔SwapConfirmationModule.kt 90%

Boundary-crossing change coupling: SwapService.kt ↔ AssetConversionExchange.kt · ×12feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/swap/SwapService.kt:1
Change coupling: UnsupportedDelegationsRepository.kt ↔ Gov2DelegationsRepository.kt · ×24feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/UnsupportedDelegationsRepository.kt:1
Change-coupling hub: SwapMainSettingsViewModel.kt → RealSwapSettingsState.kt, SwapConfirmationFragment.kt, SwapConfirmationModule.kt, SwapMainSettingsFragment.kt · ×2feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt

What to do

  1. Resolve the 12 Boundary-crossing change coupling finding(s) in Change Coupling — start with SwapService.kt (2), AccountInfoRepository.kt (2), SubstrateSdkExt.kt (2). — One of this dimension's main actionable groups (12 issue-level).
  2. Resolve the 24 Change coupling finding(s) in Change Coupling — start with SwapConfirmationFragment.kt (2), RootDependencies.kt (2), UnsupportedDelegationsRepository.kt. — One of this dimension's main actionable groups (24 warning-level).
  3. Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with SwapMainSettingsViewModel.kt, SwapFeatureModule.kt. — One of this dimension's main actionable groups (2 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition8.1 / 10Strong✓ Tool-verified

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

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

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

AX2 · Stateful singletons3.5 / 10Weak✓ Tool-verified

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

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

  • `ContextManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (activity, context; e.g. `activity` in `attachActivity` at line 33). — common/src/main/java/io/novafoundation/nova/common/resources/ContextManager.kt:13

What to do

  • Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

AX4 · Dependency direction6.7 / 10Adequate✓ Tool-verified

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

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

  • `:feature-ledger-core` is a Domain project but references `:core-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • `:feature-swap-core` is a Domain project but references `:feature-swap-core:api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • `:feature-swap-core` is a Domain project but references `:core-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.

What to do

  • Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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

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

  • `ComponentHolderModule` declares 39 abstract methods: `provideFeatureContainer`, `provideSplashFeatureHolder`, `provideDbFeature`, `provideInfrastructureFeature`, `provideAnalyticsFeature`, `provideOnboardingFeature`, `provideDAppFeature`, `provideLedgerFeature`, `provideLedgerCore`, `provideGovernanceFeature`, `provideAccountFeature`, `provideAssetsFeature`, `provideVoteFeature`, `provideWalletFeature`, `provideCurrencyFeature`, `provideMainFeature`, `provideStakingFeature`, `provideRuntimeFeature`, `provideWeb3Names`, `provideCrowdloanFeature`, `provideNftFeature`, `provideVersionsFeature`, `provideCaipFeature`, `provideExternalSignFeature`, `provideWalletConnectFeature`, `provideSettingsFeature`, `provideSwapFeature`, `provideBuyFeature`, `providePushNotificationsFeature`, `provideProxyFeature`, `provideDeepLinkingFeatureHolder`, `provideCloudBackupFeatureHolder`, `provideSwapCoreFeatureHolder`, `provideBannersFeatureApi`, `provideXcmFeatureHolder`, `provideMultisigOperationsFeatureHolder`, `provideAccountMigrationFeatureHolder`, `provideChainMigrationFeatureHolder`, `provideGiftFeature`. 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/io/novafoundation/nova/app/di/deps/ComponentHolderModule.kt:89
  • `RootDependencies` declares 30 abstract methods: `preferences`, `updateNotificationsInteractor`, `contributionsInteractor`, `crowdloanRepository`, `networkStateMixin`, `externalRequirementsFlow`, `accountRepository`, `walletRepository`, `appLinksProvider`, `legalConsentRepository`, `resourceManager`, `currencyInteractor`, `stakingRepository`, `chainRegistry`, `backgroundAccessObserver`, `safeModeService`, `rootScope`, `governanceStateUpdater`, `dappMetadataRepository`, `encryptionDefaults`, `proxyExtrinsicValidationRequestBus`, `metaAccountChangesRequestBus`, `proxyHaveEnoughFeeValidationFactory`, `context`, `toastMessageManager`, `dialogMessageManager`, `chainMigrationRepository`, `migrationInfoRepository`, `analyticsService`, `analyticsOptOutManager`. 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/io/novafoundation/nova/app/root/di/RootDependencies.kt:70
  • `Preferences` declares 20 abstract methods: `contains`, `putString`, `getString`, `putBoolean`, `getBoolean`, `putInt`, `putStringSet`, `getInt`, `putLong`, `getLong`, `getStringSet`, `getCurrentLanguage`, `saveCurrentLanguage`, `removeField`, `stringFlow`, `booleanFlow`, `stringSetFlow`, `keyFlow`, `keysFlow`, `edit`. 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. — common/src/main/java/io/novafoundation/nova/common/data/storage/Preferences.kt:8
  • `CommonApi` declares 55 abstract methods: `copyTextMixin`, `computationalCache`, `imageLoader`, `context`, `provideResourceManager`, `provideNetworkApiCreator`, `provideAppLinksProvider`, `providePreferences`, `backgroundAccessObserver`, `provideEncryptedPreferences`, `provideIconGenerator`, `provideClipboardManager`, `provideDeviceVibrator`, `signer`, `logger`, `contextManager`, `languagesHolder`, `provideJsonMapper`, `socketServiceCreator`, `provideSocketSingleRequestExecutor`, `addressIconGenerator`, `cachingAddressIconGenerator`, `networkStateMixin`, `qrCodeGenerator`, `fileProvider`, `random`, `contentResolver`, `httpExceptionHandler`, `validationExecutor`, `secretStoreV1`, `secretStoreV2`, `customDialogDisplayer`, `appVersionsProvider`, `ethereumAddressFormat`, `sharedPreferences`, `safeModeService`, `twoFactorVerificationService`, `twoFactorVerificationExecutor`, `rootScope`, `bakingParallaxCardCache`, and 15 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. — common/src/main/java/io/novafoundation/nova/common/di/CommonApi.kt:89
  • `AppDatabase` declares 35 abstract methods: `responseCacheDao`, `nodeDao`, `userDao`, `assetDao`, `operationDao`, `phishingAddressesDao`, `storageDao`, `tokenDao`, `accountStakingDao`, `stakingTotalRewardDao`, `chainDao`, `chainAssetVisibilityDao`, `metaAccountSettingsDao`, `chainAssetDao`, `metaAccountDao`, `dAppAuthorizationDao`, `nftDao`, `phishingSitesDao`, `favouriteDAppsDao`, `currencyDao`, `lockDao`, `contributionDao`, `governanceDAppsDao`, `browserHostSettingsDao`, `walletConnectSessionsDao`, `stakingDashboardDao`, `coinPriceDao`, `stakingRewardPeriodDao`, `externalBalanceDao`, `holdsDao`, `tinderGovDao`, `browserTabsDao`, `multisigOperationsDao`, `giftsDao`, `analyticsEventsDao`. 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. — core-db/src/main/java/io/novafoundation/nova/core_db/AppDatabase.kt:248
  • `ChainDao` declares 17 abstract methods: `addChainOrUpdate`, `addChainNode`, `getJoinChainInfo`, `getAllChainIds`, `joinChainInfoFlow`, `getLastChainNodeOrderId`, `chainExists`, `runtimeInfo`, `allRuntimeInfos`, `updateSyncedRuntimeVersion`, `setConnectionState`, `setNodePreferences`, `updateChainNode`, `updateChainName`, `updateAssetToken`, `deleteChain`, `deleteNode`. 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. — core-db/src/main/java/io/novafoundation/nova/core_db/dao/ChainDao.kt:22
  • `MetaAccountDao` declares 38 abstract methods: `insertMetaAccount`, `updateMetaAccount`, `insertChainAccount`, `insertChainAccounts`, `deleteChainAccounts`, `insertProxy`, `getMetaAccounts`, `getMetaAccountsByIds`, `getMetaAccount`, `getMetaAccountsQuantityByStatus`, `getMetaAccountsByStatus`, `getFullMetaAccounts`, `getJoinedMetaAccountsInfoFlow`, `getJoinedMetaAccountsInfoByStatusFlow`, `getMetaAccountsIdsByStatus`, `metaAccountsWithBalanceFlow`, `metaAccountWithBalanceFlow`, `selectMetaAccount`, `updatePositions`, `getJoinedMetaAccountInfo`, `getMetaAccountType`, `selectedMetaAccountInfoFlow`, `metaAccountInfoFlow`, `isMetaAccountExists`, `getMetaAccountInfo`, `metaAccountNameFor`, `updateName`, `findAffectedMetaIdsOnDelete`, `deleteByIds`, `nextAccountPosition`, `selectedMetaAccount`, `hasMetaAccountsCountOfTypeFlow`, `observeMetaAccountsByTypeFlow`, `deleteProxiedMetaAccountsByChain`, `hasMetaAccountsByStatus`, `hasMetaAccountsByType`, `changeAccountsStatus`, `removeMetaAccountsByStatus`. 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. — core-db/src/main/java/io/novafoundation/nova/core_db/dao/MetaAccountDao.kt:82
  • `OperationDao` declares 16 abstract methods: `insertOperationBase`, `insertTransferType`, `insertDirectRewardType`, `insertPoolRewardType`, `insertExtrinsicType`, `insertSwapType`, `insertOperationsBase`, `insertTransferTypes`, `insertDirectRewardTypes`, `insertPoolRewardTypes`, `insertExtrinsicTypes`, `insertSwapTypes`, `observe`, `observeSwapOperations`, `observeTransferOperations`, `getTransferType`. 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. — core-db/src/main/java/io/novafoundation/nova/core_db/dao/OperationDao.kt:25
  • `DbApi` declares 28 abstract methods: `responseCacheDao`, `provideDatabase`, `provideLockDao`, `provideAccountDao`, `contributionDao`, `provideNodeDao`, `provideAssetDao`, `provideOperationDao`, `providePhishingAddressDao`, `storageDao`, `tokenDao`, `accountStakingDao`, `stakingTotalRewardDao`, `chainDao`, `chainAssetDao`, `chainAssetVisibilityDao`, `metaAccountSettingsDao`, `metaAccountDao`, `dappAuthorizationDao`, `nftDao`, `governanceDAppsDao`, `browserHostSettingsDao`, `coinPriceDao`, `stakingRewardPeriodDao`, `tinderGovDao`, `browserTabsDao`, `multisigOperationsDao`, `giftsDao`. 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. — core-db/src/main/java/io/novafoundation/nova/core_db/di/DbApi.kt:41
  • `AccountFeatureApi` declares 20 abstract methods: `localIdentityProvider`, `onChainIdentityProvider`, `localWithOnChainIdentityProvider`, `metaAccountGroupingInteractor`, `accountInteractor`, `provideAccountRepository`, `externalAccountActions`, `accountUpdateScope`, `addressDisplayUseCase`, `accountUseCase`, `extrinsicService`, `extrinsicServiceFactory`, `importTypeChooserMixin`, `twoFactorVerificationExecutor`, `biometricServiceFactory`, `encryptionDefaults`, `proxyExtrinsicValidationRequestBus`, `cloudBackupFacade`, `syncWalletsBackupPasswordCommunicator`, `copyAddressMixin`. 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. — feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/di/AccountFeatureApi.kt:63
  • `AccountInteractor` declares 31 abstract methods: `getActiveMetaAccounts`, `generateMnemonic`, `getCryptoTypes`, `getPreferredCryptoType`, `isCodeSet`, `savePin`, `isPinCorrect`, `getMetaAccount`, `selectMetaAccount`, `selectedMetaAccount`, `deleteAccount`, `updateMetaAccountPositions`, `chainFlow`, `nodesFlow`, `getNode`, `getLanguages`, `getSelectedLanguage`, `changeSelectedLanguage`, `addNode`, `updateNode`, `getAccountsByNetworkTypeWithSelectedNode`, `selectNodeAndAccount`, `selectNode`, `deleteNode`, `getChainAddress`, `removeDeactivatedMetaAccounts`, `switchToNotDeactivatedAccountIfNeeded`, `hasSecretsAccounts`, `hasCustomChainAccounts`, `deleteProxiedMetaAccountsByChain`, `findMetaAccount`. 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. — feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountInteractor.kt:15
  • `AccountRepository` declares 57 abstract methods: `getEncryptionTypes`, `getNode`, `getSelectedNodeOrDefault`, `selectNode`, `getDefaultNode`, `selectAccount`, `getSelectedMetaAccount`, `getMetaAccount`, `metaAccountFlow`, `selectedMetaAccountFlow`, `findMetaAccount`, `accountNameFor`, `hasActiveMetaAccounts`, `allMetaAccountsFlow`, `activeMetaAccountsFlow`, `metaAccountsByTypeFlow`, `metaAccountBalancesFlow`, `selectMetaAccount`, `updateMetaAccountName`, `isAccountSelected`, `deleteAccount`, `getAccounts`, `getAccount`, `getAccountOrNull`, `getMyAccounts`, `isCodeSet`, `savePinCode`, `getPinCode`, `generateMnemonic`, `isBiometricEnabledFlow`, `isBiometricEnabled`, `setBiometricOn`, `setBiometricOff`, `nodesFlow`, `updateAccountsOrdering`, `getLanguages`, `selectedLanguage`, `changeLanguage`, `addNode`, `updateNode`, and 17 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. — feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountRepository.kt:19
  • `AccountDataSource` declares 42 abstract methods: `getAuthTypeFlow`, `saveAuthType`, `getAuthType`, `savePinCode`, `getPinCode`, `saveSelectedNode`, `getSelectedNode`, `anyAccountSelected`, `saveSelectedAccount`, `getSelectedMetaAccount`, `selectedMetaAccountFlow`, `findMetaAccount`, `accountNameFor`, `allMetaAccountsFlow`, `activeMetaAccountsFlow`, `metaAccountsWithBalancesFlow`, `metaAccountBalancesFlow`, `selectMetaAccount`, `updateAccountPositions`, `getSelectedLanguage`, `changeSelectedLanguage`, `accountExists`, `getMetaAccount`, `getMetaAccountType`, `metaAccountFlow`, `updateMetaAccountName`, `deleteMetaAccount`, `insertMetaAccountWithChainAccounts`, `insertMetaAccountFromSecrets`, `insertChainAccount`, `hasActiveMetaAccounts`, `removeDeactivatedMetaAccounts`, `getActiveMetaAccounts`, `getActiveMetaIds`, `getAllMetaAccounts`, `getMetaAccountsByIds`, `hasMetaAccountsCountOfTypeFlow`, `getActiveMetaAccountsQuantity`, `hasSecretsAccounts`, `deleteProxiedMetaAccountsByChain`, 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. — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/datasource/AccountDataSource.kt:24
  • `AccountFeatureComponent` declares 42 abstract methods: `advancedEncryptionComponentFactory`, `importAccountComponentFactory`, `backupMnemonicComponentFactory`, `createWalletBackupPasswordFactory`, `syncWalletsBackupPasswordFactory`, `changeBackupPasswordComponentFactory`, `restoreCloudBackupFactory`, `checkCloudBackupPasswordFactory`, `restoreCloudBackupPasswordFactory`, `pincodeComponentFactory`, `confirmMnemonicComponentFactory`, `walletManagmentComponentFactory`, `switchWalletComponentFactory`, `selectWalletComponentFactory`, `selectAddressComponentFactory`, `chainAddressSelectorComponent`, `selectMultipleWalletsComponentFactory`, `selectSingleWalletComponentFactory`, `delegatedAccountUpdatesFactory`, `accountDetailsComponentFactory`, `connectionsComponentFactory`, `nodeDetailsComponentFactory`, `languagesComponentFactory`, `addNodeComponentFactory`, `exportSeedFactory`, `exportJsonPasswordFactory`, `inject`, `createWatchOnlyComponentFactory`, `changeWatchAccountComponentFactory`, `startImportParitySignerComponentFactory`, `scanImportParitySignerComponentFactory`, `previewImportParitySignerComponentFactory`, `finishImportParitySignerComponentFactory`, `showSignParitySignerComponentFactory`, `scanSignParitySignerComponentFactory`, `startCreateWallet`, `manualBackupSelectWallet`, `manualBackupWarning`, `manualBackupSecrets`, `manualBackupSelectAccount`, 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. — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureComponent.kt:85
  • `AccountFeatureDependencies` declares 46 abstract methods: `sharedPreferences`, `logger`, `analyticsService`, `appLinksProvider`, `preferences`, `encryptedPreferences`, `resourceManager`, `iconGenerator`, `clipboardManager`, `context`, `deviceVibrator`, `userDao`, `nodeDao`, `multisigOperationsDao`, `languagesHolder`, `socketSingleRequestExecutor`, `jsonMapper`, `addressIconGenerator`, `currencyInteractor`, `cachingIconGenerator`, `random`, `secretStoreV1`, `secretStoreV2`, `metaAccountDao`, `chainRegistry`, `extrinsicBuilderFactory`, `rpcCalls`, `imageLoader`, `backgroundAccessObserver`, `appVersionProvider`, `validationExecutor`, `updateNotificationsInteractor`, `safeModeService`, `web3NamesInteractor`, `twoFactorVerificationService`, `twoFactorVerificationExecutor`, `computationalCache`, `getProxyRepository`, `cloudBackupService`, `provideActionBottomSheetLauncherFactory`, and 6 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. — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureDependencies.kt:85
  • `AccountRouter` declares 44 abstract methods: `openWelcomeScreen`, `openMain`, `openCreatePincode`, `openMnemonicScreen`, `openAdvancedSettings`, `openConfirmMnemonicOnCreate`, `openWallets`, `openSwitchWallet`, `openDelegatedAccountsUpdates`, `openNodes`, `openCreateWallet`, `openWalletDetails`, `openNodeDetails`, `openAddNode`, `openChangeWatchAccount`, `getExportMnemonicDelayedNavigation`, `getExportSeedDelayedNavigation`, `getExportJsonDelayedNavigation`, `exportJsonAction`, `openImportAccountScreen`, `openImportOptionsScreen`, `returnToWallet`, `finishExportFlow`, `openScanImportParitySigner`, `openPreviewImportParitySigner`, `openFinishImportParitySigner`, `openScanParitySignerSignature`, `finishParitySignerFlow`, `openAddLedgerChainAccountFlow`, `openCreateCloudBackupPassword`, `restoreCloudBackup`, `openSyncWalletsBackupPassword`, `openChangeBackupPasswordFlow`, `openRestoreBackupPassword`, `openChangeBackupPassword`, `openManualBackupSelectAccount`, `openManualBackupConditions`, `openManualBackupSecrets`, `openManualBackupAdvancedSecrets`, `openChainAddressSelector`, and 4 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/AccountRouter.kt:18
  • `AssetsFeatureComponent` declares 32 abstract methods: `balanceListComponentFactory`, `balanceDetailComponentFactory`, `chooseAmountComponentFactory`, `confirmTransferComponentFactory`, `transactionDetailComponentFactory`, `swapDetailComponentFactory`, `transactionHistoryComponentFactory`, `rewardDetailComponentFactory`, `poolRewardDetailComponentFactory`, `extrinsicDetailComponentFactory`, `receiveComponentFactory`, `assetSearchComponentFactory`, `manageTokensComponentFactory`, `addTokenSelectChainComponentFactory`, `addTokenEnterInfoComponentFactory`, `sendFlowComponent`, `swapFlowComponent`, `receiveFlowComponent`, `buyFlowComponent`, `sellFlowComponent`, `giftsFlowComponent`, `tradeProviderListComponent`, `tradeWebComponent`, `networkBuyFlowComponent`, `networkSellFlowComponent`, `networkReceiveFlowComponent`, `networkSendFlowComponent`, `topUpCardComponentFactory`, `networkGiftsFlowComponent`, `novaCardComponentFactory`, `waitingNovaCardTopUpComponentFactory`, `inject`. 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. — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureComponent.kt:69
  • `AssetsFeatureDependencies` declares 55 abstract methods: `assetVisibilityRepository`, `assetVisibilityUseCase`, `showReceivedAssetUseCase`, `web3NamesInteractor`, `contributionsInteractor`, `contributionsRepository`, `locksDao`, `currencyInteractor`, `currencyRepository`, `metaAccountGroupingInteractor`, `accountInteractor`, `preferences`, `encryptedPreferences`, `resourceManager`, `iconGenerator`, `clipboardManager`, `contentResolver`, `accountRepository`, `networkCreator`, `signer`, `logger`, `jsonMapper`, `addressIconGenerator`, `appLinksProvider`, `qrCodeGenerator`, `fileProvider`, `externalAccountActions`, `httpExceptionHandler`, `addressDisplayUseCase`, `chainRegistry`, `defaultAssetsRepository`, `remoteStorageSource`, `localStorageSource`, `extrinsicService`, `imageLoader`, `selectedAccountUseCase`, `validationExecutor`, `eventsRepository`, `walletRepository`, `feeLoaderMixinFactory`, and 15 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. — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureDependencies.kt:134
  • `AssetsRouter` declares 49 abstract methods: `openAssetDetails`, `finishTradeOperation`, `back`, `openFilter`, `openSend`, `openConfirmTransfer`, `openTransferDetail`, `openExtrinsicDetail`, `openRewardDetail`, `openPoolRewardDetail`, `openSwapDetail`, `openSwitchWallet`, `openSelectAddress`, `openSelectSingleWallet`, `openSelectMultipleWallets`, `openReceive`, `openAssetSearch`, `openManageTokens`, `openAddTokenEnterInfo`, `openAddTokenSelectChain`, `openSendFlow`, `openReceiveFlow`, `openBuyFlow`, `openSellFlow`, `openBuyFlowFromSendFlow`, `openNfts`, `finishAddTokenFlow`, `openWalletConnectSessions`, `openWalletConnectScan`, `openSwapTab`, `returnToMainScreen`, `closeSendFlow`, `openNovaCard`, `openAwaitingCardCreation`, `closeNovaCard`, `openSendNetworks`, `openReceiveNetworks`, `openBuyNetworks`, `openSellNetworks`, `openGiftsNetworks`, and 9 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. — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/AssetsRouter.kt:14
  • `CrowdloanFeatureDependencies` declares 28 abstract methods: `contributionDao`, `assetVisibilityUseCase`, `accountUpdaterScope`, `selectedAccountUseCase`, `walletConstants`, `storageCache`, `imageLoader`, `accountRepository`, `addressIconGenerator`, `appLinksProvider`, `walletRepository`, `tokenRepository`, `resourceManager`, `externalAccountActions`, `networkApiCreator`, `httpExceptionHandler`, `gson`, `addressxDisplayUseCase`, `extrinsicService`, `validationExecutor`, `remoteStorageSource`, `localStorageSource`, `chainStateRepository`, `chainRegistry`, `preferences`, `secretStoreV2`, `customDialogDisplayer`, `feeLoaderMixinFactory`. 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. — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/di/CrowdloanFeatureDependencies.kt:46
  • `DAppFeatureDependencies` declares 20 abstract methods: `analyticsService`, `currencyRepository`, `accountRepository`, `resourceManager`, `appLinksProvider`, `selectedAccountUseCase`, `addressIconGenerator`, `gson`, `chainRegistry`, `imageLoader`, `feeLoaderMixinFactory`, `extrinsicService`, `tokenRepository`, `secretStoreV2`, `extrinsicGson`, `apiCreator`, `runtimeVersionsRepository`, `dappAuthorizationDao`, `browserHostSettingsDao`, `toastMessageManager`. 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. — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureDependencies.kt:45
  • `GovernanceFeatureComponent` declares 29 abstract methods: `referendaListFactory`, `referendaSearchFactory`, `referendumDetailsFactory`, `descriptionFactory`, `referendumInfoFactory`, `referendumFullDetailsFactory`, `setupReferendumVoteFactory`, `setupTinderGovVoteFactory`, `confirmReferendumVoteFactory`, `confirmTinderGovVoteFactory`, `referendumVotersFactory`, `confirmGovernanceUnlockFactory`, `governanceLocksOverviewFactory`, `delegateListFactory`, `delegateSearchFactory`, `delegateDetailsFactory`, `votedReferendaFactory`, `removeVoteFactory`, `delegateDelegatorsFactory`, `yourDelegationsFactory`, `newDelegationChooseTracks`, `selectGovernanceTracks`, `newDelegationChooseAmountFactory`, `newDelegationConfirmFactory`, `revokeDelegationChooseTracksFactory`, `revokeDelegationConfirmFactory`, `referendaFiltersFactory`, `tinderGovCardsFactory`, `tinderGovBasketFactory`. 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. — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureComponent.kt:58
  • `GovernanceRouter` declares 37 abstract methods: `openReferendum`, `openReferendaSearch`, `openReferendaFilters`, `openDAppBrowser`, `openReferendumDescription`, `openReferendumFullDetails`, `openReferendumVoters`, `openSetupReferendumVote`, `openSetupTinderGovVote`, `openConfirmGovernanceUnlock`, `openConfirmVoteReferendum`, `openGovernanceLocksOverview`, `backToReferendumDetails`, `finishUnlockFlow`, `openWalletDetails`, `openAddDelegation`, `openYourDelegations`, `openDelegateDetails`, `openVotedReferenda`, `openDelegateFullDescription`, `openBecomingDelegateTutorial`, `openRemoveVotes`, `openDelegateDelegators`, `openNewDelegationChooseTracks`, `openNewDelegationChooseAmount`, `openNewDelegationConfirm`, `backToYourDelegations`, `openRevokeDelegationChooseTracks`, `openRevokeDelegationsConfirm`, `openDelegateSearch`, `openSelectGovernanceTracks`, `openTinderGovCards`, `openTinderGovBasket`, `openConfirmTinderGovVote`, `backToTinderGovCards`, `openReferendumInfo`, `openReferendumFromDeepLink`. 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. — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/GovernanceRouter.kt:22
  • `NftFeatureDependencies` declares 17 abstract methods: `analyticsService`, `accountRepository`, `resourceManager`, `selectedAccountUseCase`, `addressIconGenerator`, `gson`, `chainRegistry`, `imageLoader`, `externalAccountActions`, `addressDisplayUseCase`, `feeLoaderMixinFactory`, `extrinsicService`, `tokenRepository`, `apiCreator`, `nftDao`, `remoteStorageSource`, `exceptionHandler`. 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. — feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/di/NftFeatureDependencies.kt:24
  • `SettingsRouter` declares 21 abstract methods: `openWallets`, `openNetworks`, `openNetworkDetails`, `openCustomNode`, `openPushNotificationSettings`, `openCurrencies`, `openLanguages`, `openAppearance`, `openPrivacy`, `openChangePinCode`, `openWalletDetails`, `openSwitchWallet`, `openWalletConnectScan`, `openWalletConnectSessions`, `openCloudBackupSettings`, `openManualBackup`, `addNetwork`, `openCreateNetworkFlow`, `finishCreateNetworkFlow`, `openEditNetwork`, `returnToWallet`. 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. — feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/SettingsRouter.kt:8
  • `StakingRepository` declares 18 abstract methods: `eraStartSessionIndex`, `eraLength`, `getActiveEraIndex`, `getCurrentEraIndex`, `getHistoryDepth`, `observeActiveEraIndex`, `getElectedValidatorsExposure`, `getValidatorPrefs`, `getSlashes`, `getSlashingSpan`, `stakingStateFlow`, `ledgerFlow`, `ledger`, `getRewardDestination`, `minimumNominatorBond`, `maxNominators`, `nominatorsCount`, `getEraRewardAllocation`. 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. — feature-staking-api/src/main/java/io/novafoundation/nova/feature_staking_api/domain/api/StakingRepository.kt:21
  • `StakingFeatureComponent` declares 81 abstract methods: `bittensorStakeAmountComponentFactory`, `bittensorStakeConfirmComponentFactory`, `bittensorDetailsComponentFactory`, `bittensorExitAmountComponentFactory`, `bittensorExitReviewComponentFactory`, `bittensorSubnetPositionComponentFactory`, `bittensorRootClaimComponentFactory`, `bittensorSubnetComponentFactory`, `bittensorSelectUnstakePositionComponentFactory`, `bittensorSelectValidatorComponentFactory`, `bittensorValidatorInfoComponentFactory`, `bittensorValidatorFiltersComponentFactory`, `bittensorSubnetDetailsComponentFactory`, `bittensorSubnetAmountComponentFactory`, `bittensorSubnetReviewComponentFactory`, `dashboardComponentFactory`, `moreStakingOptionsFactory`, `startStakingLandingComponentFactory`, `setupAmountMultiStakingComponentFactory`, `setupStakingType`, `confirmMultiStakingComponentFactory`, `searchCustomValidatorsComponentFactory`, `customValidatorsSettingsComponentFactory`, `reviewCustomValidatorsComponentFactory`, `selectCustomValidatorsComponentFactory`, `startChangeValidatorsComponentFactory`, `selectPoolComponentFactory`, `searchPoolComponentFactory`, `recommendedValidatorsComponentFactory`, `stakingComponentFactory`, `stakingPeriodComponentFactory`, `confirmStakingComponentFactory`, `confirmNominationsComponentFactory`, `validatorDetailsComponentFactory`, `payoutsListFactory`, `payoutDetailsFactory`, `confirmPayoutFactory`, `selectBondMoreFactory`, `confirmBondMoreFactory`, `selectUnbondFactory`, and 41 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. — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureComponent.kt:145
  • `StakingFeatureDependencies` declares 44 abstract methods: `responseCacheDao`, `currencyRepository`, `analyticsService`, `usdRateRepository`, `assetVisibilityUseCase`, `logger`, `contextManager`, `computationalCache`, `accountRepository`, `storageCache`, `addressIconGenerator`, `appLinksProvider`, `walletRepository`, `tokenRepository`, `resourceManager`, `extrinsicBuilderFactory`, `eventsRepository`, `substrateCalls`, `externalAccountActions`, `assetCache`, `accountStakingDao`, `accountUpdateScope`, `stakingTotalRewardsDao`, `networkApiCreator`, `httpExceptionHandler`, `walletConstants`, `gson`, `addressxDisplayUseCase`, `extrinsicService`, `validationExecutor`, `remoteStorageSource`, `localStorageSource`, `localIdentity`, `chainRegistry`, `imageLoader`, `preferences`, `feeLoaderMixinFactory`, `sharedPreferences`, `stakingRewardPeriodDao`, `enoughTotalToStayAboveEDValidationFactory`, and 4 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:98
  • `MythosBindsModule` declares 20 abstract methods: `bindUserStakeRepository`, `bindStakingRepository`, `bindSessionRepository`, `bindMythosCandidateRepository`, `bindCollatorProvider`, `bindUserStakeUseCase`, `bindStakeSummaryInteractor`, `bindUnbondingInteractor`, `bindAlertsInteractor`, `bindUserRewardsInteractor`, `bindRedeemInteractor`, `bindStartStakingInteractor`, `bindUnbondInteractor`, `bindClaimRewardsInteractor`, `bindCurrentCollatorsInteractor`, `bindMythosCollatorFormatter`, `bindBlockNumberUseCase`, `bindValidationFormatter`, `bindMainPotMatcherFactory`, `bindMythosClaimPendingRewardsUseCase`. 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. — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/mythos/MythosBindsModule.kt:47
  • `StakingRouter` declares 61 abstract methods: `openChainStakingMain`, `openStartChangeValidators`, `openRecommendedValidators`, `openSelectCustomValidators`, `openCustomValidatorsSettings`, `openSearchCustomValidators`, `openReviewCustomValidators`, `openValidatorDetails`, `openConfirmStaking`, `openConfirmNominations`, `returnToStakingMain`, `openSwitchWallet`, `openPayouts`, `openPayoutDetails`, `openConfirmPayout`, `openBondMore`, `openConfirmBondMore`, `openSelectUnbond`, `openConfirmUnbond`, `openRedeem`, `openControllerAccount`, `back`, `openConfirmSetController`, `openCustomRebond`, `openConfirmRebond`, `openCurrentValidators`, `returnToCurrentValidators`, `openChangeRewardDestination`, `openConfirmRewardDestination`, `openWalletDetails`, `openRebag`, `openStakingPeriods`, `openSetupStakingType`, `openSelectPool`, `openSearchPool`, `finishSetupValidatorsFlow`, `finishSetupPoolFlow`, `finishRedeemFlow`, `openAddStakingProxy`, `openConfirmAddStakingProxy`, and 21 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. — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/StakingRouter.kt:36
  • `WalletFeatureDependencies` declares 42 abstract methods: `chainAssetVisibilityDao`, `metaAccountSettingsDao`, `preferences`, `encryptedPreferences`, `resourceManager`, `iconGenerator`, `clipboardManager`, `contentResolver`, `accountRepository`, `assetsDao`, `tokenDao`, `provideLocksDao`, `operationDao`, `currencyDao`, `contributionDao`, `networkCreator`, `signer`, `logger`, `jsonMapper`, `addressIconGenerator`, `appLinksProvider`, `qrCodeGenerator`, `fileProvider`, `externalAccountActions`, `httpExceptionHandler`, `phishingAddressesDao`, `rpcCalls`, `accountUpdateScope`, `addressDisplayUseCase`, `chainRegistry`, `defaultAssetsRepository`, `remoteStorageSource`, `localStorageSource`, `extrinsicService`, `extrinsicServiceFactory`, `imageLoader`, `selectedAccountUseCase`, `validationExecutor`, `eventsRepository`, `coinPriceDao`, 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. — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureDependencies.kt:70

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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

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

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

DM1 · Aggregate boundaries6.8 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

  • `PolkadotVaultScanFormat` references the aggregate root `SecretQrFormat` directly (via `secretQrFormat`) — hold its `SecretQrFormatId` instead. — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/paritySigner/connect/scan/PolkadotVaultScanFormat.kt:14

What to do

  • Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate8.6 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

  • `RealProfile3AccessTokenProvider.identityFor` saves `Profile3TokenStore`, `AttestationKeyPairStore` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/RealProfile3AccessTokenProvider.kt:123
  • `RealProfile3AccessTokenProvider.loadToken` saves `AttestationKeyPairStore`, `Profile3TokenStore` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/RealProfile3AccessTokenProvider.kt:135

What to do

  • Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state3.3 / 10Weak✓ Tool-verified

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

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

  • `AccountLocal`'s public constructor takes `address`, `username`, `publicKey` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AccountLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountLocal.kt:8
  • `AccountStakingLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AccountStakingLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:11
  • `AnalyticsEventLocal`'s public constructor takes `eventId`, `name`, `propsJson` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AnalyticsEventLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AnalyticsEventLocal.kt:7
  • `AssetLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AssetLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:22
  • `BalanceHoldLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BalanceHoldLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:35
  • `BalanceLockLocal`'s public constructor takes `chainId`, `type` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BalanceLockLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:34
  • `BrowserHostSettingsLocal`'s public constructor takes `hostUrl` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BrowserHostSettingsLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserHostSettingsLocal.kt:9
  • `BrowserTabLocal`'s public constructor takes `id`, `currentUrl`, `pageName`, `pageIconPath`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BrowserTabLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserTabLocal.kt:20
  • `ChainAssetVisibilityLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainAssetVisibilityLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:39
  • `CoinPriceLocal`'s public constructor takes `priceId`, `currencyId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CoinPriceLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:10
  • `ContributionLocal`'s public constructor takes `chainId`, `sourceId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ContributionLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:8
  • `CurrencyLocal`'s public constructor takes `code`, `name`, `symbol`, `coingeckoId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CurrencyLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CurrencyLocal.kt:11
  • `DappAuthorizationLocal`'s public constructor takes `baseUrl`, `dAppTitle` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `DappAuthorizationLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/DappAuthorizationLocal.kt:9
  • `ExternalBalanceLocal`'s public constructor takes `chainId`, `subtype` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ExternalBalanceLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:27
  • `FavouriteDAppLocal`'s public constructor takes `url`, `label`, `icon` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `FavouriteDAppLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/FavouriteDAppLocal.kt:10
  • `GiftLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `GiftLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:27
  • `GovernanceDAppLocal`'s public constructor takes `chainId`, `name`, `referendumUrlV1`, `referendumUrlV2`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `GovernanceDAppLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GovernanceDAppLocal.kt:7
  • `MultisigOperationCallLocal`'s public constructor takes `chainId`, `callHash`, `callInstance` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MultisigOperationCallLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/MultisigOperationCallLocal.kt:26
  • `NftLocal`'s public constructor takes `identifier`, `chainId`, `collectionId`, `instanceId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NftLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:11
  • `NodeLocal`'s public constructor takes `name`, `link` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NodeLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NodeLocal.kt:7
  • `PhishingAddressLocal`'s public constructor takes `publicKey` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PhishingAddressLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingAddressLocal.kt:7
  • `PhishingSiteLocal`'s public constructor takes `host` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PhishingSiteLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingSiteLocal.kt:7
  • `ResponseCacheLocal`'s public constructor takes `normalizedUrl`, `payload`, `key` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ResponseCacheLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ResponseCacheLocal.kt:26
  • `StakingDashboardItemLocal`'s public constructor takes `chainId`, `stakingType`, `estimatedEarnings` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `StakingDashboardItemLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingDashboardItemLocal.kt:36
  • `StakingRewardPeriodLocal`'s public constructor takes `chainId`, `stakingType`, `periodType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `StakingRewardPeriodLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingRewardPeriodLocal.kt:7
  • `StorageEntryLocal`'s public constructor takes `storageKey`, `content`, `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `StorageEntryLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/StorageEntryLocal.kt:9
  • `TinderGovBasketItemLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TinderGovBasketItemLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TinderGovBasketItemLocal.kt:28
  • `TinderGovVotingPowerLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TinderGovVotingPowerLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TinderGovVotingPowerLocal.kt:28
  • `TokenLocal`'s public constructor takes `tokenSymbol` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TokenLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TokenLocal.kt:8
  • `TotalRewardLocal`'s public constructor takes `chainId`, `stakingType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TotalRewardLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TotalRewardLocal.kt:11
  • `WalletConnectPairingLocal`'s public constructor takes `pairingTopic` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WalletConnectPairingLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/WalletConnectPairingLocal.kt:20
  • `ChainAssetLocal`'s public constructor takes `chainId`, `name`, `symbol`, `priceId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainAssetLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainAssetLocal.kt:25
  • `ChainExplorerLocal`'s public constructor takes `chainId`, `name`, `extrinsic`, `account`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainExplorerLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainExplorerLocal.kt:24
  • `ChainExternalApiLocal`'s public constructor takes `chainId`, `parameters`, `url` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainExternalApiLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainExternalApiLocal.kt:24
  • `ChainLocal`'s public constructor takes `id`, `parentId`, `name`, `icon`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainLocal.kt:14
  • `ChainNodeLocal`'s public constructor takes `chainId`, `url`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainNodeLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainNodeLocal.kt:25
  • `ChainRuntimeInfoLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainRuntimeInfoLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainRuntimeInfoLocal.kt:22
  • `NodeSelectionPreferencesLocal`'s public constructor takes `chainId`, `selectedNodeUrl` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NodeSelectionPreferencesLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/NodeSelectionPreferencesLocal.kt:25
  • `ChainAccountLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainAccountLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/ChainAccountLocal.kt:28
  • `MetaAccountLocal`'s public constructor takes `name`, `globallyUniqueId`, `typeExtras` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MetaAccountLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/MetaAccountLocal.kt:25

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

  • `AccountLocal.publicKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountLocal.kt:11
  • `AccountStakingLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:12
  • `AccountStakingLocal.chainAssetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:13
  • `AnalyticsEventLocal.eventId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AnalyticsEventLocal.kt:9
  • `AssetLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:23
  • `AssetLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:24
  • `AssetLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:25
  • `BalanceHoldLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:36
  • `BalanceHoldLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:37
  • `BalanceHoldLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:38
  • `BalanceLockLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:35
  • `BalanceLockLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:36
  • `BalanceLockLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:37
  • `BrowserTabLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserTabLocal.kt:22
  • `ChainAssetVisibilityLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:40
  • `ChainAssetVisibilityLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:41
  • `ChainAssetVisibilityLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:42
  • `CoinPriceLocal.priceId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:11
  • `CoinPriceLocal.currencyId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:12
  • `ContributionLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:9
  • `ContributionLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:10
  • `ContributionLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:11
  • `ContributionLocal.sourceId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:14
  • `CurrencyLocal.coingeckoId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CurrencyLocal.kt:18
  • `DappAuthorizationLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/DappAuthorizationLocal.kt:11
  • `ExternalBalanceLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:28
  • `ExternalBalanceLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:29
  • `ExternalBalanceLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:30
  • `GiftLocal.creatorMetaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:30
  • `GiftLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:31
  • `GiftLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:32
  • `GovernanceDAppLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GovernanceDAppLocal.kt:8
  • `MetaAccountSettingsLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/MetaAccountSettingsLocal.kt:26
  • `MultisigOperationCallLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/MultisigOperationCallLocal.kt:27
  • `MultisigOperationCallLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/MultisigOperationCallLocal.kt:28
  • `NftLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:15
  • `NftLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:16
  • `NftLocal.collectionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:17
  • `NftLocal.instanceId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:18
  • `PhishingAddressLocal.publicKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingAddressLocal.kt:8

What to do

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

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

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

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

  • `AccountLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountLocal.kt:8
  • `AccountStakingLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:11
  • `AnalyticsEventLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AnalyticsEventLocal.kt:7
  • `AssetLocal` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:22
  • `BalanceHoldLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:35
  • `BalanceLockLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:34
  • `BrowserHostSettingsLocal` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserHostSettingsLocal.kt:9
  • `BrowserTabLocal` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserTabLocal.kt:20
  • `ChainAssetVisibilityLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:39
  • `CoinPriceLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:10
  • `ContributionLocal` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:8
  • `CurrencyLocal` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/CurrencyLocal.kt:11
  • `DappAuthorizationLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/DappAuthorizationLocal.kt:9
  • `ExternalBalanceLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:27
  • `FavouriteDAppLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/FavouriteDAppLocal.kt:10
  • `GiftLocal` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:27
  • `GovernanceDAppLocal` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/GovernanceDAppLocal.kt:7
  • `MetaAccountSettingsLocal` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/MetaAccountSettingsLocal.kt:25
  • `MultisigOperationCallLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/MultisigOperationCallLocal.kt:26
  • `NftLocal` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:11
  • `NodeLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/NodeLocal.kt:7
  • `PhishingAddressLocal` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingAddressLocal.kt:7
  • `PhishingSiteLocal` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingSiteLocal.kt:7
  • `ResponseCacheLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/ResponseCacheLocal.kt:26
  • `StakingDashboardItemLocal` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingDashboardItemLocal.kt:36
  • `StakingRewardPeriodLocal` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingRewardPeriodLocal.kt:7
  • `StorageEntryLocal` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/StorageEntryLocal.kt:9
  • `TinderGovBasketItemLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TinderGovBasketItemLocal.kt:28
  • `TinderGovVotingPowerLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TinderGovVotingPowerLocal.kt:28
  • `TokenLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TokenLocal.kt:8
  • `TotalRewardLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/TotalRewardLocal.kt:11
  • `WalletConnectPairingLocal` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/WalletConnectPairingLocal.kt:20
  • `ChainAssetLocal` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainAssetLocal.kt:25
  • `ChainExplorerLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainExplorerLocal.kt:24
  • `ChainExternalApiLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainExternalApiLocal.kt:24
  • `ChainLocal` is an aggregate/entity with 23 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainLocal.kt:14
  • `ChainNodeLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainNodeLocal.kt:25
  • `ChainRuntimeInfoLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/ChainRuntimeInfoLocal.kt:22
  • `NodeSelectionPreferencesLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/NodeSelectionPreferencesLocal.kt:25
  • `ChainAccountLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/ChainAccountLocal.kt:28

What to do

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

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

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

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

  • `GiftLocal` exposes publicly writable state (id). — core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:27
  • `NodeLocal` exposes publicly writable state (id). — core-db/src/main/java/io/novafoundation/nova/core_db/model/NodeLocal.kt:7
  • `MetaAccountLocal` exposes publicly writable state (id). — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/MetaAccountLocal.kt:25

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

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

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

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 11 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
  • `bindings/hydra-dx-math/rust/Cargo.toml` 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`. — bindings/hydra-dx-math/rust/Cargo.toml:9

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.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

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

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

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

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `Retrofit.Builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — common/src/main/java/io/novafoundation/nova/common/data/network/NetworkApiCreator.kt:17

What to do

  • Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

X25 · Inert configuration knob7.0 / 10Strong✓ Tool-verified

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.

  • `AssetBalance.decimals` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — bindings/hydra-dx-math/rust/src/lib.rs:43

What to do

  • Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` 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.

X3 · Exception handling6.4 / 10Adequate✓ Tool-verified

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. (×12) — runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/BaseStorageQueryContext.kt:264, runtime/src/main/java/io/novafoundation/nova/runtime/explorer/BlockExplorerLinkFormatter.kt:37, runtime/src/main/java/io/novafoundation/nova/runtime/explorer/BlockExplorerLinkFormatter.kt:55, …
  • `catch (failure: 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. (×3) — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationHttp.kt:50, infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3Interceptor.kt:96, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorSubnetValidatorRepository.kt:258

What to do

  • Swallowed exception (caught, then discarded)
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.

X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health84.5StrongSolid.
Architecture68.7Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity58.3Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness39.3Weak — gated by P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security53.8Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling49.0Weak — gated by DM2, DM4, DM11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 4 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.

  • D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 1 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 included — 62 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~39411 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D12 Dependency Hygiene — Not scored — 68 Maven/Gradle manifest(s) were read, stating a version for 6 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • 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.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • 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, .py, .rs, 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
  • 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) — 197 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM8 Value-object opportunities — not scored — the deterministic rule found 1 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — Not assessed, and this one is on us: 20 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, 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 17 current-state document(s) make no claim of a kind M4 checks. 28 claim(s) of kinds M4 does not check were not checked (path 7, environment variable 21); M4 checks only links and versions and artefact counts.
  • 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 JavaScript/TypeScript, JVM, Rust source (69 module(s), 6161 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.
  • 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 data present for 1 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • 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.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 96 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 22 more in this group — see findings.md.
D35 · Change Coupling · Boundary-crossing change coupling · ×12
  • Boundary-crossing change coupling: SwapService.kt ↔ AssetConversionExchange.kt feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/swap/SwapService.kt:1 — `feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/swap/SwapService.kt` (context feature-swap-api) and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt` (context feature-swap-impl) sit in DIFFERENT parts of the tree yet change together 94% of the time (15 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `8dc2ab32` Warm up fee visitor to improve asset to receive loading; `f877f3ab` Cross chain quoting WIP; `f7014154` Fixed validation and swap service syncing — run `git show` on any of them.
  • Boundary-crossing change coupling: SwapService.kt ↔ AssetExchange.kt feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/swap/SwapService.kt:1 — `feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/swap/SwapService.kt` (context feature-swap-api) and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/AssetExchange.kt` (context feature-swap-impl) sit in DIFFERENT parts of the tree yet change together 81% of the time (13 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `f877f3ab` Cross chain quoting WIP; `f7014154` Fixed validation and swap service syncing; `4c1137f2` Fix stable swap quoting — run `git show` on any of them.
  • Boundary-crossing change coupling: SwapQuote.kt ↔ AssetConversionExchange.kt feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuote.kt:1 — `feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuote.kt` (context feature-swap-api) and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt` (context feature-swap-impl) sit in DIFFERENT parts of the tree yet change together 68% of the time (13 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `8e2f4fcb` Estimate execution time; `394dfcfa` Change terminology in SubmissionOrigin; `8061115e` Cross chain fees work — run `git show` on any of them.
  • Boundary-crossing change coupling: AccountInfoRepository.kt ↔ WalletRepositoryImpl.kt feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/data/repository/AccountInfoRepository.kt:1 — `feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/data/repository/AccountInfoRepository.kt` (context feature-wallet-api) and `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt` (context feature-wallet-impl) sit in DIFFERENT parts of the tree yet change together 68% of the time (13 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `0f209aee` Do not allow insufficient asset out swaps; `83918cad` Refactoring (at that commit the files were still `feature-wallet-impl/src/main/java/jp/co/soramitsu/feature_wallet_impl/data/network/blockchain/SubstrateRemoteSource.kt` and `feature-wallet-impl/src/main/java/jp/co/soramitsu/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt`); `0319cc65` remove account deps from wallet (#175) (at that commit the files were still `feature-wallet-impl/src/main/java/jp/co/soramitsu/feature_wallet_impl/data/network/blockchain/SubstrateRemoteSource.kt` and `feature-wallet-impl/src/main/java/jp/co/soramitsu/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt`) — run `git show` on any of them.
  • Boundary-crossing change coupling: SwapQuoteArgs.kt ↔ AssetConversionExchange.kt feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuoteArgs.kt:1 — `feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuoteArgs.kt` (context feature-swap-api) and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt` (context feature-swap-impl) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `4a9fc753` Multi-chain swap fees mechanism (domain); `2c5b30de` WIP SwapService interface finalized; `ced775c3` WIP — run `git show` on any of them.
  • Boundary-crossing change coupling: AccountInteractor.kt ↔ AccountRepositoryImpl.kt feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountInteractor.kt:1 — `feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountInteractor.kt` (context feature-account-api) and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/AccountRepositoryImpl.kt` (context feature-account-impl) sit in DIFFERENT parts of the tree yet change together 66% of the time (40 of the 61 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 40 shared commits counted here, the most recent 3 are `79ae97af` Fixed crash on delete chain; `5b370388` Cloud backup bugs; `ec2dae2c` Revisit usages of all accounts (#1318) — run `git show` on any of them.
  • Boundary-crossing change coupling: SubstrateSdkExt.kt ↔ BaseStorageQueryContext.kt common/src/main/java/io/novafoundation/nova/common/utils/SubstrateSdkExt.kt:1 — `common/src/main/java/io/novafoundation/nova/common/utils/SubstrateSdkExt.kt` (context common) and `runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/BaseStorageQueryContext.kt` (context runtime) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `53305533` Fix storage key encoding introduced after updating to K2 compiler (#2…; `e8c1538a` Fix storage key encoding introduced after updating to K2 compiler (#2…; `f37767e0` Feature/improve call splitter (#1902) — run `git show` on any of them.
  • Boundary-crossing change coupling: AccountFeatureApi.kt ↔ AccountFeatureModule.kt feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/di/AccountFeatureApi.kt:1 — `feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/di/AccountFeatureApi.kt` (context feature-account-api) and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureModule.kt` (context feature-account-impl) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `2a8a146d` Fix/signing is over issue (#2097); `0594f884` Use storage to check commission asset + forbid custom fee for proxy; `839dc39e` Proxies syncing in progress — run `git show` on any of them.
  • Boundary-crossing change coupling: TransferAssetValidationFailureUi.kt ↔ BaseAssetTransfers.kt feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/validation/transfers/TransferAssetValidationFailureUi.kt:1 — `feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/validation/transfers/TransferAssetValidationFailureUi.kt` (context feature-wallet-api) and `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/transfers/BaseAssetTransfers.kt` (context feature-wallet-impl) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `04b4e934` Consider delivery fee for proxied account (at that commit the file was still `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/TransferAssetValidationFailureUi.kt`); `0d936188` Warn users when sending tokens to system account (#1063) (at that commit the file was still `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/TransferAssetValidationFailureUi.kt`); `1ad028c2` Support v9420 assets update (#918) (at that commit the file was still `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/TransferAssetValidationFailureUi.kt`) — run `git show` on any of them.
  • Boundary-crossing change coupling: AccountRepository.kt ↔ AccountDataSource.kt feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountRepository.kt:1 — `feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountRepository.kt` (context feature-account-api) and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/datasource/AccountDataSource.kt` (context feature-account-impl) sit in DIFFERENT parts of the tree yet change together 54% of the time (26 of the 48 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 26 shared commits counted here, the most recent 3 are `d5d1b597` Update multisig push settings on meta account delete; `79ae97af` Fixed crash on delete chain; `bbf8f278` Sync generic ledger accounts for newly available chains — run `git show` on any of them.
  • Boundary-crossing change coupling: AccountInfoRepository.kt ↔ WalletFeatureModule.kt feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/data/repository/AccountInfoRepository.kt:1 — `feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/data/repository/AccountInfoRepository.kt` (context feature-wallet-api) and `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureModule.kt` (context feature-wallet-impl) sit in DIFFERENT parts of the tree yet change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `0f209aee` Do not allow insufficient asset out swaps; `70cf9302` Statemine/realtime updates (#134) (at that commit the file was still `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/SubstrateRemoteSource.kt`); `0319cc65` remove account deps from wallet (#175) (at that commit the files were still `feature-wallet-impl/src/main/java/jp/co/soramitsu/feature_wallet_impl/data/network/blockchain/SubstrateRemoteSource.kt` and `feature-wallet-impl/src/main/java/jp/co/soramitsu/feature_wallet_impl/di/WalletFeatureModule.kt`) — run `git show` on any of them.
  • Boundary-crossing change coupling: SubstrateSdkExt.kt ↔ ExtrinsicBuilderExt.kt common/src/main/java/io/novafoundation/nova/common/utils/SubstrateSdkExt.kt:1 — `common/src/main/java/io/novafoundation/nova/common/utils/SubstrateSdkExt.kt` (context common) and `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/ExtrinsicBuilderExt.kt` (context feature-wallet-impl) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `3c7b3b9a` Support inferred runtime api call for fee payment (at that commit the file was still `common/src/main/java/io/novafoundation/nova/common/utils/FearlessLibExt.kt`); `4ee6c793` Detect multi-location version for unversioned locations usage (at that commit the file was still `common/src/main/java/io/novafoundation/nova/common/utils/FearlessLibExt.kt`); `5bd7fceb` Swap/asset conversion directions (#1153) (at that commit the file was still `common/src/main/java/io/novafoundation/nova/common/utils/FearlessLibExt.kt`) — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×7
  • Orphaned knowledge bindings/hydra-dx-math/rust/src/lib.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
  • Orphaned knowledge feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/PayoutRepository.kt:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureComponent.kt:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/setup/SetupYieldBoostViewModel.kt:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/sync/RealExternalAccountsSyncService.kt:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AX4 · Dependency direction · Dependency-rule violation · ×3
  • Dependency-rule violation: :feature-ledger-core (Domain) → :core-api (Web) — `:feature-ledger-core` is a Domain project but references `:core-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • Dependency-rule violation: :feature-swap-core (Domain) → :feature-swap-core:api (Web) — `:feature-swap-core` is a Domain project but references `:feature-swap-core:api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • Dependency-rule violation: :feature-swap-core (Domain) → :core-api (Web) — `:feature-swap-core` is a Domain project but references `:core-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D11 · Test Reliability · Test declared unreliable · ×1
  • Test declared unreliable: runtime/src/test/java/io/novafoundation/nova/runtime/multiNetwork/runtime/RuntimeSyncServiceTest.kt runtime/src/test/java/io/novafoundation/nova/runtime/multiNetwork/runtime/RuntimeSyncServiceTest.kt:47 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Flaky tests due to concurrency issues". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D14 · License Compliance · Banned license · ×1
  • Banned license: array-bytes — `array-bytes` 6.2.3 is published on crates.io under `Apache-2.0/GPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×1
  • Aggregate holds a reference to another aggregate: PolkadotVaultScanFormat.secretQrFormat feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/paritySigner/connect/scan/PolkadotVaultScanFormat.kt:14 — `PolkadotVaultScanFormat` references the aggregate root `SecretQrFormat` directly (via `secretQrFormat`) — hold its `SecretQrFormatId` instead.
Serious — 744 finding(s)
D17 · Explicit Debt · TodoComment · ×66
  • TodoComment runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/RemoteStorageQueryContext.kt:66 — // TODO To this is not quite efficient implementation as we are de-multiplexing arrived keys into multiple flows (in sdk) and them merging them back — 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 runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/ExtrinsicValidityUseCase.kt:39 — // TODO this should calculate remaining time based on Era from payload — 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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/RealBalanceLocksRepository.kt:18 — // TODO refactoring - repository should not depend on other repository. MetaId should be passed to repository arguments — 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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt:210 — // TODO adapt for ethereum chains — 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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt:221 — // TODO adapt for ethereum chains — 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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/legacy/LegacyCrossChainWeigher.kt:58 — // TODO: Currently message doesn't contain setTopic command in the end. It will come with XCMv3 support — 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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/statemine/StatemineAssetBalance.kt:35 — // TODO Migrate low-level subscription to storage to AssetsApi — 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 feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/requests/Base.kt:36 — // TODO this code is untested since no dapp currently use redirect param — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/mixin/fee/v2/FeeUI.kt:14 — // TODO We use <V> here since star projections cause 1.7.21 compiler to fail — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/mixin/amountChooser/AmountChooserMixin.kt:63 — // TODO revisit this flag. Seems to only be used in SwapMainSettingsViewModel and its purpose and semantics looks unclear — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/Asset.kt:12 — // TODO we should remove duplication between Asset and ChainAssetBalance in regard to calculation of different balance types — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/Asset.kt:33 — // TODO move to runtime storage — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/Asset.kt:67 — // TODO move to runtime storage — 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 core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:34 — // TODO move to runtime storage — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/Asset.kt:57 — // TODO maybe move to extension fields? — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/Token.kt:30 — // TODO move out of the class when Context Receivers will be stable — 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 feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/data/network/blockhain/assets/tranfers/AssetTransfers.kt:60 — // TODO this is too specialized for this module — 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 feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/repository/SwapTransactionHistoryRepository.kt:34 — // TODO swap history — 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 feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/hydraDx/HydraDxAssetExchange.kt:647 — // Todo Hydration fee support from extrinsic — 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 feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/fee/chains/HydrationFeePaymentProvider.kt:59 — // Todo Hydration fee support from extrinsic — 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 feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapFee.kt:80 — // TODO deducting `fromCountedTowardsEd` from max amount is over-conservative — 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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/landing/StartStakingLandingViewModel.kt:323 — // TODO this should be provided by a particular staking implementation — 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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/networkInfo/NetworkInfoComponent.kt:39 — // TODO network info — 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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/setup/SetupYieldBoostViewModel.kt:411 — // TODO this creates an invalid state — 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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mappers/Validator.kt:92 — // TODO relaychain subtitles — 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.
  • + 41 more in this group — see findings.md.
DM11 · Constructible invalid state · Constructible in an invalid state · ×40
  • Constructible in an invalid state: AccountLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountLocal.kt:8 — `AccountLocal`'s public constructor takes `address`, `username`, `publicKey` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AccountLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: AccountStakingLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:11 — `AccountStakingLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AccountStakingLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: AnalyticsEventLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AnalyticsEventLocal.kt:7 — `AnalyticsEventLocal`'s public constructor takes `eventId`, `name`, `propsJson` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AnalyticsEventLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: AssetLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:22 — `AssetLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AssetLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: BalanceHoldLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:35 — `BalanceHoldLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BalanceHoldLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: BalanceLockLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:34 — `BalanceLockLocal`'s public constructor takes `chainId`, `type` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BalanceLockLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: BrowserHostSettingsLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserHostSettingsLocal.kt:9 — `BrowserHostSettingsLocal`'s public constructor takes `hostUrl` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BrowserHostSettingsLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: BrowserTabLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserTabLocal.kt:20 — `BrowserTabLocal`'s public constructor takes `id`, `currentUrl`, `pageName`, `pageIconPath`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BrowserTabLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ChainAssetVisibilityLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:39 — `ChainAssetVisibilityLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChainAssetVisibilityLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: CoinPriceLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:10 — `CoinPriceLocal`'s public constructor takes `priceId`, `currencyId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CoinPriceLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ContributionLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:8 — `ContributionLocal`'s public constructor takes `chainId`, `sourceId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ContributionLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: CurrencyLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/CurrencyLocal.kt:11 — `CurrencyLocal`'s public constructor takes `code`, `name`, `symbol`, `coingeckoId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CurrencyLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: DappAuthorizationLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/DappAuthorizationLocal.kt:9 — `DappAuthorizationLocal`'s public constructor takes `baseUrl`, `dAppTitle` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `DappAuthorizationLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ExternalBalanceLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:27 — `ExternalBalanceLocal`'s public constructor takes `chainId`, `subtype` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ExternalBalanceLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: FavouriteDAppLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/FavouriteDAppLocal.kt:10 — `FavouriteDAppLocal`'s public constructor takes `url`, `label`, `icon` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `FavouriteDAppLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: GiftLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:27 — `GiftLocal`'s public constructor takes `chainId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `GiftLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: GovernanceDAppLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/GovernanceDAppLocal.kt:7 — `GovernanceDAppLocal`'s public constructor takes `chainId`, `name`, `referendumUrlV1`, `referendumUrlV2`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `GovernanceDAppLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: MultisigOperationCallLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/MultisigOperationCallLocal.kt:26 — `MultisigOperationCallLocal`'s public constructor takes `chainId`, `callHash`, `callInstance` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MultisigOperationCallLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: NftLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:11 — `NftLocal`'s public constructor takes `identifier`, `chainId`, `collectionId`, `instanceId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NftLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: NodeLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/NodeLocal.kt:7 — `NodeLocal`'s public constructor takes `name`, `link` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NodeLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: PhishingAddressLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingAddressLocal.kt:7 — `PhishingAddressLocal`'s public constructor takes `publicKey` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PhishingAddressLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: PhishingSiteLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingSiteLocal.kt:7 — `PhishingSiteLocal`'s public constructor takes `host` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PhishingSiteLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ResponseCacheLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ResponseCacheLocal.kt:26 — `ResponseCacheLocal`'s public constructor takes `normalizedUrl`, `payload`, `key` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ResponseCacheLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: StakingDashboardItemLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingDashboardItemLocal.kt:36 — `StakingDashboardItemLocal`'s public constructor takes `chainId`, `stakingType`, `estimatedEarnings` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `StakingDashboardItemLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: StakingRewardPeriodLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingRewardPeriodLocal.kt:7 — `StakingRewardPeriodLocal`'s public constructor takes `chainId`, `stakingType`, `periodType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `StakingRewardPeriodLocal` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • + 15 more in this group — see findings.md.
DM4 · Rich vs anemic model · Anemic entity · ×40
  • Anemic entity: AccountLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountLocal.kt:8 — `AccountLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AccountStakingLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:11 — `AccountStakingLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AnalyticsEventLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AnalyticsEventLocal.kt:7 — `AnalyticsEventLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AssetLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:22 — `AssetLocal` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: BalanceHoldLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:35 — `BalanceHoldLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: BalanceLockLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:34 — `BalanceLockLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: BrowserHostSettingsLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserHostSettingsLocal.kt:9 — `BrowserHostSettingsLocal` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: BrowserTabLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserTabLocal.kt:20 — `BrowserTabLocal` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ChainAssetVisibilityLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:39 — `ChainAssetVisibilityLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CoinPriceLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:10 — `CoinPriceLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ContributionLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:8 — `ContributionLocal` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CurrencyLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/CurrencyLocal.kt:11 — `CurrencyLocal` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: DappAuthorizationLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/DappAuthorizationLocal.kt:9 — `DappAuthorizationLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ExternalBalanceLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ExternalBalanceLocal.kt:27 — `ExternalBalanceLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: FavouriteDAppLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/FavouriteDAppLocal.kt:10 — `FavouriteDAppLocal` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: GiftLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:27 — `GiftLocal` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: GovernanceDAppLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/GovernanceDAppLocal.kt:7 — `GovernanceDAppLocal` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: MetaAccountSettingsLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/MetaAccountSettingsLocal.kt:25 — `MetaAccountSettingsLocal` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: MultisigOperationCallLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/MultisigOperationCallLocal.kt:26 — `MultisigOperationCallLocal` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: NftLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/NftLocal.kt:11 — `NftLocal` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: NodeLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/NodeLocal.kt:7 — `NodeLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: PhishingAddressLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingAddressLocal.kt:7 — `PhishingAddressLocal` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: PhishingSiteLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/PhishingSiteLocal.kt:7 — `PhishingSiteLocal` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ResponseCacheLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/ResponseCacheLocal.kt:26 — `ResponseCacheLocal` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: StakingDashboardItemLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/StakingDashboardItemLocal.kt:36 — `StakingDashboardItemLocal` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • + 15 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×26
  • Duplicated block (7 lines × 2) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:119 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:119-125 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:119-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:119` 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 × 2) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:153 — feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:153-159 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:183-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:153` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/GovernanceUnlockInteractor.kt:156 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/GovernanceUnlockInteractor.kt:156-162 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/RealVoteReferendumInteractor.kt:144-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/voters/list/VotersAdapter.kt:111 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/voters/list/VotersAdapter.kt:111-117 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/voters/list/VotersAdapter.kt:149-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `item` to `ExpandableVoterRVItem) = with(binder` in one and `DelegatorVoterRVItem) = with(binder` 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, `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/voters/list/VotersAdapter.kt:148` calls `bind`, `with` and `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/voters/list/VotersAdapter.kt:109` 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) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:14 — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:14-20 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:42-48 — 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 `infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:14` 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 × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorExitValidationUi.kt:100 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorExitValidationUi.kt:100-106 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorStakeValidationUi.kt:93-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:145 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:145-151 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:177-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:145` 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 × 2) analytics/src/main/java/io/novafoundation/nova/analytics/AnalyticsLog.kt:14 — analytics/src/main/java/io/novafoundation/nova/analytics/AnalyticsLog.kt:14-20 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationLog.kt:19-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/warning/ManualBackupWarningFragment.kt:57 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/warning/ManualBackupWarningFragment.kt:57-63 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/backup/BackupMnemonicFragment.kt:61-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/extrinsic/ExtrinsicDetailViewModel.kt:112 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/extrinsic/ExtrinsicDetailViewModel.kt:112-118 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/reward/direct/RewardDetailViewModel.kt:59-65 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitInteractor.kt:419 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitInteractor.kt:419-425 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorRootClaimInteractor.kt:204-210 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:222 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:222-228 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.kt:215-221 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/selectCollatorSettings/SelectMythCollatorSettingsFragment.kt:49 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/selectCollatorSettings/SelectMythCollatorSettingsFragment.kt:49-55 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/collator/settings/SelectCollatorSettingsFragment.kt:52-58 — 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 `viewModel` to `SelectMythCollatorSettingsViewModel` in one and `SelectCollatorSettingsViewModel` 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 (7 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:195 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:195-201 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/StartParachainStakingViewModel.kt:198-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/orml/OrmlAssetHistory.kt:48 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/orml/OrmlAssetHistory.kt:48-54 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/statemine/StatemineAssetHistory.kt:48-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) analytics/src/main/java/io/novafoundation/nova/analytics/transport/AnalyticsIdentity.kt:23 — analytics/src/main/java/io/novafoundation/nova/analytics/transport/AnalyticsIdentity.kt:23-29 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationIdentity.kt:39-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:231 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:231-237 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/multisig/MultisigOperationsNavigator.kt:28-34 — 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 `payload` to `ImportAccountPayload` in one and `MultisigOperationDetailsPayload` 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 (7 lines × 2) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/dApp/DAppSearchCommunicatorImpl.kt:15 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/dApp/DAppSearchCommunicatorImpl.kt:15-21 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/topup/TopUpAddressCommunicatorImpl.kt:15-21 — 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 `request` to `SearchPayload` in one and `TopUpAddressPayload` 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 (7 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/fee/types/assetHub/AssetHubFeePaymentFetcher.kt:42 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/fee/types/assetHub/AssetHubFeePaymentFetcher.kt:42-48 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt:142-148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/selectChain/SelectChainAdapter.kt:24 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/selectChain/SelectChainAdapter.kt:24-30 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/list/MultisigPendingOperationsAdapter.kt:41-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1DAppsRepository.kt:17 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1DAppsRepository.kt:17-23 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2DAppsRepository.kt:17-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseAmount/RealNewDelegationChooseAmountInteractor.kt:168 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseAmount/RealNewDelegationChooseAmountInteractor.kt:168-174 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/removeVotes/RealRemoveTrackVotesInteractor.kt:66-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/view/GovernanceLocksView.kt:30 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/view/GovernanceLocksView.kt:30-36 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/view/ManageStakingActionView.kt:53-59 — 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: `R` names `io.novafoundation.nova.feature_governance_impl.R` in one and `io.novafoundation.nova.feature_staking_impl.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:87 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:87-93 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenSentNotificationHandler.kt:89-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/RealAddStakingProxyInteractor.kt:33 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/RealAddStakingProxyInteractor.kt:33-39 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/remove/RemoveStakingProxyInteractor.kt:30-36 — 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.
  • + 1 more in this group — see findings.md.
D35 · Change Coupling · Change coupling · ×24
  • Change coupling: UnsupportedDelegationsRepository.kt ↔ Gov2DelegationsRepository.kt feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/UnsupportedDelegationsRepository.kt:1 — `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/UnsupportedDelegationsRepository.kt` and `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/Gov2DelegationsRepository.kt` change together 100% of the time (12 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `dab84475` Fixed timepoint for details and voted referenda list (#2143); `39a15479` Enable openGov delegation feature only when subquery is present; `26adbbd8` Fix/your delegations query (#741) — run `git show` on any of them.
  • Change coupling: SwapConfirmationFragment.kt ↔ SwapConfirmationModule.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt:1 — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt` and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/di/SwapConfirmationModule.kt` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `5e43a5d5` Execution screen ui ready; `131147f9` Route short view; `1163770e` Fixed pr notes — run `git show` on any of them.
  • Change coupling: WalletFeatureDependencies.kt ↔ WalletFeatureModule.kt feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureDependencies.kt:1 — `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureDependencies.kt` and `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureModule.kt` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4ee6c793` Detect multi-location version for unversioned locations usage; `8e2f4fcb` Estimate execution time; `1902b9f5` Clean code — run `git show` on any of them.
  • Change coupling: WelcomeFragment.kt ↔ WelcomeModule.kt feature-onboarding-impl/src/main/java/io/novafoundation/nova/feature_onboarding_impl/presentation/welcome/WelcomeFragment.kt:1 — `feature-onboarding-impl/src/main/java/io/novafoundation/nova/feature_onboarding_impl/presentation/welcome/WelcomeFragment.kt` and `feature-onboarding-impl/src/main/java/io/novafoundation/nova/feature_onboarding_impl/presentation/welcome/di/WelcomeModule.kt` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `7ba30d4a` Feature/consent screen (#2307); `3480faf5` Use legacy app when there is no flag in config; `ed7e25ff` Removed hardware wallet chooser — run `git show` on any of them.
  • Change coupling: SwapConfirmationModule.kt ↔ SwapMainSettingsModule.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/di/SwapConfirmationModule.kt:1 — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/di/SwapConfirmationModule.kt` and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/di/SwapMainSettingsModule.kt` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `8c3fa5a4` Navigation fixes and swap execution improvements WIP; `131147f9` Route short view; `c6079c53` Add description bottom sheets — run `git show` on any of them.
  • Change coupling: DAppBrowserFragment.kt ↔ DAppBrowserModule.kt feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/browser/main/DAppBrowserFragment.kt:1 — `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/browser/main/DAppBrowserFragment.kt` and `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/browser/main/di/DAppBrowserModule.kt` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `0c53923e` Wallet connect pairing dapp handling (#1929); `1698f105` Fixed permission requesting in nova card; `5b63db19` Permission asker for web view — run `git show` on any of them.
  • Change coupling: RootDependencies.kt ↔ RootViewModel.kt app/src/main/java/io/novafoundation/nova/app/root/di/RootDependencies.kt:1 — `app/src/main/java/io/novafoundation/nova/app/root/di/RootDependencies.kt` and `app/src/main/java/io/novafoundation/nova/app/root/presentation/RootViewModel.kt` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `7e86be09` Fixed sell tokens and nova card restriction issues (#2038); `6eea7e0f` Fix/nova card deep link ms (#2027); `2d20dca5` Bug fixes — run `git show` on any of them.
  • Change coupling: RootDependencies.kt ↔ RootActivityModule.kt app/src/main/java/io/novafoundation/nova/app/root/di/RootDependencies.kt:1 — `app/src/main/java/io/novafoundation/nova/app/root/di/RootDependencies.kt` and `app/src/main/java/io/novafoundation/nova/app/root/presentation/di/RootActivityModule.kt` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `7e86be09` Fixed sell tokens and nova card restriction issues (#2038); `6eea7e0f` Fix/nova card deep link ms (#2027); `2d20dca5` Bug fixes — run `git show` on any of them.
  • Change coupling: AccountRepositoryImpl.kt ↔ AccountInteractorImpl.kt feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/AccountRepositoryImpl.kt:1 — `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/AccountRepositoryImpl.kt` and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/AccountInteractorImpl.kt` change together 64% of the time (47 of the 74 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 47 shared commits counted here, the most recent 3 are `79ae97af` Fixed crash on delete chain; `5b370388` Cloud backup bugs; `ec2dae2c` Revisit usages of all accounts (#1318) — run `git show` on any of them.
  • Change coupling: ConfirmMnemonicFragment.kt ↔ MnemonicContainerView.kt feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/confirm/ConfirmMnemonicFragment.kt:1 — `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/confirm/ConfirmMnemonicFragment.kt` and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/confirm/view/MnemonicContainerView.kt` change together 63% of the time (12 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `ac53b32c` Confirm mnemonic screen; `d4e84495` Backup mnemonic screen; `1ec5b3b7` Redesign/confirm mnemonic (#81) — run `git show` on any of them.
  • Change coupling: SwapInteractor.kt ↔ SwapValidations.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/interactor/SwapInteractor.kt:1 — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/interactor/SwapInteractor.kt` and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidations.kt` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `f4c4b6a0` Added MaxInRatio validation for swap; `8b9f6f18` Added warning for high price impact; `03c66e2a` Fixed sufficient balance validation in case when native asset = fee a… — run `git show` on any of them.
  • Change coupling: AccountInteractor.kt ↔ AccountRepository.kt feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountInteractor.kt:1 — `feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountInteractor.kt` and `feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountRepository.kt` change together 62% of the time (38 of the 61 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 38 shared commits counted here, the most recent 3 are `79ae97af` Fixed crash on delete chain; `5b370388` Cloud backup bugs; `ec2dae2c` Revisit usages of all accounts (#1318) — run `git show` on any of them.
  • Change coupling: SwapConfirmationFragment.kt ↔ SwapMainSettingsModule.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt:1 — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt` and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/di/SwapMainSettingsModule.kt` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `131147f9` Route short view; `c6079c53` Add description bottom sheets; `fd456b57` Swap confirmation validation + swap max, swap min — run `git show` on any of them.
  • Change coupling: ExtrinsicBuilderExt.kt ↔ RealCrossChainTransactor.kt feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/ExtrinsicBuilderExt.kt:1 — `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/ExtrinsicBuilderExt.kt` and `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/RealCrossChainTransactor.kt` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4ee6c793` Detect multi-location version for unversioned locations usage; `9047b504` Implemented xcm delivery fee; `fafc345b` Fix - xTokens with xcm v3 (#903) — run `git show` on any of them.
  • Change coupling: SwapPayloadValidation.kt ↔ SwapValidationFailureUi.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapPayloadValidation.kt:1 — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapPayloadValidation.kt` and `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `0f209aee` Do not allow insufficient asset out swaps; `4cab1cf2` Only use BUY for the first segment and use SELL for the rest. Use new…; `74cb023d` Clean code — run `git show` on any of them.
  • Change coupling: AccountFeatureDependencies.kt ↔ CustomFeeModule.kt feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureDependencies.kt:1 — `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureDependencies.kt` and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/modules/CustomFeeModule.kt` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `013ef2fd` Support fallback price for Hydration fee conversion (#1895); `b5d4068b` Fix swap quote loading on a fresh install (#1849); `4ee6c793` Detect multi-location version for unversioned locations usage — run `git show` on any of them.
  • Change coupling: BalanceDetailFragment.kt ↔ BalanceDetailModule.kt feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/detail/BalanceDetailFragment.kt:1 — `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/detail/BalanceDetailFragment.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/detail/di/BalanceDetailModule.kt` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `8965e5e7` Determine gifting state on balance details. Refactor fee capability t…; `9f94ffb5` Handle Buy sell buttons states; `620feecf` Added bottom sheet selector — run `git show` on any of them.
  • Change coupling: RootActivity.kt ↔ RootActivityModule.kt app/src/main/java/io/novafoundation/nova/app/root/presentation/RootActivity.kt:1 — `app/src/main/java/io/novafoundation/nova/app/root/presentation/RootActivity.kt` and `app/src/main/java/io/novafoundation/nova/app/root/presentation/di/RootActivityModule.kt` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `7e86be09` Fixed sell tokens and nova card restriction issues (#2038); `6eea7e0f` Fix/nova card deep link ms (#2027); `cc17899d` Implement safe mode (#697) — run `git show` on any of them.
  • Change coupling: AssetsFeatureModule.kt ↔ BalanceListViewModel.kt feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureModule.kt:1 — `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureModule.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListViewModel.kt` change together 50% of the time (12 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `c5db0e07` NW-1978: Make gifts unsupported for ms accounts (#2225); `7e86be09` Fixed sell tokens and nova card restriction issues (#2038); `6eea7e0f` Fix/nova card deep link ms (#2027) — run `git show` on any of them.
  • Change coupling: GoogleDriveBackupStorage.kt ↔ RealCloudBackupService.kt feature-cloud-backup-impl/src/main/java/io/novafoundation/nova/feature_cloud_backup_impl/data/cloudStorage/GoogleDriveBackupStorage.kt:1 — `feature-cloud-backup-impl/src/main/java/io/novafoundation/nova/feature_cloud_backup_impl/data/cloudStorage/GoogleDriveBackupStorage.kt` and `feature-cloud-backup-impl/src/main/java/io/novafoundation/nova/feature_cloud_backup_impl/domain/RealCloudBackupService.kt` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `476adc4d` Do not encrypt public backup data (#1456); `b8b4a0e0` Delete backup; `8b8499b1` Fetch backup — run `git show` on any of them.
  • Change coupling: SwapQuote.kt ↔ SwapQuoteArgs.kt feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuote.kt:1 — `feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuote.kt` and `feature-swap-api/src/main/java/io/novafoundation/nova/feature_swap_api/domain/model/SwapQuoteArgs.kt` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4a9fc753` Multi-chain swap fees mechanism (domain); `2c5b30de` WIP SwapService interface finalized; `ced775c3` WIP — run `git show` on any of them.
  • Change coupling: BrowserTabService.kt ↔ BrowserTabSession.kt feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/BrowserTabService.kt:1 — `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/BrowserTabService.kt` and `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/models/BrowserTabSession.kt` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `2d20dca5` Bug fixes; `0d2f7425` Fixed navigation issues (at that commit the files were still `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/BrowserTabPoolService.kt` and `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/models/PageSession.kt`); `6bea1599` Add memory usage restriction for tabs (at that commit the files were still `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/BrowserTabPoolService.kt` and `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/tabs/models/PageSession.kt`) — run `git show` on any of them.
  • Change coupling: SettingsFeatureDependencies.kt ↔ SettingsFeatureModule.kt feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/di/SettingsFeatureDependencies.kt:1 — `feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/di/SettingsFeatureDependencies.kt` and `feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/di/SettingsFeatureModule.kt` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `4fefceb6` Som minor fixes; `b227de62` Appearance screen; `fdc1aa37` Pre-Configured networks — run `git show` on any of them.
  • Change coupling: CreateCloudBackupPasswordInteractor.kt ↔ EnterCloudBackupInteractor.kt feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/cloudBackup/createPassword/CreateCloudBackupPasswordInteractor.kt:1 — `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/cloudBackup/createPassword/CreateCloudBackupPasswordInteractor.kt` and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/cloudBackup/enterPassword/EnterCloudBackupInteractor.kt` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `2ad7ecfd` Current session (at that commit the file was still `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/cloudBackup/enterPassword/RestoreCloudBackupInteractor.kt`); `bfdaca9e` Clean code (at that commit the file was still `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/cloudBackup/enterPassword/RestoreCloudBackupInteractor.kt`); `cfcd7bcb` Fix import flow (at that commit the file was still `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/cloudBackup/enterPassword/RestoreCloudBackupInteractor.kt`) — run `git show` on any of them.
D3 · God Classes · TooManyMethods · ×21
  • TooManyMethods: Navigator app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:115 — TooManyMethods — 122 methods. The bar is 30 methods; this is 92 over it, 4.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BittensorModule feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/BittensorModule.kt:148 — TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.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: CommonModule common/src/main/java/io/novafoundation/nova/common/di/modules/CommonModule.kt:136 — TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.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: AccountRepositoryImpl feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/AccountRepositoryImpl.kt:48 — TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. Most of these members implement interfaces.AccountRepository (57 of 60 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: RelayStakingNavigator app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/staking/relaychain/RelayStakingNavigator.kt:79 — TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. Most of these members implement presentation.StakingRouter (60 of 61 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: StakingFeatureModule feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureModule.kt:146 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: AccountFeatureModule feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureModule.kt:201 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: SwapMainSettingsViewModel feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt:150 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ChainDao core-db/src/main/java/io/novafoundation/nova/core_db/dao/ChainDao.kt:22 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: AccountDataSourceImpl feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/datasource/AccountDataSourceImpl.kt:57 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. Most of these members implement datasource.AccountDataSource (42 of 45 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: WalletFeatureModule feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureModule.kt:129 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RealSwapService feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/swap/RealSwapService.kt:140 — 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: GovernanceNavigator app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/governance/GovernanceNavigator.kt:48 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. Most of these members implement presentation.GovernanceRouter (37 of 38 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: BittensorOperationHistorySource feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorOperationHistorySource.kt:35 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: RealLocalAccountsCloudBackupFacade feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:51 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SettingsViewModel feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/settings/SettingsViewModel.kt:44 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DbModule core-db/src/main/java/io/novafoundation/nova/core_db/di/DbModule.kt:46 — 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: AppDatabase core-db/src/main/java/io/novafoundation/nova/core_db/AppDatabase.kt:248 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AccountInteractorImpl feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/AccountInteractorImpl.kt:26 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. Most of these members implement interfaces.AccountInteractor (31 of 35 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: StakingRepositoryImpl feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/StakingRepositoryImpl.kt:91 — 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: StartStakingLandingViewModel feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/landing/StartStakingLandingViewModel.kt:111 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×21
  • Edited copy of a member (13 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:19 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:19-31 | runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/chain/mappers/RemoteToLocalChainMappers.kt:245-258 — 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.
  • Edited copy of a member (13 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:5 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:5-17 | runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/chain/mappers/RemoteToLocalChainMappers.kt:260-272 — 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.
  • Edited copy of a member (13 corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:118 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:118-130 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:118-131 — 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.
  • Edited copy of a member (13 corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/moonbeam/main/MainFlowMoonbeamCustomization.kt:66 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/moonbeam/main/MainFlowMoonbeamCustomization.kt:66-78 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/moonbeam/main/MainFlowMoonbeamCustomization.kt:94-108 — 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.
  • Edited copy of a member (13 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/transfers/orml/OrmlAssetTransfers.kt:64 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/transfers/orml/OrmlAssetTransfers.kt:64-77 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/transfers/statemine/StatemineAssetTransfers.kt:78-90 — 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.
  • Edited copy of a member (13 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/dashboard/common/list/DashboardNoStakeAdapter.kt:29 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/dashboard/common/list/DashboardNoStakeAdapter.kt:29-41 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/setupStakingType/adapter/SetupStakingTypeAdapter.kt:32-44 — 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.
  • Edited copy of a member (13 corresponding lines) bindings/hydra-dx-math/rust/src/lib.rs:658 — bindings/hydra-dx-math/rust/src/lib.rs:658-670 | bindings/hydra-dx-math/rust/src/lib.rs:689-701 — 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.
  • Edited copy of a member (13 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/ConfirmReferendumVoteViewModel.kt:160 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/ConfirmReferendumVoteViewModel.kt:160-172 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tindergov/confirm/ConfirmTinderGovVoteViewModel.kt:172-186 — 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.
  • Edited copy of a member (13 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:366 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:366-378 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:393-405 — 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.
  • Edited copy of a member (13 corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanHeaderAdapter.kt:40 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanHeaderAdapter.kt:40-52 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/list/ReferendaListHeaderAdapter.kt:48-62 — 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.
  • Edited copy of a member (13 corresponding lines) runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:29 — runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:29-41 | runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:67-79 — 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.
  • Edited copy of a member (13 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/confirm/BittensorStakeConfirmViewModel.kt:238 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/confirm/BittensorStakeConfirmViewModel.kt:238-250 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.kt:798-810 — 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.
  • Edited copy of a member (13 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/custom/settings/CustomValidatorsSettingsFragment.kt:61 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/custom/settings/CustomValidatorsSettingsFragment.kt:61-75 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/custom/settings/CustomValidatorsSettingsFragment.kt:77-89 — 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.
  • Edited copy of a member (13 corresponding lines) feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/utils/stateMachine/states/AwaitPeerSecretsKeyExchangeState.kt:14 — feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/utils/stateMachine/states/AwaitPeerSecretsKeyExchangeState.kt:14-26 | feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/utils/stateMachine/states/InitialKeyExchangeState.kt:11-23 — 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.
  • Edited copy of a member (13 corresponding lines) feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/utils/common/KeyExchangeUtils.kt:34 — feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/utils/common/KeyExchangeUtils.kt:34-47 | feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/utils/common/KeyExchangeUtils.kt:49-61 — 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.
  • Edited copy of a member (13 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/polkassembly/v1/PolkassemblyV1ReferendaDataSource.kt:105 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/polkassembly/v1/PolkassemblyV1ReferendaDataSource.kt:105-117 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/subsquare/v1/SubSquareV1ReferendaDataSource.kt:52-64 — 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.
  • Edited copy of a member (13 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorGetAssetBinding.kt:17 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorGetAssetBinding.kt:17-30 | feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/mixin/getAsset/GetAssetOptionMixinUI.kt:10-22 — 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.
  • Edited copy of a member (13 corresponding lines) feature-xcm/impl/src/main/java/io/novafoundation/nova/feature_xcm_impl/converter/ForeignAssetsLocationConverter.kt:53 — feature-xcm/impl/src/main/java/io/novafoundation/nova/feature_xcm_impl/converter/ForeignAssetsLocationConverter.kt:53-65 | feature-xcm/impl/src/main/java/io/novafoundation/nova/feature_xcm_impl/converter/LocalAssetsLocationConverter.kt:63-75 — 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.
  • Edited copy of a member (13 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1ConvictionVotingRepository.kt:108 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1ConvictionVotingRepository.kt:108-120 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2ConvictionVotingRepository.kt:178-190 — 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.
  • Edited copy of a member (13 corresponding lines) runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/multisig/MultisigNode.kt:83 — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/multisig/MultisigNode.kt:83-96 | runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/proxy/ProxyNode.kt:78-90 — 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.
  • Edited copy of a member (13 corresponding lines) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/web3/metamask/states/DefaultMetamaskState.kt:274 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/web3/metamask/states/DefaultMetamaskState.kt:274-286 | feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/requests/evm/EvmWalletConnectRequestFactory.kt:70-84 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×20
  • Edited copy of a member (12 corresponding lines) feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:86 — feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:86-97 | feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/adapters/UpdateNotificationsAdapter.kt:45-57 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/common/GiftAnimationFactory.kt:25 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/common/GiftAnimationFactory.kt:25-36 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/common/GiftAnimationFactory.kt:41-52 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-banners-api/src/main/java/io/novafoundation/nova/feature_banners_api/presentation/view/switcher/SwitchersSetup.kt:53 — feature-banners-api/src/main/java/io/novafoundation/nova/feature_banners_api/presentation/view/switcher/SwitchersSetup.kt:53-64 | feature-banners-api/src/main/java/io/novafoundation/nova/feature_banners_api/presentation/view/switcher/SwitchersSetup.kt:66-77 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt:409 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt:409-425 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/hydraDx/HydraDxAssetExchange.kt:441-452 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/OffchainVotesExt.kt:29 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/OffchainVotesExt.kt:29-40 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/OffchainVotesExt.kt:42-53 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/deeplink/RealReferendumDetailsDeepLinkConfigurator.kt:22 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/deeplink/RealReferendumDetailsDeepLinkConfigurator.kt:22-33 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/details/deeplink/MultisigOperationDeepLinkConfigurator.kt:57-71 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/common/DelegationState.kt:20 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/common/DelegationState.kt:20-31 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/common/DelegationState.kt:36-48 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/RealVoteReferendumInteractor.kt:75 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/RealVoteReferendumInteractor.kt:75-86 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/RealVoteReferendumInteractor.kt:101-116 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) common/src/main/java/io/novafoundation/nova/common/presentation/scan/ScanView.kt:97 — common/src/main/java/io/novafoundation/nova/common/presentation/scan/ScanView.kt:97-108 | common/src/main/java/io/novafoundation/nova/common/presentation/scan/ScanView.kt:110-121 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/domain/paths/RealPathQuoter.kt:138 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/domain/paths/RealPathQuoter.kt:138-149 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/domain/paths/RealPathQuoter.kt:151-162 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/add/Declarations.kt:47 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/add/Declarations.kt:47-58 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/remove/Declarations.kt:29-42 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseTrack/RealChooseTrackInteractor.kt:83 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseTrack/RealChooseTrackInteractor.kt:83-94 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseTrack/RealChooseTrackInteractor.kt:96-107 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:182 — common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:182-193 | common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:205-217 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/integrityCheck/IntegrityCheckKeyPairService.kt:48 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/integrityCheck/IntegrityCheckKeyPairService.kt:48-59 | feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/utils/integrityCheck/IntegrityCheckKeyPairService.kt:61-72 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/tindergov/TinderGovBasketInteractor.kt:124 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/tindergov/TinderGovBasketInteractor.kt:124-135 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/tindergov/TinderGovInteractor.kt:132-143 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/confirm/ConfirmUnbondMythosViewModel.kt:162 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/confirm/ConfirmUnbondMythosViewModel.kt:162-173 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:239-250 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/xcm/dynamic/DynamicCrossChainTransfersConfigurationExt.kt:20 — feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/xcm/dynamic/DynamicCrossChainTransfersConfigurationExt.kt:20-34 | feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/model/xcm/legacy/LegacyCrossChainTransfersConfigurationExt.kt:36-47 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) web3names/src/main/java/io/novafoundation/nova/web3names/data/serviceEndpoint/W3NServiceEndpointHandlerV1.kt:26 — web3names/src/main/java/io/novafoundation/nova/web3names/data/serviceEndpoint/W3NServiceEndpointHandlerV1.kt:26-37 | web3names/src/main/java/io/novafoundation/nova/web3names/data/serviceEndpoint/W3NServiceEndpointHandlerV2.kt:28-39 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/overview/di/NovaCardModule.kt:83 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/overview/di/NovaCardModule.kt:83-95 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/trade/webInterface/di/TradeWebModule.kt:66-77 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) feature-proxy-api/src/main/java/io/novafoundation/nova/feature_proxy_api/domain/validators/ProxyIsNotDuplicationForAccount.kt:38 — feature-proxy-api/src/main/java/io/novafoundation/nova/feature_proxy_api/domain/validators/ProxyIsNotDuplicationForAccount.kt:38-49 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/setup/MinimumStakeValidation.kt:77-88 — 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.
D5 · Coupling · Unstable project · ×19
  • Unstable project :feature-account-impl — :feature-account-impl has instability 0.94 with 1 dependents.
  • Unstable project :feature-ahm-impl — :feature-ahm-impl has instability 0.88 with 1 dependents.
  • Unstable project :feature-assets — :feature-assets has instability 0.86 with 3 dependents.
  • Unstable project :feature-buy-impl — :feature-buy-impl has instability 0.89 with 1 dependents.
  • Unstable project :feature-cloud-backup-impl — :feature-cloud-backup-impl has instability 0.83 with 1 dependents.
  • Unstable project :feature-crowdloan-impl — :feature-crowdloan-impl has instability 0.88 with 1 dependents.
  • Unstable project :feature-dapp-impl — :feature-dapp-impl has instability 0.93 with 1 dependents.
  • Unstable project :feature-external-sign-impl — :feature-external-sign-impl has instability 0.88 with 1 dependents.
  • Unstable project :feature-gift-impl — :feature-gift-impl has instability 0.88 with 1 dependents.
  • Unstable project :feature-governance-impl — :feature-governance-impl has instability 0.91 with 1 dependents.
  • Unstable project :feature-ledger-impl — :feature-ledger-impl has instability 0.89 with 1 dependents.
  • Unstable project :feature-nft-impl — :feature-nft-impl has instability 0.88 with 1 dependents.
  • Unstable project :feature-onboarding-impl — :feature-onboarding-impl has instability 0.90 with 1 dependents.
  • Unstable project :feature-push-notifications — :feature-push-notifications has instability 0.82 with 2 dependents.
  • Unstable project :feature-settings-impl — :feature-settings-impl has instability 0.93 with 1 dependents.
  • Unstable project :feature-staking-impl — :feature-staking-impl has instability 0.94 with 1 dependents.
  • Unstable project :feature-swap-impl — :feature-swap-impl has instability 0.92 with 1 dependents.
  • Unstable project :feature-wallet-connect-impl — :feature-wallet-connect-impl has instability 0.92 with 1 dependents.
  • Unstable project :feature-wallet-impl — :feature-wallet-impl has instability 0.89 with 1 dependents.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×17
  • Edited copy of a member (16 corresponding lines) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:107 — feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:107-122 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:142-159 — 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) common/src/main/java/io/novafoundation/nova/common/mixin/actionAwaitable/ConfirmationDialog.kt:36 — common/src/main/java/io/novafoundation/nova/common/mixin/actionAwaitable/ConfirmationDialog.kt:36-51 | common/src/main/java/io/novafoundation/nova/common/mixin/actionAwaitable/ConfirmationDialog.kt:53-68 — 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) runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/BaseStorageQueryContext.kt:230 — runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/BaseStorageQueryContext.kt:230-246 | runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/BaseStorageQueryContext.kt:253-268 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorRetryController.kt:59 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorRetryController.kt:59-77 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorRetryController.kt:110-125 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/controller/set/ValidationFailureMessage.kt:11 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/controller/set/ValidationFailureMessage.kt:11-26 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/ValidationFailure.kt:12-34 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/full/ReferendumFullDetailsFragment.kt:95 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/full/ReferendumFullDetailsFragment.kt:95-111 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/full/ReferendumFullDetailsFragment.kt:113-128 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/NewDelegationConfirmViewModel.kt:205 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/NewDelegationConfirmViewModel.kt:205-226 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/revoke/confirm/RevokeDelegationConfirmViewModel.kt:183-198 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/confirm/ConfirmRebondViewModel.kt:126 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/confirm/ConfirmRebondViewModel.kt:126-143 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/custom/CustomRebondViewModel.kt:112-127 — 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/overview/webViewController/interceptors/CardCreationInterceptor.kt:43 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/overview/webViewController/interceptors/CardCreationInterceptor.kt:43-58 | feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/interceptors/mercuryo/RealMercuryoBuyRequestInterceptor.kt:41-56 — 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) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/domain/RealGiftsAccountSupportedUseCase.kt:27 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/domain/RealGiftsAccountSupportedUseCase.kt:27-43 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorImmediateExecution.kt:18-33 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/ValidationFailureMessage.kt:12 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/ValidationFailureMessage.kt:12-29 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rewardDestination/select/ValidationFailure.kt:12-27 — 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) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/validations/SwapIntermediateReceivesMeetEDValidation.kt:26 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/validations/SwapIntermediateReceivesMeetEDValidation.kt:26-41 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/validations/SwapSufficientAmountOutToStayAboveEDValidation.kt:16-37 — 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) common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:286 — common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:286-305 | common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:307-322 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/confirm/ConfirmUnbondMythosViewModel.kt:128 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/confirm/ConfirmUnbondMythosViewModel.kt:128-143 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/confirm/NominationPoolsConfirmBondMoreViewModel.kt:110-127 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/amount/di/BittensorStakeAmountModule.kt:57 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/amount/di/BittensorStakeAmountModule.kt:57-77 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/di/BittensorDetailsModule.kt:98-113 — 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/common/fee/Ui.kt:13 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/common/fee/Ui.kt:13-29 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/confirm/setupFeeLoading.kt:13-28 — 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) feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/sign/di/SignLedgerModule.kt:93 — feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/sign/di/SignLedgerModule.kt:93-110 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/connect/legacy/selectLedger/di/SelectLedgerImportLedgerModule.kt:62-77 — 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 (9 corresponding lines) · ×17
  • Edited copy of a member (9 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/LegacyDelegationScheduledRequestExecutor.kt:30 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/LegacyDelegationScheduledRequestExecutor.kt:30-38 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/LegacyDelegationScheduledRequestExecutor.kt:41-49 — 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/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:534 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:534-542 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:547-555 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/CandidatesRepository.kt:31 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/CandidatesRepository.kt:31-39 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/StakingRepositoryImpl.kt:226-234 — 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/common/buySell/BuySellSelectorMixin.kt:97 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/common/buySell/BuySellSelectorMixin.kt:97-105 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/common/buySell/BuySellSelectorMixin.kt:107-115 — 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) common/src/main/java/io/novafoundation/nova/common/di/modules/shared/MarkdownFullModule.kt:22 — common/src/main/java/io/novafoundation/nova/common/di/modules/shared/MarkdownFullModule.kt:22-31 | common/src/main/java/io/novafoundation/nova/common/di/modules/shared/MarkdownShortModule.kt:23-31 — 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) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/common/views/SwapAmountInputView.kt:93 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/common/views/SwapAmountInputView.kt:93-102 | feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/view/amount/ChooseAmountInputView.kt:90-98 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:192 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:192-202 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardParachainStakingUpdater.kt:133-141 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/StatefullComponent.kt:57 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/StatefullComponent.kt:57-69 | common/src/main/java/io/novafoundation/nova/common/mixin/actionAwaitable/ActionAwaitableProvider.kt:20-28 — 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) analytics/src/main/java/io/novafoundation/nova/analytics/di/AnalyticsFeatureHolder.kt:15 — analytics/src/main/java/io/novafoundation/nova/analytics/di/AnalyticsFeatureHolder.kt:15-24 | runtime/src/main/java/io/novafoundation/nova/runtime/di/RuntimeHolder.kt:14-22 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/ReferendumDetailsFragment.kt:97 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/ReferendumDetailsFragment.kt:97-105 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/full/ReferendumFullDetailsFragment.kt:68-76 — 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) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/welcome/PushWelcomeViewModel.kt:90 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/welcome/PushWelcomeViewModel.kt:90-98 | feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/networkManagement/networkList/preConfiguredNetworks/PreConfiguredNetworksViewModel.kt:113-122 — 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) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/common/HydrationBalanceFetcher.kt:148 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/common/HydrationBalanceFetcher.kt:148-156 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/orml/hydrationEvm/HydrationEvmOrmlAssetBalance.kt:141-152 — 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) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/ChangePasswordCloudBackupFailureToUi.kt:18 — feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/ChangePasswordCloudBackupFailureToUi.kt:18-28 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/CheckBackupAvailableFailureToUi.kt:16-24 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:106 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:106-114 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardParachainStakingUpdater.kt:120-128 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/controller/ControllerInteractor.kt:33 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/controller/ControllerInteractor.kt:33-41 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/rebond/RebondInteractor.kt:20-28 — 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) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/main/DappCategoriesAdapter.kt:31 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/main/DappCategoriesAdapter.kt:31-39 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/connect/legacy/fillWallet/FillWalletImportLedgerAdapter.kt:43-51 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeActions/parachain/ParachainStakeActionsComponent.kt:49 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeActions/parachain/ParachainStakeActionsComponent.kt:49-57 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeActions/parachain/turing/TuringStakeActionsComponent.kt:38-47 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×16
  • Low cohesion: RootActivity (LCOM4 8) app/src/main/java/io/novafoundation/nova/app/root/presentation/RootActivity.kt:28 — RootActivity'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: BalanceListViewModel (LCOM4 7) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListViewModel.kt:84 — BalanceListViewModel'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: MythosSharedComputation (LCOM4 7) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/common/MythosSharedComputation.kt:31 — MythosSharedComputation'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: BalanceDetailViewModel (LCOM4 5) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/detail/BalanceDetailViewModel.kt:86 — BalanceDetailViewModel'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: SelectDelegationTracksViewModel (LCOM4 5) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tracks/select/delegationTracks/SelectDelegationTracksViewModel.kt:32 — SelectDelegationTracksViewModel'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: BittensorDetailsViewModel (LCOM4 5) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorDetailsViewModel.kt:72 — BittensorDetailsViewModel'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: RootViewModel (LCOM4 4) app/src/main/java/io/novafoundation/nova/app/root/presentation/RootViewModel.kt:43 — RootViewModel'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: SplitScreenViewModel (LCOM4 4) app/src/main/java/io/novafoundation/nova/app/root/presentation/splitScreen/SplitScreenViewModel.kt:29 — SplitScreenViewModel'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: AccountDataSourceImpl (LCOM4 4) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/datasource/AccountDataSourceImpl.kt:57 — AccountDataSourceImpl'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: DAppSearchViewModel (LCOM4 4) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/search/DAppSearchViewModel.kt:37 — DAppSearchViewModel'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: GovV2ConvictionVotingRepository (LCOM4 4) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2ConvictionVotingRepository.kt:60 — GovV2ConvictionVotingRepository'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: RealAaveSwapQuotingSource (LCOM4 4) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/aave/RealAaveSwapQuotingSource.kt:71 — RealAaveSwapQuotingSource'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: SwapMainSettingsViewModel (LCOM4 4) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt:150 — SwapMainSettingsViewModel'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: SwapChartMixin (LCOM4 4) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/chart/SwapChartMixin.kt:49 — SwapChartMixin'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: RealWalletConnectService (LCOM4 4) feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/service/RealWalletConnectService.kt:39 — RealWalletConnectService'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: RealMultisigOperationDetailsInteractor (LCOM4 4) feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/domain/details/MultisigOperationDetailsInteractor.kt:75 — RealMultisigOperationDetailsInteractor'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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×15
  • Edited copy of a member (11 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/node/list/NodesFragment.kt:81 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/node/list/NodesFragment.kt:81-97 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/node/list/NodesFragment.kt:99-109 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/add/Declarations.kt:34 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/add/Declarations.kt:34-44 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/remove/Declarations.kt:17-27 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1ConvictionVotingRepository.kt:92 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1ConvictionVotingRepository.kt:92-102 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2ConvictionVotingRepository.kt:166-176 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/Gov2DelegationsRepository.kt:60 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/Gov2DelegationsRepository.kt:60-70 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/Gov2DelegationsRepository.kt:76-87 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) common/src/main/java/io/novafoundation/nova/common/utils/FlowExt.kt:672 — common/src/main/java/io/novafoundation/nova/common/utils/FlowExt.kt:672-682 | common/src/main/java/io/novafoundation/nova/common/utils/FlowExt.kt:684-696 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt:83 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt:83-93 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/WalletRepositoryImpl.kt:168-178 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/common/start/StartImportLedgerFragment.kt:51 — feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/common/start/StartImportLedgerFragment.kt:51-61 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/common/start/StartImportLedgerFragment.kt:63-73 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:50 — feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:50-60 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:66-76 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/favorites/DAppFavoritesViewModel.kt:52 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/favorites/DAppFavoritesViewModel.kt:52-62 | feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/main/MainDAppViewModel.kt:101-111 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/addChain/legacy/selectLedger/AddChainAccountSelectLedgerViewModel.kt:46 — feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/addChain/legacy/selectLedger/AddChainAccountSelectLedgerViewModel.kt:46-56 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/connect/legacy/selectLedger/SelectLedgerLegacyImportViewModel.kt:50-63 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/confirm/ConfirmUnbondViewModel.kt:168 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/confirm/ConfirmUnbondViewModel.kt:168-178 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/select/SelectUnbondViewModel.kt:156-166 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/NominationPoolsConfirmUnbondViewModel.kt:162 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/NominationPoolsConfirmUnbondViewModel.kt:162-172 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/setup/NominationPoolsSetupUnbondViewModel.kt:170-180 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/confirm/YieldBoostConfirmViewModel.kt:176 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/confirm/YieldBoostConfirmViewModel.kt:176-192 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/rebond/ParachainStakingRebondViewModel.kt:153-163 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/claimRewards/NominationPoolsClaimRewardsViewModel.kt:130 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/claimRewards/NominationPoolsClaimRewardsViewModel.kt:130-140 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rewardDestination/confirm/ConfirmRewardDestinationViewModel.kt:158-170 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/interceptors/mercuryo/RealMercuryoBuyRequestInterceptor.kt:29 — feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/interceptors/mercuryo/RealMercuryoBuyRequestInterceptor.kt:29-39 | feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/interceptors/mercuryo/RealMercuryoSellRequestInterceptor.kt:37-48 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×15
  • Swallowed exception (caught, then discarded) runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/BaseStorageQueryContext.kt:264 — `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) runtime/src/main/java/io/novafoundation/nova/runtime/explorer/BlockExplorerLinkFormatter.kt:37 — `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) runtime/src/main/java/io/novafoundation/nova/runtime/explorer/BlockExplorerLinkFormatter.kt:55 — `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) runtime/src/main/java/io/novafoundation/nova/runtime/explorer/BlockExplorerLinkFormatter.kt:73 — `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) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationHttp.kt:50 — `catch (failure: 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) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3Interceptor.kt:96 — `catch (failure: 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) feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/validation/EvmTokenContractValidation.kt:41 — `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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:785 — `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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorSubnetValidatorRepository.kt:258 — `catch (failure: 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) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/interceptors/mercuryo/RealMercuryoBuyRequestInterceptor.kt:53 — `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) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/interceptors/mercuryo/RealMercuryoSellRequestInterceptor.kt:71 — `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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/overview/webViewController/interceptors/CardCreationInterceptor.kt:55 — `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) feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/data/derivationPath/DerivationPathDecoder.kt:27 — `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) feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/data/derivationPath/DerivationPathDecoder.kt:36 — `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) common/src/main/java/io/novafoundation/nova/common/utils/systemCall/SystemCallExecutor.kt:45 — `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.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×14
  • Edited copy of a member (10 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/pincode/di/PinCodeModule.kt:77 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/pincode/di/PinCodeModule.kt:77-86 | feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/settings/di/SettingsModule.kt:87-97 — 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/WalletInteractorImpl.kt:136 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/WalletInteractorImpl.kt:136-145 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/WalletInteractorImpl.kt:153-170 — 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) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/RealXYKSwapQuotingSource.kt:158 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/RealXYKSwapQuotingSource.kt:158-168 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/aave/RealAaveSwapQuotingSource.kt:204-213 — 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) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/ClaimContributionViewModel.kt:123 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/ClaimContributionViewModel.kt:123-132 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/redeem/MythosRedeemViewModel.kt:120-130 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:164 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:164-174 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/setup/SetupYieldBoostViewModel.kt:238-247 — 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListFragment.kt:175 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListFragment.kt:175-184 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/search/AssetSearchFragment.kt:103-112 — 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) feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/requests/evm/EvmSendTransactionRequest.kt:25 — feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/requests/evm/EvmSendTransactionRequest.kt:25-34 | feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/requests/evm/EvmSignTransactionRequest.kt:25-34 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1OnChainReferendaRepository.kt:115 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1OnChainReferendaRepository.kt:115-124 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2OnChainReferendaRepository.kt:126-135 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/GovernanceUnlockInteractor.kt:121 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/GovernanceUnlockInteractor.kt:121-130 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/RealVoteReferendumInteractor.kt:64-73 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/bond/BondMoreInteractor.kt:52 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/bond/BondMoreInteractor.kt:52-61 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/controller/ControllerInteractor.kt:43-52 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/LegacyDelegationScheduledRequestExecutor.kt:78 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/LegacyDelegationScheduledRequestExecutor.kt:78-87 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/NewDelegationScheduledRequestExecutor.kt:92-101 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/rebond/ParachainStakingRebondInteractor.kt:44 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/rebond/ParachainStakingRebondInteractor.kt:44-53 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/unbond/ParachainStakingUnbondInteractor.kt:60-69 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/start/StartMythosStakingInteractor.kt:89 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/start/StartMythosStakingInteractor.kt:89-98 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/unbond/UnbondMythosStakingInteractor.kt:44-53 — 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) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/ExtrinsicBuilderExt.kt:23 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/ExtrinsicBuilderExt.kt:23-32 | feature-xcm/api/src/main/java/io/novafoundation/nova/feature_xcm_api/extrinsic/XcmCalls.kt:15-24 — 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 (8 corresponding lines) · ×14
  • Edited copy of a member (8 corresponding lines) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:124 — feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:124-132 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:161-168 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/swap/asset/AssetSwapFlowFragment.kt:55 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/swap/asset/AssetSwapFlowFragment.kt:55-67 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/options/SwapSettingsBottomSheetFragment.kt:49-56 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RebondValidationsModule.kt:46 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RebondValidationsModule.kt:46-53 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/setup/Declarations.kt:46-53 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/start/setupAmount/direct/DirectStakingProperties.kt:105 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/start/setupAmount/direct/DirectStakingProperties.kt:105-112 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/start/setupAmount/pools/NominationPoolStakingProperties.kt:104-111 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/dashboard/main/StakingDashboardViewModel.kt:153 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/dashboard/main/StakingDashboardViewModel.kt:153-160 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/dashboard/more/MoreStakingOptionsViewModel.kt:44-53 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/RealXYKSwapQuotingSource.kt:170 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/RealXYKSwapQuotingSource.kt:170-190 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/aave/RealAaveSwapQuotingSource.kt:215-222 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/mixin/fee/FeeLoaderMixin.kt:79 — feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/mixin/fee/FeeLoaderMixin.kt:79-86 | feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/mixin/fee/v2/FeeLoaderMixinV2Ext.kt:20-27 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/mythos/updaters/MythosCompoundPercentageUpdater.kt:24 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/mythos/updaters/MythosCompoundPercentageUpdater.kt:24-31 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/mythos/updaters/MythosReleaseQueuesUpdater.kt:24-31 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/di/AccountMigrationFeatureHolder.kt:17 — feature-account-migration/src/main/java/io/novafoundation/nova/feature_account_migration/di/AccountMigrationFeatureHolder.kt:17-26 | feature-vote/src/main/java/io/novafoundation/nova/feature_vote/di/VoteFeatureHolder.kt:16-23 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/AccountInteractorImpl.kt:230 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/domain/AccountInteractorImpl.kt:230-237 | feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/domain/CloudBackupSettingsInteractor.kt:125-132 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/backup/BackupMnemonicViewModel.kt:134 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/backup/BackupMnemonicViewModel.kt:134-141 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/confirm/ConfirmMnemonicViewModel.kt:199-206 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/unbonding/mythos/MythosUnbondingComponent.kt:70 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/unbonding/mythos/MythosUnbondingComponent.kt:70-77 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/unbonding/nominationPools/NominationPoolsUnbondingComponent.kt:74-81 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/confirm/nominations/ConfirmNominationsViewModel.kt:53 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/confirm/nominations/ConfirmNominationsViewModel.kt:53-60 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/custom/search/SearchCustomValidatorsViewModel.kt:118-125 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) common/src/main/java/io/novafoundation/nova/common/view/TapToViewContainer.kt:109 — common/src/main/java/io/novafoundation/nova/common/view/TapToViewContainer.kt:109-116 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/history/TransactionHistoryView.kt:169-176 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×13
  • Duplicated block (6 lines × 2) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:64 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:64-69 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenSentNotificationHandler.kt:65-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenSentNotificationHandler.kt:71` calls `findMetaAccount`, `accountIdOf` and `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:71` 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 (6 lines × 2) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureHolder.kt:29 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureHolder.kt:29-34 | feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/di/NftFeatureHolder.kt:22-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureHolder.kt:29` 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, `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureHolder.kt:35` calls `bannersFeatureApi`, `getFeature`, `currencyFeatureApi` and `feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/di/NftFeatureHolder.kt:28` 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 (6 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureHolder.kt:29 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureHolder.kt:29-34 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/di/LedgerFeatureHolder.kt:27-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureHolder.kt:29` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/common/listing/delegated/RealMultisigFormatter.kt:48 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/common/listing/delegated/RealMultisigFormatter.kt:48-53 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/common/listing/delegated/RealProxyFormatter.kt:39-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorDetailsViewModel.kt:425 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorDetailsViewModel.kt:425-435 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioRowMapper.kt:130-135 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/selectCollatorSettings/SelectMythCollatorSettingsFragment.kt:32 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/selectCollatorSettings/SelectMythCollatorSettingsFragment.kt:32-37 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/collator/settings/SelectCollatorSettingsFragment.kt:35-40 — 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) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:34 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:34-39 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/stableswap/model/StablePool.kt:74-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:34` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:72 — feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:72-77 | feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/adapters/UpdateNotificationsBannerAdapter.kt:44-49 — 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) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/mixin/SelectAddressMixin.kt:52 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/mixin/SelectAddressMixin.kt:52-57 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/mixin/SelectSingleWalletMixin.kt:52-57 — 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) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/importing/source/source/JsonImportSource.kt:67 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/importing/source/source/JsonImportSource.kt:67-72 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/importing/source/source/MnemonicImportSource.kt:51-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/importing/source/source/MnemonicImportSource.kt:65 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/importing/source/source/MnemonicImportSource.kt:65-70 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/importing/source/source/RawSeedImportSource.kt:47-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/multisig/MultisigSigningPresenter.kt:125 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/multisig/MultisigSigningPresenter.kt:125-130 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/proxy/sign/RealProxySigningPresenter.kt:84-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/voters/VotersFormatter.kt:114 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/voters/VotersFormatter.kt:114-119 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/common/RealReferendumFormatter.kt:442-447 — 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.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×12
  • Edited copy of a member (7 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/voters/VotersFormatter.kt:113 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/voters/VotersFormatter.kt:113-119 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/common/RealReferendumFormatter.kt:441-447 — 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) runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/api/QueryableStorageEntry3.kt:36 — runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/api/QueryableStorageEntry3.kt:36-42 | runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/query/api/QueryableStorageEntry2.kt:80-86 — 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) core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/ChainAccountLocal.kt:49 — core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/ChainAccountLocal.kt:49-56 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:51-57 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/select/BittensorSelectUnstakePositionFragment.kt:23 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/select/BittensorSelectUnstakePositionFragment.kt:23-29 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSelectValidatorFragment.kt:38-44 — 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) runtime/src/main/java/io/novafoundation/nova/runtime/util/ChainAssetParcel.kt:29 — runtime/src/main/java/io/novafoundation/nova/runtime/util/ChainAssetParcel.kt:29-35 | runtime/src/main/java/io/novafoundation/nova/runtime/util/ChainParcel.kt:29-35 — 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) web3names/src/main/java/io/novafoundation/nova/web3names/data/serviceEndpoint/W3NServiceEndpointHandlerV1.kt:18 — web3names/src/main/java/io/novafoundation/nova/web3names/data/serviceEndpoint/W3NServiceEndpointHandlerV1.kt:18-24 | web3names/src/main/java/io/novafoundation/nova/web3names/data/serviceEndpoint/W3NServiceEndpointHandlerV2.kt:19-26 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/Bindings.kt:118 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/Bindings.kt:118-124 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2ConvictionVotingRepository.kt:228-234 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorDashboardSnapshotSource.kt:129 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorDashboardSnapshotSource.kt:129-135 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt:431-437 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:197 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:197-203 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/ParachainStakingUnbondViewModel.kt:234-241 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/NominationPoolsBondMoreInteractor.kt:44 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/NominationPoolsBondMoreInteractor.kt:44-50 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/NominationPoolsClaimRewardsInteractor.kt:61-67 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/rebond/validations/ParachainStakingUnbondValidationSystem.kt:8 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/rebond/validations/ParachainStakingUnbondValidationSystem.kt:8-14 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/redeem/validations/ParachainStakingUnbondValidationSystem.kt:8-14 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/start/validations/StartMythosStakingValidationSystem.kt:60 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/start/validations/StartMythosStakingValidationSystem.kt:60-66 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/start/validations/StartParachainStakingValidationSystem.kt:47-54 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×12
  • Duplicated block (10 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosFragment.kt:50 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosFragment.kt:50-59 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/ParachainStakingUnbondFragment.kt:55-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosFragment.kt:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `SetupUnbondMythosViewModel` in one and `ParachainStakingUnbondViewModel` 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 (10 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:111 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:111-120 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetDetailsFragment.kt:123-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `BittensorSubnetPositionViewModel) = with(binder` in one and `BittensorSubnetDetailsViewModel) = with(binder` 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, `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:121` calls `setReferencePrice`, `orEmpty` and `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetDetailsFragment.kt:133` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/search/DelegateSearchViewModel.kt:78 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/search/DelegateSearchViewModel.kt:78-87 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegated/YourDelegationsViewModel.kt:33-46 — 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 (10 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/info/ReferendumInfoViewModel.kt:100 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/info/ReferendumInfoViewModel.kt:100-109 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/ReferendumDetailsViewModel.kt:291-300 — 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 (10 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/addAccount/secrets/MnemonicAddAccountRepository.kt:24 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/addAccount/secrets/MnemonicAddAccountRepository.kt:24-33 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/addAccount/secrets/SeedAddAccountRepository.kt:29-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanViewModel.kt:199 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanViewModel.kt:199-208 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/ReferendumDetailsViewModel.kt:531-540 — 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: `R` names `io.novafoundation.nova.feature_crowdloan_impl.R` in one and `io.novafoundation.nova.feature_governance_impl.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/di/modules/sign/EvmSignModule.kt:43 — feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/di/modules/sign/EvmSignModule.kt:43-52 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/di/components/RelaychainModule.kt:110-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/di/modules/sign/EvmSignModule.kt:43` 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/setup/NominationPoolsSetupUnbondViewModel.kt:159 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/setup/NominationPoolsSetupUnbondViewModel.kt:159-168 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/select/SelectUnbondViewModel.kt:145-154 — 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 (10 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/add/confirm/ConfirmAddStakingProxyViewModel.kt:134 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/add/confirm/ConfirmAddStakingProxyViewModel.kt:134-143 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/revoke/ConfirmRemoveStakingProxyViewModel.kt:147-156 — 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 (10 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/nominationPools/NominationPoolsStakeSummaryComponent.kt:71 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/nominationPools/NominationPoolsStakeSummaryComponent.kt:71-80 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/parachain/ParachainStakeSummaryComponent.kt:77-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/nominationPools/NominationPoolsStakeSummaryComponent.kt:71` 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) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:57 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:57-66 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionExecutedNotificationHandler.kt:57-66 — before extracting anything, compare `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt` and `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionExecutedNotificationHandler.kt` as WHOLE FILES: 87% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:57` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:32 — runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:32-41 | runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:70-79 — 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 `runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/WebSocketWeb3jService.kt:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×12
  • Duplicated block (8 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/OffchainVotesExt.kt:56 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/OffchainVotesExt.kt:56-63 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/common/OffchainVotesExt.kt:70-77 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/mythos/MythosAlertsComponent.kt:87 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/mythos/MythosAlertsComponent.kt:87-94 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/parachain/ParachainAlertsComponent.kt:91-98 — 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 (8 lines × 2) feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:90 — feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:90-97 | feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/adapters/UpdateNotificationsAdapter.kt:50-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-versions-impl/src/main/java/io/novafoundation/nova/feature_versions_impl/presentation/update/UpdateNotificationsAdapter.kt:90` 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/list/ReferendaListViewModel.kt:174 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/list/ReferendaListViewModel.kt:174-181 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/search/ReferendaSearchViewModel.kt:80-87 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/mythos/MythosAlertsComponent.kt:69 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/mythos/MythosAlertsComponent.kt:69-76 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/parachain/ParachainAlertsComponent.kt:73-80 — 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/io/novafoundation/nova/app/root/presentation/requestBusHandler/MultisigExtrinsicValidationRequestBusHandler.kt:16 — app/src/main/java/io/novafoundation/nova/app/root/presentation/requestBusHandler/MultisigExtrinsicValidationRequestBusHandler.kt:16-24 | app/src/main/java/io/novafoundation/nova/app/root/presentation/requestBusHandler/ProxyExtrinsicValidationRequestBusHandler.kt:20-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: `ValidationResponse` names `io.novafoundation.nova.feature_account_api.data.multisig.validation.MultisigExtrinsicValidationRequestBus.ValidationResponse` in one and `io.novafoundation.nova.feature_account_api.data.proxy.validation.ProxyExtrinsicValidationRequestBus.ValidationResponse` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/multisig/MultisigSigningPresenter.kt:39 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/multisig/MultisigSigningPresenter.kt:39-46 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/proxy/sign/RealProxySigningPresenter.kt:35-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/domain/referendum/filters/ReferendumTypeFilter.kt:11 — feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/domain/referendum/filters/ReferendumTypeFilter.kt:11-18 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/filters/ReferendumTypeFilter.kt:11-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.
  • Duplicated block (8 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/setup/NominationPoolsSetupBondMoreFragment.kt:34 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/setup/NominationPoolsSetupBondMoreFragment.kt:34-41 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/select/SelectBondMoreFragment.kt:47-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `NominationPoolsSetupBondMoreViewModel` in one and `SelectBondMoreViewModel` 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 (8 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/select/SelectBondMoreViewModel.kt:108 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/select/SelectBondMoreViewModel.kt:108-115 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/custom/CustomRebondViewModel.kt:103-110 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeActions/ManageStakeAction.kt:80 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeActions/ManageStakeAction.kt:80-87 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeActions/parachain/ParachainStakeActionsComponent.kt:129-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. 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 × 2) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:44 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:44-51 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxRouterSwapExtractor.kt:44-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:44` 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.
D3 · God Classes · FileTooLong · ×11
  • FileTooLong: subnet/BittensorSubnetAmountViewModel.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt — FileTooLong — 783 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: BittensorSubnetAmountViewModel (123-1026). The bar is 500 significant lines; this is 283 over it, 1.57× 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: di/AccountFeatureModule.kt feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureModule.kt — FileTooLong — 753 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: AccountFeatureModule (201-881). The bar is 500 significant lines; this is 253 over it, 1.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs bindings/hydra-dx-math/rust/src/lib.rs — FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: main/SwapMainSettingsViewModel.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt — FileTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: SwapMainSettingsViewModel (150-994). The bar is 500 significant lines; this is 212 over it, 1.42× 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: swap/RealSwapService.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/swap/RealSwapService.kt — FileTooLong — 710 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: RealSwapService (140-1071). The bar is 500 significant lines; this is 210 over it, 1.42× 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: navigators/Navigator.kt app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt — FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: Navigator (115-968). The bar is 500 significant lines; this is 170 over it, 1.34× 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: exit/BittensorExitReviewViewModel.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt — FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: BittensorExitReviewViewModel (146-883). The bar is 500 significant lines; this is 159 over it, 1.32× 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: di/BittensorModule.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/BittensorModule.kt — FileTooLong — 653 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: BittensorModule (148-744). The bar is 500 significant lines; this is 153 over it, 1.31× 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: di/StakingFeatureModule.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureModule.kt — FileTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: StakingFeatureModule (146-733). The bar is 500 significant lines; this is 133 over it, 1.27× 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: subnet/BittensorSubnetReviewViewModel.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.kt — FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: BittensorSubnetReviewViewModel (139-811). The bar is 500 significant lines; this is 113 over it, 1.23× 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: exit/BittensorExitAmountViewModel.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitAmountViewModel.kt — FileTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: BittensorExitAmountViewModel (151-801). The bar is 500 significant lines; this is 94 over it, 1.19× 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.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×11
  • Edited copy of a member (6 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/nominationPools/network/blockhain/updater/DelegatedStakeUpdater.kt:23 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/nominationPools/network/blockhain/updater/DelegatedStakeUpdater.kt:23-28 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/network/blockhain/updaters/DelegatorStateUpdater.kt:23-30 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:851 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:851-856 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.kt:787-792 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:250 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:250-258 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/governance/GovernanceNavigator.kt:106-111 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/bindings/Nominations.kt:18 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/bindings/Nominations.kt:18-24 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/bindings/StakingLedger.kt:20-25 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/StakingRewardNotificationHandler.kt:98 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/StakingRewardNotificationHandler.kt:98-104 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:99-104 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/backup/BackupMnemonicFragment.kt:69 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/backup/BackupMnemonicFragment.kt:69-77 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/startCreateWallet/StartCreateWalletFragment.kt:45-50 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorStakingInteractor.kt:76 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorStakingInteractor.kt:76-82 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubnetStakingInteractor.kt:202-207 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/multisig/MultisigCallNode.kt:44 — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/multisig/MultisigCallNode.kt:44-49 | runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/multisig/MultisigNode.kt:130-139 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:34 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:34-39 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorRootDetailsFragment.kt:29-34 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/aave/RealAaveSwapQuotingSource.kt:237 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/aave/RealAaveSwapQuotingSource.kt:237-242 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/RealOmniPoolQuotingSource.kt:238-243 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/userRewards/parachain/ParachainUserRewardsComponent.kt:81 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/userRewards/parachain/ParachainUserRewardsComponent.kt:81-86 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/userRewards/relaychain/RelaychainUserRewardsComponent.kt:97-102 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D3 · God Classes · ClassTooLong · ×10
  • ClassTooLong: BittensorSubnetAmountViewModel feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:123 — ClassTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 243 over it, 1.61× 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: RealSwapService feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/swap/RealSwapService.kt:140 — ClassTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 168 over it, 1.42× 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: SwapMainSettingsViewModel feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt:150 — ClassTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 166 over it, 1.42× 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: Navigator app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:115 — ClassTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), 122 methods. The bar is 400 significant lines; this is 158 over it, 1.40× 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: AccountFeatureModule feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureModule.kt:201 — ClassTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 400 significant lines; this is 157 over it, 1.39× 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: BittensorExitReviewViewModel feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:146 — ClassTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 122 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: BittensorModule feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/BittensorModule.kt:148 — ClassTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 110 over it, 1.28× 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: StakingFeatureModule feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureModule.kt:146 — ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 91 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: BittensorSubnetReviewViewModel feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.kt:139 — ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 78 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.
  • ClassTooLong: BittensorExitAmountViewModel feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitAmountViewModel.kt:151 — ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 62 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×10
  • Edited copy of a member (19 corresponding lines) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:13 — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:13-31 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3ResponseAdapters.kt:40-61 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/mythos/MythosAlertsComponent.kt:78 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/mythos/MythosAlertsComponent.kt:78-96 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/parachain/ParachainAlertsComponent.kt:82-106 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt:251 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt:251-271 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt:277-295 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/mercurio/MercuryoProvider.kt:29 — feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/mercurio/MercuryoProvider.kt:29-47 | feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/transak/TransakProvider.kt:30-48 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:129 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:129-147 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:146-166 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationSigning.kt:64 — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationSigning.kt:64-83 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3Signing.kt:50-68 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/NominationPoolsConfirmUnbondViewModel.kt:141 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/NominationPoolsConfirmUnbondViewModel.kt:141-160 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/confirm/ConfirmUnbondViewModel.kt:148-166 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/confirm/ConfirmUnbondViewModel.kt:128 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/confirm/ConfirmUnbondViewModel.kt:128-146 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/select/SelectUnbondViewModel.kt:121-143 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/evmErc20/EvmErc20AssetHistory.kt:35 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/evmErc20/EvmErc20AssetHistory.kt:35-54 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/evmNative/EvmNativeAssetHistory.kt:48-66 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/ClaimContributionViewModel.kt:103 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/ClaimContributionViewModel.kt:103-121 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/redeem/MythosRedeemViewModel.kt:100-118 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×10
  • Edited copy of a member (14 corresponding lines) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:144 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:144-157 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:176-189 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:127 — feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:127-140 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:145-158 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:90 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:90-103 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/xyk/model/XYKPool.kt:110-123 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/events/orml/OrmlAssetEventDetector.kt:41 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/events/orml/OrmlAssetEventDetector.kt:41-54 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/events/statemine/StatemineAssetEventDetector.kt:44-57 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/ConfirmReferendumVoteViewModel.kt:141 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/ConfirmReferendumVoteViewModel.kt:141-158 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bagList/rebag/RebagViewModel.kt:137-150 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/start/common/types/direct/ParachainStakingTypeDetailsInteractor.kt:43 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/start/common/types/direct/ParachainStakingTypeDetailsInteractor.kt:43-56 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/start/common/types/direct/RelaychainStakingTypeDetailsInteractor.kt:41-54 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/governance/PushGovernanceSettingsFragment.kt:56 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/governance/PushGovernanceSettingsFragment.kt:56-69 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/staking/PushStakingSettingsFragment.kt:53-66 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanViewModel.kt:184 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanViewModel.kt:184-197 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/ReferendumDetailsViewModel.kt:275-289 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/ConfirmReferendumVoteViewModel.kt:126 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/ConfirmReferendumVoteViewModel.kt:126-139 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tindergov/confirm/ConfirmTinderGovVoteViewModel.kt:137-150 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/di/BittensorSelectValidatorModule.kt:46 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/di/BittensorSelectValidatorModule.kt:46-59 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/di/BittensorSubnetModule.kt:61-74 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×10
  • Duplicated block (11 lines × 2) common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:204 — common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:204-214 | common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:226-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 `common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:204` 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) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/SecretsWalletDetailsMixin.kt:32 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/SecretsWalletDetailsMixin.kt:32-42 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/WatchOnlyWalletDetailsMixin.kt:42-52 — 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 (11 lines × 2) feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/pdc20/Pdc20Provider.kt:76 — feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/pdc20/Pdc20Provider.kt:76-87 | feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/rmrkV1/RmrkV1NftProvider.kt:36-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/pdc20/Pdc20Provider.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/rmrkV1/RmrkV1NftProvider.kt:32` calls `UnsupportedOperationException` and `feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/pdc20/Pdc20Provider.kt:71` 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 × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/subsquare/v1/SubSquareV1ReferendaDataSource.kt:40 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/subsquare/v1/SubSquareV1ReferendaDataSource.kt:40-50 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/subsquare/v2/SubSquareV2ReferendaDataSource.kt:41-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. Read the line range as the matched WINDOW rather than a finished unit: at `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/subsquare/v2/SubSquareV2ReferendaDataSource.kt:41` 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 (11 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/pools/searchPool/SearchPoolViewModel.kt:120 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/pools/searchPool/SearchPoolViewModel.kt:120-130 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/pools/selectPool/SelectPoolViewModel.kt:114-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/pools/searchPool/SearchPoolViewModel.kt:120` 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:50 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:50-60 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/networks/AssetNetworksInteractor.kt:55-65 — before extracting anything, compare `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/networks/AssetNetworksInteractor.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:50` 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1DAppsRepository.kt:26 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1DAppsRepository.kt:26-36 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2DAppsRepository.kt:26-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/currentCollators/MythosCurrentCollatorsFragment.kt:21 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/currentCollators/MythosCurrentCollatorsFragment.kt:21-31 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/collator/current/CurrentCollatorsFragment.kt:21-31 — 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 `viewModel` to `MythosCurrentCollatorsViewModel` in one and `CurrentCollatorsViewModel` 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 (11 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:200 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:200-210 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.kt:193-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:200` 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) bindings/hydra-dx-math/rust/src/lib.rs:815 — bindings/hydra-dx-math/rust/src/lib.rs:815-825 | bindings/hydra-dx-math/rust/src/lib.rs:898-908 — 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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×7
  • Edited copy of a member (15 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/NewDelegationScheduledRequestExecutor.kt:30 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/NewDelegationScheduledRequestExecutor.kt:30-45 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/parachainStaking/repository/scheduledRequests/NewDelegationScheduledRequestExecutor.kt:48-62 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/LegacyLedgerWalletDetailsMixin.kt:61 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/LegacyLedgerWalletDetailsMixin.kt:61-78 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/ProxiedWalletDetailsMixin.kt:52-66 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/polkassembly/v2/PolkassemblyV2ReferendaDataSource.kt:58 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/polkassembly/v2/PolkassemblyV2ReferendaDataSource.kt:58-76 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/offchain/referendum/subsquare/v2/SubSquareV2ReferendaDataSource.kt:53-67 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/BittensorDashboardDetailsSource.kt:218 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/BittensorDashboardDetailsSource.kt:218-233 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/BittensorDashboardDetailsSource.kt:235-249 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:55 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:55-69 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardParachainStakingUpdater.kt:45-60 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/presentation/common/fieldValidation/RealEnoughAmountFieldValidator.kt:31 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/presentation/common/fieldValidation/RealEnoughAmountFieldValidator.kt:31-45 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/presentation/common/fieldValidation/RealMinAmountFieldValidator.kt:36-52 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/statemine/StatemineAssetBalance.kt:61 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/statemine/StatemineAssetBalance.kt:61-76 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/statemine/StatemineAssetBalance.kt:100-114 — 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 copies of one member (3 members, 11+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/equilibrium/EquilibriumAssetBalance.kt:80 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/equilibrium/EquilibriumAssetBalance.kt:80-92 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/orml/OrmlAssetBalance.kt:47-59 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/balances/utility/NativeAssetBalance.kt:84-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:82 — feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:82-92 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:98-108 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/callFormatting/formatters/RealMultisigCallFormatter.kt:115-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/redeem/NominationPoolsRedeemViewModel.kt:132 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/redeem/NominationPoolsRedeemViewModel.kt:132-142 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/redeem/ParachainStakingRedeemViewModel.kt:133-143 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/redeem/RedeemViewModel.kt:129-139 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/data/settings/model/CommonMappingExt.kt:8 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/data/settings/model/CommonMappingExt.kt:8-18 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/data/settings/model/PushSettingsCacheV1.kt:25-35 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/data/settings/model/PushSettingsCacheV2.kt:27-37 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/detail/BalanceDetailFragment.kt:97 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/detail/BalanceDetailFragment.kt:97-107 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/confirm/ConfirmSendFragment.kt:48-58 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/reward/pool/PoolRewardDetailFragment.kt:46-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/confirm/ConfirmContributeFragment.kt:47 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/confirm/ConfirmContributeFragment.kt:47-57 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/CustomContributeFragment.kt:43-53 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/select/CrowdloanContributeFragment.kt:52-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/sign/scan/di/ScanSignParitySignerModule.kt:50 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/sign/scan/di/ScanSignParitySignerModule.kt:50-62 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tracks/select/governanceTracks/di/SelectGovernanceTracksModule.kt:34-44 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/connect/legacy/selectAddress/di/SelectAddressImportLedgerLegacyModule.kt:56-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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 · Duplicated block (9 lines × 2) · ×7
  • Duplicated block (9 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:178 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:178-186 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:252-260 — 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, `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:249` calls `clearChainAccountsSecrets` and `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/cloudBackup/RealLocalAccountsCloudBackupFacade.kt:176` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:52 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:52-60 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:72-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:52` 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, `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:83` calls `setupExternalActions` and `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:63` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) common/src/main/java/io/novafoundation/nova/common/view/AmountView.kt:53 — common/src/main/java/io/novafoundation/nova/common/view/AmountView.kt:53-61 | feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/view/amount/ChooseAmountInputView.kt:45-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) feature-banners-impl/src/main/java/io/novafoundation/nova/feature_banners_impl/di/BannersFeatureHolder.kt:15 — feature-banners-impl/src/main/java/io/novafoundation/nova/feature_banners_impl/di/BannersFeatureHolder.kt:15-23 | feature-xcm/impl/src/main/java/io/novafoundation/nova/feature_xcm_impl/di/XcmFeatureHolder.kt:14-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:178 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:178-186 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardRelayStakingUpdater.kt:140-148 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:178` 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 (9 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/RealAddStakingProxyInteractor.kt:41 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/RealAddStakingProxyInteractor.kt:41-49 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/remove/RemoveStakingProxyInteractor.kt:42-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/staking/delegation/proxy/remove/RemoveStakingProxyInteractor.kt:42` 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 (9 lines × 2) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/orml/OrmlAssetHistory.kt:38 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/orml/OrmlAssetHistory.kt:38-46 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/statemine/StatemineAssetHistory.kt:38-46 — 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.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×6
  • Edited copy of a member (21 corresponding lines) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/web3/metamask/states/DefaultMetamaskState.kt:183 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/web3/metamask/states/DefaultMetamaskState.kt:183-203 | feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/web3/polkadotJs/states/DefaultPolkadotJsState.kt:72-94 — 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.
  • Edited copy of a member (21 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosFragment.kt:39 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosFragment.kt:39-59 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/ParachainStakingUnbondFragment.kt:41-64 — 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.
  • Edited copy of a member (21 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/TokenRepositoryImpl.kt:22 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/TokenRepositoryImpl.kt:22-42 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/repository/TokenRepositoryImpl.kt:44-64 — 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.
  • Edited copy of a member (21 corresponding lines) common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:197 — common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:197-217 | common/src/main/java/io/novafoundation/nova/common/data/storage/encrypt/EncryptionUtil.kt:219-239 — 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.
  • Edited copy of a member (21 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/addAccount/paritySigner/ParitySignerAddAccountRepository.kt:24 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/addAccount/paritySigner/ParitySignerAddAccountRepository.kt:24-45 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/addAccount/watchOnly/WatchOnlyAddAccountRepository.kt:39-59 — 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.
  • Edited copy of a member (21 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:205 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/SetupUnbondMythosViewModel.kt:205-225 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/ParachainStakingUnbondViewModel.kt:243-264 — 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 · Duplicated block (13 lines × 2) · ×6
  • Duplicated block (13 lines × 2) common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:286 — common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:286-298 | common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:307-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/io/novafoundation/nova/common/utils/formatting/NumberFormatters.kt:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (13 lines × 2) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/claim/ClaimGiftViewModel.kt:190 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/claim/ClaimGiftViewModel.kt:190-202 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/share/ShareGiftViewModel.kt:149-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/claim/ClaimGiftViewModel.kt:190` 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:57 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:57-69 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardParachainStakingUpdater.kt:47-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:344 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:344-356 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionViewModel.kt:221-233 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:344` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:30 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:30-42 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxRouterSwapExtractor.kt:30-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:30` 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 (13 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:181 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:181-193 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/StartParachainStakingViewModel.kt:184-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `amount` to `Balance` in one and `BigDecimal` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×6
  • Duplicated block (5 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:9 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/stats/api/StakingTypeMappers.kt:9-13 | runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/chain/mappers/RemoteToLocalChainMappers.kt:263-267 — 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/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:640 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:640-644 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/chainMigration/ChainMigrationNavigator.kt:12-16 — 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) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/assets/AssetGiftsFlowViewModel.kt:82 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/assets/AssetGiftsFlowViewModel.kt:82-86 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/flow/asset/AssetSendFlowViewModel.kt:85-89 — before extracting anything, compare `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/assets/AssetGiftsFlowViewModel.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/flow/asset/AssetSendFlowViewModel.kt` as WHOLE FILES: 88% 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.
  • Duplicated block (5 lines × 2) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/data/mappers/OperationMappers.kt:31 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/data/mappers/OperationMappers.kt:31-35 | feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/data/mappers/Operation.kt:9-13 — 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 `status` to `OperationBaseLocal.Status) = when (status` in one and `Operation.Status) = when (status` 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 (5 lines × 2) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/acala/bonus/AcalaContributeViewState.kt:36 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/acala/bonus/AcalaContributeViewState.kt:36-40 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/astar/AstarContributeViewState.kt:36-40 — 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) common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:86 — common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:86-90 | common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:148-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.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×5
  • Edited copy of a member (20 corresponding lines) bindings/hydra-dx-math/rust/src/lib.rs:779 — bindings/hydra-dx-math/rust/src/lib.rs:779-798 | bindings/hydra-dx-math/rust/src/lib.rs:862-881 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:41 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:41-60 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:59-80 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/add/confirm/ConfirmAddStakingProxyViewModel.kt:111 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/add/confirm/ConfirmAddStakingProxyViewModel.kt:111-132 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/revoke/ConfirmRemoveStakingProxyViewModel.kt:112-131 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/confirm/ConfirmMultiStakingViewModel.kt:156 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/confirm/ConfirmMultiStakingViewModel.kt:156-175 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/setupAmount/SetupAmountMultiStakingViewModel.kt:188-216 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/nominationPool/NominationPoolStakingUpdatersModule.kt:166 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/nominationPool/NominationPoolStakingUpdatersModule.kt:166-185 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/relaychain/RelaychainStakingUpdatersModule.kt:425-449 — 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 copy of a member (17 corresponding lines) · ×5
  • Edited copy of a member (17 corresponding lines) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:45 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:45-61 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:67-83 — 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) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/warning/ManualBackupWarningFragment.kt:39 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/warning/ManualBackupWarningFragment.kt:39-55 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/mnemonic/backup/BackupMnemonicFragment.kt:43-59 — 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/detail/votedReferenda/VotedReferendaViewModel.kt:54 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/detail/votedReferenda/VotedReferendaViewModel.kt:54-70 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/search/ReferendaSearchViewModel.kt:62-78 — 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) runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/SocketServiceAsyncAdapter.kt:17 — runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/SocketServiceAsyncAdapter.kt:17-33 | runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/SocketServiceAsyncAdapter.kt:38-54 — 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) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/sign/show/di/ShowSignParitySignerModule.kt:58 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/sign/show/di/ShowSignParitySignerModule.kt:58-75 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/topup/di/TopUpAddressModule.kt:46-62 — 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 (18 corresponding lines) · ×5
  • Edited copy of a member (18 corresponding lines) runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/chain/mappers/DomainToLocalChainMapper.kt:86 — runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/chain/mappers/DomainToLocalChainMapper.kt:86-105 | runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/chain/mappers/RemoteToLocalChainMappers.kt:159-176 — 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) feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/sdk/application/substrate/legacyApp/LegacySubstrateLedgerApplication.kt:31 — feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/sdk/application/substrate/legacyApp/LegacySubstrateLedgerApplication.kt:31-48 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/sdk/application/substrate/newApp/NewSubstrateLedgerApplication.kt:38-58 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/claimRewards/NominationPoolsClaimRewardsViewModel.kt:107 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/claimRewards/NominationPoolsClaimRewardsViewModel.kt:107-128 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/redeem/NominationPoolsRedeemViewModel.kt:113-130 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.kt:125 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.kt:125-142 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/StartParachainStakingViewModel.kt:142-161 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/di/BittensorExitAmountModule.kt:66 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/di/BittensorExitAmountModule.kt:66-90 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/di/BittensorDetailsModule.kt:136-153 — 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 (5 corresponding lines) · ×5
  • Edited copy of a member (5 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorExitRuntimeSource.kt:35 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorExitRuntimeSource.kt:35-54 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorRootClaimSource.kt:115-119 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationSigning.kt:52 — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationSigning.kt:52-56 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3Signing.kt:31-35 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/nominationPools/network/blockhain/updater/PoolMetadataUpdater.kt:22 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/nominationPools/network/blockhain/updater/PoolMetadataUpdater.kt:22-26 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/nominationPools/network/blockhain/updater/SubPoolsUpdater.kt:22-26 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/push/PushNotificationsNavigator.kt:16 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/push/PushNotificationsNavigator.kt:16-20 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/settings/SettingsNavigator.kt:85-89 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/info/ReferendumInfoViewModel.kt:111 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/info/ReferendumInfoViewModel.kt:111-115 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/ReferendumDetailsViewModel.kt:227-231 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×4
  • Edited copy of a member (26 corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/ReferendumStateUpdateNotificationHandler.kt:52 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/ReferendumStateUpdateNotificationHandler.kt:52-77 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/StakingRewardNotificationHandler.kt:56-82 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/start/StartParachainStakingInteractor.kt:46 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/start/StartParachainStakingInteractor.kt:46-71 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/parachainStaking/start/StartParachainStakingInteractor.kt:73-100 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/validations/referendum/VoteReferendumValidationSystem.kt:21 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/validations/referendum/VoteReferendumValidationSystem.kt:21-48 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/validations/tindergov/VoteTinderGovValidationSystem.kt:19-44 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/transaction/builder/RealEvmTransactionBuilder.kt:28 — runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/transaction/builder/RealEvmTransactionBuilder.kt:28-55 | runtime/src/main/java/io/novafoundation/nova/runtime/ethereum/transaction/builder/RealEvmTransactionBuilder.kt:61-86 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×4
  • Edited copy of a member (22 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/NominationPoolsConfirmUnbondViewModel.kt:118 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/NominationPoolsConfirmUnbondViewModel.kt:118-139 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/setup/NominationPoolsSetupUnbondViewModel.kt:131-157 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseAmount/RealDelegateAssistant.kt:32 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseAmount/RealDelegateAssistant.kt:32-53 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/vote/RealGovernanceLocksEstimator.kt:74-99 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt:320 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/assetConversion/AssetConversionExchange.kt:320-346 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/data/assetExchange/hydraDx/HydraDxAssetExchange.kt:365-386 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/chooseAmount/NewDelegationChooseAmountViewModel.kt:172 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/chooseAmount/NewDelegationChooseAmountViewModel.kt:172-193 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/select/SelectBondMoreViewModel.kt:117-139 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×4
  • Edited copy of a member (4 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:965 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:965-973 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.kt:770-773 — 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorPositionSource.kt:52 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorPositionSource.kt:52-55 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorPricesSource.kt:111-114 — 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) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationSigning.kt:104 — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationSigning.kt:104-107 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3Signing.kt:80-83 — 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) feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/updater/AccountInfoUpdater.kt:43 — feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/domain/updater/AccountInfoUpdater.kt:43-47 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/transfers/utility/NativeAssetTransfers.kt:113-116 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/SelectSendViewModel.kt:238 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/SelectSendViewModel.kt:238-249 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/topup/TopUpAddressViewModel.kt:124-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/SelectSendViewModel.kt:238` 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) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:71 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:71-82 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:110-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:71` 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:129 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.kt:129-140 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/StartParachainStakingViewModel.kt:125-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. 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) feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:50 — feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:50-61 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:72-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/data/assetExchange/conversion/types/hydra/sources/omnipool/model/OmniPool.kt:50` 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.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: :bindings:metadata_shortener — :bindings:metadata_shortener: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: :core-db — :core-db: abstractness 0.14, instability 0.03, distance 0.82 — zone of pain — concrete and depended on by 28 project(s), so it's rigid to change.
  • Off the main sequence: :analytics — :analytics: abstractness 0.03, instability 0.18, distance 0.80 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
  • Off the main sequence: :runtime — :runtime: abstractness 0.18, instability 0.08, distance 0.73 — zone of pain — concrete and depended on by 44 project(s), so it's rigid to change.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt:77 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in BittensorSubmissionExecutor.execute at line 77. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 02:38:55 +04:00' --until='2026-11-17 02:38:55 +04:00' --full-history --no-merges -- feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.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: feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:651 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in BittensorExitReviewViewModel.confirmClicked at line 651. 3 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 02:38:55 +04:00' --until='2026-11-17 02:38:55 +04:00' --full-history --no-merges -- feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.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: feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt:148 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ResponseCache.observe at line 148. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 02:38:55 +04:00' --until='2026-11-17 02:38:55 +04:00' --full-history --no-merges -- feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.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.
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×3
  • Edited copy of a member (36 corresponding lines) bindings/hydra-dx-math/rust/src/lib.rs:811 — bindings/hydra-dx-math/rust/src/lib.rs:811-846 | bindings/hydra-dx-math/rust/src/lib.rs:894-929 — 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.
  • Edited copy of a member (36 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:159 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:159-200 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:206-241 — 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.
  • Edited copy of a member (36 corresponding lines) feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/kodadot/KodadotProvider.kt:77 — feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/kodadot/KodadotProvider.kt:77-112 | feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/unique_network/UniqueNetworkProvider.kt:96-134 — 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 (23 corresponding lines) · ×3
  • Edited copy of a member (23 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:88 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:88-113 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/dashboard/RealStakingDashboardInteractor.kt:115-137 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/PayoutRepository.kt:242 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/PayoutRepository.kt:242-264 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/PayoutRepository.kt:269-293 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/pdc20/Pdc20Provider.kt:75 — feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/pdc20/Pdc20Provider.kt:75-98 | feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/data/source/providers/rmrkV1/RmrkV1NftProvider.kt:35-57 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 12+ corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionFragment.kt:136 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionFragment.kt:136-147 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionFragment.kt:149-164 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionFragment.kt:166-182 — 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.
  • Edited copies of one member (3 members, 12+ corresponding lines) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/di/BuyFeatureHolder.kt:19 — feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/di/BuyFeatureHolder.kt:19-30 | feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/di/ExternalSignFeatureHolder.kt:21-32 | feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/di/NftFeatureHolder.kt:20-32 — 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.
  • Edited copies of one member (3 members, 12+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/mythos/MythosStakeSummaryComponent.kt:54 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/mythos/MythosStakeSummaryComponent.kt:54-65 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/nominationPools/NominationPoolsStakeSummaryComponent.kt:56-67 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/parachain/ParachainStakeSummaryComponent.kt:62-73 — 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 (3 members, 17+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 17+ corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:321 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:321-337 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:339-356 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionViewModel.kt:217-233 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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.
  • Edited copies of one member (3 members, 17+ corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/sync/MultisigAccountsSyncDataSource.kt:180 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/sync/MultisigAccountsSyncDataSource.kt:180-196 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/sync/MultisigAccountsSyncDataSource.kt:202-218 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/sync/ProxyExternalAccountsSyncDataSource.kt:113-129 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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.
  • Edited copies of one member (3 members, 17+ corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/list/multipleSelecting/SelectMultipleWalletsViewModel.kt:55 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/list/multipleSelecting/SelectMultipleWalletsViewModel.kt:55-73 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/settings/PushSettingsViewModel.kt:132-148 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/setupStakingType/SetupStakingTypeViewModel.kt:131-149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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 (5 members, 6+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 6+ corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt:48 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt:48-56 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionFragment.kt:77-82 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/fee/SwapFeeFragment.kt:37-45 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/options/SwapSettingsBottomSheetFragment.kt:42-47 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/route/SwapRouteFragment.kt:51-59 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 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.
  • Edited copies of one member (5 members, 6+ corresponding lines) feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/created/MultisigCreatedBottomSheet.kt:15 — feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/created/MultisigCreatedBottomSheet.kt:15-20 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/details/full/MultisigOperationFullDetailsFragment.kt:33-41 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/details/general/MultisigOperationDetailsFragment.kt:70-78 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/enterCall/MultisigOperationEnterCallFragment.kt:25-33 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/list/MultisigPendingOperationsFragment.kt:43-51 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 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.
  • Edited copies of one member (5 members, 6+ corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/governance/PushGovernanceSettingsFragment.kt:49 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/governance/PushGovernanceSettingsFragment.kt:49-54 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/multisigs/PushMultisigSettingsFragment.kt:34-39 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/settings/PushSettingsFragment.kt:38-43 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/staking/PushStakingSettingsFragment.kt:46-51 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/welcome/PushWelcomeFragment.kt:38-43 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 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 · Duplicated block (8 lines × 3) · ×3
  • Duplicated block (8 lines × 3) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:52 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:52-59 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:72-79 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetDetailsFragment.kt:75-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:52` 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, `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionFragment.kt:83` calls `setupExternalActions` and `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorPortfolioFragment.kt:63` 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 lines × 3) feature-ledger-core/src/main/java/io/novafoundation/nova/feature_ledger_core/LedgerFeatureHolder.kt:14 — feature-ledger-core/src/main/java/io/novafoundation/nova/feature_ledger_core/LedgerFeatureHolder.kt:14-22 | feature-proxy-impl/src/main/java/io/novafoundation/nova/feature_proxy_impl/di/ProxyFeatureHolder.kt:14-21 | feature-swap-core/src/main/java/io/novafoundation/nova/feature_swap_core/di/SwapCoreHolder.kt:14-22 — 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) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:56 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:56-63 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionExecutedNotificationHandler.kt:56-63 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionInitiatedNotificationHandler.kt:56-63 — before extracting anything, compare `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt` and `feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionExecutedNotificationHandler.kt` as WHOLE FILES: 87% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • Duplicated block (15 lines × 2) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/astar/AstarContributeSubmitter.kt:22 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/astar/AstarContributeSubmitter.kt:22-36 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/bifrost/BifrostContributeSubmitter.kt:22-36 — before extracting anything, compare `feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/astar/AstarContributeSubmitter.kt` and `feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/bifrost/BifrostContributeSubmitter.kt` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/astar/AstarContributeSubmitter.kt:22` 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/datasource/reward/DirectStakingRewardsDataSource.kt:18 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/datasource/reward/DirectStakingRewardsDataSource.kt:18-32 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/repository/datasource/reward/PoolStakingRewardsDataSource.kt:18-32 — 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 (15 lines × 2) bindings/metadata_shortener/rust/src/lib.rs:74 — bindings/metadata_shortener/rust/src/lib.rs:74-88 | bindings/metadata_shortener/rust/src/lib.rs:132-146 — 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 `bindings/metadata_shortener/rust/src/lib.rs:74` 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.
DM5 · Encapsulated state · Mutable entity · ×3
  • Mutable entity: GiftLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/GiftLocal.kt:27 — `GiftLocal` exposes publicly writable state (id).
  • Mutable entity: NodeLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/NodeLocal.kt:7 — `NodeLocal` exposes publicly writable state (id).
  • Mutable entity: MetaAccountLocal core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/MetaAccountLocal.kt:25 — `MetaAccountLocal` exposes publicly writable state (id).
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: StackBlur.blur common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:8 — MethodTooLong — blur runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: AccountMappers.mapMetaAccountLocalToMetaAccount feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/mappers/AccountMappers.kt:44 — MethodTooLong — mapMetaAccountLocalToMetaAccount runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D35 · Change Coupling · Change-coupling hub · ×2
  • Change-coupling hub: SwapMainSettingsViewModel.kt → RealSwapSettingsState.kt, SwapConfirmationFragment.kt, SwapConfirmationModule.kt, SwapMainSettingsFragment.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsViewModel.kt` changes together with 4 other files — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/common/state/RealSwapSettingsState.kt`, `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt`, `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/di/SwapConfirmationModule.kt`, `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapMainSettingsFragment.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
  • Change-coupling hub: SwapFeatureModule.kt → SwapFeatureDependencies.kt, RealSwapSettingsState.kt, SwapConfirmationFragment.kt, SwapConfirmationModule.kt feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/di/SwapFeatureModule.kt — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/di/SwapFeatureModule.kt` changes together with 4 other files — `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/di/SwapFeatureDependencies.kt`, `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/common/state/RealSwapSettingsState.kt`, `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationFragment.kt`, `feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/di/SwapConfirmationModule.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorExitValidationUi.kt:98 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorExitValidationUi.kt:98-139 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorStakeValidationUi.kt:91-124 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:158 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:158-195 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.kt:155-188 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×2
  • Edited copy of a member (39 corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:21 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxOmniPoolSwapExtractor.kt:21-59 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/realtime/substrate/hydraDx/HydraDxRouterSwapExtractor.kt:21-59 — These two members are one piece of code written twice and then edited apart: 39 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 (39 corresponding lines) runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/batch/BatchAllNode.kt:38 — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/batch/BatchAllNode.kt:38-76 | runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/batch/ForceBatchNode.kt:50-98 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×2
  • Edited copy of a member (38 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/amount/BittensorStakeAmountViewModel.kt:458 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/amount/BittensorStakeAmountViewModel.kt:458-495 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/confirm/BittensorStakeConfirmViewModel.kt:263-303 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/SelectSendViewModel.kt:214 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/SelectSendViewModel.kt:214-258 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/topup/TopUpAddressViewModel.kt:106-143 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×2
  • Edited copy of a member (27 corresponding lines) feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionViewModel.kt:345 — feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionViewModel.kt:345-372 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/execution/SwapExecutionViewModel.kt:374-400 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) app/src/main/java/io/novafoundation/nova/app/root/presentation/di/RootActivityModule.kt:73 — app/src/main/java/io/novafoundation/nova/app/root/presentation/di/RootActivityModule.kt:73-100 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/di/BittensorExitReviewModule.kt:74-100 — 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 (25 corresponding lines) · ×2
  • Edited copy of a member (25 corresponding lines) feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/common/selectAddress/SelectAddressLedgerViewModel.kt:154 — feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/common/selectAddress/SelectAddressLedgerViewModel.kt:154-178 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/connect/generic/preview/PreviewImportGenericLedgerViewModel.kt:92-120 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core-db/src/main/java/io/novafoundation/nova/core_db/model/operation/OperationLocal.kt:26 — core-db/src/main/java/io/novafoundation/nova/core_db/model/operation/OperationLocal.kt:26-52 | core-db/src/main/java/io/novafoundation/nova/core_db/model/operation/OperationLocal.kt:64-88 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 13+ corresponding lines) feature-ahm-impl/src/main/java/io/novafoundation/nova/feature_ahm_impl/di/ChainMigrationFeatureHolder.kt:19 — feature-ahm-impl/src/main/java/io/novafoundation/nova/feature_ahm_impl/di/ChainMigrationFeatureHolder.kt:19-33 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/di/GiftFeatureHolder.kt:20-32 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/di/MultisigOperationsFeatureHolder.kt:20-35 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureHolder.kt:21-33 — 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.
  • Edited copies of one member (4 members, 13+ corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/domain/claimContributions/validation/ClaimContributionValidationSystem.kt:14 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/domain/claimContributions/validation/ClaimContributionValidationSystem.kt:14-26 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/redeem/validations/RedeemMythosValidationSystem.kt:13-25 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/start/validations/StartMythosStakingValidationSystem.kt:31-43 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/unbond/validations/UnbondMythosValidationSystem.kt:20-32 — 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 copies of one member (3 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 9+ corresponding lines) bindings/hydra-dx-math/rust/src/lib.rs:648 — bindings/hydra-dx-math/rust/src/lib.rs:648-656 | bindings/hydra-dx-math/rust/src/lib.rs:679-687 | bindings/hydra-dx-math/rust/src/lib.rs:710-718 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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.
  • Edited copies of one member (3 members, 9+ corresponding lines) feature-cloud-backup-impl/src/main/java/io/novafoundation/nova/feature_cloud_backup_impl/di/CloudBackupFeatureHolder.kt:17 — feature-cloud-backup-impl/src/main/java/io/novafoundation/nova/feature_cloud_backup_impl/di/CloudBackupFeatureHolder.kt:17-25 | feature-currency-impl/src/main/java/io/novafoundation/nova/feature_currency_impl/di/CurrencyFeatureHolder.kt:17-25 | web3names/src/main/java/io/novafoundation/nova/web3names/di/Web3NamesHolder.kt:16-27 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 9+ corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/common/buySell/BuySellRestrictionCheckMixin.kt:31 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/common/buySell/BuySellRestrictionCheckMixin.kt:31-39 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/common/gifts/GiftsRestrictionCheckMixin.kt:29-37 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/common/NovaCardRestrictionCheckMixin.kt:71-79 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/common/NovaCardRestrictionCheckMixin.kt:81-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 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.
  • Edited copies of one member (4 members, 9+ corresponding lines) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/ClaimContributionFragment.kt:27 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/ClaimContributionFragment.kt:27-35 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/custom/moonbeam/terms/MoonbeamCrowdloanTermsFragment.kt:48-56 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contributions/UserContributionsFragment.kt:41-49 | feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/main/CrowdloanFragment.kt:44-52 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 17+ corresponding lines) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/di/SelectGiftAmountModule.kt:57 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/di/SelectGiftAmountModule.kt:57-76 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/detail/main/di/DelegateDetailsModule.kt:47-63 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/confirm/di/BittensorStakeConfirmModule.kt:57-76 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/di/exchanges/HydraDxExchangeModule.kt:82-99 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 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.
  • Edited copies of one member (4 members, 17+ corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/removeVotes/RemoveVotesViewModel.kt:110 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/removeVotes/RemoveVotesViewModel.kt:110-126 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/revoke/confirm/RevokeDelegationConfirmViewModel.kt:153-169 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/rebond/ParachainStakingRebondViewModel.kt:135-151 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/redeem/ParachainStakingRedeemViewModel.kt:115-131 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 6+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/updaters/AccountNominationsUpdater.kt:22 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/updaters/AccountNominationsUpdater.kt:22-27 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/updaters/AccountRewardDestinationUpdater.kt:22-27 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/updaters/AccountValidatorPrefsUpdater.kt:22-27 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/updaters/BagListNodeUpdater.kt:22-27 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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.
  • Edited copies of one member (4 members, 6+ corresponding lines) feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/scan/WalletConnectScanFragment.kt:19 — feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/scan/WalletConnectScanFragment.kt:19-24 | feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/sessions/approve/WalletConnectApproveSessionFragment.kt:40-48 | feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/sessions/details/WalletConnectSessionDetailsFragment.kt:44-52 | feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/sessions/list/WalletConnectSessionsFragment.kt:40-48 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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 · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/config/variants/PolkadotVaultConfig.kt:20 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/config/variants/PolkadotVaultConfig.kt:20-37 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/config/variants/PolkadotVaultConfig.kt:48-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/config/variants/PolkadotVaultConfig.kt:20` 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) feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/cloudBackup/settings/di/CloudBackupSettingsModule.kt:48 — feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/cloudBackup/settings/di/CloudBackupSettingsModule.kt:48-65 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/setupStakingType/di/SetupStakingTypeModule.kt:79-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/cloudBackup/settings/di/CloudBackupSettingsModule.kt:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/di/SelectGiftAmountModule.kt:61 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/di/SelectGiftAmountModule.kt:61-76 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/confirm/di/BittensorStakeConfirmModule.kt:61-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/di/SelectGiftAmountModule.kt:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/di/AddTokenSelectChainModule.kt:19 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/di/AddTokenSelectChainModule.kt:19-34 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/selectChain/di/AddTokenSelectChainModule.kt:19-34 — before extracting anything, compare `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/di/AddTokenSelectChainModule.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/selectChain/di/AddTokenSelectChainModule.kt` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2
  • Duplicated block (9 lines × 3) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/banxa/BanxaProvider.kt:31 — feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/banxa/BanxaProvider.kt:31-39 | feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/mercurio/MercuryoProvider.kt:30-38 | feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/transak/TransakProvider.kt:31-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/banxa/BanxaProvider.kt:31` 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) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:212 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/ConfirmStartMythosStakingViewModel.kt:212-220 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.kt:205-213 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/confirm/ParachainStakingUnbondConfirmViewModel.kt:204-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:67 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:67-72 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:67-72 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/networks/AssetNetworksInteractor.kt:72-82 — before extracting anything, compare `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/networks/AssetNetworksInteractor.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:67` 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 (6 lines × 3) bindings/hydra-dx-math/rust/src/lib.rs:404 — bindings/hydra-dx-math/rust/src/lib.rs:404-409 | bindings/hydra-dx-math/rust/src/lib.rs:486-491 | bindings/hydra-dx-math/rust/src/lib.rs:567-572 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bindings/hydra-dx-math/rust/src/lib.rs:485` calls `get_str` and `bindings/hydra-dx-math/rust/src/lib.rs:403` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2
  • Duplicated block (13 lines × 4) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/removeVotes/validations/RemoveVotesValidationSystem.kt:8 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/removeVotes/validations/RemoveVotesValidationSystem.kt:8-20 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/revoke/validations/RevokeDelegationValidationSystem.kt:8-20 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/validations/VoteReferendumValidationSystem.kt:8-20 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bagList/rebag/validations/RebagValidationSystem.kt:8-20 — 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.
  • Duplicated block (13 lines × 4) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/claimRewards/validations/Declarations.kt:20 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/mythos/claimRewards/validations/Declarations.kt:20-32 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/Declarations.kt:52-64 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/redeem/validations/Declarations.kt:35-47 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/unbond/validations/Declarations.kt:51-63 — 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.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/Declarations.kt:33 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/Declarations.kt:33-39 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/Declarations.kt:33-39 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/redeem/validations/Declarations.kt:27-33 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/unbond/validations/Declarations.kt:43-49 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/Declarations.kt:30` calls `profitableClaim` and `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/redeem/validations/Declarations.kt:24` 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 (7 lines × 4) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/AlertsComponent.kt:30 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/AlertsComponent.kt:30-36 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/stakeSummary/StakeSummaryComponent.kt:48-54 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/unbonding/UnbondingComponent.kt:66-72 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/userRewards/UserRewardsComponent.kt:51-57 — 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 `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/alerts/AlertsComponent.kt:30` 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.
DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×2
  • One operation mutates 2 aggregates: RealProfile3AccessTokenProvider.identityFor infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/RealProfile3AccessTokenProvider.kt:123 — `RealProfile3AccessTokenProvider.identityFor` saves `Profile3TokenStore`, `AttestationKeyPairStore` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: RealProfile3AccessTokenProvider.loadToken infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/RealProfile3AccessTokenProvider.kt:135 — `RealProfile3AccessTokenProvider.loadToken` saves `AttestationKeyPairStore`, `Profile3TokenStore` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
AX2 · Stateful singletons · Stateful singleton · ×1
  • Stateful singleton: ContextManager common/src/main/java/io/novafoundation/nova/common/resources/ContextManager.kt:13 — `ContextManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (activity, context; e.g. `activity` in `attachActivity` at line 33).
D1 · Cyclomatic Complexity · BittensorSubmissionExecutor.execute (cyclomatic 37) · ×1
  • BittensorSubmissionExecutor.execute (cyclomatic 37) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt:77 — BittensorSubmissionExecutor.execute has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ResponseCache.observe (cyclomatic 24) · ×1
  • ResponseCache.observe (cyclomatic 24) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt:148 — ResponseCache.observe has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AddFragmentNavigator.navigate (cyclomatic 23) · ×1
  • AddFragmentNavigator.navigate (cyclomatic 23) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/AddFragmentNavigator.java:130 — AddFragmentNavigator.navigate has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics (cyclomatic 18) · ×1
  • BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics (cyclomatic 18) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorOperationAnalyticsMapping.kt:22 — BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · BittensorExitReviewViewModel.confirmClicked (cyclomatic 18) · ×1
  • BittensorExitReviewViewModel.confirmClicked (cyclomatic 18) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:651 — BittensorExitReviewViewModel.confirmClicked has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MetaAccountLocal.equals (cyclomatic 17) · ×1
  • MetaAccountLocal.equals (cyclomatic 17) core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/MetaAccountLocal.kt:92 — MetaAccountLocal.equals has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BittensorExitAmountViewModel.reprepareAndValidate (cyclomatic 17) · ×1
  • BittensorExitAmountViewModel.reprepareAndValidate (cyclomatic 17) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitAmountViewModel.kt:725 — BittensorExitAmountViewModel.reprepareAndValidate has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · AccountSecretsFactory.chainAccountSecrets (cyclomatic 16) · ×1
  • AccountSecretsFactory.chainAccountSecrets (cyclomatic 16) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/secrets/AccountSecretsFactory.kt:55 — AccountSecretsFactory.chainAccountSecrets 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.
D17 · Explicit Debt · FixmeComment · ×1
  • FixmeComment runtime/src/test/java/io/novafoundation/nova/runtime/multiNetwork/runtime/RuntimeProviderTest.kt:26 — // FIXME — 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.
D2 · Cognitive Complexity · BittensorSubmissionExecutor.execute (cognitive 45) · ×1
  • BittensorSubmissionExecutor.execute (cognitive 45) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubmissionExecutor.kt:77 — BittensorSubmissionExecutor.execute has cognitive complexity 45 (threshold 15). Drivers by points: if/else 17 (24 pts), error handling 7 (9 pts), match/switch 5 (8 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResponseCache.observe (cognitive 41) · ×1
  • ResponseCache.observe (cognitive 41) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/cache/ResponseCache.kt:148 — ResponseCache.observe has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 8, error handling 2 (4 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AddFragmentNavigator.navigate (cognitive 34) · ×1
  • AddFragmentNavigator.navigate (cognitive 34) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/AddFragmentNavigator.java:130 — AddFragmentNavigator.navigate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 8 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StackBlur.blur (cognitive 30) · ×1
  • StackBlur.blur (cognitive 30) common/src/main/java/io/novafoundation/nova/common/utils/blur/StackBlur.kt:8 — StackBlur.blur has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 7 (11 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.
D2 · Cognitive Complexity · BittensorMevTracker.scan (cognitive 28) · ×1
  • BittensorMevTracker.scan (cognitive 28) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/mev/BittensorMevTracker.kt:84 — BittensorMevTracker.scan has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), error handling 2 (4 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · BittensorExitReviewViewModel.confirmClicked (cognitive 24) · ×1
  • BittensorExitReviewViewModel.confirmClicked (cognitive 24) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:651 — BittensorExitReviewViewModel.confirmClicked has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (15 pts), error handling 4 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · BittensorExitRemainderValidationKt.dustRemainders (cognitive 21) · ×1
  • BittensorExitRemainderValidationKt.dustRemainders (cognitive 21) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/validations/BittensorExitRemainderValidation.kt:27 — BittensorExitRemainderValidationKt.dustRemainders has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OperationMappersKt.mapOperationToOperationModel (cognitive 19) · ×1
  • OperationMappersKt.mapOperationToOperationModel (cognitive 19) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/history/mixin/OperationMappers.kt:205 — OperationMappersKt.mapOperationToOperationModel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics (cognitive 17) · ×1
  • BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics (cognitive 17) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorOperationAnalyticsMapping.kt:22 — BittensorOperationAnalyticsMappingKt.mapBittensorOperationAnalytics has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 3 (4 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.
D2 · Cognitive Complexity · QrCodeView.renderQRImage (cognitive 16) · ×1
  • QrCodeView.renderQRImage (cognitive 16) common/src/main/java/io/novafoundation/nova/common/view/QrCodeView.kt:110 — QrCodeView.renderQRImage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (7 pts), boolean chains 6, loops 2 (3 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.
D2 · Cognitive Complexity · MetaAccountLocal.equals (cognitive 16) · ×1
  • MetaAccountLocal.equals (cognitive 16) core-db/src/main/java/io/novafoundation/nova/core_db/model/chain/account/MetaAccountLocal.kt:92 — MetaAccountLocal.equals has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ChainAccountSecrets.equals (cognitive 16) · ×1
  • ChainAccountSecrets.equals (cognitive 16) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/domain/model/CloudBackup.kt:142 — ChainAccountSecrets.equals 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.
D2 · Cognitive Complexity · BittensorExitBasis.plan (cognitive 16) · ×1
  • BittensorExitBasis.plan (cognitive 16) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitBasis.kt:63 — BittensorExitBasis.plan has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RealProfile3AccessTokenProvider.loadToken (cognitive 16) · ×1
  • RealProfile3AccessTokenProvider.loadToken (cognitive 16) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/RealProfile3AccessTokenProvider.kt:135 — RealProfile3AccessTokenProvider.loadToken has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (28 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (28 members, 50+ identical tokens) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/di/BalanceListModule.kt:108 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/di/BalanceListModule.kt:108-132 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/di/SelectSendModule.kt:61-85 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/chooseAmount/di/NewDelegationChooseAmountModule.kt:50-68 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/di/NewDelegationConfirmModule.kt:64-89 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/removeVotes/di/RemoveVotesModule.kt:72-90 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/revoke/confirm/di/RevokeDelegationConfirmModule.kt:87-108 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/di/ReferendumDetailsModule.kt:66-88 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/di/ConfirmReferendumVoteModule.kt:60-83 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/setup/referenda/di/SetupReferendumVoteModule.kt:50-68 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tindergov/confirm/di/ConfirmTinderGovVoteModule.kt:71-95 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/unlock/confirm/di/ConfirmGovernanceUnlockModule.kt:66-85 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/details/general/di/MultisigOperationDetailsModule.kt:82-104 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/di/ConfirmStartMythosStakingModule.kt:65-90 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/confirm/di/ConfirmUnbondMythosModule.kt:58-80 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/di/SetupUnbondMythosModule.kt:54-74 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/confirm/di/NominationPoolsConfirmBondMoreModule.kt:51-69 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/di/NominationPoolsConfirmUnbondModule.kt:53-72 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/rebond/di/ParachainStakingRebondModule.kt:78-98 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/redeem/di/ParachainStakingRedeemModule.kt:75-93 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/di/ConfirmStartParachainStakingModule.kt:65-90 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/di/SetupStartParachainStakingModule.kt:73-97 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/confirm/di/ParachainStakingUnbondConfirmModule.kt:58-80 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/di/ParachainStakingUnbondModule.kt:52-71 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/confirm/di/YieldBoostConfirmModule.kt:52-71 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/add/set/di/AddStakingProxyModule.kt:56-76 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/di/StakingModule.kt:58-78 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/confirm/di/ConfirmMultiStakingModule.kt:76-96 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/landing/di/StartStakingLandingModule.kt:75-98 — These 28 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 28 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 28 times.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) bindings/hydra-dx-math/rust/src/lib.rs:125 — bindings/hydra-dx-math/rust/src/lib.rs:125-166 | bindings/hydra-dx-math/rust/src/lib.rs:209-252 | bindings/hydra-dx-math/rust/src/lib.rs:433-471 | bindings/hydra-dx-math/rust/src/lib.rs:514-552 | bindings/hydra-dx-math/rust/src/lib.rs:595-637 — These 5 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 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (57 corresponding lines) · ×1
  • Edited copy of a member (57 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:855 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:855-913 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.kt:571-627 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:70 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:70-103 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/list/repository/ReferendaCommonRepository.kt:109-141 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 39+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 39+ corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:52 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionCancelledNotificationHandler.kt:52-95 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionExecutedNotificationHandler.kt:52-95 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionInitiatedNotificationHandler.kt:52-90 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/multisig/MultisigTransactionNewApprovalNotificationHandler.kt:55-104 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 39 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 (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/SelectGiftAmountViewModel.kt:145 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/SelectGiftAmountViewModel.kt:145-185 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/confirm/CreateGiftConfirmViewModel.kt:133-169 — 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureHolder.kt:48 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureHolder.kt:48-80 | feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/di/SettingsFeatureHolder.kt:32-55 — 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 (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:57 — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:57-85 | feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenSentNotificationHandler.kt:57-87 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) common/src/main/java/io/novafoundation/nova/common/utils/recyclerView/expandable/ExpandableItemAnimator.kt:46 — common/src/main/java/io/novafoundation/nova/common/utils/recyclerView/expandable/ExpandableItemAnimator.kt:46-75 | common/src/main/java/io/novafoundation/nova/common/utils/recyclerView/expandable/ExpandableItemAnimator.kt:77-106 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 24+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:144 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardMythosUpdater.kt:144-167 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:149-172 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardParachainStakingUpdater.kt:92-115 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardRelayStakingUpdater.kt:111-134 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationInterceptor.kt:103 — infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationInterceptor.kt:103-143 | infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/profile3/Profile3Interceptor.kt:105-132 — 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, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureHolder.kt:27 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureHolder.kt:27-42 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureHolder.kt:27-47 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/di/LedgerFeatureHolder.kt:25-43 | feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/di/SwapFeatureHolder.kt:28-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 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, 17+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 17+ corresponding lines) feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:13 — feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:13-36 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:38-57 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:73-89 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:91-107 | feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/action/CloudBackupActions.kt:109-125 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 17 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 (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/BittensorExitValidationsModule.kt:27 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/BittensorExitValidationsModule.kt:27-73 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/BittensorStakeValidationsModule.kt:25-72 — These two members are one piece of code written twice and then edited apart: 47 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 (6 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 17+ corresponding lines) bindings/hydra-dx-math/rust/src/lib.rs:95 — bindings/hydra-dx-math/rust/src/lib.rs:95-115 | bindings/hydra-dx-math/rust/src/lib.rs:179-199 | bindings/hydra-dx-math/rust/src/lib.rs:263-279 | bindings/hydra-dx-math/rust/src/lib.rs:403-423 | bindings/hydra-dx-math/rust/src/lib.rs:484-504 | bindings/hydra-dx-math/rust/src/lib.rs:565-585 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 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 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/networkInfo/nominationPools/NominationPoolsNetworkInfoComponent.kt:61 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/networkInfo/nominationPools/NominationPoolsNetworkInfoComponent.kt:61-73 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/networkInfo/parachain/ParachainNetworkInfoComponent.kt:74-86 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/components/networkInfo/relaychain/RelaychainNetworkInfoComponent.kt:74-86 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1OnChainReferendaRepository.kt:92 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1OnChainReferendaRepository.kt:92-101 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v1/GovV1OnChainReferendaRepository.kt:103-113 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2OnChainReferendaRepository.kt:102-112 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2OnChainReferendaRepository.kt:114-124 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 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, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/orml/OrmlAssetHistory.kt:62 — feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/orml/OrmlAssetHistory.kt:62-79 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/statemine/StatemineAssetHistory.kt:62-76 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/blockchain/assets/history/utility/NativeAssetHistory.kt:66-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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 (5 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 18+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/payouts/confirm/di/ConfirmPayoutModule.kt:52 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/payouts/confirm/di/ConfirmPayoutModule.kt:52-70 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/bond/confirm/di/ConfirmBondMoreModule.kt:48-65 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/confirm/di/ConfirmRebondModule.kt:50-68 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/confirm/di/ConfirmUnbondModule.kt:52-71 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/confirm/di/ConfirmChangeValidatorsModule.kt:59-76 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 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 copies of one member (6 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 8+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RedeemValidationsModule.kt:33 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RedeemValidationsModule.kt:33-40 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RewardDestinationValidationsModule.kt:48-55 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/UnbondValidationsModule.kt:76-83 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/Declarations.kt:43-50 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/redeem/validations/Declarations.kt:51-58 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/unbond/validations/Declarations.kt:82-89 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 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 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/claimRewards/MythosClaimRewardsViewModel.kt:130 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/claimRewards/MythosClaimRewardsViewModel.kt:130-143 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/confirm/NominationPoolsConfirmBondMoreViewModel.kt:129-142 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rebond/confirm/ConfirmRebondViewModel.kt:145-158 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/model/MetaAccount.kt:244 — feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/model/MetaAccount.kt:244-256 | feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/model/MetaAccount.kt:258-270 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/common/listing/MetaAccountWithBalanceListingMixin.kt:118-130 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/details/general/SignatoryListFormatter.kt:118-129 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/WalletDetailsFragment.kt:63 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/WalletDetailsFragment.kt:63-73 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/node/details/NodeDetailsFragment.kt:40-49 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/pincode/PincodeFragment.kt:34-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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 (7 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 4+ corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListFragment.kt:109 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListFragment.kt:109-117 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/novacard/overview/NovaCardFragment.kt:13-21 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/receive/ReceiveFragment.kt:51-59 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/SelectSendFragment.kt:61-69 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/swap/asset/AssetSwapFlowFragment.kt:50-53 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/topup/TopUpAddressFragment.kt:31-39 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/filter/TransactionHistoryFilterFragment.kt:42-49 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 4 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/NominationPoolsBondMoreInteractor.kt:36 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/NominationPoolsBondMoreInteractor.kt:36-42 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/NominationPoolsClaimRewardsInteractor.kt:53-59 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/redeem/NominationPoolsRedeemInteractor.kt:65-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/enterInfo/di/AddTokenEnterInfoModule.kt:37 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/tokens/add/enterInfo/di/AddTokenEnterInfoModule.kt:37-46 | feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/di/WalletFeatureModule.kt:266-275 | runtime/src/main/java/io/novafoundation/nova/runtime/storage/source/RemoteStorageSource.kt:48-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 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 · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/SelectGiftAmountViewModel.kt:163 — feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/SelectGiftAmountViewModel.kt:163-180 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/confirm/CreateGiftConfirmViewModel.kt:149-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/amount/SelectGiftAmountViewModel.kt:163` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17 lines × 28) · ×1
  • Duplicated block (17 lines × 28) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/di/BalanceListModule.kt:116 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/di/BalanceListModule.kt:116-132 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/amount/di/SelectSendModule.kt:69-85 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/chooseAmount/di/NewDelegationChooseAmountModule.kt:52-68 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/di/NewDelegationConfirmModule.kt:73-89 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/removeVotes/di/RemoveVotesModule.kt:74-90 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/revoke/confirm/di/RevokeDelegationConfirmModule.kt:92-108 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/details/di/ReferendumDetailsModule.kt:72-88 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/confirm/di/ConfirmReferendumVoteModule.kt:67-83 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/vote/setup/referenda/di/SetupReferendumVoteModule.kt:52-68 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tindergov/confirm/di/ConfirmTinderGovVoteModule.kt:79-95 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/unlock/confirm/di/ConfirmGovernanceUnlockModule.kt:69-85 | feature-multisig/operations/src/main/java/io/novafoundation/nova/feature_multisig_operations/presentation/details/general/di/MultisigOperationDetailsModule.kt:88-104 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/confirm/di/ConfirmStartMythosStakingModule.kt:74-90 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/confirm/di/ConfirmUnbondMythosModule.kt:64-80 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/unbond/setup/di/SetupUnbondMythosModule.kt:58-74 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/confirm/di/NominationPoolsConfirmBondMoreModule.kt:53-69 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/unbond/confirm/di/NominationPoolsConfirmUnbondModule.kt:56-72 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/rebond/di/ParachainStakingRebondModule.kt:82-98 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/redeem/di/ParachainStakingRedeemModule.kt:77-93 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/di/ConfirmStartParachainStakingModule.kt:74-90 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/di/SetupStartParachainStakingModule.kt:81-97 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/confirm/di/ParachainStakingUnbondConfirmModule.kt:64-80 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/di/ParachainStakingUnbondModule.kt:55-71 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/yieldBoost/confirm/di/YieldBoostConfirmModule.kt:55-71 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/add/set/di/AddStakingProxyModule.kt:60-76 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/main/di/StakingModule.kt:62-78 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/confirm/di/ConfirmMultiStakingModule.kt:80-96 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/landing/di/StartStakingLandingModule.kt:82-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 28 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 28 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/di/BalanceListModule.kt:116` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/mercurio/MercuryoProvider.kt:31 — feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/mercurio/MercuryoProvider.kt:31-47 | feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/transak/TransakProvider.kt:32-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-buy-impl/src/main/java/io/novafoundation/nova/feature_buy_impl/presentation/trade/providers/mercurio/MercuryoProvider.kt:31` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1
  • Duplicated block (13–16 lines × 2) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/LegacyLedgerWalletDetailsMixin.kt:63 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/LegacyLedgerWalletDetailsMixin.kt:63-78 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/ProxiedWalletDetailsMixin.kt:54-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/account/details/mixin/LegacyLedgerWalletDetailsMixin.kt:63` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:76 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:76-91 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardRelayStakingUpdater.kt:69-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/dashboard/network/updaters/chain/StakingDashboardNominationPoolsUpdater.kt:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/mappers/AccountMappers.kt:73 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/mappers/AccountMappers.kt:73-86 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/mappers/AccountMappers.kt:90-103 | feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/mappers/AccountMappers.kt:123-136 — 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 `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/mappers/AccountMappers.kt:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/data/thresold/gov1/Gov1VotingThreshold.kt:29 — feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/data/thresold/gov1/Gov1VotingThreshold.kt:29-42 | feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/data/thresold/gov1/Gov1VotingThreshold.kt:54-67 — 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.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/NewDelegationConfirmViewModel.kt:213 — feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/NewDelegationConfirmViewModel.kt:213-226 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/revoke/confirm/RevokeDelegationConfirmViewModel.kt:188-198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegation/create/confirm/NewDelegationConfirmViewModel.kt:213` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 14) · ×1
  • Duplicated block (6 lines × 14) app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:322 — app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:322-328 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:461-466 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:654-659 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:667-672 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:713-719 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:751-757 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:764-770 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:772-778 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:780-786 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:788-794 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:869-874 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt:876-881 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/staking/relaychain/RelayStakingNavigator.kt:261-266 | app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/staking/relaychain/RelayStakingNavigator.kt:268-273 — there are 14 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 14 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 `payload` to `AddTokenEnterInfoPayload` in one and `AddAccountPayload.ChainAccount` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) common/src/main/java/io/novafoundation/nova/common/list/NestedAdapter.kt:49 — common/src/main/java/io/novafoundation/nova/common/list/NestedAdapter.kt:49-58 | common/src/main/java/io/novafoundation/nova/common/list/SingleItemAdapter.kt:19-28 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/list/DelegateBannerAdapter.kt:31-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1
  • Duplicated block (11 lines × 6) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/connect/preview/di/PreviewImportParitySignerModule.kt:43 — feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/connect/preview/di/PreviewImportParitySignerModule.kt:43-53 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/delegators/di/DelegateDelegatorsModule.kt:34-44 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/detail/votedReferenda/di/VotedReferendaModule.kt:34-44 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/referenda/search/di/ReferendaSearchModule.kt:34-44 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/proxy/list/di/StakingProxyListModule.kt:34-44 | feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/presentation/sessions/details/di/WalletConnectSessionDetailsModule.kt:34-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/paritySigner/connect/preview/di/PreviewImportParitySignerModule.kt:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:35 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:35-45 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt:35-45 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/networks/AssetNetworksInteractor.kt:40-50 — before extracting anything, compare `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByTokensAssetSearchInteractor.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/networks/AssetNetworksInteractor.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/domain/assets/search/ByNetworkAssetSearchInteractor.kt:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/assets/AssetGiftsFlowViewModel.kt:64 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/assets/AssetGiftsFlowViewModel.kt:64-70 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/receive/flow/asset/AssetReceiveFlowViewModel.kt:57-63 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/flow/asset/AssetSendFlowViewModel.kt:67-73 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/trade/buy/flow/asset/AssetBuyFlowViewModel.kt:58-63 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/trade/sell/flow/asset/AssetSellFlowViewModel.kt:58-63 — before extracting anything, compare `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/assets/AssetGiftsFlowViewModel.kt` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/flow/asset/AssetSendFlowViewModel.kt` as WHOLE FILES: 88% 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.
D4 · Code Duplication · Duplicated block (13 lines × 7) · ×1
  • Duplicated block (13 lines × 7) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/networks/di/NetworkGiftsFlowModule.kt:43 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/networks/di/NetworkGiftsFlowModule.kt:43-55 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/receive/flow/network/di/NetworkReceiveFlowModule.kt:43-55 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/flow/network/di/NetworkSendFlowModule.kt:43-55 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/trade/buy/flow/network/di/NetworkBuyFlowModule.kt:43-55 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/trade/sell/flow/network/di/NetworkSellFlowModule.kt:43-55 | feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/tindergov/basket/di/TinderGovBasketModule.kt:38-50 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/connect/generic/preview/di/PreviewImportGenericLedgerModule.kt:54-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/gifts/networks/di/NetworkGiftsFlowModule.kt:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/extrinsic/ExtrinsicDetailFragment.kt:54 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/extrinsic/ExtrinsicDetailFragment.kt:54-64 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/reward/direct/RewardDetailFragment.kt:43-53 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/swap/SwapDetailFragment.kt:56-66 | feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/transfer/TransferDetailFragment.kt:52-62 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/swap/SwapDetailFragment.kt:70` calls `observeDescription` and `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/extrinsic/ExtrinsicDetailFragment.kt:69` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/swap/di/SwapDetailModule.kt:44 — feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/swap/di/SwapDetailModule.kt:44-59 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/claim/di/ClaimGiftModule.kt:49-64 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/bondMore/setup/di/NominationPoolsSetupBondMoreModule.kt:45-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/detail/swap/di/SwapDetailModule.kt:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 6) · ×1
  • Duplicated block (17 lines × 6) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/di/ClaimContributionModule.kt:53 — feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/di/ClaimContributionModule.kt:53-69 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/confirm/di/CreateGiftConfirmModule.kt:51-67 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bagList/rebag/di/RebagModule.kt:74-90 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/nominationPools/claimRewards/di/NominationPoolsClaimRewardsModule.kt:81-97 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/controller/set/di/SetControllerModule.kt:45-61 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/unbond/select/di/SelectUnbondModule.kt:46-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/claimControbution/di/ClaimContributionModule.kt:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/main/di/MainDAppModule.kt:41 — feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/main/di/MainDAppModule.kt:41-52 | feature-gift-impl/src/main/java/io/novafoundation/nova/feature_gift_impl/presentation/gifts/di/GiftsModule.kt:41-52 | feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/presentation/networkManagement/add/networkDetails/di/AddNetworkModule.kt:49-60 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/currentCollators/di/MythosCurrentCollatorsModule.kt:36-47 — 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 `feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/main/di/MainDAppModule.kt:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/addChain/generic/selectLedger/di/AddEvmAccountSelectGenericLedgerModule.kt:42 — feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/addChain/generic/selectLedger/di/AddEvmAccountSelectGenericLedgerModule.kt:42-55 | feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/addChain/legacy/selectAddress/di/AddLedgerChainAccountSelectAddressModule.kt:75-88 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/collator/current/di/CurrentCollatorsModule.kt:56-69 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/current/di/CurrentValidatorsModule.kt:40-53 — 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 `feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/addChain/generic/selectLedger/di/AddEvmAccountSelectGenericLedgerModule.kt:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/controller/confirm/di/ConfirmSetControllerModule.kt:45 — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/controller/confirm/di/ConfirmSetControllerModule.kt:45-61 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/redeem/di/RedeemModule.kt:46-62 | feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/rewardDestination/confirm/di/ConfirmRewardDestinationModule.kt:46-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/delegation/controller/confirm/di/ConfirmSetControllerModule.kt:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23–26 lines × 2) · ×1
  • Duplicated block (23–26 lines × 2) bindings/hydra-dx-math/rust/src/lib.rs:127 — bindings/hydra-dx-math/rust/src/lib.rs:127-149 | bindings/hydra-dx-math/rust/src/lib.rs:211-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×1
  • Duplicated block (8–9 lines × 3) bindings/hydra-dx-math/rust/src/lib.rs:367 — bindings/hydra-dx-math/rust/src/lib.rs:367-374 | bindings/hydra-dx-math/rust/src/lib.rs:446-454 | bindings/hydra-dx-math/rust/src/lib.rs:528-535 — 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 5) · ×1
  • Duplicated block (7–8 lines × 5) bindings/hydra-dx-math/rust/src/lib.rs:126 — bindings/hydra-dx-math/rust/src/lib.rs:126-133 | bindings/hydra-dx-math/rust/src/lib.rs:210-217 | bindings/hydra-dx-math/rust/src/lib.rs:434-440 | bindings/hydra-dx-math/rust/src/lib.rs:515-521 | bindings/hydra-dx-math/rust/src/lib.rs:596-603 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) bindings/hydra-dx-math/rust/src/lib.rs:142 — bindings/hydra-dx-math/rust/src/lib.rs:142-146 | bindings/hydra-dx-math/rust/src/lib.rs:226-231 | bindings/hydra-dx-math/rust/src/lib.rs:612-616 — 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 `bindings/hydra-dx-math/rust/src/lib.rs:142` 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.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience common/src/main/java/io/novafoundation/nova/common/data/network/NetworkApiCreator.kt:17 — `Retrofit.Builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
X25 · Inert configuration knob · Configuration option is read nowhere · ×1
  • Configuration option is read nowhere bindings/hydra-dx-math/rust/src/lib.rs:43 — `AssetBalance.decimals` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Minor — 1057 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×926
  • Orphaned file feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/extrinsic/RealExtrinsicService.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 feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/domain/locks/RealClaimScheduleCalculator.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 feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/history/mixin/OperationMappers.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 feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/domain/sign/polkadot/PolkadotExternalSignInteractor.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/nominationPool/NominationPoolModule.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/relaychain/RelaychainStakingUpdatersModule.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 runtime/src/main/java/io/novafoundation/nova/runtime/multiNetwork/ChainRegistry.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 feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/send/confirm/ConfirmSendViewModel.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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/dynamic/dryRun/XcmTransferDryRunner.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 feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/domain/sign/evm/EvmSignInteractor.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 feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/v2/GovV2OnChainReferendaRepository.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 feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/data/network/crosschain/legacy/LegacyCrossChainWeigher.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 feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/RealWalletConnectSessionInteractor.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/io/novafoundation/nova/app/root/navigation/navigators/AddFragmentNavigator.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/unbond/setup/ParachainStakingUnbondViewModel.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 feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/delegation/delegate/detail/main/DelegateDetailsViewModel.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/setup/StartParachainStakingViewModel.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 feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/presentation/contribute/select/CrowdloanContributeViewModel.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 feature-ledger-impl/src/main/java/io/novafoundation/nova/feature_ledger_impl/presentation/account/common/selectLedger/SelectLedgerViewModel.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 feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/GovernanceUnlockInteractor.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/common/singleSelect/start/StartSingleSelectStakingViewModel.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/mythos/start/setup/SetupStartMythosStakingViewModel.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/staking/start/setupAmount/SetupAmountMultiStakingViewModel.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 feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/web3/metamask/states/DefaultMetamaskState.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/parachainStaking/start/confirm/ConfirmStartParachainStakingViewModel.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.
  • + 901 more in this group — see findings.md.
DM2 · Strongly-typed ids · Primitive id on a domain type · ×40
  • Primitive id on a domain type: AccountLocal.publicKey core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountLocal.kt:11 — `AccountLocal.publicKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: AccountStakingLocal.chainId core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:12 — `AccountStakingLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: AccountStakingLocal.chainAssetId core-db/src/main/java/io/novafoundation/nova/core_db/model/AccountStakingLocal.kt:13 — `AccountStakingLocal.chainAssetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: AnalyticsEventLocal.eventId core-db/src/main/java/io/novafoundation/nova/core_db/model/AnalyticsEventLocal.kt:9 — `AnalyticsEventLocal.eventId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: AssetLocal.assetId core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:23 — `AssetLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: AssetLocal.chainId core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:24 — `AssetLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: AssetLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/AssetLocal.kt:25 — `AssetLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: BalanceHoldLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:36 — `BalanceHoldLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: BalanceHoldLocal.chainId core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:37 — `BalanceHoldLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: BalanceHoldLocal.assetId core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceHoldLocal.kt:38 — `BalanceHoldLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: BalanceLockLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:35 — `BalanceLockLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: BalanceLockLocal.chainId core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:36 — `BalanceLockLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: BalanceLockLocal.assetId core-db/src/main/java/io/novafoundation/nova/core_db/model/BalanceLockLocal.kt:37 — `BalanceLockLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: BrowserTabLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/BrowserTabLocal.kt:22 — `BrowserTabLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: ChainAssetVisibilityLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:40 — `ChainAssetVisibilityLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: ChainAssetVisibilityLocal.chainId core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:41 — `ChainAssetVisibilityLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: ChainAssetVisibilityLocal.assetId core-db/src/main/java/io/novafoundation/nova/core_db/model/ChainAssetVisibilityLocal.kt:42 — `ChainAssetVisibilityLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: CoinPriceLocal.priceId core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:11 — `CoinPriceLocal.priceId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: CoinPriceLocal.currencyId core-db/src/main/java/io/novafoundation/nova/core_db/model/CoinPriceLocal.kt:12 — `CoinPriceLocal.currencyId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: ContributionLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:9 — `ContributionLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • Primitive id on a domain type: ContributionLocal.chainId core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:10 — `ContributionLocal.chainId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: ContributionLocal.assetId core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:11 — `ContributionLocal.assetId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that.
  • Primitive id on a domain type: ContributionLocal.sourceId core-db/src/main/java/io/novafoundation/nova/core_db/model/ContributionLocal.kt:14 — `ContributionLocal.sourceId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: CurrencyLocal.coingeckoId core-db/src/main/java/io/novafoundation/nova/core_db/model/CurrencyLocal.kt:18 — `CurrencyLocal.coingeckoId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: DappAuthorizationLocal.metaId core-db/src/main/java/io/novafoundation/nova/core_db/model/DappAuthorizationLocal.kt:11 — `DappAuthorizationLocal.metaId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that.
  • + 15 more in this group — see findings.md.
AX6 · Interface segregation · Fat interface · ×31
  • Fat interface: ComponentHolderModule (39 abstract methods) app/src/main/java/io/novafoundation/nova/app/di/deps/ComponentHolderModule.kt:89 — `ComponentHolderModule` declares 39 abstract methods: `provideFeatureContainer`, `provideSplashFeatureHolder`, `provideDbFeature`, `provideInfrastructureFeature`, `provideAnalyticsFeature`, `provideOnboardingFeature`, `provideDAppFeature`, `provideLedgerFeature`, `provideLedgerCore`, `provideGovernanceFeature`, `provideAccountFeature`, `provideAssetsFeature`, `provideVoteFeature`, `provideWalletFeature`, `provideCurrencyFeature`, `provideMainFeature`, `provideStakingFeature`, `provideRuntimeFeature`, `provideWeb3Names`, `provideCrowdloanFeature`, `provideNftFeature`, `provideVersionsFeature`, `provideCaipFeature`, `provideExternalSignFeature`, `provideWalletConnectFeature`, `provideSettingsFeature`, `provideSwapFeature`, `provideBuyFeature`, `providePushNotificationsFeature`, `provideProxyFeature`, `provideDeepLinkingFeatureHolder`, `provideCloudBackupFeatureHolder`, `provideSwapCoreFeatureHolder`, `provideBannersFeatureApi`, `provideXcmFeatureHolder`, `provideMultisigOperationsFeatureHolder`, `provideAccountMigrationFeatureHolder`, `provideChainMigrationFeatureHolder`, `provideGiftFeature`. 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: RootDependencies (30 abstract methods) app/src/main/java/io/novafoundation/nova/app/root/di/RootDependencies.kt:70 — `RootDependencies` declares 30 abstract methods: `preferences`, `updateNotificationsInteractor`, `contributionsInteractor`, `crowdloanRepository`, `networkStateMixin`, `externalRequirementsFlow`, `accountRepository`, `walletRepository`, `appLinksProvider`, `legalConsentRepository`, `resourceManager`, `currencyInteractor`, `stakingRepository`, `chainRegistry`, `backgroundAccessObserver`, `safeModeService`, `rootScope`, `governanceStateUpdater`, `dappMetadataRepository`, `encryptionDefaults`, `proxyExtrinsicValidationRequestBus`, `metaAccountChangesRequestBus`, `proxyHaveEnoughFeeValidationFactory`, `context`, `toastMessageManager`, `dialogMessageManager`, `chainMigrationRepository`, `migrationInfoRepository`, `analyticsService`, `analyticsOptOutManager`. 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: Preferences (20 abstract methods) common/src/main/java/io/novafoundation/nova/common/data/storage/Preferences.kt:8 — `Preferences` declares 20 abstract methods: `contains`, `putString`, `getString`, `putBoolean`, `getBoolean`, `putInt`, `putStringSet`, `getInt`, `putLong`, `getLong`, `getStringSet`, `getCurrentLanguage`, `saveCurrentLanguage`, `removeField`, `stringFlow`, `booleanFlow`, `stringSetFlow`, `keyFlow`, `keysFlow`, `edit`. 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: CommonApi (55 abstract methods) common/src/main/java/io/novafoundation/nova/common/di/CommonApi.kt:89 — `CommonApi` declares 55 abstract methods: `copyTextMixin`, `computationalCache`, `imageLoader`, `context`, `provideResourceManager`, `provideNetworkApiCreator`, `provideAppLinksProvider`, `providePreferences`, `backgroundAccessObserver`, `provideEncryptedPreferences`, `provideIconGenerator`, `provideClipboardManager`, `provideDeviceVibrator`, `signer`, `logger`, `contextManager`, `languagesHolder`, `provideJsonMapper`, `socketServiceCreator`, `provideSocketSingleRequestExecutor`, `addressIconGenerator`, `cachingAddressIconGenerator`, `networkStateMixin`, `qrCodeGenerator`, `fileProvider`, `random`, `contentResolver`, `httpExceptionHandler`, `validationExecutor`, `secretStoreV1`, `secretStoreV2`, `customDialogDisplayer`, `appVersionsProvider`, `ethereumAddressFormat`, `sharedPreferences`, `safeModeService`, `twoFactorVerificationService`, `twoFactorVerificationExecutor`, `rootScope`, `bakingParallaxCardCache`, and 15 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: AppDatabase (35 abstract methods) core-db/src/main/java/io/novafoundation/nova/core_db/AppDatabase.kt:248 — `AppDatabase` declares 35 abstract methods: `responseCacheDao`, `nodeDao`, `userDao`, `assetDao`, `operationDao`, `phishingAddressesDao`, `storageDao`, `tokenDao`, `accountStakingDao`, `stakingTotalRewardDao`, `chainDao`, `chainAssetVisibilityDao`, `metaAccountSettingsDao`, `chainAssetDao`, `metaAccountDao`, `dAppAuthorizationDao`, `nftDao`, `phishingSitesDao`, `favouriteDAppsDao`, `currencyDao`, `lockDao`, `contributionDao`, `governanceDAppsDao`, `browserHostSettingsDao`, `walletConnectSessionsDao`, `stakingDashboardDao`, `coinPriceDao`, `stakingRewardPeriodDao`, `externalBalanceDao`, `holdsDao`, `tinderGovDao`, `browserTabsDao`, `multisigOperationsDao`, `giftsDao`, `analyticsEventsDao`. 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: ChainDao (17 abstract methods) core-db/src/main/java/io/novafoundation/nova/core_db/dao/ChainDao.kt:22 — `ChainDao` declares 17 abstract methods: `addChainOrUpdate`, `addChainNode`, `getJoinChainInfo`, `getAllChainIds`, `joinChainInfoFlow`, `getLastChainNodeOrderId`, `chainExists`, `runtimeInfo`, `allRuntimeInfos`, `updateSyncedRuntimeVersion`, `setConnectionState`, `setNodePreferences`, `updateChainNode`, `updateChainName`, `updateAssetToken`, `deleteChain`, `deleteNode`. 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: MetaAccountDao (38 abstract methods) core-db/src/main/java/io/novafoundation/nova/core_db/dao/MetaAccountDao.kt:82 — `MetaAccountDao` declares 38 abstract methods: `insertMetaAccount`, `updateMetaAccount`, `insertChainAccount`, `insertChainAccounts`, `deleteChainAccounts`, `insertProxy`, `getMetaAccounts`, `getMetaAccountsByIds`, `getMetaAccount`, `getMetaAccountsQuantityByStatus`, `getMetaAccountsByStatus`, `getFullMetaAccounts`, `getJoinedMetaAccountsInfoFlow`, `getJoinedMetaAccountsInfoByStatusFlow`, `getMetaAccountsIdsByStatus`, `metaAccountsWithBalanceFlow`, `metaAccountWithBalanceFlow`, `selectMetaAccount`, `updatePositions`, `getJoinedMetaAccountInfo`, `getMetaAccountType`, `selectedMetaAccountInfoFlow`, `metaAccountInfoFlow`, `isMetaAccountExists`, `getMetaAccountInfo`, `metaAccountNameFor`, `updateName`, `findAffectedMetaIdsOnDelete`, `deleteByIds`, `nextAccountPosition`, `selectedMetaAccount`, `hasMetaAccountsCountOfTypeFlow`, `observeMetaAccountsByTypeFlow`, `deleteProxiedMetaAccountsByChain`, `hasMetaAccountsByStatus`, `hasMetaAccountsByType`, `changeAccountsStatus`, `removeMetaAccountsByStatus`. 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: OperationDao (16 abstract methods) core-db/src/main/java/io/novafoundation/nova/core_db/dao/OperationDao.kt:25 — `OperationDao` declares 16 abstract methods: `insertOperationBase`, `insertTransferType`, `insertDirectRewardType`, `insertPoolRewardType`, `insertExtrinsicType`, `insertSwapType`, `insertOperationsBase`, `insertTransferTypes`, `insertDirectRewardTypes`, `insertPoolRewardTypes`, `insertExtrinsicTypes`, `insertSwapTypes`, `observe`, `observeSwapOperations`, `observeTransferOperations`, `getTransferType`. 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: DbApi (28 abstract methods) core-db/src/main/java/io/novafoundation/nova/core_db/di/DbApi.kt:41 — `DbApi` declares 28 abstract methods: `responseCacheDao`, `provideDatabase`, `provideLockDao`, `provideAccountDao`, `contributionDao`, `provideNodeDao`, `provideAssetDao`, `provideOperationDao`, `providePhishingAddressDao`, `storageDao`, `tokenDao`, `accountStakingDao`, `stakingTotalRewardDao`, `chainDao`, `chainAssetDao`, `chainAssetVisibilityDao`, `metaAccountSettingsDao`, `metaAccountDao`, `dappAuthorizationDao`, `nftDao`, `governanceDAppsDao`, `browserHostSettingsDao`, `coinPriceDao`, `stakingRewardPeriodDao`, `tinderGovDao`, `browserTabsDao`, `multisigOperationsDao`, `giftsDao`. 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: AccountFeatureApi (20 abstract methods) feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/di/AccountFeatureApi.kt:63 — `AccountFeatureApi` declares 20 abstract methods: `localIdentityProvider`, `onChainIdentityProvider`, `localWithOnChainIdentityProvider`, `metaAccountGroupingInteractor`, `accountInteractor`, `provideAccountRepository`, `externalAccountActions`, `accountUpdateScope`, `addressDisplayUseCase`, `accountUseCase`, `extrinsicService`, `extrinsicServiceFactory`, `importTypeChooserMixin`, `twoFactorVerificationExecutor`, `biometricServiceFactory`, `encryptionDefaults`, `proxyExtrinsicValidationRequestBus`, `cloudBackupFacade`, `syncWalletsBackupPasswordCommunicator`, `copyAddressMixin`. 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: AccountInteractor (31 abstract methods) feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountInteractor.kt:15 — `AccountInteractor` declares 31 abstract methods: `getActiveMetaAccounts`, `generateMnemonic`, `getCryptoTypes`, `getPreferredCryptoType`, `isCodeSet`, `savePin`, `isPinCorrect`, `getMetaAccount`, `selectMetaAccount`, `selectedMetaAccount`, `deleteAccount`, `updateMetaAccountPositions`, `chainFlow`, `nodesFlow`, `getNode`, `getLanguages`, `getSelectedLanguage`, `changeSelectedLanguage`, `addNode`, `updateNode`, `getAccountsByNetworkTypeWithSelectedNode`, `selectNodeAndAccount`, `selectNode`, `deleteNode`, `getChainAddress`, `removeDeactivatedMetaAccounts`, `switchToNotDeactivatedAccountIfNeeded`, `hasSecretsAccounts`, `hasCustomChainAccounts`, `deleteProxiedMetaAccountsByChain`, `findMetaAccount`. 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: AccountRepository (57 abstract methods) feature-account-api/src/main/java/io/novafoundation/nova/feature_account_api/domain/interfaces/AccountRepository.kt:19 — `AccountRepository` declares 57 abstract methods: `getEncryptionTypes`, `getNode`, `getSelectedNodeOrDefault`, `selectNode`, `getDefaultNode`, `selectAccount`, `getSelectedMetaAccount`, `getMetaAccount`, `metaAccountFlow`, `selectedMetaAccountFlow`, `findMetaAccount`, `accountNameFor`, `hasActiveMetaAccounts`, `allMetaAccountsFlow`, `activeMetaAccountsFlow`, `metaAccountsByTypeFlow`, `metaAccountBalancesFlow`, `selectMetaAccount`, `updateMetaAccountName`, `isAccountSelected`, `deleteAccount`, `getAccounts`, `getAccount`, `getAccountOrNull`, `getMyAccounts`, `isCodeSet`, `savePinCode`, `getPinCode`, `generateMnemonic`, `isBiometricEnabledFlow`, `isBiometricEnabled`, `setBiometricOn`, `setBiometricOff`, `nodesFlow`, `updateAccountsOrdering`, `getLanguages`, `selectedLanguage`, `changeLanguage`, `addNode`, `updateNode`, and 17 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: AccountDataSource (42 abstract methods) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/data/repository/datasource/AccountDataSource.kt:24 — `AccountDataSource` declares 42 abstract methods: `getAuthTypeFlow`, `saveAuthType`, `getAuthType`, `savePinCode`, `getPinCode`, `saveSelectedNode`, `getSelectedNode`, `anyAccountSelected`, `saveSelectedAccount`, `getSelectedMetaAccount`, `selectedMetaAccountFlow`, `findMetaAccount`, `accountNameFor`, `allMetaAccountsFlow`, `activeMetaAccountsFlow`, `metaAccountsWithBalancesFlow`, `metaAccountBalancesFlow`, `selectMetaAccount`, `updateAccountPositions`, `getSelectedLanguage`, `changeSelectedLanguage`, `accountExists`, `getMetaAccount`, `getMetaAccountType`, `metaAccountFlow`, `updateMetaAccountName`, `deleteMetaAccount`, `insertMetaAccountWithChainAccounts`, `insertMetaAccountFromSecrets`, `insertChainAccount`, `hasActiveMetaAccounts`, `removeDeactivatedMetaAccounts`, `getActiveMetaAccounts`, `getActiveMetaIds`, `getAllMetaAccounts`, `getMetaAccountsByIds`, `hasMetaAccountsCountOfTypeFlow`, `getActiveMetaAccountsQuantity`, `hasSecretsAccounts`, `deleteProxiedMetaAccountsByChain`, 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: AccountFeatureComponent (42 abstract methods) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureComponent.kt:85 — `AccountFeatureComponent` declares 42 abstract methods: `advancedEncryptionComponentFactory`, `importAccountComponentFactory`, `backupMnemonicComponentFactory`, `createWalletBackupPasswordFactory`, `syncWalletsBackupPasswordFactory`, `changeBackupPasswordComponentFactory`, `restoreCloudBackupFactory`, `checkCloudBackupPasswordFactory`, `restoreCloudBackupPasswordFactory`, `pincodeComponentFactory`, `confirmMnemonicComponentFactory`, `walletManagmentComponentFactory`, `switchWalletComponentFactory`, `selectWalletComponentFactory`, `selectAddressComponentFactory`, `chainAddressSelectorComponent`, `selectMultipleWalletsComponentFactory`, `selectSingleWalletComponentFactory`, `delegatedAccountUpdatesFactory`, `accountDetailsComponentFactory`, `connectionsComponentFactory`, `nodeDetailsComponentFactory`, `languagesComponentFactory`, `addNodeComponentFactory`, `exportSeedFactory`, `exportJsonPasswordFactory`, `inject`, `createWatchOnlyComponentFactory`, `changeWatchAccountComponentFactory`, `startImportParitySignerComponentFactory`, `scanImportParitySignerComponentFactory`, `previewImportParitySignerComponentFactory`, `finishImportParitySignerComponentFactory`, `showSignParitySignerComponentFactory`, `scanSignParitySignerComponentFactory`, `startCreateWallet`, `manualBackupSelectWallet`, `manualBackupWarning`, `manualBackupSecrets`, `manualBackupSelectAccount`, 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: AccountFeatureDependencies (46 abstract methods) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/di/AccountFeatureDependencies.kt:85 — `AccountFeatureDependencies` declares 46 abstract methods: `sharedPreferences`, `logger`, `analyticsService`, `appLinksProvider`, `preferences`, `encryptedPreferences`, `resourceManager`, `iconGenerator`, `clipboardManager`, `context`, `deviceVibrator`, `userDao`, `nodeDao`, `multisigOperationsDao`, `languagesHolder`, `socketSingleRequestExecutor`, `jsonMapper`, `addressIconGenerator`, `currencyInteractor`, `cachingIconGenerator`, `random`, `secretStoreV1`, `secretStoreV2`, `metaAccountDao`, `chainRegistry`, `extrinsicBuilderFactory`, `rpcCalls`, `imageLoader`, `backgroundAccessObserver`, `appVersionProvider`, `validationExecutor`, `updateNotificationsInteractor`, `safeModeService`, `web3NamesInteractor`, `twoFactorVerificationService`, `twoFactorVerificationExecutor`, `computationalCache`, `getProxyRepository`, `cloudBackupService`, `provideActionBottomSheetLauncherFactory`, and 6 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: AccountRouter (44 abstract methods) feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/AccountRouter.kt:18 — `AccountRouter` declares 44 abstract methods: `openWelcomeScreen`, `openMain`, `openCreatePincode`, `openMnemonicScreen`, `openAdvancedSettings`, `openConfirmMnemonicOnCreate`, `openWallets`, `openSwitchWallet`, `openDelegatedAccountsUpdates`, `openNodes`, `openCreateWallet`, `openWalletDetails`, `openNodeDetails`, `openAddNode`, `openChangeWatchAccount`, `getExportMnemonicDelayedNavigation`, `getExportSeedDelayedNavigation`, `getExportJsonDelayedNavigation`, `exportJsonAction`, `openImportAccountScreen`, `openImportOptionsScreen`, `returnToWallet`, `finishExportFlow`, `openScanImportParitySigner`, `openPreviewImportParitySigner`, `openFinishImportParitySigner`, `openScanParitySignerSignature`, `finishParitySignerFlow`, `openAddLedgerChainAccountFlow`, `openCreateCloudBackupPassword`, `restoreCloudBackup`, `openSyncWalletsBackupPassword`, `openChangeBackupPasswordFlow`, `openRestoreBackupPassword`, `openChangeBackupPassword`, `openManualBackupSelectAccount`, `openManualBackupConditions`, `openManualBackupSecrets`, `openManualBackupAdvancedSecrets`, `openChainAddressSelector`, and 4 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AssetsFeatureComponent (32 abstract methods) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureComponent.kt:69 — `AssetsFeatureComponent` declares 32 abstract methods: `balanceListComponentFactory`, `balanceDetailComponentFactory`, `chooseAmountComponentFactory`, `confirmTransferComponentFactory`, `transactionDetailComponentFactory`, `swapDetailComponentFactory`, `transactionHistoryComponentFactory`, `rewardDetailComponentFactory`, `poolRewardDetailComponentFactory`, `extrinsicDetailComponentFactory`, `receiveComponentFactory`, `assetSearchComponentFactory`, `manageTokensComponentFactory`, `addTokenSelectChainComponentFactory`, `addTokenEnterInfoComponentFactory`, `sendFlowComponent`, `swapFlowComponent`, `receiveFlowComponent`, `buyFlowComponent`, `sellFlowComponent`, `giftsFlowComponent`, `tradeProviderListComponent`, `tradeWebComponent`, `networkBuyFlowComponent`, `networkSellFlowComponent`, `networkReceiveFlowComponent`, `networkSendFlowComponent`, `topUpCardComponentFactory`, `networkGiftsFlowComponent`, `novaCardComponentFactory`, `waitingNovaCardTopUpComponentFactory`, `inject`. 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: AssetsFeatureDependencies (55 abstract methods) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureDependencies.kt:134 — `AssetsFeatureDependencies` declares 55 abstract methods: `assetVisibilityRepository`, `assetVisibilityUseCase`, `showReceivedAssetUseCase`, `web3NamesInteractor`, `contributionsInteractor`, `contributionsRepository`, `locksDao`, `currencyInteractor`, `currencyRepository`, `metaAccountGroupingInteractor`, `accountInteractor`, `preferences`, `encryptedPreferences`, `resourceManager`, `iconGenerator`, `clipboardManager`, `contentResolver`, `accountRepository`, `networkCreator`, `signer`, `logger`, `jsonMapper`, `addressIconGenerator`, `appLinksProvider`, `qrCodeGenerator`, `fileProvider`, `externalAccountActions`, `httpExceptionHandler`, `addressDisplayUseCase`, `chainRegistry`, `defaultAssetsRepository`, `remoteStorageSource`, `localStorageSource`, `extrinsicService`, `imageLoader`, `selectedAccountUseCase`, `validationExecutor`, `eventsRepository`, `walletRepository`, `feeLoaderMixinFactory`, and 15 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: AssetsRouter (49 abstract methods) feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/AssetsRouter.kt:14 — `AssetsRouter` declares 49 abstract methods: `openAssetDetails`, `finishTradeOperation`, `back`, `openFilter`, `openSend`, `openConfirmTransfer`, `openTransferDetail`, `openExtrinsicDetail`, `openRewardDetail`, `openPoolRewardDetail`, `openSwapDetail`, `openSwitchWallet`, `openSelectAddress`, `openSelectSingleWallet`, `openSelectMultipleWallets`, `openReceive`, `openAssetSearch`, `openManageTokens`, `openAddTokenEnterInfo`, `openAddTokenSelectChain`, `openSendFlow`, `openReceiveFlow`, `openBuyFlow`, `openSellFlow`, `openBuyFlowFromSendFlow`, `openNfts`, `finishAddTokenFlow`, `openWalletConnectSessions`, `openWalletConnectScan`, `openSwapTab`, `returnToMainScreen`, `closeSendFlow`, `openNovaCard`, `openAwaitingCardCreation`, `closeNovaCard`, `openSendNetworks`, `openReceiveNetworks`, `openBuyNetworks`, `openSellNetworks`, `openGiftsNetworks`, and 9 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: CrowdloanFeatureDependencies (28 abstract methods) feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/di/CrowdloanFeatureDependencies.kt:46 — `CrowdloanFeatureDependencies` declares 28 abstract methods: `contributionDao`, `assetVisibilityUseCase`, `accountUpdaterScope`, `selectedAccountUseCase`, `walletConstants`, `storageCache`, `imageLoader`, `accountRepository`, `addressIconGenerator`, `appLinksProvider`, `walletRepository`, `tokenRepository`, `resourceManager`, `externalAccountActions`, `networkApiCreator`, `httpExceptionHandler`, `gson`, `addressxDisplayUseCase`, `extrinsicService`, `validationExecutor`, `remoteStorageSource`, `localStorageSource`, `chainStateRepository`, `chainRegistry`, `preferences`, `secretStoreV2`, `customDialogDisplayer`, `feeLoaderMixinFactory`. 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: DAppFeatureDependencies (20 abstract methods) feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/di/DAppFeatureDependencies.kt:45 — `DAppFeatureDependencies` declares 20 abstract methods: `analyticsService`, `currencyRepository`, `accountRepository`, `resourceManager`, `appLinksProvider`, `selectedAccountUseCase`, `addressIconGenerator`, `gson`, `chainRegistry`, `imageLoader`, `feeLoaderMixinFactory`, `extrinsicService`, `tokenRepository`, `secretStoreV2`, `extrinsicGson`, `apiCreator`, `runtimeVersionsRepository`, `dappAuthorizationDao`, `browserHostSettingsDao`, `toastMessageManager`. 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: GovernanceFeatureComponent (29 abstract methods) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureComponent.kt:58 — `GovernanceFeatureComponent` declares 29 abstract methods: `referendaListFactory`, `referendaSearchFactory`, `referendumDetailsFactory`, `descriptionFactory`, `referendumInfoFactory`, `referendumFullDetailsFactory`, `setupReferendumVoteFactory`, `setupTinderGovVoteFactory`, `confirmReferendumVoteFactory`, `confirmTinderGovVoteFactory`, `referendumVotersFactory`, `confirmGovernanceUnlockFactory`, `governanceLocksOverviewFactory`, `delegateListFactory`, `delegateSearchFactory`, `delegateDetailsFactory`, `votedReferendaFactory`, `removeVoteFactory`, `delegateDelegatorsFactory`, `yourDelegationsFactory`, `newDelegationChooseTracks`, `selectGovernanceTracks`, `newDelegationChooseAmountFactory`, `newDelegationConfirmFactory`, `revokeDelegationChooseTracksFactory`, `revokeDelegationConfirmFactory`, `referendaFiltersFactory`, `tinderGovCardsFactory`, `tinderGovBasketFactory`. 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: GovernanceRouter (37 abstract methods) feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/GovernanceRouter.kt:22 — `GovernanceRouter` declares 37 abstract methods: `openReferendum`, `openReferendaSearch`, `openReferendaFilters`, `openDAppBrowser`, `openReferendumDescription`, `openReferendumFullDetails`, `openReferendumVoters`, `openSetupReferendumVote`, `openSetupTinderGovVote`, `openConfirmGovernanceUnlock`, `openConfirmVoteReferendum`, `openGovernanceLocksOverview`, `backToReferendumDetails`, `finishUnlockFlow`, `openWalletDetails`, `openAddDelegation`, `openYourDelegations`, `openDelegateDetails`, `openVotedReferenda`, `openDelegateFullDescription`, `openBecomingDelegateTutorial`, `openRemoveVotes`, `openDelegateDelegators`, `openNewDelegationChooseTracks`, `openNewDelegationChooseAmount`, `openNewDelegationConfirm`, `backToYourDelegations`, `openRevokeDelegationChooseTracks`, `openRevokeDelegationsConfirm`, `openDelegateSearch`, `openSelectGovernanceTracks`, `openTinderGovCards`, `openTinderGovBasket`, `openConfirmTinderGovVote`, `backToTinderGovCards`, `openReferendumInfo`, `openReferendumFromDeepLink`. 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: NftFeatureDependencies (17 abstract methods) feature-nft-impl/src/main/java/io/novafoundation/nova/feature_nft_impl/di/NftFeatureDependencies.kt:24 — `NftFeatureDependencies` declares 17 abstract methods: `analyticsService`, `accountRepository`, `resourceManager`, `selectedAccountUseCase`, `addressIconGenerator`, `gson`, `chainRegistry`, `imageLoader`, `externalAccountActions`, `addressDisplayUseCase`, `feeLoaderMixinFactory`, `extrinsicService`, `tokenRepository`, `apiCreator`, `nftDao`, `remoteStorageSource`, `exceptionHandler`. 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: SettingsRouter (21 abstract methods) feature-settings-impl/src/main/java/io/novafoundation/nova/feature_settings_impl/SettingsRouter.kt:8 — `SettingsRouter` declares 21 abstract methods: `openWallets`, `openNetworks`, `openNetworkDetails`, `openCustomNode`, `openPushNotificationSettings`, `openCurrencies`, `openLanguages`, `openAppearance`, `openPrivacy`, `openChangePinCode`, `openWalletDetails`, `openSwitchWallet`, `openWalletConnectScan`, `openWalletConnectSessions`, `openCloudBackupSettings`, `openManualBackup`, `addNetwork`, `openCreateNetworkFlow`, `finishCreateNetworkFlow`, `openEditNetwork`, `returnToWallet`. 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.
  • + 6 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×18
  • Duplicated predicate feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorDetailsViewModel.kt:121 — `!refreshing && (state.isLoading() || state.dataOrNull?.dataStatus is BittensorDataStatus.Loading)` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorDetailsViewModel.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorRootDetailsViewModel.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 feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt:90 — `accountRepository.isNotSingleMetaAccount() && accountName != null` appears character-identically in 2 files — feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenReceivedNotificationHandler.kt, feature-push-notifications/src/main/java/io/novafoundation/nova/feature_push_notifications/presentation/handling/types/TokenSentNotificationHandler.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorRootDetailsViewModel.kt:215 — `allowed && state.dataOrNull?.canWithdraw == true` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorRootDetailsViewModel.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionViewModel.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitInteractor.kt:167 — `amount.isPositive() && amount.bitLength() <= 64` appears character-identically in 3 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitInteractor.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitModels.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitPlan.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 runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/multisig/MultisigCallNode.kt:19 — `call.module.name == Modules.MULTISIG && call.function.name == "as_multi"` appears character-identically in 2 files — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/multisig/MultisigCallNode.kt, runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/multisig/MultisigNode.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 runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/proxy/ProxyCallNode.kt:19 — `call.module.name == Modules.PROXY && call.function.name in proxyCalls` appears character-identically in 2 files — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/proxy/ProxyCallNode.kt, runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/proxy/ProxyNode.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 runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/batch/BatchAllCallNode.kt:9 — `call.module.name == Modules.UTILITY && call.function.name == "batch_all"` appears character-identically in 2 files — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/batch/BatchAllCallNode.kt, runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/batch/BatchAllNode.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 runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/batch/ForceBatchCallNode.kt:9 — `call.module.name == Modules.UTILITY && call.function.name == "force_batch"` appears character-identically in 2 files — runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/call/impl/nodes/batch/ForceBatchCallNode.kt, runtime/src/main/java/io/novafoundation/nova/runtime/extrinsic/visitor/extrinsic/impl/nodes/batch/ForceBatchNode.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorBlockRequotes.kt:53 — `cause is CancellationException && cause !is TimeoutCancellationException` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorBlockRequotes.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/common/BittensorRetryController.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorRootDetailsViewModel.kt:175 — `data == null || data.dataStatus !is BittensorDataStatus.Fresh || primary == null` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/details/BittensorRootDetailsViewModel.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/position/BittensorSubnetPositionViewModel.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/mev/BittensorMevReview.kt:38 — `e is CancellationException && e !is TimeoutCancellationException` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/mev/BittensorMevReview.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/mev/BittensorMevService.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSlippage.kt:13 — `fraction.isNonNegative && fraction < BigDecimal.ONE` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSlippage.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorSubnetQuoteInteractor.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorSubnetStakeOperation.kt:19 — `hotkey.value.size == 32 && beneficiary.value.size == 32` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorSubnetStakeOperation.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorExitOperation.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorPositionSource.kt:54 — `it.metaAccountId == metaAccountId && it.normalizedUrl == key` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorPositionSource.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorPricesSource.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorValidatorMapping.kt:98 — `maxCommissionRate.isNonNegative && maxCommissionRate <= BigDecimal.ONE` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/bittensor/BittensorValidatorMapping.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bittensor/BittensorValidatorSelection.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt:602 — `mevSupported.first() && !validating.value && feeLoaderMixin.fee.value is FeeStatus.Loaded` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/exit/BittensorExitReviewViewModel.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.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 common/src/main/java/io/novafoundation/nova/common/utils/search/SearchComparator.kt:43 — `phraseSearch != null && phraseSearch.isPhraseQuery()` appears character-identically in 2 files — common/src/main/java/io/novafoundation/nova/common/utils/search/SearchComparator.kt, common/src/main/java/io/novafoundation/nova/common/utils/search/SearchFilter.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 feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt:494 — `quote == null || annual == null || subnet == null` appears character-identically in 2 files — feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetAmountViewModel.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/bittensor/subnet/BittensorSubnetReviewViewModel.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.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×17
  • Projects may be oversized for their cohesion feature-staking-impl/build.gradle:1 — `feature-staking-impl` (84254 LoC, 2957 module-visible types across 495 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-account-impl/build.gradle:1 — `feature-account-impl` (25111 LoC, 813 module-visible types across 224 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-governance-impl/build.gradle:1 — `feature-governance-impl` (22926 LoC, 745 module-visible types across 180 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion common/build.gradle:1 — `common` (22285 LoC, 1134 module-visible types across 126 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-assets/build.gradle:1 — `feature-assets` (18091 LoC, 571 module-visible types across 122 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-account-api/build.gradle:1 — `feature-account-api` (6308 LoC, 527 module-visible types across 94 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-ledger-impl/build.gradle:1 — `feature-ledger-impl` (6809 LoC, 285 module-visible types across 71 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-wallet-impl/build.gradle:1 — `feature-wallet-impl` (9840 LoC, 215 module-visible types across 70 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-crowdloan-impl/build.gradle:1 — `feature-crowdloan-impl` (6824 LoC, 277 module-visible types across 69 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion runtime/build.gradle:1 — `runtime` (10577 LoC, 484 module-visible types across 65 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-dapp-impl/build.gradle:1 — `feature-dapp-impl` (8261 LoC, 345 module-visible types across 62 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-wallet-api/build.gradle:1 — `feature-wallet-api` (8971 LoC, 567 module-visible types across 59 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion app/build.gradle:1 — `app` (7608 LoC, 178 module-visible types across 54 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-swap-impl/build.gradle:1 — `feature-swap-impl` (10418 LoC, 269 module-visible types across 51 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-settings-impl/build.gradle:1 — `feature-settings-impl` (5598 LoC, 209 module-visible types across 45 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion core-db/build.gradle:1 — `core-db` (6387 LoC, 335 module-visible types across 11 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion feature-push-notifications/build.gradle:1 — `feature-push-notifications` (4880 LoC, 187 module-visible types across 27 directories) overshoots its size bounds. 17 of 68 build unit(s) (Cargo, Gradle) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D21 · Naming Consistency · `sufficientBalanceToStayAboveEd` spells `Ed` where 46 names in the project spell it `ED` · ×2
  • `sufficientBalanceToStayAboveEd` spells `Ed` where 46 names in the project spell it `ED` feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/add/Declarations.kt:32 — 46 of 48 names in project feature-staking-impl spell the token `ED` (46 of 48; unit: names in project feature-staking-impl containing `ED`). Peers: StakingFeatureDependencies.enoughTotalToStayAboveEDValidationFactory (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:274); AddStakingProxyValidationsModule.provideAddStakingProxyValidationSystem(enoughTotalToStayAboveEDValidationFactory) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/AddStakingProxyValidationsModule.kt:24); BondMoreValidationsModule.provideBondMoreValidationSystem(enoughTotalToStayAboveEDValidationFactory) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/BondMoreValidationsModule.kt:16); RebondValidationsModule.provideEnoughTotalToStayAboveEDValidation (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RebondValidationsModule.kt:44); RebondValidationsModule.provideEnoughTotalToStayAboveEDValidation(enoughTotalToStayAboveEDValidationFactory) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RebondValidationsModule.kt:44). Rename to `sufficientBalanceToStayAboveED`. [rule N6]
  • `sufficientBalanceToStayAboveEd` spells `Ed` where 46 names in the project spell it `ED` feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/validations/delegation/proxy/remove/Declarations.kt:15 — 46 of 48 names in project feature-staking-impl spell the token `ED` (46 of 48; unit: names in project feature-staking-impl containing `ED`). Peers: StakingFeatureDependencies.enoughTotalToStayAboveEDValidationFactory (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:274); AddStakingProxyValidationsModule.provideAddStakingProxyValidationSystem(enoughTotalToStayAboveEDValidationFactory) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/AddStakingProxyValidationsModule.kt:24); BondMoreValidationsModule.provideBondMoreValidationSystem(enoughTotalToStayAboveEDValidationFactory) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/BondMoreValidationsModule.kt:16); RebondValidationsModule.provideEnoughTotalToStayAboveEDValidation (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RebondValidationsModule.kt:44); RebondValidationsModule.provideEnoughTotalToStayAboveEDValidation(enoughTotalToStayAboveEDValidationFactory) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/validations/RebondValidationsModule.kt:44). Rename to `sufficientBalanceToStayAboveED`. [rule N6]
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch feature-crowdloan-impl/src/main/java/io/novafoundation/nova/feature_crowdloan_impl/domain/contributions/RealContributionsInteractor.kt:79 — `getParachainMetadata` swallows every exception into `emptyMap()` — 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 feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/data/repository/MultiSourceOffChainReferendaInfoRepository.kt:22 — `referendumPreviews` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 41 significant file(s) lose their only recent owner: app/src/main/java/io/novafoundation/nova/app/root/navigation/navigators/Navigator.kt, common/src/main/java/io/novafoundation/nova/common/di/modules/CommonModule.kt, feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/balance/list/BalanceListViewModel.kt, infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/ClientAttestationService.kt, feature-assets/src/main/java/io/novafoundation/nova/feature_assets/di/AssetsFeatureModule.kt, feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt, feature-dapp-impl/src/main/java/io/novafoundation/nova/feature_dapp_impl/presentation/browser/main/DAppBrowserFragment.kt, feature-wallet-api/src/main/java/io/novafoundation/nova/feature_wallet_api/presentation/view/priceCharts/PriceChartsView.kt (+33 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (43 single-owned of 1976 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1976 of the 6239 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: runtime/src/main/java/io/novafoundation/nova/runtime/network/updaters/BlockTimeSampling.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/data/network/blockhain/updaters/ValidatorExposureUpdater.kt.
D21 · Naming Consistency · `EmptyGroupRVItem` spells `RV` where 12 names in the project spell it `Rv` · ×1
  • `EmptyGroupRVItem` spells `RV` where 12 names in the project spell it `Rv` feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/wallets/ManualBackupWalletsAdapter.kt:23 — 12 of 13 names in project feature-account-impl spell the token `Rv` (12 of 13; unit: names in project feature-account-impl containing `Rv`). Peers: io.novafoundation.nova.feature_account_impl.presentation.manualBackup.accounts.adapter.ManualBackupRvItem (feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/accounts/adapter/ManualBackupRvItem.kt:5); io.novafoundation.nova.feature_account_impl.presentation.manualBackup.accounts.adapter.ManualBackupAccountGroupRvItem (feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/accounts/adapter/ManualBackupRvItem.kt:7); io.novafoundation.nova.feature_account_impl.presentation.manualBackup.accounts.adapter.ManualBackupAccountRvItem (feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/accounts/adapter/ManualBackupRvItem.kt:11); io.novafoundation.nova.feature_account_impl.presentation.manualBackup.secrets.common.adapter.viewHolders.ManualBackupChainRvItem (feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/secrets/common/adapter/viewHolders/ManualBackupChainItem.kt:8); io.novafoundation.nova.feature_account_impl.presentation.manualBackup.secrets.common.adapter.viewHolders.ManualBackupCryptoTypeRvItem (feature-account-impl/src/main/java/io/novafoundation/nova/feature_account_impl/presentation/manualBackup/secrets/common/adapter/viewHolders/ManualBackupCryptoTypeItem.kt:8). Rename to `EmptyGroupRvItem`. [rule N6]
D21 · Naming Consistency · `CloudBackupChangingWarningMixinUIKt` spells `UI` where 14 names in the project spell it `Ui` · ×1
  • `CloudBackupChangingWarningMixinUIKt` spells `UI` where 14 names in the project spell it `Ui` feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/mixin/CloudBackupChangingWarningMixinUI.kt:1 — 14 of 15 names in project feature-cloud-backup-api spell the token `Ui` (14 of 15; unit: names in project feature-cloud-backup-api containing `Ui`). Peers: io.novafoundation.nova.feature_cloud_backup_api.presenter.errorHandling.ChangePasswordCloudBackupFailureToUiKt (feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/ChangePasswordCloudBackupFailureToUi.kt:1); ChangePasswordCloudBackupFailureToUiKt.mapChangePasswordValidationStatusToUi (feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/ChangePasswordCloudBackupFailureToUi.kt:14); io.novafoundation.nova.feature_cloud_backup_api.presenter.errorHandling.CheckBackupAvailableFailureToUiKt (feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/CheckBackupAvailableFailureToUi.kt:1); CheckBackupAvailableFailureToUiKt.mapCheckBackupAvailableFailureToUi (feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/CheckBackupAvailableFailureToUi.kt:12); io.novafoundation.nova.feature_cloud_backup_api.presenter.errorHandling.ConnectCloudBackupFailureToUiKt (feature-cloud-backup-api/src/main/java/io/novafoundation/nova/feature_cloud_backup_api/presenter/errorHandling/ConnectCloudBackupFailureToUi.kt:1). Rename to `CloudBackupChangingWarningMixinUiKt`. [rule N6]
D21 · Naming Consistency · `ShareReferendumUIKt` spells `UI` where 67 names in the project spell it `Ui` · ×1
  • `ShareReferendumUIKt` spells `UI` where 67 names in the project spell it `Ui` feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/presentation/common/share/ShareReferendumUI.kt:1 — 67 of 68 names in project feature-governance-impl spell the token `Ui` (67 of 68; unit: names in project feature-governance-impl containing `Ui`). Peers: GovernanceFeatureDependencies.walletUiUseCase (feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/di/GovernanceFeatureDependencies.kt:141); io.novafoundation.nova.feature_governance_impl.domain.delegation.delegation.create.chooseAmount.validation.ValidationFailureUiKt (feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/create/chooseAmount/validation/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_governance_impl.domain.delegation.delegation.removeVotes.validations.ValidationFailureUiKt (feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/removeVotes/validations/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_governance_impl.domain.delegation.delegation.revoke.validations.ValidationFailureUiKt (feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/delegation/delegation/revoke/validations/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_governance_impl.domain.referendum.unlock.validations.ValidationFailureUiKt (feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/validations/ValidationFailureUi.kt:1). Rename to `ShareReferendumUiKt`. [rule N6]
D21 · Naming Consistency · `RewardDestinationUIKt` spells `UI` where 153 names in the project spell it `Ui` · ×1
  • `RewardDestinationUIKt` spells `UI` where 153 names in the project spell it `Ui` feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/common/rewardDestination/RewardDestinationUI.kt:1 — 153 of 157 names in project feature-staking-impl spell the token `Ui` (153 of 157; unit: names in project feature-staking-impl containing `Ui`). Peers: StakingFeatureDependencies.walletUiUseCase (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:131); io.novafoundation.nova.feature_staking_impl.domain.bagList.rebag.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bagList/rebag/validations/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.bondMore.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:1); ValidationFailureUiKt.nominationPoolsBondMoreValidationFailure(updateAmountInUi) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:18); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.claimRewards.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/ValidationFailureUi.kt:1). Rename to `RewardDestinationUiKt`. [rule N6]
D21 · Naming Consistency · `SelectPoolValidationFailureUIKt` spells `UI` where 153 names in the project spell it `Ui` · ×1
  • `SelectPoolValidationFailureUIKt` spells `UI` where 153 names in the project spell it `Ui` feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/pools/searchPool/SelectPoolValidationFailureUI.kt:1 — 153 of 157 names in project feature-staking-impl spell the token `Ui` (153 of 157; unit: names in project feature-staking-impl containing `Ui`). Peers: StakingFeatureDependencies.walletUiUseCase (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:131); io.novafoundation.nova.feature_staking_impl.domain.bagList.rebag.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bagList/rebag/validations/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.bondMore.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:1); ValidationFailureUiKt.nominationPoolsBondMoreValidationFailure(updateAmountInUi) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:18); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.claimRewards.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/ValidationFailureUi.kt:1). Rename to `SelectPoolValidationFailureUiKt`. [rule N6]
D21 · Naming Consistency · `ChangeStakingValidationFailureUIKt` spells `UI` where 153 names in the project spell it `Ui` · ×1
  • `ChangeStakingValidationFailureUIKt` spells `UI` where 153 names in the project spell it `Ui` feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/ChangeStakingValidationFailureUI.kt:1 — 153 of 157 names in project feature-staking-impl spell the token `Ui` (153 of 157; unit: names in project feature-staking-impl containing `Ui`). Peers: StakingFeatureDependencies.walletUiUseCase (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:131); io.novafoundation.nova.feature_staking_impl.domain.bagList.rebag.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bagList/rebag/validations/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.bondMore.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:1); ValidationFailureUiKt.nominationPoolsBondMoreValidationFailure(updateAmountInUi) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:18); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.claimRewards.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/ValidationFailureUi.kt:1). Rename to `ChangeStakingValidationFailureUiKt`. [rule N6]
D21 · Naming Consistency · `mapAddEvmTokensValidationFailureToUI` spells `UI` where 153 names in the project spell it `Ui` · ×1
  • `mapAddEvmTokensValidationFailureToUI` spells `UI` where 153 names in the project spell it `Ui` feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/presentation/validators/change/ChangeStakingValidationFailureUI.kt:8 — 153 of 157 names in project feature-staking-impl spell the token `Ui` (153 of 157; unit: names in project feature-staking-impl containing `Ui`). Peers: StakingFeatureDependencies.walletUiUseCase (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/StakingFeatureDependencies.kt:131); io.novafoundation.nova.feature_staking_impl.domain.bagList.rebag.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/bagList/rebag/validations/ValidationFailureUi.kt:1); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.bondMore.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:1); ValidationFailureUiKt.nominationPoolsBondMoreValidationFailure(updateAmountInUi) (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/bondMore/validations/ValidationFailureUi.kt:18); io.novafoundation.nova.feature_staking_impl.domain.nominationPools.claimRewards.validations.ValidationFailureUiKt (feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/domain/nominationPools/claimRewards/validations/ValidationFailureUi.kt:1). Rename to `mapAddEvmTokensValidationFailureToUi`. [rule N6]
D21 · Naming Consistency · `countedTowardsEd` spells `Ed` where 18 names in the project spell it `ED` · ×1
  • `countedTowardsEd` spells `Ed` where 18 names in the project spell it `ED` feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/SwapMaximum.kt:6 — 18 of 20 names in project feature-swap-impl spell the token `ED` (18 of 20; unit: names in project feature-swap-impl containing `ED`). Peers: io.novafoundation.nova.feature_swap_impl.domain.validation.SwapValidationFailure.NotEnoughFunds.ToPayFeeAndStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:47); io.novafoundation.nova.feature_swap_impl.domain.validation.SwapValidationFailure.AmountOutIsTooLowToStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:55); io.novafoundation.nova.feature_swap_impl.domain.validation.SwapValidationFailure.IntermediateAmountOutIsTooLowToStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:61); BalanceNotConsiderConsumers.assetInED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:82); SwapValidationsKt.sufficientAmountOutToStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidations.kt:125). Rename to `countedTowardsED`. [rule N6]
D21 · Naming Consistency · `checkSegmentDestinationMeetsEd` spells `Ed` where 18 names in the project spell it `ED` · ×1
  • `checkSegmentDestinationMeetsEd` spells `Ed` where 18 names in the project spell it `ED` feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/validations/SwapIntermediateReceivesMeetEDValidation.kt:26 — 18 of 20 names in project feature-swap-impl spell the token `ED` (18 of 20; unit: names in project feature-swap-impl containing `ED`). Peers: io.novafoundation.nova.feature_swap_impl.domain.validation.SwapValidationFailure.NotEnoughFunds.ToPayFeeAndStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:47); io.novafoundation.nova.feature_swap_impl.domain.validation.SwapValidationFailure.AmountOutIsTooLowToStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:55); io.novafoundation.nova.feature_swap_impl.domain.validation.SwapValidationFailure.IntermediateAmountOutIsTooLowToStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:61); BalanceNotConsiderConsumers.assetInED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidationFailure.kt:82); SwapValidationsKt.sufficientAmountOutToStayAboveED (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/domain/validation/SwapValidations.kt:125). Rename to `checkSegmentDestinationMeetsED`. [rule N6]
D21 · Naming Consistency · `mapSwapValidationFailureToUI` spells `UI` where 15 names in the project spell it `Ui` · ×1
  • `mapSwapValidationFailureToUI` spells `UI` where 15 names in the project spell it `Ui` feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/main/SwapValidationFailureUi.kt:33 — 15 of 16 names in project feature-swap-impl spell the token `Ui` (15 of 16; unit: names in project feature-swap-impl containing `Ui`). Peers: SwapFeatureDependencies.walletUiUseCase (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/di/SwapFeatureDependencies.kt:122); SwapRouteView.addChainIcon(chainUi) (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/common/route/SwapRouteView.kt:68); SwapRouteView.addChainName(chainUi) (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/common/route/SwapRouteView.kt:76); SwapConfirmationViewModel.walletUiUseCase (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/SwapConfirmationViewModel.kt:101); SwapConfirmationModule.provideViewModel(walletUiUseCase) (feature-swap-impl/src/main/java/io/novafoundation/nova/feature_swap_impl/presentation/confirmation/di/SwapConfirmationModule.kt:41). Rename to `mapSwapValidationFailureToUi`. [rule N6]
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 926 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: feature-governance-api/src/main/java/io/novafoundation/nova/feature_governance_api/domain/locks/RealClaimScheduleCalculator.kt, feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/domain/sign/polkadot/PolkadotExternalSignInteractor.kt, feature-external-sign-impl/src/main/java/io/novafoundation/nova/feature_external_sign_impl/domain/sign/evm/EvmSignInteractor.kt, feature-wallet-connect-impl/src/main/java/io/novafoundation/nova/feature_wallet_connect_impl/domain/session/RealWalletConnectSessionInteractor.kt, feature-governance-impl/src/main/java/io/novafoundation/nova/feature_governance_impl/domain/referendum/unlock/GovernanceUnlockInteractor.kt, feature-assets/src/main/java/io/novafoundation/nova/feature_assets/presentation/transaction/history/mixin/OperationMappers.kt, feature-wallet-impl/src/main/java/io/novafoundation/nova/feature_wallet_impl/domain/RealCrossChainTransfersUseCase.kt, feature-staking-impl/src/main/java/io/novafoundation/nova/feature_staking_impl/di/staking/nominationPool/NominationPoolModule.kt (and 918 more) (933 orphaned of 1981 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1981 of the 6239 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:4 — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 11 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation bindings/hydra-dx-math/rust/Cargo.toml:9 — `bindings/hydra-dx-math/rust/Cargo.toml` 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`.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex infrastructure/src/main/java/io/novafoundation/nova/infrastructure/attestation/AttestationHttp.kt:15 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
Minor — 1 finding(s)
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: :common — :common: abstractness 0.21, instability 0.02, distance 0.78 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-60a7cd17e7e74c4c96a0e463004570ad/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-60a7cd17e7e74c4c96a0e463004570ad/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-60a7cd17e7e74c4c96a0e463004570ad/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=1361" --report-format json --report-path /tmp/watchdog-gitleaks-60a7cd17e7e74c4c96a0e463004570ad/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-60a7cd17e7e74c4c96a0e463004570ad/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .73artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .10artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 197 file(s) — `analytics/src/main/java/io/novafoundation/nova/analytics/transport/AnalyticsUploader.kt`, `app/src/main/java/io/novafoundation/nova/app/root/domain/RootInteractor.kt`, `common/src/main/java/io/novafoundation/nova/common/address/format/AddressFormat.kt`, `common/src/main/java/io/novafoundation/nova/common/data/memory/ComputationalScope.kt`, `common/src/main/java/io/novafoundation/nova/common/data/memory/SharedComputation.kt`, … (+192 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1e6a0-b9e0-7916-a6f5-9cb68c6ce606 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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