Public report of Adyen/adyen-android, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 15:07 UTC · Survey ID cd_4c2d3aaf10054ff9b2c3940e5acbbc74
Adyen/adyen-android
Measured 17 November 2026, 15:06 UTC, at code version 50de9a5
First survey, so nothing to compare with yet
CAI scoreAt risk
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: 120,729 lines of product code in 61 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Production Readiness, 66.9
Findings by how serious they are
41 critical603 serious234 minor
10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 15:06 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
52of 52 dimensions measured by tools.
706of 878 findings point to an exact file and line, so you can open each one in the code. The other 172 concern the repository as a whole, such as missing documentation.
52dimensions across 6 lenses, read from 120,729 lines of product code in 61 projects.
Adyen/adyen-android is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 73.3 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 66.9, is the weakest lens and counts most in the score. The best first step for the work it takes is adding automated tests, worth about 3.8 points. Adding tests for untested code comes next, worth about 5.7 points. Raising Production Readiness to 70 would lift the score to about 74.7.
Twenty-nine known security holes in the packages the code depends on can be used by attackers. Two pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and nine sets of files in separate parts keep changing together, which points to hidden dependencies. Updating the vulnerable packages, passing outside input through environment variables and making the hidden dependencies explicit would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once.
The product code is 120,729 lines, about €330,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 66.9 to 70, the lowest score rated Strong, the score would rise from 73.3 to about 74.7.
Code composition: what the lines of code are
Product code 63%Tests 37%
Rebuild cost: about €330,000 · Estimate
Cost to rebuild
€110,000 to €550,000, for 1,809 to 5,738 hours of work, about 2.2 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×1.1 at a score of 73. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 120,729 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 7 Tests reach code only in some runs finding(s) in Code Coverage — start with ProjectExtensions.kt, ContextGetString.kt, JSONOptFunctions.kt.
Raises the score by about 3.8 points · Low effort · Code Coverage
2
Resolve the 23 Low coverage finding(s) in Code Coverage — start with AggregateDependencyListsPlugin.kt, CheckoutAndroidLibraryPlugin.kt, DetektConventionPlugin.kt.
Raises the score by about 5.7 points · Medium effort · Code Coverage
3
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Resolve the 7 Tests reach code only in some runs finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 3.8 points for low effort, because it clears the 7 Code Coverage 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.
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.
1061 modules, with 3040 dependencies between them. 57 loops run through 190 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 1021 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.
components.core.action uses components.core, so a change to components.core can break components.core.action, while a change to components.core.action can't break components.core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
components.core.internal.ui.model uses core.old, so a change to core.old can break components.core.internal.ui.model, while a change to components.core.internal.ui.model can't break core.old.
Position
Below the diagonal: components.core.internal.ui.model uses a module listed above it, which is the healthy direction.
10→19 components.core.internal.ui.model uses components.core.internalpart of a loop✕
Connections
1 pair of types, where a type in components.core.internal.ui.model uses a type in components.core.internal.
components.core.internal.ui.model uses components.core.internal, so a change to components.core.internal can break components.core.internal.ui.model, while a change to components.core.internal.ui.model can't break components.core.internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→21 components.core.internal.ui.model uses components.corepart of a loop✕
Connections
9 pairs of types, where a type in components.core.internal.ui.model uses a type in components.core.
components.core.internal.ui.model uses components.core, so a change to components.core can break components.core.internal.ui.model, while a change to components.core.internal.ui.model can't break components.core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
core.common.internal uses core.components.data.model, so a change to core.components.data.model can break core.common.internal, while a change to core.common.internal can't break core.components.data.model.
Position
Below the diagonal: core.common.internal uses a module listed above it, which is the healthy direction.
11→20 core.common.internal uses core.components.internalpart of a loop✕
Connections
3 pairs of types, where a type in core.common.internal uses a type in core.components.internal.
core.common.internal uses core.components.internal, so a change to core.components.internal can break core.common.internal, while a change to core.common.internal can't break core.components.internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→22 core.common.internal uses core.componentspart of a loop✕
Connections
3 pairs of types, where a type in core.common.internal uses a type in core.components.
core.common.internal uses core.components, so a change to core.components can break core.common.internal, while a change to core.common.internal can't break core.components.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→25 core.common.internal uses core.commonpart of a loop✕
Connections
3 pairs of types, where a type in core.common.internal uses a type in core.common.
core.common.internal uses core.common, so a change to core.common can break core.common.internal, while a change to core.common.internal can't break core.common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
core.components.data uses core.components.data.model, so a change to core.components.data.model can break core.components.data, while a change to core.components.data can't break core.components.data.model.
Position
Below the diagonal: core.components.data uses a module listed above it, which is the healthy direction.
core.components.data.model.paymentmethod uses core.components.data.model, so a change to core.components.data.model can break core.components.data.model.paymentmethod, while a change to core.components.data.model.paymentmethod can't break core.components.data.model.
Position
Below the diagonal: core.components.data.model.paymentmethod uses a module listed above it, which is the healthy direction.
core.components.internal.ui.state.model uses core.components.data.model, so a change to core.components.data.model can break core.components.internal.ui.state.model, while a change to core.components.internal.ui.state.model can't break core.components.data.model.
Position
Below the diagonal: core.components.internal.ui.state.model uses a module listed above it, which is the healthy direction.
core.old.internal.util uses core.old, so a change to core.old can break core.old.internal.util, while a change to core.old.internal.util can't break core.old.
Position
Below the diagonal: core.old.internal.util uses a module listed above it, which is the healthy direction.
components.core.internal.ui uses core.old.exception, so a change to core.old.exception can break components.core.internal.ui, while a change to components.core.internal.ui can't break core.old.exception.
Position
Below the diagonal: components.core.internal.ui uses a module listed above it, which is the healthy direction.
components.core.internal.ui uses components.core.action, so a change to components.core.action can break components.core.internal.ui, while a change to components.core.internal.ui can't break components.core.action.
Position
Below the diagonal: components.core.internal.ui uses a module listed above it, which is the healthy direction.
components.core.internal.ui uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break components.core.internal.ui, while a change to components.core.internal.ui can't break components.core.internal.ui.model.
Position
Below the diagonal: components.core.internal.ui uses a module listed above it, which is the healthy direction.
16→19 components.core.internal.ui uses components.core.internalpart of a loop✕
Connections
3 pairs of types, where a type in components.core.internal.ui uses a type in components.core.internal.
components.core.internal.ui uses components.core.internal, so a change to components.core.internal can break components.core.internal.ui, while a change to components.core.internal.ui can't break components.core.internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→21 components.core.internal.ui uses components.corepart of a loop✕
Connections
1 pair of types, where a type in components.core.internal.ui uses a type in components.core.
components.core.internal.ui uses components.core, so a change to components.core can break components.core.internal.ui, while a change to components.core.internal.ui can't break components.core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
core.analytics.internal uses core.common.internal, so a change to core.common.internal can break core.analytics.internal, while a change to core.analytics.internal can't break core.common.internal.
Position
Below the diagonal: core.analytics.internal uses a module listed above it, which is the healthy direction.
17→20 core.analytics.internal uses core.components.internalpart of a loop✕
Connections
1 pair of types, where a type in core.analytics.internal uses a type in core.components.internal.
core.analytics.internal uses core.components.internal, so a change to core.components.internal can break core.analytics.internal, while a change to core.analytics.internal can't break core.components.internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ui.core.old.internal.ui.model uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break ui.core.old.internal.ui.model, while a change to ui.core.old.internal.ui.model can't break components.core.internal.ui.model.
Position
Below the diagonal: ui.core.old.internal.ui.model uses a module listed above it, which is the healthy direction.
18→27 ui.core.old.internal.ui.model uses ui.core.old.internal.uipart of a loop✕
Connections
1 pair of types, where a type in ui.core.old.internal.ui.model uses a type in ui.core.old.internal.ui.
ui.core.old.internal.ui.model uses ui.core.old.internal.ui, so a change to ui.core.old.internal.ui can break ui.core.old.internal.ui.model, while a change to ui.core.old.internal.ui.model can't break ui.core.old.internal.ui.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
components.core.internal uses core.old, so a change to core.old can break components.core.internal, while a change to components.core.internal can't break core.old.
Position
Below the diagonal: components.core.internal uses a module listed above it, which is the healthy direction.
components.core.internal uses core.old.exception, so a change to core.old.exception can break components.core.internal, while a change to components.core.internal can't break core.old.exception.
Position
Below the diagonal: components.core.internal uses a module listed above it, which is the healthy direction.
components.core.internal uses components.core.action, so a change to components.core.action can break components.core.internal, while a change to components.core.internal can't break components.core.action.
Position
Below the diagonal: components.core.internal uses a module listed above it, which is the healthy direction.
components.core.internal uses components.core.internal.ui, so a change to components.core.internal.ui can break components.core.internal, while a change to components.core.internal can't break components.core.internal.ui.
Position
Below the diagonal: components.core.internal uses a module listed above it, which is the healthy direction.
19→21 components.core.internal uses components.corepart of a loop✕
Connections
19 pairs of types, where a type in components.core.internal uses a type in components.core.
components.core.internal uses components.core, so a change to components.core can break components.core.internal, while a change to components.core.internal can't break components.core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
core.components.internal uses core.action.data, so a change to core.action.data can break core.components.internal, while a change to core.components.internal can't break core.action.data.
Position
Below the diagonal: core.components.internal uses a module listed above it, which is the healthy direction.
core.components.internal uses core.common.internal, so a change to core.common.internal can break core.components.internal, while a change to core.components.internal can't break core.common.internal.
Position
Below the diagonal: core.components.internal uses a module listed above it, which is the healthy direction.
core.components.internal uses core.components.data, so a change to core.components.data can break core.components.internal, while a change to core.components.internal can't break core.components.data.
Position
Below the diagonal: core.components.internal uses a module listed above it, which is the healthy direction.
core.components.internal uses core.components.data.model.paymentmethod, so a change to core.components.data.model.paymentmethod can break core.components.internal, while a change to core.components.internal can't break core.components.data.model.paymentmethod.
Position
Below the diagonal: core.components.internal uses a module listed above it, which is the healthy direction.
core.components.internal uses core.analytics.internal, so a change to core.analytics.internal can break core.components.internal, while a change to core.components.internal can't break core.analytics.internal.
Position
Below the diagonal: core.components.internal uses a module listed above it, which is the healthy direction.
20→22 core.components.internal uses core.componentspart of a loop✕
Connections
27 pairs of types, where a type in core.components.internal uses a type in core.components. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
core.components.internal uses core.components, so a change to core.components can break core.components.internal, while a change to core.components.internal can't break core.components.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→25 core.components.internal uses core.commonpart of a loop✕
Connections
6 pairs of types, where a type in core.components.internal uses a type in core.common.
core.components.internal uses core.common, so a change to core.common can break core.components.internal, while a change to core.components.internal can't break core.common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
components.core uses core.old.exception, so a change to core.old.exception can break components.core, while a change to components.core can't break core.old.exception.
Position
Below the diagonal: components.core uses a module listed above it, which is the healthy direction.
components.core uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break components.core, while a change to components.core can't break components.core.internal.ui.model.
Position
Below the diagonal: components.core uses a module listed above it, which is the healthy direction.
components.core uses components.core.internal, so a change to components.core.internal can break components.core, while a change to components.core can't break components.core.internal.
Position
Below the diagonal: components.core uses a module listed above it, which is the healthy direction.
core.components uses core.action.data, so a change to core.action.data can break core.components, while a change to core.components can't break core.action.data.
Position
Below the diagonal: core.components uses a module listed above it, which is the healthy direction.
core.components uses core.components.data, so a change to core.components.data can break core.components, while a change to core.components can't break core.components.data.
Position
Below the diagonal: core.components uses a module listed above it, which is the healthy direction.
core.components uses core.components.data.model.paymentmethod, so a change to core.components.data.model.paymentmethod can break core.components, while a change to core.components can't break core.components.data.model.paymentmethod.
Position
Below the diagonal: core.components uses a module listed above it, which is the healthy direction.
core.components uses core.components.internal, so a change to core.components.internal can break core.components, while a change to core.components can't break core.components.internal.
Position
Below the diagonal: core.components uses a module listed above it, which is the healthy direction.
22→25 core.components uses core.commonpart of a loop✕
Connections
5 pairs of types, where a type in core.components uses a type in core.common.
components.core.internal.analytics uses core.old, so a change to core.old can break components.core.internal.analytics, while a change to components.core.internal.analytics can't break core.old.
Position
Below the diagonal: components.core.internal.analytics uses a module listed above it, which is the healthy direction.
components.core.internal.analytics uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break components.core.internal.analytics, while a change to components.core.internal.analytics can't break components.core.internal.ui.model.
Position
Below the diagonal: components.core.internal.analytics uses a module listed above it, which is the healthy direction.
components.core.internal.analytics uses components.core, so a change to components.core can break components.core.internal.analytics, while a change to components.core.internal.analytics can't break components.core.
Position
Below the diagonal: components.core.internal.analytics uses a module listed above it, which is the healthy direction.
components.core.internal.provider uses components.core.action, so a change to components.core.action can break components.core.internal.provider, while a change to components.core.internal.provider can't break components.core.action.
Position
Below the diagonal: components.core.internal.provider uses a module listed above it, which is the healthy direction.
components.core.internal.provider uses components.core, so a change to components.core can break components.core.internal.provider, while a change to components.core.internal.provider can't break components.core.
Position
Below the diagonal: components.core.internal.provider uses a module listed above it, which is the healthy direction.
core.common uses core.components.data.model.paymentmethod, so a change to core.components.data.model.paymentmethod can break core.common, while a change to core.common can't break core.components.data.model.paymentmethod.
Position
Below the diagonal: core.common uses a module listed above it, which is the healthy direction.
sessions.core uses components.core.action, so a change to components.core.action can break sessions.core, while a change to sessions.core can't break components.core.action.
Position
Below the diagonal: sessions.core uses a module listed above it, which is the healthy direction.
sessions.core uses components.core.internal, so a change to components.core.internal can break sessions.core, while a change to sessions.core can't break components.core.internal.
Position
Below the diagonal: sessions.core uses a module listed above it, which is the healthy direction.
sessions.core uses components.core, so a change to components.core can break sessions.core, while a change to sessions.core can't break components.core.
Position
Below the diagonal: sessions.core uses a module listed above it, which is the healthy direction.
ui.core.old.internal.ui uses core.old, so a change to core.old can break ui.core.old.internal.ui, while a change to ui.core.old.internal.ui can't break core.old.
Position
Below the diagonal: ui.core.old.internal.ui uses a module listed above it, which is the healthy direction.
ui.core.old.internal.ui uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break ui.core.old.internal.ui, while a change to ui.core.old.internal.ui can't break components.core.internal.ui.model.
Position
Below the diagonal: ui.core.old.internal.ui uses a module listed above it, which is the healthy direction.
ui.core.old.internal.ui uses components.core.internal.ui, so a change to components.core.internal.ui can break ui.core.old.internal.ui, while a change to ui.core.old.internal.ui can't break components.core.internal.ui.
Position
Below the diagonal: ui.core.old.internal.ui uses a module listed above it, which is the healthy direction.
ui.core.old.internal.ui uses ui.core.old.internal.ui.model, so a change to ui.core.old.internal.ui.model can break ui.core.old.internal.ui, while a change to ui.core.old.internal.ui can't break ui.core.old.internal.ui.model.
Position
Below the diagonal: ui.core.old.internal.ui uses a module listed above it, which is the healthy direction.
ui.core.old.internal.ui uses components.core.internal, so a change to components.core.internal can break ui.core.old.internal.ui, while a change to ui.core.old.internal.ui can't break components.core.internal.
Position
Below the diagonal: ui.core.old.internal.ui uses a module listed above it, which is the healthy direction.
ui.core.old.internal.ui uses components.core, so a change to components.core can break ui.core.old.internal.ui, while a change to ui.core.old.internal.ui can't break components.core.
Position
Below the diagonal: ui.core.old.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses core.old.exception, so a change to core.old.exception can break action.core.internal.ui, while a change to action.core.internal.ui can't break core.old.exception.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core.action, so a change to components.core.action can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.action.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.internal.ui.model.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses core.old.internal.util, so a change to core.old.internal.util can break action.core.internal.ui, while a change to action.core.internal.ui can't break core.old.internal.util.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core.internal.ui, so a change to components.core.internal.ui can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.internal.ui.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core.internal, so a change to components.core.internal can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.internal.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core, so a change to components.core can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core.internal.analytics, so a change to components.core.internal.analytics can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.internal.analytics.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses components.core.internal.provider, so a change to components.core.internal.provider can break action.core.internal.ui, while a change to action.core.internal.ui can't break components.core.internal.provider.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
action.core.internal.ui uses ui.core.old.internal.ui, so a change to ui.core.old.internal.ui can break action.core.internal.ui, while a change to action.core.internal.ui can't break ui.core.old.internal.ui.
Position
Below the diagonal: action.core.internal.ui uses a module listed above it, which is the healthy direction.
card.internal.ui.state uses core.components.data.model, so a change to core.components.data.model can break card.internal.ui.state, while a change to card.internal.ui.state can't break core.components.data.model.
Position
Below the diagonal: card.internal.ui.state uses a module listed above it, which is the healthy direction.
card.internal.ui.state uses core.components.data, so a change to core.components.data can break card.internal.ui.state, while a change to card.internal.ui.state can't break core.components.data.
Position
Below the diagonal: card.internal.ui.state uses a module listed above it, which is the healthy direction.
card.internal.ui.state uses core.components.data.model.paymentmethod, so a change to core.components.data.model.paymentmethod can break card.internal.ui.state, while a change to card.internal.ui.state can't break core.components.data.model.paymentmethod.
Position
Below the diagonal: card.internal.ui.state uses a module listed above it, which is the healthy direction.
card.internal.ui.state uses core.components.internal.ui.state.model, so a change to core.components.internal.ui.state.model can break card.internal.ui.state, while a change to card.internal.ui.state can't break core.components.internal.ui.state.model.
Position
Below the diagonal: card.internal.ui.state uses a module listed above it, which is the healthy direction.
card.internal.ui.state uses core.common, so a change to core.common can break card.internal.ui.state, while a change to card.internal.ui.state can't break core.common.
Position
Below the diagonal: card.internal.ui.state uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses components.core.paymentmethod, so a change to components.core.paymentmethod can break card.old.internal.ui, while a change to card.old.internal.ui can't break components.core.paymentmethod.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses core.old, so a change to core.old can break card.old.internal.ui, while a change to card.old.internal.ui can't break core.old.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses core.old.exception, so a change to core.old.exception can break card.old.internal.ui, while a change to card.old.internal.ui can't break core.old.exception.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break card.old.internal.ui, while a change to card.old.internal.ui can't break components.core.internal.ui.model.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses components.core.internal.ui, so a change to components.core.internal.ui can break card.old.internal.ui, while a change to card.old.internal.ui can't break components.core.internal.ui.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses ui.core.old.internal.ui.model, so a change to ui.core.old.internal.ui.model can break card.old.internal.ui, while a change to card.old.internal.ui can't break ui.core.old.internal.ui.model.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses components.core.internal, so a change to components.core.internal can break card.old.internal.ui, while a change to card.old.internal.ui can't break components.core.internal.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses components.core, so a change to components.core can break card.old.internal.ui, while a change to card.old.internal.ui can't break components.core.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses components.core.internal.analytics, so a change to components.core.internal.analytics can break card.old.internal.ui, while a change to card.old.internal.ui can't break components.core.internal.analytics.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
card.old.internal.ui uses ui.core.old.internal.ui, so a change to ui.core.old.internal.ui can break card.old.internal.ui, while a change to card.old.internal.ui can't break ui.core.old.internal.ui.
Position
Below the diagonal: card.old.internal.ui uses a module listed above it, which is the healthy direction.
30→36 card.old.internal.ui uses card.oldpart of a loop✕
Connections
8 pairs of types, where a type in card.old.internal.ui uses a type in card.old.
card.old.internal.ui uses card.old, so a change to card.old can break card.old.internal.ui, while a change to card.old.internal.ui can't break card.old.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dropin.internal.ui uses core.action.data, so a change to core.action.data can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.action.data.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.common.internal, so a change to core.common.internal can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.common.internal.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.components.data, so a change to core.components.data can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.components.data.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.components.data.model.paymentmethod, so a change to core.components.data.model.paymentmethod can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.components.data.model.paymentmethod.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.analytics.internal, so a change to core.analytics.internal can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.analytics.internal.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.components.internal, so a change to core.components.internal can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.components.internal.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.components, so a change to core.components can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.components.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
dropin.internal.ui uses core.common, so a change to core.common can break dropin.internal.ui, while a change to dropin.internal.ui can't break core.common.
Position
Below the diagonal: dropin.internal.ui uses a module listed above it, which is the healthy direction.
sessions.core.internal.data.model uses components.core.paymentmethod, so a change to components.core.paymentmethod can break sessions.core.internal.data.model, while a change to sessions.core.internal.data.model can't break components.core.paymentmethod.
Position
Below the diagonal: sessions.core.internal.data.model uses a module listed above it, which is the healthy direction.
sessions.core.internal.data.model uses core.old, so a change to core.old can break sessions.core.internal.data.model, while a change to sessions.core.internal.data.model can't break core.old.
Position
Below the diagonal: sessions.core.internal.data.model uses a module listed above it, which is the healthy direction.
sessions.core.internal.data.model uses components.core.action, so a change to components.core.action can break sessions.core.internal.data.model, while a change to sessions.core.internal.data.model can't break components.core.action.
Position
Below the diagonal: sessions.core.internal.data.model uses a module listed above it, which is the healthy direction.
sessions.core.internal.data.model uses components.core, so a change to components.core can break sessions.core.internal.data.model, while a change to sessions.core.internal.data.model can't break components.core.
Position
Below the diagonal: sessions.core.internal.data.model uses a module listed above it, which is the healthy direction.
sessions.core.internal.data.model uses sessions.core, so a change to sessions.core can break sessions.core.internal.data.model, while a change to sessions.core.internal.data.model can't break sessions.core.
Position
Below the diagonal: sessions.core.internal.data.model uses a module listed above it, which is the healthy direction.
sessions.core.internal.provider uses components.core, so a change to components.core can break sessions.core.internal.provider, while a change to sessions.core.internal.provider can't break components.core.
Position
Below the diagonal: sessions.core.internal.provider uses a module listed above it, which is the healthy direction.
sessions.core.internal.provider uses sessions.core, so a change to sessions.core can break sessions.core.internal.provider, while a change to sessions.core.internal.provider can't break sessions.core.
Position
Below the diagonal: sessions.core.internal.provider uses a module listed above it, which is the healthy direction.
action.core.internal uses core.old, so a change to core.old can break action.core.internal, while a change to action.core.internal can't break core.old.
Position
Below the diagonal: action.core.internal uses a module listed above it, which is the healthy direction.
action.core.internal uses components.core.action, so a change to components.core.action can break action.core.internal, while a change to action.core.internal can't break components.core.action.
Position
Below the diagonal: action.core.internal uses a module listed above it, which is the healthy direction.
action.core.internal uses components.core.internal.ui, so a change to components.core.internal.ui can break action.core.internal, while a change to action.core.internal can't break components.core.internal.ui.
Position
Below the diagonal: action.core.internal uses a module listed above it, which is the healthy direction.
action.core.internal uses components.core.internal, so a change to components.core.internal can break action.core.internal, while a change to action.core.internal can't break components.core.internal.
Position
Below the diagonal: action.core.internal uses a module listed above it, which is the healthy direction.
action.core.internal uses action.core.internal.ui, so a change to action.core.internal.ui can break action.core.internal, while a change to action.core.internal can't break action.core.internal.ui.
Position
Below the diagonal: action.core.internal uses a module listed above it, which is the healthy direction.
action.core uses components.core.action, so a change to components.core.action can break action.core, while a change to action.core can't break components.core.action.
Position
Below the diagonal: action.core uses a module listed above it, which is the healthy direction.
action.core uses components.core.internal.ui, so a change to components.core.internal.ui can break action.core, while a change to action.core can't break components.core.internal.ui.
Position
Below the diagonal: action.core uses a module listed above it, which is the healthy direction.
action.core uses components.core.internal, so a change to components.core.internal can break action.core, while a change to action.core can't break components.core.internal.
Position
Below the diagonal: action.core uses a module listed above it, which is the healthy direction.
action.core uses ui.core.old.internal.ui, so a change to ui.core.old.internal.ui can break action.core, while a change to action.core can't break ui.core.old.internal.ui.
Position
Below the diagonal: action.core uses a module listed above it, which is the healthy direction.
action.core uses action.core.internal.ui, so a change to action.core.internal.ui can break action.core, while a change to action.core can't break action.core.internal.ui.
Position
Below the diagonal: action.core uses a module listed above it, which is the healthy direction.
action.core uses action.core.internal, so a change to action.core.internal can break action.core, while a change to action.core can't break action.core.internal.
Position
Below the diagonal: action.core uses a module listed above it, which is the healthy direction.
card.old uses components.core.paymentmethod, so a change to components.core.paymentmethod can break card.old, while a change to card.old can't break components.core.paymentmethod.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
card.old uses components.core.internal.ui, so a change to components.core.internal.ui can break card.old, while a change to card.old can't break components.core.internal.ui.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
card.old uses components.core.internal, so a change to components.core.internal can break card.old, while a change to card.old can't break components.core.internal.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
card.old uses ui.core.old.internal.ui, so a change to ui.core.old.internal.ui can break card.old, while a change to card.old can't break ui.core.old.internal.ui.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
card.old uses action.core.internal.ui, so a change to action.core.internal.ui can break card.old, while a change to card.old can't break action.core.internal.ui.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
card.old uses card.old.internal.ui, so a change to card.old.internal.ui can break card.old, while a change to card.old can't break card.old.internal.ui.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
card.old uses action.core.internal, so a change to action.core.internal can break card.old, while a change to card.old can't break action.core.internal.
Position
Below the diagonal: card.old uses a module listed above it, which is the healthy direction.
googlepay.old uses components.core.paymentmethod, so a change to components.core.paymentmethod can break googlepay.old, while a change to googlepay.old can't break components.core.paymentmethod.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses core.old.exception, so a change to core.old.exception can break googlepay.old, while a change to googlepay.old can't break core.old.exception.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses components.core.internal.ui, so a change to components.core.internal.ui can break googlepay.old, while a change to googlepay.old can't break components.core.internal.ui.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses components.core.internal, so a change to components.core.internal can break googlepay.old, while a change to googlepay.old can't break components.core.internal.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses components.core, so a change to components.core can break googlepay.old, while a change to googlepay.old can't break components.core.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses ui.core.old.internal.ui, so a change to ui.core.old.internal.ui can break googlepay.old, while a change to googlepay.old can't break ui.core.old.internal.ui.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses action.core.internal.ui, so a change to action.core.internal.ui can break googlepay.old, while a change to googlepay.old can't break action.core.internal.ui.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
googlepay.old uses action.core.internal, so a change to action.core.internal can break googlepay.old, while a change to googlepay.old can't break action.core.internal.
Position
Below the diagonal: googlepay.old uses a module listed above it, which is the healthy direction.
dropin.old.DropInConfiguration uses core.old, so a change to core.old can break dropin.old.DropInConfiguration, while a change to dropin.old.DropInConfiguration can't break core.old.
Position
Below the diagonal: dropin.old.DropInConfiguration uses a module listed above it, which is the healthy direction.
dropin.old.DropInConfiguration uses components.core.internal, so a change to components.core.internal can break dropin.old.DropInConfiguration, while a change to dropin.old.DropInConfiguration can't break components.core.internal.
Position
Below the diagonal: dropin.old.DropInConfiguration uses a module listed above it, which is the healthy direction.
dropin.old.DropInConfiguration uses action.core.internal, so a change to action.core.internal can break dropin.old.DropInConfiguration, while a change to dropin.old.DropInConfiguration can't break action.core.internal.
Position
Below the diagonal: dropin.old.DropInConfiguration uses a module listed above it, which is the healthy direction.
dropin.old.DropInConfiguration uses card.old, so a change to card.old can break dropin.old.DropInConfiguration, while a change to dropin.old.DropInConfiguration can't break card.old.
Position
Below the diagonal: dropin.old.DropInConfiguration uses a module listed above it, which is the healthy direction.
dropin.old.DropInConfiguration uses googlepay.old, so a change to googlepay.old can break dropin.old.DropInConfiguration, while a change to dropin.old.DropInConfiguration can't break googlepay.old.
Position
Below the diagonal: dropin.old.DropInConfiguration uses a module listed above it, which is the healthy direction.
38→39 dropin.old.DropInConfiguration uses dropin.oldpart of a loop✕
Connections
1 pair of types, where a type in dropin.old.DropInConfiguration uses a type in dropin.old.
dropin.old.DropInConfiguration uses dropin.old, so a change to dropin.old can break dropin.old.DropInConfiguration, while a change to dropin.old.DropInConfiguration can't break dropin.old.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dropin.old uses components.core.internal, so a change to components.core.internal can break dropin.old, while a change to dropin.old can't break components.core.internal.
Position
Below the diagonal: dropin.old uses a module listed above it, which is the healthy direction.
dropin.old uses components.core.internal.analytics, so a change to components.core.internal.analytics can break dropin.old, while a change to dropin.old can't break components.core.internal.analytics.
Position
Below the diagonal: dropin.old uses a module listed above it, which is the healthy direction.
dropin.old uses dropin.old.DropInConfiguration, so a change to dropin.old.DropInConfiguration can break dropin.old, while a change to dropin.old can't break dropin.old.DropInConfiguration.
Position
Below the diagonal: dropin.old uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses components.core.paymentmethod, so a change to components.core.paymentmethod can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break components.core.paymentmethod.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses core.old, so a change to core.old can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break core.old.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses components.core.action, so a change to components.core.action can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break components.core.action.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses components.core.internal.ui.model, so a change to components.core.internal.ui.model can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break components.core.internal.ui.model.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses core.old.internal.util, so a change to core.old.internal.util can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break core.old.internal.util.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses ui.core.old.internal.ui.model, so a change to ui.core.old.internal.ui.model can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break ui.core.old.internal.ui.model.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses components.core.internal, so a change to components.core.internal can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break components.core.internal.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
61 pairs of types, where a type in dropin.old.internal.ui uses a type in components.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
dropin.old.internal.ui uses components.core, so a change to components.core can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break components.core.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses components.core.internal.analytics, so a change to components.core.internal.analytics can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break components.core.internal.analytics.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses sessions.core, so a change to sessions.core can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break sessions.core.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses sessions.core.internal.data.model, so a change to sessions.core.internal.data.model can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break sessions.core.internal.data.model.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses action.core, so a change to action.core can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break action.core.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses card.old, so a change to card.old can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break card.old.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses googlepay.old, so a change to googlepay.old can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break googlepay.old.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
dropin.old.internal.ui uses dropin.old, so a change to dropin.old can break dropin.old.internal.ui, while a change to dropin.old.internal.ui can't break dropin.old.
Position
Below the diagonal: dropin.old.internal.ui uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
50
High / Critical
A05:2025 — Injection
15
High / Critical
Roadmap
Top priorities: Resolve the 23 Low coverage finding(s) in Code Coverage — start with AggregateDependencyListsPlugin.kt, CheckoutAndroidLibraryPlugin.kt, DetektConventionPlugin.kt; Resolve the 7 Tests reach code only in some runs finding(s) in Code Coverage — start with ProjectExtensions.kt, ContextGetString.kt, JSONOptFunctions.kt; Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 7 Tests reach code only in some runs finding(s) in Code Coverage — start with ProjectExtensions.kt, ContextGetString.kt, JSONOptFunctions.kt.
Resolve the 23 Low coverage finding(s) in Code Coverage — start with AggregateDependencyListsPlugin.kt, CheckoutAndroidLibraryPlugin.kt, DetektConventionPlugin.kt.
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).
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 — 41
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 — 603
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 — 234
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 52 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 706 of 878 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
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 package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (wechatpay/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.
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. `3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Configuration.kt`, `ach/src/main/java/com/adyen/checkout/ach/ACHDirectDebitConfiguration.kt`, `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt`, `action-core/src/main/java/com/adyen/checkout/action/core/GenericActionComponent.kt`, `await/src/main/java/com/adyen/checkout/await/old/AwaitConfiguration.kt`, … (+81 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 (wechatpay/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.
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 no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CardView.highlightValidationErrors at 25. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DefaultLocalizationSource.getString at 119 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/src/main/java/com/adyen/checkout/core/common/localization/internal/DefaultLocalizationSource.kt (DefaultLocalizationSource.getString at 119), core/src/main/java/com/adyen/checkout/core/components/data/model/paymentmethod/PaymentMethod.kt (PaymentMethod.getChildSerializer at 47), components-core/src/main/java/com/adyen/checkout/components/core/paymentmethod/PaymentMethodDetails.kt (PaymentMethodDetails.getChildSerializer at 38), drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/provider/ComponentProvider.kt (ComponentProviderKt.getComponentFor at 32), card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStateReducer.kt (CardComponentStateReducer.reduce at 20). 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.
Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with CardView.highlightValidationErrors (cyclomatic 25), PayToView.highlightValidationErrors (cyclomatic 24). — 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 2 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with CardView.highlightValidationErrors (cognitive 31), PayToView.highlightValidationErrors (cognitive 30), AddressFormInput.highlightValidationErrors (cognitive 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.8 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.
Do you agree with this assessment?
D3 · God Classes9.6 / 10Stronggated by 20 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.
Resolve the 8 TooManyMethods finding(s) in God Classes — start with DropInActivity.kt, DefaultCardDelegate.kt, CardView.kt. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 ClassTooLong finding(s) in God Classes — start with DefaultCardDelegate.kt, CardView.kt, DropInActivity.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 FileTooLong finding(s) in God Classes — start with DefaultCardDelegate.kt, CardView.kt, DropInActivity.kt. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
231 duplicated block group(s) detected. 11.3 % of the production lines (13,687 of 120,729) are in a reported copy. A further 170 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 60 of the 401 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (9 corresponding lines) · ×13components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:24
+ 143 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 19 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with DefaultACHDirectDebitDelegate.kt (2), HttpClientExt.kt (2), OkHttpClient.kt (2). — One of this dimension's main actionable groups (19 warning-level).
Resolve the 16 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with IdealComponentProvider.kt (2), TwintComponentProvider.kt (2), ACHDirectDebitComponentProvider.kt. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 15 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with BcmcComponentProvider.kt, ImageLoader.kt, FullQRCodeView.kt. — One of this dimension's main actionable groups (15 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.1 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
61 production modules (Gradle), 0 dependency cycle(s), 5 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; 8 module(s) off the main sequence, with abstractness counted on 58 of the 61 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: .:ui · ×8
Unstable project .:bcmc · ×5
What to do
Resolve the 8 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Unstable project . finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with BaseDropInService.kt, ActionComponentDialogFragment.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage2.9 / 10Weak✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 0.0% — 23 file(s) below 50%. Measured from the Java/Kotlin suite (repository root, Gradle: the JaCoCo agent on the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 171 line(s) in 7 file(s) were executed in some runs and not in others, so they are not counted.
Tests reach code only in some runs: build-logic/convention/src/main/kotlin/com/adyen/checkout/ProjectExtensions.kt · ×7build-logic/convention/src/main/kotlin/com/adyen/checkout/ProjectExtensions.kt:16
What to do
Resolve the 23 Low coverage finding(s) in Code Coverage — start with AggregateDependencyListsPlugin.kt, CheckoutAndroidLibraryPlugin.kt, DetektConventionPlugin.kt. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 7 Tests reach code only in some runs finding(s) in Code Coverage — start with ProjectExtensions.kt, ContextGetString.kt, JSONOptFunctions.kt. — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 493 artifact(s) resolved, 296 of them gradable against Maven Central, and 149 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
Outdated (compile): com.google.guava:guava · ×149
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 45 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 63 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 8 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 37 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
47 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt. Counted over 639 of the 1819 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×3
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.
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.
94 deducted task-comment markers across 120729 LoC (0.1/KLoC) → score 9.8. 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 repeated across 10 filesgooglepay/src/main/java/com/adyen/checkout/googlepay/BillingAddressParameters.kt:47
What to do
Resolve the 84 TodoComment finding(s) in Explicit Debt — start with AwaitComponent.kt (4), CheckoutSessionInitializer.kt (3), DropIn.kt (3). — One of this dimension's main actionable groups (84 warning-level).
Resolve the 1 TodoComment repeated across 10 files finding(s) in Explicit Debt — start with BillingAddressParameters.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.
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.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 3 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
5 of 58 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×5core/build.gradle:1
What to do
Resolve the 5 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle (5). — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
41 % of calls cross a namespace and 15 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
15 finding(s): 0 critical, 3 high, 12 medium, 0 low. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
Resolve the 15 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
37 of 639 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt. Counted over 639 of the 1819 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with CardComponentParamsMapper.kt (2), DefaultCardDelegate.kt (2), BcmcComponentParamsMapper.kt. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 15 Change coupling finding(s) in Change Coupling — start with CardInputData.kt (2), CardComponentStateReducer.kt (2), MBWayComponentStateFactory.kt (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with DropInActivity.kt, BaseDropInServiceInterfaces.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 83 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether 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.
`ExternalConfigurationReader` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (cardConfiguration; e.g. `cardConfiguration` in `apply` at line 33). — example-app/src/main/java/com/adyen/checkout/example/data/storage/ExternalConfigurationReader.kt:28
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
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.
`Protocol` declares 18 abstract methods: `showPreselectedDialog`, `showPaymentMethodsDialog`, `showStoredComponentDialog`, `showComponentDialog`, `requestPaymentsCall`, `requestDetailsCall`, `showError`, `terminateDropIn`, `requestBalanceCall`, `requestPartialPayment`, `requestOrderCancellation`, `finishWithAction`, `removeStoredPaymentMethod`, `onRedirect`, `onBinValue`, `onBinLookup`, `onAddressLookupQuery`, `onAddressLookupCompletion`. 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. — drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInBottomSheetDialogFragment.kt:97
`KeyValueStorage` declares 34 abstract methods: `getShopperReference`, `setShopperReference`, `getOldAmount`, `getAmount`, `setAmount`, `setCurrency`, `getCountry`, `setCountry`, `getShopperLocale`, `setShopperLocale`, `getThreeDSMode`, `setThreeDSMode`, `getShopperEmail`, `setShopperEmail`, `getMerchantAccount`, `setMerchantAccount`, `isSplitCardFundingSources`, `setSplitCardFundingSources`, `getCardAddressMode`, `setCardAddressMode`, `isRemoveStoredPaymentMethodEnabled`, `setRemoveStoredPaymentMethodEnabled`, `getInstantPaymentMethodType`, `setInstantPaymentMethodType`, `getInstallmentOptionsMode`, `setInstallmentOptionsMode`, `isInstallmentAmountShown`, `setInstallmentAmountShown`, `getIntegrationFlow`, `setIntegrationFlow`, `getAnalyticsMode`, `setAnalyticsMode`, `getOnBeforeSubmitMode`, `setOnBeforeSubmitMode`. 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. — example-app/src/main/java/com/adyen/checkout/example/data/storage/KeyValueStorage.kt:33
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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.
`dependency-graph/project.dot` draws the system's parts, and the drawing no longer matches the code: it leaves out `3ds2`, `address`, `authentication`, `card-scanning`, `core`, `lint`, `meal-voucher-fr`, `paybybank-us`, `payto`, `twint`, `twint-action`, `ui`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — dependency-graph/project.dot:1
What to do
Update dependency-graph/project.dot so it draws the parts the code has today: add 3ds2, address, authentication, card-scanning, core, lint, meal-voucher-fr, paybybank-us, payto, twint, twint-action, ui.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
`codeql.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · 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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether suspend functions that make a cancellable request accept or pass on the coroutine's cancellation (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 1/2 suspend functions that make a cancellable request (Ktor, OkHttp newCall, URL streams) accept the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a screen navigated away from, a disposed widget, a superseded search. In a suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`load` suspends, but makes its request with `call.execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/ImageLoader.kt:42
What to do
Thread the coroutine's cancellation through suspend functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether 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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — core/src/main/java/com/adyen/checkout/core/internal/image/InMemoryCache.kt:31, checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/InMemoryCache.kt:31
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 22 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~70236 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.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
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) — 86 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 264 value object(s); 26 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 4 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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's JVM source (58 module(s), 1751 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 23 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
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: CardComponentParamsMapper.kt ↔ GenericComponentParamsMapper.kt card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt:1— `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt` (context card) and `components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/GenericComponentParamsMapper.kt` (context components-core) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c9bd4c7e` Update all component params mappers to use CommonComponentParamsMapper; `6a7b66eb` Make CardComponent accept CheckoutConfiguration; `9da0e755` Override amount in component params with the amount coming from sessions — run `git show` on any of them.
Boundary-crossing change coupling: BcmcComponentParamsMapper.kt ↔ CardComponentParamsMapper.kt bcmc/src/main/java/com/adyen/checkout/bcmc/internal/ui/model/BcmcComponentParamsMapper.kt:1— `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/ui/model/BcmcComponentParamsMapper.kt` (context bcmc) and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt` (context card) sit in DIFFERENT parts of the tree yet 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) — 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 `b171b87f` Display pay button in components if created by drop in; `c9bd4c7e` Update all component params mappers to use CommonComponentParamsMapper; `9da0e755` Override amount in component params with the amount coming from sessions — run `git show` on any of them.
Boundary-crossing change coupling: CardComponentParamsMapper.kt ↔ IssuerListComponentParamsMapper.kt card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt:1— `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt` (context card) and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/model/IssuerListComponentParamsMapper.kt` (context issuer-list) sit in DIFFERENT parts of the tree yet change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 `b171b87f` Display pay button in components if created by drop in; `c9bd4c7e` Update all component params mappers to use CommonComponentParamsMapper; `9da0e755` Override amount in component params with the amount coming from sessions — run `git show` on any of them.
Boundary-crossing change coupling: StoredCardDelegate.kt ↔ AddressLookupDelegate.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:1— `card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt` (context card) and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/AddressLookupDelegate.kt` (context ui-core) sit in DIFFERENT parts of the tree yet 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) — 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 `480a19f2` Make AddressInputModel internal (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/StoredCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/AddressLookupDelegate.kt`); `b660eddd` Handle errors on address lookup completion call (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/StoredCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/AddressLookupDelegate.kt`); `ca4069ac` Initialize address lookup with the most recent address value from car… (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/StoredCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/AddressLookupDelegate.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: DefaultCardDelegate.kt ↔ AddressLookupOptionsAdapter.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:1— `card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt` (context card) and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupOptionsAdapter.kt` (context ui-core) sit in DIFFERENT parts of the tree yet 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) — 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 `17abf50f` Move all address lookup events out of AddressLookupView (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/DefaultCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressLookupOptionsAdapter.kt`); `764029c3` Create a model class for address lookup adapter to decouple it from m… (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/DefaultCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressLookupOptionsAdapter.kt`); `75ee5483` Extract address lookup related code and move it to ui-core (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/DefaultCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressLookupOptionsAdapter.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: GenericComponentParamsMapper.kt ↔ GooglePayComponentParamsMapper.kt components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/GenericComponentParamsMapper.kt:1— `components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/GenericComponentParamsMapper.kt` (context components-core) and `googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt` (context googlepay) sit in DIFFERENT parts of the tree yet 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) — 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 `c9bd4c7e` Update all component params mappers to use CommonComponentParamsMapper; `9da0e755` Override amount in component params with the amount coming from sessions; `14bdcbf2` Use default amount if overridden amount is empty in GooglePay (at that commit the files were still `components-core/src/main/java/com/adyen/checkout/components/base/GenericComponentParamsMapper.kt` and `googlepay/src/main/java/com/adyen/checkout/googlepay/GooglePayComponentParamsMapper.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: AddressInputModel.kt ↔ AddressFormInput.kt components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/AddressInputModel.kt:1— `components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/AddressInputModel.kt` (context components-core) and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt` (context ui-core) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `794b6d7f` Display full country name in address lookup result (at that commit the file was still `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressFormInput.kt`); `c499e8eb` FullAddressForm: Fix pr comments (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/AddressInputModel.kt` and `card/src/main/java/com/adyen/checkout/card/ui/AddressFormInput.kt`); `21fea504` FullAddressForm: Add apartment suite field (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/AddressInputModel.kt` and `card/src/main/java/com/adyen/checkout/card/ui/AddressFormInput.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: GooglePayComponentParamsMapper.kt ↔ IssuerListComponentParamsMapper.kt googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:1— `googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt` (context googlepay) and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/model/IssuerListComponentParamsMapper.kt` (context issuer-list) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c9bd4c7e` Update all component params mappers to use CommonComponentParamsMapper; `9da0e755` Override amount in component params with the amount coming from sessions; `14bdcbf2` Use default amount if overridden amount is empty in GooglePay (at that commit the files were still `googlepay/src/main/java/com/adyen/checkout/googlepay/GooglePayComponentParamsMapper.kt` and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/IssuerListComponentParamsMapper.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: DefaultCardDelegate.kt ↔ AddressLookupView.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:1— `card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt` (context card) and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt` (context ui-core) sit in DIFFERENT parts of the tree yet change together 53% of the time (16 of the 30 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 16 shared commits counted here, the most recent 3 are `480a19f2` Make AddressInputModel internal (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/DefaultCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressLookupView.kt`); `b660eddd` Handle errors on address lookup completion call (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/DefaultCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressLookupView.kt`); `136e132a` Display submit address button only when it's AddressLookupState.Form (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/DefaultCardDelegate.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/internal/ui/view/AddressLookupView.kt`) — run `git show` on any of them.
TodoComment voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/DefaultVoucherDelegate.kt:151— // TODO remove action.url when it's fixed from backend side — 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 ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AdyenTextInputEditText.kt:41— // TODO temporary measure to avoid notifying changes for disabled edit texts. — 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 ui/src/main/java/com/adyen/checkout/ui/internal/element/ValuePicker.kt:34— // TODO - ValuePicker: Scroll the selected item into view when the picker opens. A long list, such as the address — 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 twint/src/main/java/com/adyen/checkout/twint/internal/ui/StoredTwintDelegate.kt:103— // TODO: Here we only call this method on initialization. The checkoutAttemptId will only be available if it is — 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 cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:105— // TODO: Here we only call this method on initialization. The checkoutAttemptId will only be available if it is — 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 blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/StoredBlikDelegate.kt:121— // TODO: Here we only call this method on initialization. The checkoutAttemptId will only be available if it is — 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 ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt:122— // TODO: Here we only call this method on initialization. The checkoutAttemptId will only be available if it is — 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 sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/CheckoutSessionInitializer.kt:36— // TODO Once Backend provides the correct amount in the SessionSetupResponse use that in SessionDetails instead of — 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 redirect/src/main/java/com/adyen/checkout/redirect/old/internal/ui/DefaultRedirectDelegate.kt:138— // TODO look into emitting a value to tell observers that a redirect was launched so they can track its — 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 redirect/src/main/java/com/adyen/checkout/redirect/internal/ui/RedirectComponent.kt:117— // TODO look into emitting a value to tell observers that a redirect was launched so they can track its — 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 payto/src/main/java/com/adyen/checkout/payto/internal/ui/StoredPayToDelegate.kt:138— // TODO Here we only call this method on initialization. The checkoutAttemptId will only be available if it is — 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 mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStateValidator.kt:18— // TODO - Should we strip the leading zeros? Depends on validation — 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 mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayPaymentComponentState.kt:19— // TODO - check if we need to make this public — 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 ideal/src/main/java/com/adyen/checkout/ideal/IdealConfiguration.kt:47— // TODO Decouple this configuration from IssuerListConfiguration when we can break the API contract. — 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 googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/ui/model/GooglePayComponentParamsMapper.kt:92— // TODO return true by default in v6 — 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 googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/GooglePayFactory.kt:76— // TODO - Remove casting when paymentMethod object is typed — 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 card/src/main/java/com/adyen/checkout/card/internal/ui/CardFactory.kt:155— // TODO - Remove casting when paymentMethod object is typed — 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 googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:32— // TODO - Pass isCreatedByDropIn — 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 googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:205— // TODO - Use this logic once the isCreatedByDropIn flag is available — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Screen.kt:161— // TODO do not hide button if component is not valid on click — 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 example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:227— // TODO - read the session id and data from the public session data API once it is available, instead of reaching — 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 example-app/src/main/java/com/adyen/checkout/example/service/ExampleV6DropInService.kt:45— // TODO - Move return url creation to the new redirect component — 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 example-app/src/main/java/com/adyen/checkout/example/repositories/PaymentsRepository.kt:57— // TODO - get rid of old api call and improve this one — 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 example-app/src/main/java/com/adyen/checkout/example/data/api/CheckoutApiService.kt:30— // TODO - Remove annotation after removing old functions — 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 drop-in/src/main/java/com/adyen/checkout/dropin/DropIn.kt:24— // TODO - Discuss the current Drop-in approach. Do we need DropIn object and can we make improvement? — 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.
Low coverage: build-logic/convention/src/main/kotlin/AggregateDependencyListsPlugin.kt build-logic/convention/src/main/kotlin/AggregateDependencyListsPlugin.kt:1— 0.0% line coverage (0/24).
Low coverage: build-logic/convention/src/main/kotlin/CheckoutAndroidLibraryPlugin.kt build-logic/convention/src/main/kotlin/CheckoutAndroidLibraryPlugin.kt:1— 0.0% line coverage (0/104).
Low coverage: build-logic/convention/src/main/kotlin/DetektConventionPlugin.kt build-logic/convention/src/main/kotlin/DetektConventionPlugin.kt:1— 0.0% line coverage (0/24).
Low coverage: build-logic/convention/src/main/kotlin/DokkaConventionPlugin.kt build-logic/convention/src/main/kotlin/DokkaConventionPlugin.kt:1— 0.0% line coverage (0/26).
Low coverage: build-logic/convention/src/main/kotlin/GenerateDependencyListPlugin.kt build-logic/convention/src/main/kotlin/GenerateDependencyListPlugin.kt:1— 0.0% line coverage (0/14).
Low coverage: build-logic/convention/src/main/kotlin/JavaConventionPlugin.kt build-logic/convention/src/main/kotlin/JavaConventionPlugin.kt:1— 0.0% line coverage (0/15).
Low coverage: build-logic/convention/src/main/kotlin/KoverConventionPlugin.kt build-logic/convention/src/main/kotlin/KoverConventionPlugin.kt:1— 0.0% line coverage (0/63).
Low coverage: build-logic/convention/src/main/kotlin/KtlintConventionPlugin.kt build-logic/convention/src/main/kotlin/KtlintConventionPlugin.kt:1— 0.0% line coverage (0/48).
Low coverage: build-logic/convention/src/main/kotlin/PublishConventionPlugin.kt build-logic/convention/src/main/kotlin/PublishConventionPlugin.kt:1— 0.0% line coverage (0/109).
Low coverage: build-logic/convention/src/main/kotlin/ResolveDependenciesPlugin.kt build-logic/convention/src/main/kotlin/ResolveDependenciesPlugin.kt:1— 0.0% line coverage (0/47).
Low coverage: build-logic/convention/src/main/kotlin/SonarConventionPlugin.kt build-logic/convention/src/main/kotlin/SonarConventionPlugin.kt:1— 0.0% line coverage (0/20).
Low coverage: build-logic/convention/src/main/kotlin/com/adyen/checkout/AggregateDependencyListsTask.kt build-logic/convention/src/main/kotlin/com/adyen/checkout/AggregateDependencyListsTask.kt:1— 0.0% line coverage (0/27).
Low coverage: build-logic/convention/src/main/kotlin/com/adyen/checkout/CoverageExclusions.kt build-logic/convention/src/main/kotlin/com/adyen/checkout/CoverageExclusions.kt:1— 0.0% line coverage (0/91).
Low coverage: build-logic/convention/src/main/kotlin/com/adyen/checkout/GenerateDependencyListTask.kt build-logic/convention/src/main/kotlin/com/adyen/checkout/GenerateDependencyListTask.kt:1— 0.0% line coverage (0/11).
Low coverage: build-logic/convention/src/main/kotlin/com/adyen/checkout/ProjectExtensions.kt build-logic/convention/src/main/kotlin/com/adyen/checkout/ProjectExtensions.kt:1— 0.0% line coverage (0/1). 1 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Low coverage: build-logic/convention/src/main/kotlin/com/adyen/checkout/ResolveDependenciesTask.kt build-logic/convention/src/main/kotlin/com/adyen/checkout/ResolveDependenciesTask.kt:1— 0.0% line coverage (0/4).
Low coverage: lint/src/main/java/com/adyen/checkout/lint/ContextGetString.kt lint/src/main/java/com/adyen/checkout/lint/ContextGetString.kt:1— 0.0% line coverage (0/29). 29 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Low coverage: lint/src/main/java/com/adyen/checkout/lint/JSONOptFunctions.kt lint/src/main/java/com/adyen/checkout/lint/JSONOptFunctions.kt:1— 0.0% line coverage (0/38). 37 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Low coverage: lint/src/main/java/com/adyen/checkout/lint/LintIssueRegistry.kt lint/src/main/java/com/adyen/checkout/lint/LintIssueRegistry.kt:1— 0.0% line coverage (0/9).
Low coverage: lint/src/main/java/com/adyen/checkout/lint/NotAdyenLog.kt lint/src/main/java/com/adyen/checkout/lint/NotAdyenLog.kt:1— 0.0% line coverage (0/19). 19 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Low coverage: lint/src/main/java/com/adyen/checkout/lint/NotDispatcherProvider.kt lint/src/main/java/com/adyen/checkout/lint/NotDispatcherProvider.kt:1— 0.0% line coverage (0/27). 27 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Low coverage: lint/src/main/java/com/adyen/checkout/lint/ObjectInPublicSealedClass.kt lint/src/main/java/com/adyen/checkout/lint/ObjectInPublicSealedClass.kt:1— 0.0% line coverage (0/36). 36 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Low coverage: lint/src/main/java/com/adyen/checkout/lint/TextInLayoutXml.kt lint/src/main/java/com/adyen/checkout/lint/TextInLayoutXml.kt:1— 0.0% line coverage (0/22). 22 more line(s) were executed in some of the 3 runs of the suite and not in others, so they are not counted as covered.
Duplicated block (9 lines × 2) ideal/src/main/java/com/adyen/checkout/ideal/internal/ui/DefaultIdealDelegate.kt:59— ideal/src/main/java/com/adyen/checkout/ideal/internal/ui/DefaultIdealDelegate.kt:59-67 | instant/src/main/java/com/adyen/checkout/instant/internal/ui/DefaultInstantPaymentDelegate.kt:89-97 — 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 (9 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/Sha256.kt:20— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/Sha256.kt:20-28 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/Sha256.kt:20-28 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/Sha256.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/helper/Sha256.kt` as WHOLE FILES: 95% 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.
Duplicated block (9 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:476— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:476-484 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:218-226 — 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 `action` to `RedirectAction` in one and `QrCodeAction` 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 (9 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:144— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:144-152 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:169-177 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:234— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:234-242 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:114-122 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:225— await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:225-233 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:315-323 — before extracting anything, compare `await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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. 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:27— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:27-35 | core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt:27-35 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:27` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:42— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:42-50 | core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt:42-50 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:37— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:37-45 | core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt:35-43 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:37` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:52— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:52-60 | core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt:50-58 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:52` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/ResultExt.kt:16— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/ResultExt.kt:16-24 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/ResultExt.kt:16-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.
Duplicated block (9 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:59— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:59-67 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt:59-67 — before extracting anything, compare `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt` and `core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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. Note first that the copies are not typed on the same thing: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/AnalyticsService.kt:31— components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/AnalyticsService.kt:31-39 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/api/AnalyticsService.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. Read the line range as the matched WINDOW rather than a finished unit: at `components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/AnalyticsService.kt:31` 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: `AnalyticsSetupRequest` names `com.adyen.checkout.components.core.internal.data.model.AnalyticsSetupRequest` in one and `com.adyen.checkout.core.analytics.internal.data.remote.model.AnalyticsSetupRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/AnalyticsService.kt:45— components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/AnalyticsService.kt:45-53 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/api/AnalyticsService.kt:59-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. Read the line range as the matched WINDOW rather than a finished unit: at `components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/AnalyticsService.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. Note first that the copies are not typed on the same thing: `AnalyticsTrackRequest` names `com.adyen.checkout.components.core.internal.data.model.AnalyticsTrackRequest` in one and `com.adyen.checkout.core.analytics.internal.data.remote.model.AnalyticsTrackRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) core/src/main/java/com/adyen/checkout/core/components/internal/ui/GenericPaymentComponent.kt:74— core/src/main/java/com/adyen/checkout/core/components/internal/ui/GenericPaymentComponent.kt:74-82 | core/src/main/java/com/adyen/checkout/core/components/internal/ui/GenericStoredPaymentComponent.kt:79-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) redirect/src/main/java/com/adyen/checkout/redirect/internal/data/api/NativeRedirectService.kt:27— redirect/src/main/java/com/adyen/checkout/redirect/internal/data/api/NativeRedirectService.kt:27-35 | redirect/src/main/java/com/adyen/checkout/redirect/old/internal/data/api/NativeRedirectService.kt:27-35 — 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 `redirect/src/main/java/com/adyen/checkout/redirect/internal/data/api/NativeRedirectService.kt:27` 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: `NativeRedirectRequest` names `com.adyen.checkout.redirect.internal.data.model.NativeRedirectRequest` in one and `com.adyen.checkout.redirect.old.internal.data.model.NativeRedirectRequest` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/view/FullVoucherView.kt:140— voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/view/FullVoucherView.kt:140-148 | voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/view/SimpleVoucherView.kt:89-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:135— example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:135-143 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:134-142 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:135` 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 (9 lines × 2) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:370— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:370-378 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:147-155 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt` and `example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:370` 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 (13 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:193— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:193-205 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:389-401 — 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:440— card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:440-452 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/StoredCardView.kt:118-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.kt:61— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.kt:61-73 | core/src/main/java/com/adyen/checkout/core/common/internal/model/ModelUtils.kt:44-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (13 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:59— checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:59-71 | core/src/main/java/com/adyen/checkout/core/common/helper/CardNumberValidator.kt:56-68 — 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 `checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:83— ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:83-95 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:84-96 — before extracting anything, compare `ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt` and `paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 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 `ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:167— ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:167-179 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:169-181 — before extracting anything, compare `ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt` and `paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 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 `ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:332— paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:332-344 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:440-452 — 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 `paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:332` 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) twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:106— twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:106-118 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:184-196 — 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 `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:261— twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:261-273 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:348-360 — 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 `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:536— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:536-548 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:520-532 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt` and `authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 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. 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: `ChallengeToken` names `com.adyen.checkout.authentication.internal.data.model.ChallengeToken` in one and `com.adyen.checkout.threeds2.old.internal.data.model.ChallengeToken` 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 (13 lines × 2) action-core/src/main/java/com/adyen/checkout/action/core/internal/ui/DefaultGenericActionDelegate.kt:101— action-core/src/main/java/com/adyen/checkout/action/core/internal/ui/DefaultGenericActionDelegate.kt:101-113 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:145-157 — 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 `action-core/src/main/java/com/adyen/checkout/action/core/internal/ui/DefaultGenericActionDelegate.kt:101` 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) card-scanning/src/main/java/com/adyen/checkout/card/scanning/internal/CardScannerInitializer.kt:31— card-scanning/src/main/java/com/adyen/checkout/card/scanning/internal/CardScannerInitializer.kt:31-43 | card-scanning/src/main/java/com/adyen/checkout/card/scanning/old/AdyenCardScanner.kt:39-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. 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: `Environment` names `com.adyen.checkout.core.common.Environment` in one and `com.adyen.checkout.core.old.Environment` 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 (13 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt:68— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt:68-80 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/LogcatLogger.kt:68-80 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/helper/LogcatLogger.kt` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt:68` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (13 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:34— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:34-46 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt:34-46 — before extracting anything, compare `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt` and `core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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. Note first that the copies are not typed on the same thing: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` 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 (13 lines × 2) core/src/main/java/com/adyen/checkout/core/sessions/internal/data/model/SessionDetails.kt:35— core/src/main/java/com/adyen/checkout/core/sessions/internal/data/model/SessionDetails.kt:35-47 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/data/model/SessionDetails.kt:35-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. Note first that the copies are not typed on the same thing: `CheckoutSession` names `com.adyen.checkout.core.sessions.CheckoutSession` in one and `com.adyen.checkout.sessions.core.CheckoutSession` 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 (13 lines × 2) qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:103— qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:103-115 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/SimpleQRCodeView.kt:132-144 — 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×15
Change coupling: DropInViewModel.kt ↔ DropInActivityEvent.kt drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/DropInViewModel.kt:1— `drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/DropInViewModel.kt` and `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/model/DropInActivityEvent.kt` change together 85% of the time (11 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 11 shared commits counted here, the most recent 3 are `e91f5fe8` Track error event when `/payments` call failed (at that commit the file was still `drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/model/DropInActivityEvent.kt`); `c654ff2a` COAND-663: use CheckoutSession instead of SessionModel to launch drop-in (at that commit the files were still `drop-in/src/main/java/com/adyen/checkout/dropin/ui/viewmodel/DropInViewModel.kt` and `drop-in/src/main/java/com/adyen/checkout/dropin/ui/viewmodel/DropInActivityEvent.kt`); `b7667a53` COAND-663: rename Session to SessionModel (at that commit the files were still `drop-in/src/main/java/com/adyen/checkout/dropin/ui/viewmodel/DropInViewModel.kt` and `drop-in/src/main/java/com/adyen/checkout/dropin/ui/viewmodel/DropInActivityEvent.kt`) — run `git show` on any of them.
Change coupling: DefaultImageLoader.kt ↔ Images.kt core/src/main/java/com/adyen/checkout/core/internal/image/DefaultImageLoader.kt:1— `core/src/main/java/com/adyen/checkout/core/internal/image/DefaultImageLoader.kt` and `core/src/main/java/com/adyen/checkout/core/internal/image/Images.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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `0d58bdc4` Make DefaultImageLoader testable; `263425d9` Only join in-flight image requests that are still running; `927ace1b` Pre-load bitmaps — run `git show` on any of them.
Change coupling: CardInputData.kt ↔ CardOutputData.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardInputData.kt:1— `card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardOutputData.kt` change together 68% of the time (17 of the 25 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 17 shared commits counted here, the most recent 3 are `4b852e9f` Use string representation of expiry date in card component state (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardOutputData.kt`); `089c34af` Refactor dual branded card logic into DualBrandedCardHandler (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardOutputData.kt`); `2d57fa92` Display card brand selection section in CardView (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardOutputData.kt`) — run `git show` on any of them.
Change coupling: AnalyticsManager.kt ↔ DefaultAnalyticsRepository.kt components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/AnalyticsManager.kt:1— `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/AnalyticsManager.kt` and `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/DefaultAnalyticsRepository.kt` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7a5aea3f` Create analytics manager factory and use it for MBWay component; `ee1c2c89` Implement timer and send logic; `d7c56a35` Make reading and writing in data stores synchronized — run `git show` on any of them.
Change coupling: CardComponentStateReducer.kt ↔ CardViewStateProducer.kt card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStateReducer.kt:1— `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStateReducer.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardViewStateProducer.kt` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 8 shared commits counted here, the most recent 3 are `c75d22c5` Use function as constructor for InstallmentModel; Clean up the code a…; `3b6e947e` Move the InstallmentUtils functions into specific classes; Introduce …; `467a8170` Add card scanning state and intents to v6 card component. — run `git show` on any of them.
Change coupling: CardComponent.kt ↔ CardOutputData.kt card/src/main/java/com/adyen/checkout/card/old/CardComponent.kt:1— `card/src/main/java/com/adyen/checkout/card/old/CardComponent.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardOutputData.kt` change together 60% of the time (31 of the 52 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 31 shared commits counted here, the most recent 3 are `75ee5483` Extract address lookup related code and move it to ui-core (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/CardComponent.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardOutputData.kt`); `0ea2b01c` Add on address completion callback to address lookup flow (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/CardComponent.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardOutputData.kt`); `bb651ed1` Refactor bcmc to inherit card component (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/CardComponent.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardOutputData.kt`) — run `git show` on any of them.
Change coupling: AwaitFactory.kt ↔ ActionComponentProvider.kt await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitFactory.kt:1— `await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitFactory.kt` and `core/src/main/java/com/adyen/checkout/core/action/internal/ActionComponentProvider.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 `3cc37fff` Make ActionFactory generic over action type; `37791fbe` Move Analytics manager creation to payment facilitator layer; `442d7794` Move component params for actions to payment facilitator layer — run `git show` on any of them.
Change coupling: CardComponentStateReducer.kt ↔ CardComponentStateValidator.kt card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStateReducer.kt:1— `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStateReducer.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStateValidator.kt` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `96c363a9` Keep the confirmed billing address in the card state; `f6e4dd02` Group error message and visibility; `d75b7d29` Add Postal Code field to Card Component — run `git show` on any of them.
Change coupling: CardValidationMapper.kt ↔ DefaultLocalizationSource.kt card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationMapper.kt:1— `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationMapper.kt` and `core/src/main/java/com/adyen/checkout/core/common/localization/internal/DefaultLocalizationSource.kt` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 `5bd51dc5` Align card security code strings with iOS and Web; `d75b7d29` Add Postal Code field to Card Component; `3c0ec86f` Create scaffold for KCP fields — run `git show` on any of them.
Change coupling: CardViewStateProducer.kt ↔ CardContent.kt card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardViewStateProducer.kt:1— `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardViewStateProducer.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardContent.kt` change together 53% of the time (20 of the 38 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 20 shared commits counted here, the most recent 3 are `9b754191` Show the billing address row and route its screens; `bec299a0` Render card form from ordered elements; `7699c923` Hide PayButton if configuration.showSubmitButton is false — run `git show` on any of them.
Change coupling: CardInputData.kt ↔ CardView.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardInputData.kt:1— `card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt` change together 52% of the time (13 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `4b852e9f` Use string representation of expiry date in card component state (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardView.kt`); `089c34af` Refactor dual branded card logic into DualBrandedCardHandler (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardView.kt`); `2d57fa92` Display card brand selection section in CardView (at that commit the files were still `card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardInputData.kt` and `card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardView.kt`) — run `git show` on any of them.
Change coupling: ActionComponent.kt ↔ PaymentComponent.kt core/src/main/java/com/adyen/checkout/core/action/internal/ActionComponent.kt:1— `core/src/main/java/com/adyen/checkout/core/action/internal/ActionComponent.kt` and `core/src/main/java/com/adyen/checkout/core/components/internal/ui/PaymentComponent.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 `8ef65f24` Extract navigation fields into separate interface; `5b5d70d4` Setup component specific navigation; `8ae921cb` Pass shopperLocale to PaymentFacilitator for localizing the content — run `git show` on any of them.
Change coupling: GooglePayConfiguration.kt ↔ GooglePayComponentParams.kt googlepay/src/main/java/com/adyen/checkout/googlepay/GooglePayConfiguration.kt:1— `googlepay/src/main/java/com/adyen/checkout/googlepay/GooglePayConfiguration.kt` and `googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParams.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 `011b430b` Rename Google Pay button styling to appearance; `1d959d25` Support multiple payment methods in Google Pay configuration; `1cd57134` Add checkoutOption configuration to Google Pay — run `git show` on any of them.
Change coupling: MBWayComponentStateFactory.kt ↔ MBWayContent.kt mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStateFactory.kt:1— `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStateFactory.kt` and `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/view/MBWayContent.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 `148bb4ef` Separate TextInputState into component and view state (at that commit the file was still `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/view/MbWayComponent.kt`); `28385e41` Remove test input field (at that commit the files were still `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewStateFactory.kt` and `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/view/MbWayComponent.kt`); `99f65f82` Add extra input to MBWay for testing (at that commit the files were still `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewStateFactory.kt` and `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/view/MbWayComponent.kt`) — run `git show` on any of them.
Change coupling: MBWayComponentStateFactory.kt ↔ MBWayViewState.kt mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStateFactory.kt:1— `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStateFactory.kt` and `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewState.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 `148bb4ef` Separate TextInputState into component and view state; `28385e41` Remove test input field (at that commit the file was still `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewStateFactory.kt`); `99f65f82` Add extra input to MBWay for testing (at that commit the file was still `mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewStateFactory.kt`) — run `git show` on any of them.
Duplicated block (10 lines × 2) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:208— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:208-217 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:460-470 — before extracting anything, compare `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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 `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:208` 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 (10 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/ImageLoader.kt:101— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/ImageLoader.kt:101-110 | core/src/main/java/com/adyen/checkout/core/internal/image/ImageLoaderProvider.kt:39-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.
Duplicated block (10 lines × 2) qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:139— qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:139-148 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/SimpleQRCodeView.kt:152-161 — 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 `qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:139` 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 (10 lines × 2) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:239— ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:239-248 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:273-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (10 lines × 2) await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:207— await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:207-216 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:279-288 — before extracting anything, compare `await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:151— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:151-160 | core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt:162-171 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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. 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, `core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt:153` calls `serializeStringList`, `JSONArray` and `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:142` 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.kt:97— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.kt:97-106 | core/src/main/java/com/adyen/checkout/core/common/internal/model/ModelUtils.kt:102-111 — 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 (10 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:48— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:48-57 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt:48-57 — before extracting anything, compare `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt` and `core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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. Note first that the copies are not typed on the same thing: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` 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) core/src/main/java/com/adyen/checkout/core/common/internal/ui/CheckoutNetworkLogo.kt:91— core/src/main/java/com/adyen/checkout/core/common/internal/ui/CheckoutNetworkLogo.kt:91-100 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/ImageLoadingExtensions.kt:98-107 — 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) await/src/main/java/com/adyen/checkout/await/internal/ui/view/AwaitContent.kt:34— await/src/main/java/com/adyen/checkout/await/internal/ui/view/AwaitContent.kt:34-43 | redirect/src/main/java/com/adyen/checkout/redirect/internal/ui/view/RedirectContent.kt:34-43 — 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 `await/src/main/java/com/adyen/checkout/await/internal/ui/view/AwaitContent.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 (10 lines × 2) blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/view/BlikView.kt:64— blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/view/BlikView.kt:64-73 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/view/PayByBankView.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. Note first that the copies are not typed on the same thing: `R` names `com.adyen.checkout.blik.R` in one and `com.adyen.checkout.paybybank.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) core/src/main/java/com/adyen/checkout/core/components/CheckoutAction.kt:34— core/src/main/java/com/adyen/checkout/core/components/CheckoutAction.kt:34-43 | core/src/main/java/com/adyen/checkout/core/components/CheckoutPaymentMethod.kt:38-47 — 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 `core/src/main/java/com/adyen/checkout/core/components/CheckoutAction.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 (10 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:127— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:127-136 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:176-185 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:127` 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 (10 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:49— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:49-58 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayFragment.kt:46-55 — 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 (10 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Screen.kt:232— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Screen.kt:232-241 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Screen.kt:243-252 — 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 `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Screen.kt:232` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×13
Edited copy of a member (9 corresponding lines) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:24— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:24-32 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt:24-32 — 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) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/model/ChallengeResult.kt:37— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/model/ChallengeResult.kt:37-45 | authentication/src/main/java/com/adyen/checkout/authentication/internal/data/model/ChallengeResult.kt:37-45 — 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) sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt:162— sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt:162-170 | sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt:180-190 — 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) issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/IssuersUtils.kt:26— issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/IssuersUtils.kt:26-34 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/DefaultPayByBankDelegate.kt:180-188 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:62— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:62-71 | core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt:60-68 — 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) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/api/SubmitFingerprintService.kt:27— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/api/SubmitFingerprintService.kt:27-35 | authentication/src/main/java/com/adyen/checkout/authentication/internal/data/api/SubmitFingerprintService.kt:27-35 — 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) card/src/main/java/com/adyen/checkout/card/internal/data/api/BinLookupService.kt:27— card/src/main/java/com/adyen/checkout/card/internal/data/api/BinLookupService.kt:27-35 | card/src/main/java/com/adyen/checkout/card/old/internal/data/api/BinLookupService.kt:29-37 — 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) components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusService.kt:24— components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusService.kt:24-32 | core/src/main/java/com/adyen/checkout/core/components/internal/data/api/StatusService.kt:24-32 — 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) components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:207— components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:207-215 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:95-104 — 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) components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:294— components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:294-302 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:166-175 — 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) core/src/main/java/com/adyen/checkout/core/components/CheckoutController.kt:40— core/src/main/java/com/adyen/checkout/core/components/CheckoutController.kt:40-48 | core/src/main/java/com/adyen/checkout/core/components/internal/PaymentMethodProvider.kt:55-64 — 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) core/src/main/java/com/adyen/checkout/core/components/CheckoutController.kt:67— core/src/main/java/com/adyen/checkout/core/components/CheckoutController.kt:67-75 | core/src/main/java/com/adyen/checkout/core/components/internal/PaymentMethodProvider.kt:104-114 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:141— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:141-149 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:123-131 — 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.
Duplicated block (15 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:114— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:114-128 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:356-370 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:226— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:226-240 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:454-468 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:386— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:386-400 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:484-498 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:386` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:499— card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:499-513 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:288-302 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:499` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:498` calls `setNumber` and `card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:287` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:208— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:208-222 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:202-216 — before extracting anything, compare `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt` and `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 127 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 `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:208` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/InMemoryCache.kt:29— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/InMemoryCache.kt:29-43 | core/src/main/java/com/adyen/checkout/core/internal/image/InMemoryCache.kt:29-43 — 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 (15 lines × 2) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:179— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:179-193 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:169-183 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (15 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:114— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:114-128 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:207-221 — 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 `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:114` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:185— googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:185-199 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:174-188 — before extracting anything, compare `googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt` and `instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 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 `googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:185` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:114— meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:114-128 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:207-221 — 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 `meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:114` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientFactory.kt:25— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientFactory.kt:25-39 | core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientFactory.kt:25-39 — 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: `Environment` names `com.adyen.checkout.core.common.Environment` in one and `com.adyen.checkout.core.old.Environment` 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 (15 lines × 2) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:230— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:230-244 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:117-131 — 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 `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:144— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:144-158 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt:196-210 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (14 corresponding lines) · ×12
Edited copy of a member (14 corresponding lines) boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:97— boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:97-110 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.kt:308-321 — 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) boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:112— boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:112-125 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.kt:323-336 — 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) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodAdapter.kt:147— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodAdapter.kt:147-160 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PreselectedStoredPaymentMethodFragment.kt:193-209 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardSecurityCodeValidator.kt:34— checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardSecurityCodeValidator.kt:34-47 | core/src/main/java/com/adyen/checkout/core/common/helper/CardSecurityCodeValidator.kt:33-46 — 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) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:407— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:407-424 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:385-398 — 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) sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt:199— sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt:199-212 | sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt:221-234 — 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) card/src/main/java/com/adyen/checkout/card/internal/helper/CardConfigDataGenerator.kt:63— card/src/main/java/com/adyen/checkout/card/internal/helper/CardConfigDataGenerator.kt:63-76 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/CardConfigDataGenerator.kt:64-77 — 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) card/src/main/java/com/adyen/checkout/card/internal/ui/view/StoredCardContent.kt:104— card/src/main/java/com/adyen/checkout/card/internal/ui/view/StoredCardContent.kt:104-124 | blik/src/main/java/com/adyen/checkout/blik/internal/ui/view/BlikContent.kt:98-111 — 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) authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:404— authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:404-422 | 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:429-442 — 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) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:299— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:299-312 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:332-350 — 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) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:127— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:127-140 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:85-98 — 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) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:283— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:283-297 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:178-191 — 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.
Duplicated block (8 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/model/ChallengeResult.kt:38— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/model/ChallengeResult.kt:38-45 | authentication/src/main/java/com/adyen/checkout/authentication/internal/data/model/ChallengeResult.kt:38-45 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/model/ChallengeResult.kt` and `authentication/src/main/java/com/adyen/checkout/authentication/internal/data/model/ChallengeResult.kt` as WHOLE FILES: 97% 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. 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) card/src/main/java/com/adyen/checkout/card/internal/data/api/NetworkCardBrandDetectionService.kt:69— card/src/main/java/com/adyen/checkout/card/internal/data/api/NetworkCardBrandDetectionService.kt:69-76 | card/src/main/java/com/adyen/checkout/card/old/internal/data/api/DefaultDetectCardTypeRepository.kt:199-206 — 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: `Brand` names `com.adyen.checkout.card.internal.data.model.Brand` in one and `com.adyen.checkout.card.old.internal.data.model.Brand` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `card/src/main/java/com/adyen/checkout/card/internal/data/api/NetworkCardBrandDetectionService.kt:78` calls `isHiddenCardType` and `card/src/main/java/com/adyen/checkout/card/old/internal/data/api/DefaultDetectCardTypeRepository.kt:207` 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 × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:25— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt:25-32 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt:25-32 — before extracting anything, compare `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/AnalyticsTrackRequestProvider.kt` and `core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/AnalyticsTrackRequestProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AnalyticsPlatformParams` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsPlatformParams` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsPlatformParams` 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) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:550— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:550-557 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:299-306 — 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) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:72— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:72-79 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/StoredTwintDelegate.kt:70-77 — 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 `componentState` to `CashAppPayComponentState` in one and `TwintComponentState` 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:98— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:98-105 | core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt:99-106 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/JSONObjectParceler.kt:30— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/JSONObjectParceler.kt:30-37 | core/src/main/java/com/adyen/checkout/core/common/internal/model/JSONObjectParceler.kt:30-37 — 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) drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInResultContract.kt:24— drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInResultContract.kt:24-31 | drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInResultContract.kt:26-33 — 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 (8 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/view/GiftCardNumberInput.kt:46— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/view/GiftCardNumberInput.kt:46-53 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/SocialSecurityNumberInput.kt:44-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:142— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:142-149 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:124-131 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:142` 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, `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:133` calls `onAction`, `handleAction` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:151` 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 × 2) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:81— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:81-88 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:70-77 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:70— example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:70-77 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:66-73 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:103— card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:103-109 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/StoredCardView.kt:70-76 — 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) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/DefaultAnalyticsRepository.kt:33— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/DefaultAnalyticsRepository.kt:33-39 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/DefaultAnalyticsRepository.kt:33-39 — 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: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` 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) components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/AnalyticsParams.kt:33— components-core/src/main/java/com/adyen/checkout/components/core/internal/ui/model/AnalyticsParams.kt:33-39 | core/src/main/java/com/adyen/checkout/core/common/internal/CheckoutParamsFactory.kt:79-85 — 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: `AnalyticsConfiguration` names `com.adyen.checkout.components.core.AnalyticsConfiguration` in one and `com.adyen.checkout.core.components.AnalyticsConfiguration` 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) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:88— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:88-94 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:82-88 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 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. 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, `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:99` calls `Suppress` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:90` 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 (7 lines × 2) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:152— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:152-158 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardPaymentConfirmationDialogFragment.kt:125-131 — 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) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:113— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:113-119 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/ui/model/GooglePayComponentParamsMapper.kt:136-142 — 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: `AllowedCardNetworks` names `com.adyen.checkout.googlepay.AllowedCardNetworks` in one and `com.adyen.checkout.googlepay.old.AllowedCardNetworks` 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) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:124— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:124-130 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/ui/model/GooglePayComponentParamsMapper.kt:147-153 — 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 `googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:124` 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: `Environment` names `com.adyen.checkout.core.common.Environment` in one and `com.adyen.checkout.core.old.Environment` 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) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/view/CashAppPayView.kt:59— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/view/CashAppPayView.kt:59-65 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/view/TwintView.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) qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:133— qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:133-139 | voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/DefaultVoucherDelegate.kt:91-97 — 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) scripts/drop_all_open_ossrh_repositories.py:64— scripts/drop_all_open_ossrh_repositories.py:64-73 | scripts/drop_all_open_ossrh_repositories.py:78-84 — 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. 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) scripts/generate_release_notes.py:99— scripts/generate_release_notes.py:99-105 | scripts/validate_dependencies_for_release_notes.py:16-23 — 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×9
Edited copy of a member (12 corresponding lines) components-core/src/main/java/com/adyen/checkout/components/core/internal/util/AmountFormat.kt:46— components-core/src/main/java/com/adyen/checkout/components/core/internal/util/AmountFormat.kt:46-64 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/AmountFormat.kt:43-54 — 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) blik/src/main/java/com/adyen/checkout/blik/internal/ui/BlikFactory.kt:61— blik/src/main/java/com/adyen/checkout/blik/internal/ui/BlikFactory.kt:61-72 | core/src/main/java/com/adyen/checkout/core/components/internal/ui/GenericPaymentComponentFactory.kt:32-43 — 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) blik/src/main/java/com/adyen/checkout/blik/internal/ui/BlikComponent.kt:78— blik/src/main/java/com/adyen/checkout/blik/internal/ui/BlikComponent.kt:78-89 | mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/MBWayComponent.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) ui/src/main/java/com/adyen/checkout/ui/internal/element/SearchableValuePicker.kt:65— ui/src/main/java/com/adyen/checkout/ui/internal/element/SearchableValuePicker.kt:65-77 | ui/src/main/java/com/adyen/checkout/ui/internal/element/ValuePicker.kt:70-81 — 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) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:74— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:74-85 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardPaymentConfirmationDialogFragment.kt:83-94 — 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) core/src/main/java/com/adyen/checkout/core/sessions/internal/data/api/SessionRepository.kt:59— core/src/main/java/com/adyen/checkout/core/sessions/internal/data/api/SessionRepository.kt:59-70 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/data/api/SessionRepository.kt:67-78 — 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) upi/src/main/java/com/adyen/checkout/upi/internal/ui/view/UPIIntentGenericAppViewHolder.kt:20— upi/src/main/java/com/adyen/checkout/upi/internal/ui/view/UPIIntentGenericAppViewHolder.kt:20-31 | upi/src/main/java/com/adyen/checkout/upi/internal/ui/view/UPIIntentPaymentAppViewHolder.kt:22-37 — 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) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:111— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:111-123 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:93-104 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikActivity.kt:96— example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikActivity.kt:96-107 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:101-112 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:367— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:367-378 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:465-476 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:367` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:60— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:60-71 | core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt:60-71 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt:73` calls `Suppress` and `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:73` 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 (12 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:131— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:131-142 | core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt:133-144 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt:153` calls `serializeStringList`, `JSONArray` and `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:151` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.kt:21— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.kt:21-32 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/AdyenLog.kt:21-32 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/helper/AdyenLog.kt` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AdyenLogger` names `com.adyen.checkout.core.common.AdyenLogger` in one and `com.adyen.checkout.core.old.AdyenLogger` 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 (12 lines × 2) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:162— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:162-173 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:152-163 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 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. 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: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (12 lines × 2) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:189— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:189-200 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:170-181 — 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: `GooglePayComponentParams` names `com.adyen.checkout.googlepay.internal.ui.model.GooglePayComponentParams` in one and `com.adyen.checkout.googlepay.old.internal.ui.model.GooglePayComponentParams` 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 (12 lines × 2) await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitComponent.kt:65— await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitComponent.kt:65-77 | redirect/src/main/java/com/adyen/checkout/redirect/internal/ui/RedirectComponent.kt:71-82 — 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 (12 lines × 2) example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:61— example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:61-72 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt:58-69 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt` and `example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.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 (12 lines × 2) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:354— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:354-365 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:131-142 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt` and `example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:354` 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 (5 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/DefaultComponentEventHandler.kt:32— components-core/src/main/java/com/adyen/checkout/components/core/internal/DefaultComponentEventHandler.kt:32-36 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/GiftCardComponentEventHandler.kt:32-37 — 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 `components-core/src/main/java/com/adyen/checkout/components/core/internal/DefaultComponentEventHandler.kt:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `PaymentComponentEvent<T>` in one and `PaymentComponentEvent<GiftCardComponentState>` 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, `components-core/src/main/java/com/adyen/checkout/components/core/internal/DefaultComponentEventHandler.kt:37` calls `onSubmit` and `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/GiftCardComponentEventHandler.kt:38` 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 (5 lines × 2) bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:292— bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:292-296 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:377-381 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:107— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt:107-111 | core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt:108-112 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/HttpClientExt.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/HttpClientExt.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.kt:43— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.kt:43-47 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/AdyenLog.kt:43-47 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/helper/AdyenLog.kt` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/AdyenLog.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. Note first that the copies are not typed on the same thing: `AdyenLogger` names `com.adyen.checkout.core.common.AdyenLogger` in one and `com.adyen.checkout.core.old.AdyenLogger` 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 (5 lines × 2) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:90— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:90-94 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:87-91 — 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: `GooglePayComponentParams` names `com.adyen.checkout.googlepay.internal.ui.model.GooglePayComponentParams` in one and `com.adyen.checkout.googlepay.old.internal.ui.model.GooglePayComponentParams` 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 (5 lines × 2) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:103— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:103-107 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:100-104 — 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: `GooglePayComponentParams` names `com.adyen.checkout.googlepay.internal.ui.model.GooglePayComponentParams` in one and `com.adyen.checkout.googlepay.old.internal.ui.model.GooglePayComponentParams` 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 (5 lines × 2) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:219— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:219-223 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:197-201 — 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) blik/src/main/java/com/adyen/checkout/blik/internal/ui/state/BlikViewStateProducer.kt:21— blik/src/main/java/com/adyen/checkout/blik/internal/ui/state/BlikViewStateProducer.kt:21-27 | card/src/main/java/com/adyen/checkout/card/internal/ui/state/StoredCardViewStateProducer.kt:21-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 (5 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:127— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:127-131 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt:145-149 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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.
TooManyMethods: DropInActivity drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInActivity.kt:73— TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DefaultCardDelegate card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:101— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.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: CardView card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:64— 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: DefaultAdyen3DS2Delegate 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:75— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: Builder drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInConfiguration.kt:114— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: StoredCardDelegate card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:73— 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: AuthenticationComponent authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:73— 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: DropInViewModel drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInViewModel.kt:57— 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×8
Edited copy of a member (10 corresponding lines) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:130— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:130-140 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:114-123 — 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) address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressPickerField.kt:38— address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressPickerField.kt:38-47 | address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressFormContent.kt:172-181 — 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) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:102— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/ui/model/GooglePayComponentParamsMapper.kt:102-111 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/ui/model/GooglePayComponentParamsMapper.kt:125-134 — 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) issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/view/IssuerListRecyclerAdapter.kt:50— issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/view/IssuerListRecyclerAdapter.kt:50-61 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/view/PayByBankRecyclerAdapter.kt:42-51 — 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) await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitComponent.kt:79— await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitComponent.kt:79-90 | redirect/src/main/java/com/adyen/checkout/redirect/internal/ui/RedirectComponent.kt:84-93 — 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) paybybank-us/src/main/java/com/adyen/checkout/paybybankus/PayByBankUSConfiguration.kt:75— paybybank-us/src/main/java/com/adyen/checkout/paybybankus/PayByBankUSConfiguration.kt:75-84 | paybybank/src/main/java/com/adyen/checkout/paybybank/PayByBankConfiguration.kt:93-102 — 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) await/src/main/java/com/adyen/checkout/await/old/internal/ui/view/AwaitView.kt:56— await/src/main/java/com/adyen/checkout/await/old/internal/ui/view/AwaitView.kt:56-65 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/view/PayByBankView.kt:53-64 — 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) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:397— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:397-414 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:186-195 — 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.
Duplicated block (14 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:115— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:115-128 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:90-103 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:115` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:181— await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:181-194 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:236-249 — before extracting anything, compare `await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `action` to `Action` in one and `QrCodeAction` 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 (14 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:105— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt:105-118 | core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt:94-107 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/JsonUtils.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/model/JsonUtils.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:97— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:97-110 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt:76-89 — before extracting anything, compare `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt` and `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `paymentComponentState` to `GiftCardComponentState` in one and `T` 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 (14 lines × 2) online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:114— online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:114-127 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:208-221 — 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 `online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:114` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) card/src/main/java/com/adyen/checkout/card/internal/data/model/Brand.kt:78— card/src/main/java/com/adyen/checkout/card/internal/data/model/Brand.kt:78-91 | card/src/main/java/com/adyen/checkout/card/old/internal/data/model/Brand.kt:91-104 — 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 `card/src/main/java/com/adyen/checkout/card/internal/data/model/Brand.kt:78` 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 (14 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:55— example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:55-68 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:51-64 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:55` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:53` calls `applyInsetsToRootLayout` and `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:49` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:92— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:92-105 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt:93-106 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:92` 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.
Off the main sequence: .:ui — .:ui: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: .:checkout-core — .:checkout-core: abstractness 0.12, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: .:3ds2 — .:3ds2: abstractness 0.04, instability 0.14, distance 0.82 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: .:sessions-core — .:sessions-core: abstractness 0.14, instability 0.04, distance 0.81 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: .:core — .:core: abstractness 0.10, instability 0.10, distance 0.80 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: .:ui-core — .:ui-core: abstractness 0.18, instability 0.04, distance 0.78 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
Off the main sequence: .:authentication — .:authentication: abstractness 0.04, instability 0.20, distance 0.76 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: .:components-core — .:components-core: abstractness 0.13, instability 0.13, distance 0.74 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×7
Edited copy of a member (8 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:188— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:188-195 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:183-192 — 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) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardNumberInput.kt:60— card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardNumberInput.kt:60-68 | sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/view/IbanInput.kt:22-29 — 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) mbway/src/main/java/com/adyen/checkout/mbway/old/internal/ui/model/MBWayOutputData.kt:23— mbway/src/main/java/com/adyen/checkout/mbway/old/internal/ui/model/MBWayOutputData.kt:23-35 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/model/PayToOutputData.kt:67-74 — 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) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:47— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:47-54 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GooglePayComponentDialogFragment.kt:51-58 — 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) twint-action/src/main/java/com/adyen/checkout/twint/action/internal/ui/DefaultTwintActionDelegate.kt:137— twint-action/src/main/java/com/adyen/checkout/twint/action/internal/ui/DefaultTwintActionDelegate.kt:137-149 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/ui/DefaultWeChatDelegate.kt:156-163 — 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) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:653— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:653-660 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:664-671 — 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) components-core/src/main/java/com/adyen/checkout/components/core/internal/util/ContextExtensions.kt:34— components-core/src/main/java/com/adyen/checkout/components/core/internal/util/ContextExtensions.kt:34-44 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/ContextExtensions.kt:18-25 — 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.
Duplicated block (16 lines × 2) await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:120— await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:120-135 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:165-180 — before extracting anything, compare `await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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 `await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:120` 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) card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:49— card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:49-64 | card/src/main/java/com/adyen/checkout/card/old/internal/util/CardValidationUtils.kt:43-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. Read the line range as the matched WINDOW rather than a finished unit: at `card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `CardNumberValidationResult` names `com.adyen.checkout.core.common.helper.CardNumberValidationResult` in one and `com.adyen.checkout.core.old.ui.validation.CardNumberValidationResult` 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 (16 lines × 2) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:145— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:145-160 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:135-150 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (16 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:131— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:131-146 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt:107-122 — before extracting anything, compare `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt` and `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `sessionComponentCallback` to `SessionsGiftCardComponentCallback` in one and `SessionComponentCallback<T>` 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 (16 lines × 2) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:36— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:36-51 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:36-51 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 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 `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:109— components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:109-124 | core/src/main/java/com/adyen/checkout/core/components/internal/data/api/StatusRepository.kt:116-131 — 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 (16 lines × 2) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/ui/model/BcmcComponentParamsMapper.kt:39— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/ui/model/BcmcComponentParamsMapper.kt:39-54 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardComponentParamsMapper.kt:75-90 — 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 `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/ui/model/BcmcComponentParamsMapper.kt:39` 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.
ClassTooLong: DefaultCardDelegate card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:101— ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 400 significant lines; this is 186 over it, 1.47× 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: CardView card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:64— ClassTooLong — 493 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 93 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: DropInActivity drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInActivity.kt:73— ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 400 significant lines; this is 52 over it, 1.13× 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: DefaultAdyen3DS2Delegate 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:75— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 43 over it, 1.11× 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: AuthenticationComponent authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:73— ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 38 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.
ClassTooLong: CardComponentProvider card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:70— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 4 over it, 1.01× 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 (24 corresponding lines) · ×6
Edited copy of a member (24 corresponding lines) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/view/GiftCardView.kt:92— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/view/GiftCardView.kt:92-115 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/ui/view/MealVoucherFRView.kt:124-152 — 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.
Edited copy of a member (24 corresponding lines) qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:335— qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:335-366 | voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/DefaultVoucherDelegate.kt:191-214 — 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.
Edited copy of a member (24 corresponding lines) googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:153— googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:153-178 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:136-159 — 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.
Edited copy of a member (24 corresponding lines) twint-action/src/main/java/com/adyen/checkout/twint/action/internal/ui/DefaultTwintActionDelegate.kt:112— twint-action/src/main/java/com/adyen/checkout/twint/action/internal/ui/DefaultTwintActionDelegate.kt:112-135 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/ui/DefaultWeChatDelegate.kt:130-154 — 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.
Edited copy of a member (24 corresponding lines) card-scanning/src/main/java/com/adyen/checkout/card/scanning/internal/CardScannerInitializer.kt:45— card-scanning/src/main/java/com/adyen/checkout/card/scanning/internal/CardScannerInitializer.kt:45-73 | card-scanning/src/main/java/com/adyen/checkout/card/scanning/old/AdyenCardScanner.kt:53-76 — 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.
Edited copy of a member (24 corresponding lines) example-app/src/main/java/com/adyen/checkout/example/ui/main/MainViewModel.kt:179— example-app/src/main/java/com/adyen/checkout/example/ui/main/MainViewModel.kt:179-202 | example-app/src/main/java/com/adyen/checkout/example/ui/main/MainViewModel.kt:204-230 — 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 (17 corresponding lines) · ×6
Edited copy of a member (17 corresponding lines) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/AddressValidationUtils.kt:59— ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/AddressValidationUtils.kt:59-75 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/AddressValidationUtils.kt:104-120 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:55— checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:55-71 | core/src/main/java/com/adyen/checkout/core/common/helper/CardNumberValidator.kt:52-68 — 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) core/src/main/java/com/adyen/checkout/core/components/internal/CheckoutInitializer.kt:65— core/src/main/java/com/adyen/checkout/core/components/internal/CheckoutInitializer.kt:65-81 | core/src/main/java/com/adyen/checkout/core/components/internal/CheckoutInitializer.kt:85-102 — 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) action-core/src/main/java/com/adyen/checkout/action/core/internal/provider/GenericActionComponentProvider.kt:86— action-core/src/main/java/com/adyen/checkout/action/core/internal/provider/GenericActionComponentProvider.kt:86-102 | voucher/src/main/java/com/adyen/checkout/voucher/internal/provider/VoucherComponentProvider.kt:77-93 — 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) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/data/api/DefaultAddressRepository.kt:67— ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/data/api/DefaultAddressRepository.kt:67-83 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/data/api/DefaultAddressRepository.kt:96-113 — 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) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/model/CashAppPayComponentParamsMapper.kt:84— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/model/CashAppPayComponentParamsMapper.kt:84-103 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/model/TwintComponentParamsMapper.kt:30-46 — 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 (16 corresponding lines) · ×6
Edited copy of a member (16 corresponding lines) qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:138— qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:138-153 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/SimpleQRCodeView.kt:151-166 — 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) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:68— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:68-86 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:65-80 — 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) card/src/main/java/com/adyen/checkout/card/internal/helper/LocalCardBrandMapper.kt:23— card/src/main/java/com/adyen/checkout/card/internal/helper/LocalCardBrandMapper.kt:23-39 | card/src/main/java/com/adyen/checkout/card/old/internal/data/api/DefaultDetectCardTypeRepository.kt:117-132 — 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) googlepay/src/main/java/com/adyen/checkout/googlepay/GooglePayConfiguration.kt:82— googlepay/src/main/java/com/adyen/checkout/googlepay/GooglePayConfiguration.kt:82-98 | card/src/main/java/com/adyen/checkout/card/CardConfiguration.kt:72-87 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.kt:107— example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.kt:107-126 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt:128-143 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:134— example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:134-149 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:133-148 — 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.
Duplicated block (18 lines × 2) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:105— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:105-122 | bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:212-229 — 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 `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:105` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:125— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:125-142 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:237-254 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:125` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:107— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:107-124 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:188-205 — 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 `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:107` 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) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:134— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:134-151 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:213-230 — 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 `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:134` 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 (18 lines × 2) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodListDialogFragment.kt:194— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodListDialogFragment.kt:194-211 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PreselectedStoredPaymentMethodFragment.kt:212-229 — 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 `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodListDialogFragment.kt:194` 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) scripts/drop_all_open_ossrh_repositories.py:47— scripts/drop_all_open_ossrh_repositories.py:47-64 | scripts/move_ossrh_repository_to_central_portal.py:59-76 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scripts/move_ossrh_repository_to_central_portal.py:56` calls `upper` and `scripts/drop_all_open_ossrh_repositories.py:46` 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· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:141— card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:141-153 | card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:186-196 — 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) core/src/main/java/com/adyen/checkout/core/common/helper/RunCompileOnly.kt:16— core/src/main/java/com/adyen/checkout/core/common/helper/RunCompileOnly.kt:16-26 | checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/RunCompileOnly.kt:15-25 — 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) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/protocol/DefaultGiftCardProtocol.kt:26— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/protocol/DefaultGiftCardProtocol.kt:26-36 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/ui/protocol/MealVoucherFRProtocol.kt:28-38 — 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) core/src/main/java/com/adyen/checkout/core/common/internal/helper/CountryUtils.kt:23— core/src/main/java/com/adyen/checkout/core/common/internal/helper/CountryUtils.kt:23-33 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/CountryUtils.kt:23-33 — 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) cashapppay/src/main/java/com/adyen/checkout/cashapppay/CashAppPayConfiguration.kt:179— cashapppay/src/main/java/com/adyen/checkout/cashapppay/CashAppPayConfiguration.kt:179-191 | twint/src/main/java/com/adyen/checkout/twint/TwintConfiguration.kt:143-153 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (21 lines × 2) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:132— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:132-152 | bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:239-259 — 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 `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (21 lines × 2) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:119— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:119-139 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:139-159 — before extracting anything, compare `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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 `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.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 (21 lines × 2) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:226— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:226-246 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:251-271 — before extracting anything, compare `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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 `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:226` 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 (21 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:152— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:152-172 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:264-284 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:152` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (21 lines × 2) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:381— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:381-401 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:368-388 — before extracting anything, compare `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt` and `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 127 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 `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:381` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:268— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:268-287 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:359-378 — 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 `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:268` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:63— components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:63-82 | core/src/main/java/com/adyen/checkout/core/components/internal/data/api/StatusRepository.kt:63-82 — 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 `components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:128— twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:128-147 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:205-224 — 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 `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:128` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:80— example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:80-99 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:76-95 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:80` 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 (20 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Activity.kt:39— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Activity.kt:39-58 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsActivity.kt:39-58 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Activity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsActivity.kt` as WHOLE FILES: 91% 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. 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 `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Activity.kt:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:339— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:339-355 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:305-321 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt` and `authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:102— blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:102-118 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:187-203 — 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 `blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:102` 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 (17 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:74— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:74-90 | core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt:71-87 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (17 lines × 2) payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:102— payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:102-118 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:187-203 — 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 `payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:102` 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 (17 lines × 2) card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardNumberField.kt:182— card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardNumberField.kt:182-198 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardNumberField.kt:201-217 — 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 `card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardNumberField.kt:182` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/AddressValidationUtils.kt:63— ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/AddressValidationUtils.kt:63-68 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/AddressValidationUtils.kt:108-113 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:111— card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:111-116 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/StoredCardView.kt:78-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.
Duplicated block (6 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:133— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:133-138 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayFragment.kt:114-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `BacsEvent` in one and `GooglePayEvent` 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 (6 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:195— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:195-200 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt:248-253 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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) scripts/move_ossrh_repository_to_central_portal.py:76— scripts/move_ossrh_repository_to_central_portal.py:76-87 | scripts/move_ossrh_repository_to_central_portal.py:92-97 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
FileTooLong: ui/DefaultCardDelegate.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: DefaultCardDelegate (101-955). The bar is 500 significant lines; this is 176 over it, 1.35× 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: view/CardView.kt card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: CardView (64-802). The bar is 500 significant lines; this is 44 over it, 1.09× 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: ui/DropInActivity.kt drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInActivity.kt— FileTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: DropInActivity (73-761). The bar is 500 significant lines; this is 11 over it, 1.02× 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: ui/DefaultAdyen3DS2Delegate.kt 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt— FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: DefaultAdyen3DS2Delegate (75-749). The bar is 500 significant lines; this is 7 over it, 1.01× 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 (27 corresponding lines) · ×4
Edited copy of a member (27 corresponding lines) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:96— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:96-125 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt:75-101 — 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) card/src/main/java/com/adyen/checkout/card/internal/ui/view/HolderNameField.kt:39— card/src/main/java/com/adyen/checkout/card/internal/ui/view/HolderNameField.kt:39-65 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/PostalCodeField.kt:34-61 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:73— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:73-99 | core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt:70-96 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:163— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:163-189 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6ViewModel.kt:215-242 — 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 (21 corresponding lines) · ×4
Edited copy of a member (21 corresponding lines) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/DefaultAnalyticsSetupProvider.kt:31— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/remote/DefaultAnalyticsSetupProvider.kt:31-51 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/remote/DefaultAnalyticsSetupProvider.kt:31-52 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:105— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/api/OkHttpClient.kt:105-127 | core/src/main/java/com/adyen/checkout/core/common/internal/api/OkHttpClient.kt:102-122 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) core/src/main/java/com/adyen/checkout/core/sessions/internal/model/SessionParamsFactory.kt:32— core/src/main/java/com/adyen/checkout/core/sessions/internal/model/SessionParamsFactory.kt:32-54 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/ui/model/SessionParamsFactory.kt:35-55 — 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) card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt:74— card/src/main/java/com/adyen/checkout/card/internal/ui/model/CardComponentParamsMapper.kt:74-94 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/model/CardComponentParamsMapper.kt:138-158 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×4
Edited copy of a member (23 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:615— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:615-637 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:626-648 — 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) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:444— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:444-466 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:428-450 — 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) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:229— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:229-254 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.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) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:87— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:87-110 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardViewModel.kt:64-86 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:38— checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:38-52 | core/src/main/java/com/adyen/checkout/core/common/helper/CardNumberValidator.kt:35-49 — 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) qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:155— qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt:155-170 | voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/view/FullVoucherView.kt:244-258 — 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) issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/DefaultIssuerListDelegate.kt:160— issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/DefaultIssuerListDelegate.kt:160-174 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/ui/DefaultOnlineBankingDelegate.kt:156-170 — 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) await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitFactory.kt:31— await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitFactory.kt:31-46 | redirect/src/main/java/com/adyen/checkout/redirect/internal/ui/RedirectFactory.kt:30-44 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) drop-in/src/main/java/com/adyen/checkout/dropin/internal/manage/StoredPaymentMethodManagementViewModel.kt:82— drop-in/src/main/java/com/adyen/checkout/dropin/internal/manage/StoredPaymentMethodManagementViewModel.kt:82-96 | drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/PaymentMethodListViewModel.kt:202-214 — 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) googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:183— googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.kt:183-195 | googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:203-217 — 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) core/src/main/java/com/adyen/checkout/core/common/internal/helper/CustomTabsLauncher.kt:20— core/src/main/java/com/adyen/checkout/core/common/internal/helper/CustomTabsLauncher.kt:20-32 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/CustomTabsLauncher.kt:22-34 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:103— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:103-121 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:97-109 — 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 (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/IssuersUtils.kt:17— issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/IssuersUtils.kt:17-23 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/DefaultPayByBankDelegate.kt:171-177 — 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) bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/BacsDirectDebitValidationUtils.kt:45— bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/BacsDirectDebitValidationUtils.kt:45-51 | boleto/src/main/java/com/adyen/checkout/boleto/internal/util/BoletoValidationUtils.kt:34-40 — 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) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/JSONObjectParceler.kt:22— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/JSONObjectParceler.kt:22-28 | core/src/main/java/com/adyen/checkout/core/common/internal/model/JSONObjectParceler.kt:22-28 — 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) boleto/src/main/java/com/adyen/checkout/boleto/internal/util/BoletoValidationUtils.kt:26— boleto/src/main/java/com/adyen/checkout/boleto/internal/util/BoletoValidationUtils.kt:26-32 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/model/PayToOutputData.kt:135-142 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (25 lines × 2) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:297— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:297-321 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:386-410 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:297` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:94— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:94-118 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:94-118 — before extracting anything, compare `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt` and `meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 101 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 `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:94` 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 (25 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:187— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:187-211 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:187-211 — before extracting anything, compare `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt` and `meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 101 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 `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:187` 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 (25 lines × 2) twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:287— twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:287-311 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:373-397 — 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 `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:287` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:273— blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:273-291 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:381-399 — 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 `blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:273` 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 (19 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/DefaultAnalyticsRepository.kt:44— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/DefaultAnalyticsRepository.kt:44-62 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/DefaultAnalyticsRepository.kt:44-62 — 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. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (19 lines × 2) paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:276— paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:276-294 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:382-400 — 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 `paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:276` 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 (19 lines × 2) payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:272— payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:272-290 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:380-398 — 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 `payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:272` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:73— components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:73-85 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:118-130 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:339-351 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:384-396 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 4) components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:164— components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:164-176 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:250-262 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:430-442 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:477-489 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 4) sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:59— sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:59-71 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:237-249 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionStoredPaymentComponentProvider.kt:60-72 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionStoredPaymentComponentProvider.kt:241-253 — before extracting anything, compare `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt` and `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionStoredPaymentComponentProvider.kt` as WHOLE FILES: 85% 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 `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:59` 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 (13 lines × 4) sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:130— sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:130-142 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:275-287 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionStoredPaymentComponentProvider.kt:132-144 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionStoredPaymentComponentProvider.kt:280-292 — before extracting anything, compare `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt` and `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionStoredPaymentComponentProvider.kt` as WHOLE FILES: 85% 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 `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/provider/SessionPaymentComponentProvider.kt:130` 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 (10 lines × 3) await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:83— await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:83-92 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/provider/QRCodeComponentProvider.kt:82-91 | twint-action/src/main/java/com/adyen/checkout/twint/action/internal/provider/TwintActionComponentProvider.kt:81-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `qr-code/src/main/java/com/adyen/checkout/qrcode/internal/provider/QRCodeComponentProvider.kt:92` calls `QRCodeCountDownTimer` and `await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:93` 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 × 3) blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/StoredBlikDelegate.kt:70— blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/StoredBlikDelegate.kt:70-79 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/StoredPayByBankUSDelegate.kt:67-76 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/StoredPayToDelegate.kt:70-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 3) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:180— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:180-189 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:170-179 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/PdfOpener.kt:74-84 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 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 `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:180` 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. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 × 3) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:124— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:124-133 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:111-120 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/compose/SessionsGooglePayViewModel.kt:106-115 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:124` 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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:88— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:88-105 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GooglePayComponentDialogFragment.kt:91-109 — 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) address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressFormContent.kt:85— address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressFormContent.kt:85-102 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardContent.kt:135-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.
Edited copy of a member (18 corresponding lines) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:60— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:60-77 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayFragment.kt:57-74 — 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.
Duplicated block (23 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:165— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:165-187 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:393-415 — 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 `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:165` 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 (23 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt:31— checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt:31-53 | core/src/main/java/com/adyen/checkout/core/common/internal/helper/LogcatLogger.kt:31-53 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/helper/LogcatLogger.kt` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (23 lines × 2) example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:101— example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:101-123 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt:97-119 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt` and `example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (11 lines × 2) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:65— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:65-75 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt:56-66 — before extracting anything, compare `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt` and `sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/SessionComponentEventHandler.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `PaymentComponentEvent<GiftCardComponentState>` in one and `PaymentComponentEvent<T>` 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) components-core/src/main/java/com/adyen/checkout/components/core/internal/SavedStateHandleContainer.kt:39— components-core/src/main/java/com/adyen/checkout/components/core/internal/SavedStateHandleContainer.kt:39-49 | core/src/main/java/com/adyen/checkout/core/common/internal/SavedStateHandleContainer.kt:41-51 — before extracting anything, compare `components-core/src/main/java/com/adyen/checkout/components/core/internal/SavedStateHandleContainer.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/SavedStateHandleContainer.kt` as WHOLE FILES: 84% 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.
Duplicated block (11 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:149— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:149-159 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:198-208 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (13 lines × 3) econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:150— econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:150-162 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:153-165 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:157-169 — before extracting anything, compare `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt` and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:150` 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 (13 lines × 3) econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:258— econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:258-270 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:259-271 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:270-282 — before extracting anything, compare `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt` and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:258` 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 (13 lines × 3) address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressCityField.kt:31— address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressCityField.kt:31-43 | address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressHouseNumberField.kt:31-43 | address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressStreetField.kt:31-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressCityField.kt:31` 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:60— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:60-100 | example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.kt:58-89 | example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:59-86 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:71-98 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayViewModel.kt:70-100 | example-app/src/main/java/com/adyen/checkout/example/ui/instant/InstantViewModel.kt:58-88 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:143— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:143-163 | example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:126-146 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:175-195 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:213-233 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayViewModel.kt:165-185 | example-app/src/main/java/com/adyen/checkout/example/ui/instant/InstantViewModel.kt:121-140 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:112— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:112-133 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:99-120 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardViewModel.kt:88-109 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/compose/SessionsGooglePayViewModel.kt:94-115 | example-app/src/main/java/com/adyen/checkout/example/ui/main/MainViewModel.kt:241-254 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:72-117 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
MethodTooLong: ComponentProviderKt.getComponentFor drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/provider/ComponentProvider.kt:220— MethodTooLong — getComponentFor runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DefaultLocalizationSource.getString core/src/main/java/com/adyen/checkout/core/common/localization/internal/DefaultLocalizationSource.kt:18— MethodTooLong — getString runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change-coupling hub: DropInActivity.kt → DropInServiceResult.kt, BaseDropInService.kt, BaseDropInServiceInterfaces.kt, DropInActivityEvent.kt drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/DropInActivity.kt— `drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/DropInActivity.kt` changes together with 4 other files — `drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInServiceResult.kt`, `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/service/BaseDropInService.kt`, `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/service/BaseDropInServiceInterfaces.kt`, `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/model/DropInActivityEvent.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: BaseDropInServiceInterfaces.kt → BaseDropInServiceContract.kt, CardComponentDialogFragment.kt, DropInBottomSheetDialogFragment.kt drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/service/BaseDropInServiceInterfaces.kt— `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/service/BaseDropInServiceInterfaces.kt` changes together with 3 other files — `drop-in/src/main/java/com/adyen/checkout/dropin/old/BaseDropInServiceContract.kt`, `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/CardComponentDialogFragment.kt`, `drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInBottomSheetDialogFragment.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:72— components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:72-85 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:117-130 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:338-351 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:383-396 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:163— components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:163-176 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:249-262 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:429-442 | components-compose/src/main/java/com/adyen/checkout/components/compose/ComposeExtensions.kt:476-489 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×2
Edited copy of a member (47 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:488— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:488-534 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:462-518 — 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.
Edited copy of a member (47 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:357— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:357-403 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:323-381 — 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 copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/GiftCardComponentEventHandler.kt:28— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/GiftCardComponentEventHandler.kt:28-68 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/SessionsGiftCardComponentEventHandler.kt:63-91 — 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.
Edited copy of a member (29 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/api/SubmitFingerprintRepository.kt:28— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/data/api/SubmitFingerprintRepository.kt:28-59 | authentication/src/main/java/com/adyen/checkout/authentication/internal/data/api/SubmitFingerprintRepository.kt:28-56 — 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 (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodListDialogFragment.kt:193— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodListDialogFragment.kt:193-218 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PreselectedStoredPaymentMethodFragment.kt:211-236 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Activity.kt:33— example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6Activity.kt:33-58 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsActivity.kt:33-58 — 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) · ×2
Edited copy of a member (22 corresponding lines) card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:48— card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardValidationUtils.kt:48-69 | card/src/main/java/com/adyen/checkout/card/old/internal/util/CardValidationUtils.kt:42-63 — 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) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:105— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsFragment.kt:105-131 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayFragment.kt:91-112 — 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 (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/DefaultAnalyticsManager.kt:72— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/DefaultAnalyticsManager.kt:72-90 | core/src/main/java/com/adyen/checkout/core/analytics/internal/DefaultAnalyticsManager.kt:53-73 — 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) core/src/main/java/com/adyen/checkout/core/components/Checkout.kt:86— core/src/main/java/com/adyen/checkout/core/components/Checkout.kt:86-104 | core/src/main/java/com/adyen/checkout/core/components/Checkout.kt:116-134 — 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 copies of one member (4 members, 16+ corresponding lines) · ×2
Edited copies of one member (4 members, 16+ corresponding lines) issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/view/IssuerListSpinnerAdapter.kt:40— issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/view/IssuerListSpinnerAdapter.kt:40-55 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/CountryAdapter.kt:41-56 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/LocalizedTextListAdapter.kt:48-63 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/TextListAdapter.kt:44-59 — 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.
Edited copies of one member (4 members, 16+ corresponding lines) await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:118— await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:118-135 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.kt:163-180 | redirect/src/main/java/com/adyen/checkout/redirect/old/internal/ui/DefaultRedirectDelegate.kt:105-121 | voucher/src/main/java/com/adyen/checkout/voucher/internal/ui/DefaultVoucherDelegate.kt:118-133 — 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 copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) blik/src/main/java/com/adyen/checkout/blik/internal/ui/view/BlikContent.kt:58— blik/src/main/java/com/adyen/checkout/blik/internal/ui/view/BlikContent.kt:58-77 | mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/view/MBWayContent.kt:65-86 — 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) payto/src/main/java/com/adyen/checkout/payto/internal/ui/DefaultPayToDelegate.kt:147— payto/src/main/java/com/adyen/checkout/payto/internal/ui/DefaultPayToDelegate.kt:147-169 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/DefaultTwintDelegate.kt:122-141 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 22+ corresponding lines) · ×2
Edited copies of one member (4 members, 22+ corresponding lines) address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressCityField.kt:49— address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressCityField.kt:49-70 | address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressHouseNumberField.kt:49-70 | address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressPostalCodeField.kt:58-82 | address/src/main/java/com/adyen/checkout/address/internal/ui/view/AddressStreetField.kt:49-71 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 22+ corresponding lines) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:42— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:42-71 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:47-68 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardActivity.kt:43-68 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardActivity.kt:41-64 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×2
Edited copies of one member (4 members, 12+ corresponding lines) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:205— ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:205-219 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:221-232 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:258-270 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressLookupView.kt:272-284 — 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.
Edited copies of one member (4 members, 12+ corresponding lines) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:125— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:125-136 | example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.kt:128-139 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayViewModel.kt:147-158 | example-app/src/main/java/com/adyen/checkout/example/ui/instant/InstantViewModel.kt:142-154 — 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 copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewStateProducer.kt:21— mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayViewStateProducer.kt:21-29 | card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardViewStateProducer.kt:24-29 — 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) await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitComponent.kt:126— await/src/main/java/com/adyen/checkout/await/internal/ui/AwaitComponent.kt:126-131 | await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:173-178 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/BaseComponentDialogFragment.kt:180— drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/BaseComponentDialogFragment.kt:180-183 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/GiftCardComponentDialogFragment.kt:145-148 | drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PreselectedStoredPaymentMethodFragment.kt:188-191 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) econtext/src/main/java/com/adyen/checkout/econtext/internal/EContextComponent.kt:79— econtext/src/main/java/com/adyen/checkout/econtext/internal/EContextComponent.kt:79-82 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/IssuerListComponent.kt:84-87 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/OnlineBankingComponent.kt:81-84 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:584— card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:584-588 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:344-348 — 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) card/src/main/java/com/adyen/checkout/card/internal/ui/CardComponent.kt:438— card/src/main/java/com/adyen/checkout/card/internal/ui/CardComponent.kt:438-444 | card/src/main/java/com/adyen/checkout/card/internal/ui/StoredCardComponent.kt:181-185 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (30 lines × 2) blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:121— blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:121-150 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:206-235 — 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 `blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:121` 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 (30 lines × 2) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:288— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:288-317 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:502-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:288` 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, `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:319` calls `Suppress` and `card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:533` 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 (20 lines × 3) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:507— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:507-526 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:463-482 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:450-469 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 3) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:193— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:193-212 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:217-236 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/DefaultGiftCardDelegate.kt:120-139 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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 `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:193` 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–15 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:123— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:123-135 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:103-117 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:94— googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:94-108 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:89-101 — before extracting anything, compare `googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt` and `instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 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 `googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 2) econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:92— econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:92-106 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:94-107 — before extracting anything, compare `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt` and `online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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 `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:92` 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 (14–15 lines × 2) econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:179— econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:179-193 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:186-199 — before extracting anything, compare `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt` and `online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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 `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:179` 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 (14 lines × 3) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:219— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:219-232 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:128-141 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:326-339 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:218` calls `adyenLog` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:127` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 3) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:486— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:486-499 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:442-455 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:429-442 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:486` 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 (13–14 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:201— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:201-214 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:189-201 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:201` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:87— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:87-100 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt:52-64 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:84` calls `checkPaymentState`, `checkAdditionalData` and `example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt:49` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (37 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/analytics/ThreeDS2Events.kt:25— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/analytics/ThreeDS2Events.kt:25-61 | authentication/src/main/java/com/adyen/checkout/authentication/internal/analytics/AuthenticationEvents.kt:23-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. Read the line range as the matched WINDOW rather than a finished unit: at `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/analytics/ThreeDS2Events.kt:25` 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: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` 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 (37 lines × 2) core/src/main/java/com/adyen/checkout/core/sessions/internal/data/api/SessionService.kt:31— core/src/main/java/com/adyen/checkout/core/sessions/internal/data/api/SessionService.kt:31-67 | sessions-core/src/main/java/com/adyen/checkout/sessions/core/internal/data/api/SessionService.kt:42-134 — 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 `core/src/main/java/com/adyen/checkout/core/sessions/internal/data/api/SessionService.kt:31` 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: `SessionDetailsRequest` names `com.adyen.checkout.core.sessions.internal.data.model.SessionDetailsRequest` in one and `com.adyen.checkout.sessions.core.internal.data.model.SessionDetailsRequest` 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.
Low cohesion: BaseDropInService (LCOM4 8) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/service/BaseDropInService.kt:44— BaseDropInService'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: ActionComponentDialogFragment (LCOM4 4) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/ActionComponentDialogFragment.kt:43— ActionComponentDialogFragment'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.
Swallowed exception (caught, then discarded) core/src/main/java/com/adyen/checkout/core/internal/image/InMemoryCache.kt:31— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/InMemoryCache.kt:31— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Stateful singleton: ExternalConfigurationReader example-app/src/main/java/com/adyen/checkout/example/data/storage/ExternalConfigurationReader.kt:28— `ExternalConfigurationReader` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (cardConfiguration; e.g. `cardConfiguration` in `apply` at line 33).
CardView.highlightValidationErrors (cyclomatic 25) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:218— CardView.highlightValidationErrors has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PayToView.highlightValidationErrors (cyclomatic 24) payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.kt:339— PayToView.highlightValidationErrors 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.
TodoComment repeated across 10 files googlepay/src/main/java/com/adyen/checkout/googlepay/BillingAddressParameters.kt:47— The identical TodoComment appears in 10 files (10 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 10 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO - Change RuntimeException into a clearer error. Also remove the suppresion.". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
CardView.highlightValidationErrors (cognitive 31) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:218— CardView.highlightValidationErrors has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 7 (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.
PayToView.highlightValidationErrors (cognitive 30) payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.kt:339— PayToView.highlightValidationErrors has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 8 (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.
AddressFormInput.highlightValidationErrors (cognitive 21) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:154— AddressFormInput.highlightValidationErrors has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (21 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.
BacsDirectDebitInputView.highlightValidationErrors (cognitive 16) bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:86— BacsDirectDebitInputView.highlightValidationErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BoletoView.highlightValidationErrors (cognitive 16) boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:182— BoletoView.highlightValidationErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5 (nesting depth added 3). 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.
Change coupling clique: CardValidationUtils.kt, CardExpiryDateValidator.kt, MealVoucherFRValidationUtils.kt card/src/main/java/com/adyen/checkout/card/old/internal/util/CardValidationUtils.kt— 3 files — `card/src/main/java/com/adyen/checkout/card/old/internal/util/CardValidationUtils.kt`, `checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardExpiryDateValidator.kt`, `meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/util/MealVoucherFRValidationUtils.kt` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Members sharing a duplicated core (24 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (24 members, 50+ identical tokens) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:192— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:192-245 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:388-439 | bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:170-239 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:272-343 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:380-452 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:176-250 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:267-321 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:358-410 | econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:175-246 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:181-256 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:166-233 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:169-237 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:178-246 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:170-241 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:182-258 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:275-344 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:381-452 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:168-236 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:271-342 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:379-449 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:171-240 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:260-311 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:347-397 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:165-237 — These 24 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 24 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 24 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) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:309— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:309-351 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:82-129 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:83-131 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:105-147 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:183-224 — 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 (85 corresponding lines) · ×1
Edited copy of a member (85 corresponding lines) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:218— card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:218-302 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.kt:339-441 — These two members are one piece of code written twice and then edited apart: 85 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 79+ corresponding lines) · ×1
Edited copies of one member (4 members, 79+ corresponding lines) bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:204— bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:204-297 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:453-531 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:181-261 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:181-261 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 79 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 (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:462— card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:462-536 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:266-322 — 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 (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:246— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:246-319 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:201-291 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 57+ corresponding lines) · ×1
Edited copies of one member (3 members, 57+ corresponding lines) card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:355— card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:355-415 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:88-144 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:88-144 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 57 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:88— econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:88-138 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:90-145 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:101— blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:101-150 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:186-235 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 50+ corresponding lines) · ×1
Edited copies of one member (5 members, 50+ corresponding lines) bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:84— bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:84-133 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:84-133 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:101-154 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:101-150 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:85-134 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 50 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, 49+ corresponding lines) · ×1
Edited copies of one member (6 members, 49+ corresponding lines) boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:85— boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:85-139 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:84-132 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:92-141 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:190-238 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:186-234 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:79-128 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 49 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 copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:106— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:106-151 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:90-143 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:31— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:31-65 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:31-62 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:62— components-core/src/main/java/com/adyen/checkout/components/core/internal/data/api/StatusRepository.kt:62-98 | core/src/main/java/com/adyen/checkout/core/components/internal/data/api/StatusRepository.kt:62-105 — 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) card/src/main/java/com/adyen/checkout/card/internal/data/api/NetworkCardBrandDetectionService.kt:60— card/src/main/java/com/adyen/checkout/card/internal/data/api/NetworkCardBrandDetectionService.kt:60-87 | card/src/main/java/com/adyen/checkout/card/old/internal/data/api/DefaultDetectCardTypeRepository.kt:188-212 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) card/src/main/java/com/adyen/checkout/card/internal/ui/view/ExpiryDateField.kt:52— card/src/main/java/com/adyen/checkout/card/internal/ui/view/ExpiryDateField.kt:52-86 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/SecurityCodeField.kt:57-96 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 35+ corresponding lines) · ×1
Edited copies of one member (4 members, 35+ corresponding lines) ui/src/main/java/com/adyen/checkout/ui/internal/element/button/Buttons.kt:64— ui/src/main/java/com/adyen/checkout/ui/internal/element/button/Buttons.kt:64-98 | ui/src/main/java/com/adyen/checkout/ui/internal/element/button/Buttons.kt:123-157 | ui/src/main/java/com/adyen/checkout/ui/internal/element/button/Buttons.kt:182-216 | ui/src/main/java/com/adyen/checkout/ui/internal/element/button/Buttons.kt:241-275 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 35 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 (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:201— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:201-238 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:137-177 — 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 copies of one member (5 members, 27+ corresponding lines) · ×1
Edited copies of one member (5 members, 27+ corresponding lines) blik/src/main/java/com/adyen/checkout/blik/internal/ui/view/BlikCodeField.kt:41— blik/src/main/java/com/adyen/checkout/blik/internal/ui/view/BlikCodeField.kt:41-75 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardNumberField.kt:91-130 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/KCPCardPasswordField.kt:38-68 | card/src/main/java/com/adyen/checkout/card/internal/ui/view/SocialSecurityNumberField.kt:39-71 | mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/view/MBWayPhoneNumberField.kt:41-67 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 27 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 (5 members, 20+ corresponding lines) · ×1
Edited copies of one member (5 members, 20+ corresponding lines) ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:317— ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:317-337 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:357-376 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:378-398 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:400-420 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/AddressFormInput.kt:422-442 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 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) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:161— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:161-188 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:191-224 — 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 (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInService.kt:123— drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInService.kt:123-148 | drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInService.kt:150-174 | drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInService.kt:176-200 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:190— bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:190-206 | bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:208-222 | bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:224-238 — 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 (7 members, 15+ corresponding lines) · ×1
Edited copies of one member (7 members, 15+ corresponding lines) card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:439— card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:439-454 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:468-482 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:484-501 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:508-526 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:528-545 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:547-562 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/StoredCardView.kt:117-132 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) econtext/src/main/java/com/adyen/checkout/econtext/internal/ui/view/EContextView.kt:139— econtext/src/main/java/com/adyen/checkout/econtext/internal/ui/view/EContextView.kt:139-155 | econtext/src/main/java/com/adyen/checkout/econtext/internal/ui/view/EContextView.kt:183-199 | econtext/src/main/java/com/adyen/checkout/econtext/internal/ui/view/EContextView.kt:201-217 — 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 (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:214— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:214-232 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:124-141 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:321-339 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 19+ corresponding lines) · ×1
Edited copies of one member (4 members, 19+ corresponding lines) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:190— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:190-212 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:214-236 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:191-209 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/DefaultGiftCardDelegate.kt:117-139 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:82— await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:82-104 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/provider/QRCodeComponentProvider.kt:81-107 | redirect/src/main/java/com/adyen/checkout/redirect/old/internal/provider/RedirectComponentProvider.kt:79-101 | twint-action/src/main/java/com/adyen/checkout/twint/action/internal/provider/TwintActionComponentProvider.kt:80-100 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 14+ corresponding lines) · ×1
Edited copies of one member (8 members, 14+ corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/provider/Adyen3DS2ComponentProvider.kt:64— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/provider/Adyen3DS2ComponentProvider.kt:64-79 | action-core/src/main/java/com/adyen/checkout/action/core/internal/provider/GenericActionComponentProvider.kt:62-80 | await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:63-76 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/provider/QRCodeComponentProvider.kt:61-75 | redirect/src/main/java/com/adyen/checkout/redirect/old/internal/provider/RedirectComponentProvider.kt:59-73 | twint-action/src/main/java/com/adyen/checkout/twint/action/internal/provider/TwintActionComponentProvider.kt:59-74 | voucher/src/main/java/com/adyen/checkout/voucher/internal/provider/VoucherComponentProvider.kt:57-71 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/provider/WeChatPayActionComponentProvider.kt:59-74 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 12+ corresponding lines) · ×1
Edited copies of one member (7 members, 12+ corresponding lines) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Configuration.kt:143— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Configuration.kt:143-154 | await/src/main/java/com/adyen/checkout/await/old/AwaitConfiguration.kt:108-119 | qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeConfiguration.kt:108-119 | redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectConfiguration.kt:107-118 | twint-action/src/main/java/com/adyen/checkout/twint/action/TwintActionConfiguration.kt:106-117 | voucher/src/main/java/com/adyen/checkout/voucher/VoucherConfiguration.kt:108-119 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/WeChatPayActionConfiguration.kt:107-118 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:549— authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:549-566 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:569-586 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:588-605 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:607-624 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) blik/src/main/java/com/adyen/checkout/blik/internal/ui/state/BlikComponentStatePostProcessor.kt:23— blik/src/main/java/com/adyen/checkout/blik/internal/ui/state/BlikComponentStatePostProcessor.kt:23-31 | card/src/main/java/com/adyen/checkout/card/internal/ui/state/StoredCardComponentStatePostProcessor.kt:25-33 | mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStatePostProcessor.kt:23-31 — 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 (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/model/GiftCardComponentParamsMapper.kt:27— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/model/GiftCardComponentParamsMapper.kt:27-43 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/model/IssuerListComponentParamsMapper.kt:33-48 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/ui/model/MealVoucherFRComponentParamsMapper.kt:28-44 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 18+ corresponding lines) · ×1
Edited copies of one member (7 members, 18+ corresponding lines) ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt:124— ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt:124-142 | blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/DefaultBlikDelegate.kt:134-152 | blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/StoredBlikDelegate.kt:123-141 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/ui/DefaultMBWayDelegate.kt:138-156 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/StoredPayToDelegate.kt:140-158 | sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/DefaultSepaDelegate.kt:125-142 | upi/src/main/java/com/adyen/checkout/upi/internal/ui/DefaultUPIDelegate.kt:202-221 — These 7 members are one piece of code written 7 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 7 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) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:107— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:107-125 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/DefaultPayByBankUSDelegate.kt:105-122 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/StoredPayByBankUSDelegate.kt:115-133 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/DefaultPayByBankDelegate.kt:146-164 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/StoredTwintDelegate.kt:105-123 — 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, 13+ corresponding lines) · ×1
Edited copies of one member (6 members, 13+ corresponding lines) entercash/src/main/java/com/adyen/checkout/entercash/EntercashConfiguration.kt:96— entercash/src/main/java/com/adyen/checkout/entercash/EntercashConfiguration.kt:96-108 | eps/src/main/java/com/adyen/checkout/eps/EPSConfiguration.kt:107-119 | ideal/src/main/java/com/adyen/checkout/ideal/IdealConfiguration.kt:113-125 | molpay/src/main/java/com/adyen/checkout/molpay/MolpayConfiguration.kt:95-107 | online-banking-pl/src/main/java/com/adyen/checkout/onlinebankingpl/OnlineBankingPLConfiguration.kt:97-109 | openbanking/src/main/java/com/adyen/checkout/openbanking/OpenBankingConfiguration.kt:96-108 — These 6 members are one piece of code written 6 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 6 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) card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:184— card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:184-193 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:160-170 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:61-70 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/StoredTwintDelegate.kt:59-68 — 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, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) boleto/src/main/java/com/adyen/checkout/boleto/internal/util/BoletoValidationUtils.kt:18— boleto/src/main/java/com/adyen/checkout/boleto/internal/util/BoletoValidationUtils.kt:18-24 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/model/PayToOutputData.kt:126-133 | upi/src/main/java/com/adyen/checkout/upi/internal/ui/DefaultUPIDelegate.kt:174-178 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) redirect/src/main/java/com/adyen/checkout/redirect/old/internal/ui/DefaultRedirectDelegate.kt:213— redirect/src/main/java/com/adyen/checkout/redirect/old/internal/ui/DefaultRedirectDelegate.kt:213-220 | twint-action/src/main/java/com/adyen/checkout/twint/action/internal/ui/DefaultTwintActionDelegate.kt:226-233 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/ui/DefaultWeChatDelegate.kt:192-198 — 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, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) blik/src/main/java/com/adyen/checkout/blik/internal/ui/state/BlikComponentStatePostProcessor.kt:44— blik/src/main/java/com/adyen/checkout/blik/internal/ui/state/BlikComponentStatePostProcessor.kt:44-46 | card/src/main/java/com/adyen/checkout/card/internal/ui/state/StoredCardComponentStatePostProcessor.kt:46-48 | mbway/src/main/java/com/adyen/checkout/mbway/internal/ui/state/MBWayComponentStatePostProcessor.kt:44-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (41 lines × 2) core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:101— core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:101-141 | ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:91-131 — before extracting anything, compare `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:99` calls `Suppress` and `ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.kt:88` 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 (33–34 lines × 2) blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:311— blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:311-343 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:419-452 — 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 `blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:311` 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 (31–33 lines × 2) econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:205— econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:205-235 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:213-245 — before extracting anything, compare `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt` and `online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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 `econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:205` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (33 lines × 2) payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:310— payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:310-342 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:417-449 — 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 `payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:310` 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 (22–25 lines × 23) bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:198— bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:198-219 | bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:252-274 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:300-322 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:408-432 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:206-230 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:277-298 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:491-512 | econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:206-227 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:214-236 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:213-235 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:192-213 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:196-217 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:205-226 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:198-220 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:214-236 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:214-235 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:303-324 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:408-432 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:195-216 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:299-321 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:406-428 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:199-220 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:193-217 — before extracting anything, compare `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt` and `bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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 `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:197` calls `SubmitHandler` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:205` 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 (24 lines × 2) payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:127— payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:127-150 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:211-234 — 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 `payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:126` calls `SubmitHandler` and `payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:210` 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 (22–23 lines × 2) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:134— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:134-155 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:329-351 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:288— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:288-307 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:255-275 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt` and `authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 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 `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:288` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` 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 (19 lines × 3) cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:384— cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:384-402 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:285-303 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:371-389 — before extracting anything, compare `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt` and `twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 127 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 `cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:384` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–19 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:375— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:375-392 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:343-361 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt` and `authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 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 `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:375` 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. Note first that the copies are not typed on the same thing: `AdyenLogLevel` names `com.adyen.checkout.core.common.AdyenLogLevel` in one and `com.adyen.checkout.core.old.AdyenLogLevel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17–18 lines × 2) paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:102— paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:102-119 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:191-207 — 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 `paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:102` 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 (14–16 lines × 2) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:202— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:202-215 | authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt:138-153 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt` and `authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 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 `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:202` 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. Note first that the copies are not typed on the same thing: `ErrorEvent` names `com.adyen.checkout.components.core.internal.analytics.ErrorEvent` in one and `com.adyen.checkout.core.analytics.internal.ErrorEvent` 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 (12 lines × 7) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:197— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:197-208 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:393-404 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:181-192 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:171-182 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:173-184 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:265-276 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:352-363 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:197` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 5) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:314— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:314-325 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:87-98 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:88-99 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:110-121 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:188-199 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:314` 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 (10 lines × 23) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:201— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:201-210 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:397-406 | bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:180-189 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:282-291 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:390-399 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:185-194 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:278-287 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:369-378 | econtext/src/main/java/com/adyen/checkout/econtext/internal/provider/EContextComponentProvider.kt:186-195 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:190-201 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:179-188 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/provider/IssuerListComponentProvider.kt:189-198 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:180-189 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/provider/OnlineBankingComponentProvider.kt:192-201 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:285-294 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:391-400 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:177-186 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:281-290 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:389-398 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:181-190 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:269-278 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:356-365 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:175-184 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:201` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:179` calls `getBacsDirectDebitConfiguration` and `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:200` 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 (9–10 lines × 2) boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:199— boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:199-208 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.kt:259-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. Read the line range as the matched WINDOW rather than a finished unit: at `boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:199` 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 (8 lines × 10) bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:171— bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:171-178 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:273-280 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:381-388 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:171-178 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:276-283 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:382-389 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:272-279 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:380-387 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:172-179 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:166-173 — before extracting anything, compare `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt` and `blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 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 `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:171` 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 (34 lines × 3) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52-85 | qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt:52-85 | redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54-113 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 240 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 `redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54` 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 (24 lines × 4) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52-85 | await/src/main/java/com/adyen/checkout/await/old/AwaitComponent.kt:49-72 | qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt:52-85 | redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54-113 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 240 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 `redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54` 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 (45 lines × 2) card/src/main/java/com/adyen/checkout/card/internal/analytics/CardScannerEvents.kt:19— card/src/main/java/com/adyen/checkout/card/internal/analytics/CardScannerEvents.kt:19-63 | card/src/main/java/com/adyen/checkout/card/old/internal/analytics/CardEvents.kt:19-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `card/src/main/java/com/adyen/checkout/card/internal/analytics/CardScannerEvents.kt:19` 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: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` 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 (29 lines × 2) checkout-core/src/main/java/com/adyen/checkout/core/old/DispatcherProvider.kt:29— checkout-core/src/main/java/com/adyen/checkout/core/old/DispatcherProvider.kt:29-57 | core/src/main/java/com/adyen/checkout/core/common/internal/api/DispatcherProvider.kt:29-57 — before extracting anything, compare `checkout-core/src/main/java/com/adyen/checkout/core/old/DispatcherProvider.kt` and `core/src/main/java/com/adyen/checkout/core/common/internal/api/DispatcherProvider.kt` as WHOLE FILES: 91% 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.
Duplicated block (122 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/GenericEvents.kt:24— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/GenericEvents.kt:24-145 | core/src/main/java/com/adyen/checkout/core/analytics/internal/GenericEvents.kt:24-154 — before extracting anything, compare `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/GenericEvents.kt` and `core/src/main/java/com/adyen/checkout/core/analytics/internal/GenericEvents.kt` as WHOLE FILES: 95% 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 `components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/GenericEvents.kt:24` 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 × 6) components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/local/ErrorAnalyticsLocalDataStore.kt:22— components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/local/ErrorAnalyticsLocalDataStore.kt:22-36 | components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/local/InfoAnalyticsLocalDataStore.kt:22-36 | components-core/src/main/java/com/adyen/checkout/components/core/internal/analytics/data/local/LogAnalyticsLocalDataStore.kt:22-36 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/local/ErrorAnalyticsLocalDataStore.kt:22-36 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/local/InfoAnalyticsLocalDataStore.kt:22-36 | core/src/main/java/com/adyen/checkout/core/analytics/internal/data/local/LogAnalyticsLocalDataStore.kt:22-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Note first that the copies are not typed on the same thing: `AnalyticsEvent` names `com.adyen.checkout.components.core.internal.analytics.AnalyticsEvent` in one and `com.adyen.checkout.core.analytics.internal.AnalyticsEvent` 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 (159 lines × 2) components-core/src/main/java/com/adyen/checkout/components/core/internal/provider/PaymentComponentProvider.kt:58— components-core/src/main/java/com/adyen/checkout/components/core/internal/provider/PaymentComponentProvider.kt:58-216 | components-core/src/main/java/com/adyen/checkout/components/core/internal/provider/StoredPaymentComponentProvider.kt:57-215 — 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 `components-core/src/main/java/com/adyen/checkout/components/core/internal/provider/PaymentComponentProvider.kt:58` 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 (20 lines × 7) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52-85 | await/src/main/java/com/adyen/checkout/await/old/AwaitComponent.kt:49-72 | qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt:52-85 | redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54-113 | twint-action/src/main/java/com/adyen/checkout/twint/action/TwintActionComponent.kt:47-66 | voucher/src/main/java/com/adyen/checkout/voucher/VoucherComponent.kt:48-67 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/WeChatPayActionComponent.kt:50-79 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 240 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 `redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `twint-action/src/main/java/com/adyen/checkout/twint/action/TwintActionComponent.kt:71` calls `TwintActionComponentProvider` and `redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:114` 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 (30 lines × 4) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt:52-85 | qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt:52-85 | redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54-113 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/WeChatPayActionComponent.kt:50-79 — before extracting anything, compare `3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Component.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeComponent.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 240 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 `redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectComponent.kt:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 7) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Configuration.kt:160— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Configuration.kt:160-170 | await/src/main/java/com/adyen/checkout/await/old/AwaitConfiguration.kt:126-136 | qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeConfiguration.kt:126-136 | redirect/src/main/java/com/adyen/checkout/redirect/old/RedirectConfiguration.kt:124-134 | twint-action/src/main/java/com/adyen/checkout/twint/action/TwintActionConfiguration.kt:123-133 | voucher/src/main/java/com/adyen/checkout/voucher/VoucherConfiguration.kt:125-135 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/WeChatPayActionConfiguration.kt:124-134 — before extracting anything, compare `await/src/main/java/com/adyen/checkout/await/old/AwaitConfiguration.kt` and `qr-code/src/main/java/com/adyen/checkout/qrcode/QRCodeConfiguration.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. 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 × 8) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/provider/Adyen3DS2ComponentProvider.kt:122— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/provider/Adyen3DS2ComponentProvider.kt:122-132 | action-core/src/main/java/com/adyen/checkout/action/core/internal/provider/GenericActionComponentProvider.kt:112-122 | await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:114-124 | qr-code/src/main/java/com/adyen/checkout/qrcode/internal/provider/QRCodeComponentProvider.kt:117-127 | redirect/src/main/java/com/adyen/checkout/redirect/old/internal/provider/RedirectComponentProvider.kt:111-121 | twint-action/src/main/java/com/adyen/checkout/twint/action/internal/provider/TwintActionComponentProvider.kt:110-120 | voucher/src/main/java/com/adyen/checkout/voucher/internal/provider/VoucherComponentProvider.kt:103-113 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/provider/WeChatPayActionComponentProvider.kt:110-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/provider/Adyen3DS2ComponentProvider.kt:122` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `twint-action/src/main/java/com/adyen/checkout/twint/action/internal/provider/TwintActionComponentProvider.kt:122` calls `listOf` and `await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:126` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 4) 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:113— 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:113-122 | redirect/src/main/java/com/adyen/checkout/redirect/old/internal/ui/DefaultRedirectDelegate.kt:90-99 | twint-action/src/main/java/com/adyen/checkout/twint/action/internal/ui/DefaultTwintActionDelegate.kt:97-106 | wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/ui/DefaultWeChatDelegate.kt:84-93 — 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 `3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:113` 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 × 24) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:167— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:167-179 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:363-375 | bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:145-157 | bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:179-191 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:162-174 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:247-259 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:151-163 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:163-175 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:242-254 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:156-168 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:156-168 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:141-153 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:144-156 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:145-157 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:156-168 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:166-178 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:250-262 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:143-155 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:162-174 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:246-258 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:146-158 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:159-171 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:236-248 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:140-152 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:167` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:181` calls `Suppress` and `blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:176` 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 (13 lines × 25) ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:258— ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:258-270 | ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:451-463 | bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:252-264 | bcmc/src/main/java/com/adyen/checkout/bcmc/internal/provider/BcmcComponentProvider.kt:309-321 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:355-367 | blik/src/main/java/com/adyen/checkout/blik/old/internal/provider/BlikComponentProvider.kt:464-476 | boleto/src/main/java/com/adyen/checkout/boleto/internal/provider/BoletoComponentProvider.kt:262-274 | card/src/main/java/com/adyen/checkout/card/old/internal/provider/CardComponentProvider.kt:543-555 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:333-345 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/provider/CashAppPayComponentProvider.kt:422-434 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/provider/GiftCardComponentProvider.kt:273-285 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/provider/GooglePayComponentProvider.kt:268-280 | ideal/src/main/java/com/adyen/checkout/ideal/internal/provider/IdealComponentProvider.kt:245-257 | instant/src/main/java/com/adyen/checkout/instant/internal/provider/InstantPaymentComponentProvider.kt:249-261 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/provider/MBWayComponentProvider.kt:253-265 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:273-285 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:356-368 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/provider/PayByBankUSComponentProvider.kt:464-476 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/provider/PayByBankComponentProvider.kt:248-260 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:354-366 | payto/src/main/java/com/adyen/checkout/payto/internal/provider/PayToComponentProvider.kt:461-473 | sepa/src/main/java/com/adyen/checkout/sepa/internal/provider/SepaComponentProvider.kt:252-264 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:323-335 | twint/src/main/java/com/adyen/checkout/twint/internal/provider/TwintComponentProvider.kt:409-421 | upi/src/main/java/com/adyen/checkout/upi/internal/provider/UPIComponentProvider.kt:249-261 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt` and `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt:258` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/provider/MealVoucherFRComponentProvider.kt:287` calls `Suppress` and `bacs/src/main/java/com/adyen/checkout/bacs/internal/provider/BacsDirectDebitComponentProvider.kt:266` 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 (7 lines × 17) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:125— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:125-131 | bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/DefaultBacsDirectDebitDelegate.kt:71-77 | blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/DefaultBlikDelegate.kt:77-83 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:106-112 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/DefaultCashAppPayDelegate.kt:116-122 | econtext/src/main/java/com/adyen/checkout/econtext/internal/ui/DefaultEContextDelegate.kt:86-92 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/DefaultGiftCardDelegate.kt:109-115 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/ui/DefaultGooglePayDelegate.kt:99-105 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/DefaultIssuerListDelegate.kt:81-87 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/ui/DefaultMBWayDelegate.kt:78-84 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/ui/DefaultOnlineBankingDelegate.kt:99-105 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/DefaultPayByBankUSDelegate.kt:72-78 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/DefaultPayByBankDelegate.kt:83-89 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/DefaultPayToDelegate.kt:79-85 | sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/DefaultSepaDelegate.kt:70-76 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/DefaultTwintDelegate.kt:70-76 | upi/src/main/java/com/adyen/checkout/upi/internal/ui/DefaultUPIDelegate.kt:81-87 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt` and `boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/DefaultGiftCardDelegate.kt:106` calls `fetchPublicKey` and `bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/DefaultBacsDirectDebitDelegate.kt:68` 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 (10 lines × 8) ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:346— ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:346-355 | ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt:170-179 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt:199-208 | card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.kt:176-185 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/DefaultCashAppPayDelegate.kt:128-137 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/ui/DefaultGiftCardDelegate.kt:145-154 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/ui/DefaultGooglePayDelegate.kt:125-134 | online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/ui/DefaultOnlineBankingDelegate.kt:111-120 — before extracting anything, compare `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt` and `card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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 `ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:346` 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 `callback` to `(PaymentComponentEvent<ACHDirectDebitComponentState>) -> Unit` in one and `(PaymentComponentEvent<CardComponentState>) -> Unit` 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 × 3) ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt:108— ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt:108-115 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/StoredPayByBankUSDelegate.kt:78-85 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/StoredPayToDelegate.kt:81-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 19) bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/DefaultBacsDirectDebitDelegate.kt:83— bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/DefaultBacsDirectDebitDelegate.kt:83-92 | blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/DefaultBlikDelegate.kt:89-98 | blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/StoredBlikDelegate.kt:85-94 | boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt:281-290 | cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/StoredCashAppPayDelegate.kt:85-94 | econtext/src/main/java/com/adyen/checkout/econtext/internal/ui/DefaultEContextDelegate.kt:186-195 | ideal/src/main/java/com/adyen/checkout/ideal/internal/ui/DefaultIdealDelegate.kt:73-82 | instant/src/main/java/com/adyen/checkout/instant/internal/ui/DefaultInstantPaymentDelegate.kt:103-112 | issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/DefaultIssuerListDelegate.kt:93-102 | mbway/src/main/java/com/adyen/checkout/mbway/old/internal/ui/DefaultMBWayDelegate.kt:90-99 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/DefaultPayByBankUSDelegate.kt:84-93 | paybybank-us/src/main/java/com/adyen/checkout/paybybankus/internal/StoredPayByBankUSDelegate.kt:95-104 | paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/DefaultPayByBankDelegate.kt:95-104 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/DefaultPayToDelegate.kt:91-100 | payto/src/main/java/com/adyen/checkout/payto/internal/ui/StoredPayToDelegate.kt:98-107 | sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/DefaultSepaDelegate.kt:82-91 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/DefaultTwintDelegate.kt:82-91 | twint/src/main/java/com/adyen/checkout/twint/internal/ui/StoredTwintDelegate.kt:83-92 | upi/src/main/java/com/adyen/checkout/upi/internal/ui/DefaultUPIDelegate.kt:93-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 19 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 19 times. Read the line range as the matched WINDOW rather than a finished unit: at `bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/DefaultBacsDirectDebitDelegate.kt:83` 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 `callback` to `(PaymentComponentEvent<BacsDirectDebitComponentState>) -> Unit` in one and `(PaymentComponentEvent<BlikComponentState>) -> Unit` 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 (17 lines × 5) boleto/src/main/java/com/adyen/checkout/boleto/BoletoConfiguration.kt:166— boleto/src/main/java/com/adyen/checkout/boleto/BoletoConfiguration.kt:166-182 | googlepay/src/main/java/com/adyen/checkout/googlepay/old/GooglePayConfiguration.kt:491-507 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/MealVoucherFRConfiguration.kt:171-187 | molpay/src/main/java/com/adyen/checkout/molpay/MolpayConfiguration.kt:140-156 | upi/src/main/java/com/adyen/checkout/upi/UPIConfiguration.kt:153-169 — before extracting anything, compare `meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/MealVoucherFRConfiguration.kt` and `upi/src/main/java/com/adyen/checkout/upi/UPIConfiguration.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.
Duplicated block (11 lines × 4) giftcard/src/main/java/com/adyen/checkout/giftcard/internal/util/GiftCardValidationUtils.kt:17— giftcard/src/main/java/com/adyen/checkout/giftcard/internal/util/GiftCardValidationUtils.kt:17-27 | giftcard/src/main/java/com/adyen/checkout/giftcard/internal/util/GiftCardValidationUtils.kt:29-39 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/util/MealVoucherFRValidationUtils.kt:23-33 | meal-voucher-fr/src/main/java/com/adyen/checkout/mealvoucherfr/internal/util/MealVoucherFRValidationUtils.kt:35-45 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: `R` names `com.adyen.checkout.giftcard.R` in one and `com.adyen.checkout.mealvoucherfr.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.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) scripts/drop_all_open_ossrh_repositories.py:41— scripts/drop_all_open_ossrh_repositories.py:41-88 | scripts/move_ossrh_repository_to_central_portal.py:50-101 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:80— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:80-106 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:48-73 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt:43-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (22 lines × 2) example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:91— example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:91-112 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt:80-101 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverActivity.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardActivity.kt:91` 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 × 6) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:74— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:74-86 | example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.kt:65-77 | example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:60-72 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:72-84 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayViewModel.kt:71-83 | example-app/src/main/java/com/adyen/checkout/example/ui/instant/InstantViewModel.kt:59-71 — 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.
Duplicated block (9–11 lines × 3) example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:93— example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:93-101 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt:60-70 | example-app/src/main/java/com/adyen/checkout/example/service/ExampleSessionsDropInService.kt:57-67 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt` and `example-app/src/main/java/com/adyen/checkout/example/service/ExampleDropInService.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/service/ExampleAdvancedDropInService.kt:93` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 6) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:146— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:146-154 | example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:129-137 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:178-186 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:216-224 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayViewModel.kt:168-176 | example-app/src/main/java/com/adyen/checkout/example/ui/instant/InstantViewModel.kt:123-131 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:146` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:124` calls `onStateChanged` and `example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:211` 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 (9 lines × 4) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:113— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:113-121 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:100-108 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardViewModel.kt:89-97 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/compose/SessionsGooglePayViewModel.kt:95-103 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 6) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:114— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:114-121 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:101-108 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardViewModel.kt:90-97 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/compose/SessionsGooglePayViewModel.kt:96-103 | example-app/src/main/java/com/adyen/checkout/example/ui/main/MainViewModel.kt:241-248 | example-app/src/main/java/com/adyen/checkout/example/ui/v6/V6SessionsViewModel.kt:74-81 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:123— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:123-130 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:110-117 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/SessionsGiftCardViewModel.kt:99-106 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/compose/SessionsGooglePayViewModel.kt:105-112 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 7) example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:118— example-app/src/main/java/com/adyen/checkout/example/ui/bacs/BacsViewModel.kt:118-123 | example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.kt:141-146 | example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt:165-170 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:214-219 | example-app/src/main/java/com/adyen/checkout/example/ui/giftcard/GiftCardViewModel.kt:283-288 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/GooglePayViewModel.kt:140-145 | example-app/src/main/java/com/adyen/checkout/example/ui/instant/InstantViewModel.kt:156-161 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/CardViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:138— example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:138-143 | example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt:125-130 | example-app/src/main/java/com/adyen/checkout/example/ui/googlepay/compose/SessionsGooglePayViewModel.kt:120-125 — before extracting anything, compare `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt` and `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `example-app/src/main/java/com/adyen/checkout/example/ui/card/SessionsCardTakenOverViewModel.kt:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) scripts/generate_release_notes.py:126— scripts/generate_release_notes.py:126-133 | scripts/validate_dependencies_for_release_notes.py:46-55 — 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 `scripts/validate_dependencies_for_release_notes.py:46` 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.
P3 · Security & performance tooling· SAST runs, but gates no merge · ×1
SAST runs, but gates no merge — `codeql.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked package.json:2— package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X2 · Cancellation propagation· Suspend function with a blocking request · ×1
Suspend function with a blocking request: load checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/ImageLoader.kt:42— `load` suspends, but makes its request with `call.execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Orphaned file ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.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 sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.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 boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.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 drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodsListViewModel.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 ach/src/main/java/com/adyen/checkout/ach/ACHDirectDebitConfiguration.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 ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.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 card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/StoredCardView.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 qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.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 components-core/src/main/java/com/adyen/checkout/components/core/PaymentComponentData.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 example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikViewModel.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 components-core/src/main/java/com/adyen/checkout/components/core/action/VoucherAction.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 checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.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 components-core/src/main/java/com/adyen/checkout/components/core/paymentmethod/CardPaymentMethod.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 boleto/src/main/java/com/adyen/checkout/boleto/BoletoComponent.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 components-core/src/main/java/com/adyen/checkout/components/core/StoredPaymentMethod.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 online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/ui/OnlineBankingView.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 example-app/src/main/java/com/adyen/checkout/example/ui/blik/BlikActivity.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 ach/src/main/java/com/adyen/checkout/ach/ACHDirectDebitComponent.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 components-core/src/main/java/com/adyen/checkout/components/core/PaymentMethod.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 components-core/src/main/java/com/adyen/checkout/components/core/CheckoutCurrency.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 components-core/src/main/java/com/adyen/checkout/components/core/action/SdkAction.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 ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/ui/view/RoundCornerImageView.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 sessions-core/src/main/java/com/adyen/checkout/sessions/core/SessionSetupConfiguration.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 components-core/src/main/java/com/adyen/checkout/components/core/paymentmethod/ACHDirectDebitPaymentMethod.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 components-core/src/main/java/com/adyen/checkout/components/core/action/Action.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.
Duplicated predicate issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/IssuersUtils.kt:18— `!isDisabled && id != null && name != null` appears character-identically in 3 files — issuer-list/src/main/java/com/adyen/checkout/issuerlist/internal/ui/IssuersUtils.kt, online-banking-core/src/main/java/com/adyen/checkout/onlinebankingcore/internal/util/IssuersExt.kt, paybybank/src/main/java/com/adyen/checkout/paybybank/internal/ui/DefaultPayByBankDelegate.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 ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:279— `!outputData.isValid || publicKey == null` appears character-identically in 3 files — ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/DefaultCardDelegate.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/StoredCardDelegate.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 checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/InMemoryCache.kt:36— `Build.VERSION.SDK_INT >= Build.VERSION_CODES.O && bitmap.config == Bitmap.Config.RGBA_F16` appears character-identically in 2 files — checkout-core/src/main/java/com/adyen/checkout/core/old/internal/ui/InMemoryCache.kt, core/src/main/java/com/adyen/checkout/core/internal/image/InMemoryCache.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 await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:210— `StatusResponseUtils.isFinalResult(statusResponse) && !payload.isNullOrEmpty()` appears character-identically in 2 files — await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt, qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.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 cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/DefaultCashAppPayDelegate.kt:329— `_viewFlow.value is ButtonComponentViewType && componentParams.showStorePaymentField` appears character-identically in 2 files — cashapppay/src/main/java/com/adyen/checkout/cashapppay/internal/ui/DefaultCashAppPayDelegate.kt, twint/src/main/java/com/adyen/checkout/twint/internal/ui/DefaultTwintDelegate.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 boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:211— `binding.addressFormInput.isVisible && !it.addressState.isValid` appears character-identically in 2 files — boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.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 boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:186— `binding.textInputLayoutFirstName.isVisible && firstNameValidation is Validation.Invalid` appears character-identically in 2 files — boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt, payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.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 boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:192— `binding.textInputLayoutLastName.isVisible && lastNameValidation is Validation.Invalid` appears character-identically in 2 files — boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt, payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.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 boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt:200— `binding.textInputLayoutSocialSecurityNumber.isVisible && socialSecurityNumberValidation is Validation.Invalid` appears character-identically in 2 files — boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/view/BoletoView.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.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 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt:341— `directoryServerId == null || directoryServerPublicKey == null || directoryServerRootCertificates == null` appears character-identically in 2 files — 3ds2/src/main/java/com/adyen/checkout/threeds2/old/internal/ui/DefaultAdyen3DS2Delegate.kt, authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.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 checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt:47— `enableLuhnCheck && !isLuhnChecksumValid(normalizedNumber)` appears character-identically in 2 files — checkout-core/src/main/java/com/adyen/checkout/core/old/ui/validation/CardNumberValidator.kt, core/src/main/java/com/adyen/checkout/core/common/helper/CardNumberValidator.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 googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt:160— `infoJson != null && !infoJson.isNull(CARD_NETWORK)` appears character-identically in 2 files — googlepay/src/main/java/com/adyen/checkout/googlepay/internal/helper/GooglePayUtils.kt, googlepay/src/main/java/com/adyen/checkout/googlepay/old/internal/util/GooglePayUtils.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 ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt:385— `isConfirmationRequired() && componentParams.isSubmitButtonVisible` appears character-identically in 19 files — ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt, bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/DefaultBacsDirectDebitDelegate.kt, blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/DefaultBlikDelegate.kt, blik/src/main/java/com/adyen/checkout/blik/old/internal/ui/StoredBlikDelegate.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 core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt:75— `launchNative(context, uri) || launchWithCustomTabs(context, uri) || launchBrowser(context, uri)` appears character-identically in 2 files — core/src/main/java/com/adyen/checkout/core/redirect/internal/DefaultRedirectHandler.kt, ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/DefaultRedirectHandler.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 checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.kt:98— `modelList == null || modelList.isEmpty()` appears character-identically in 2 files — checkout-core/src/main/java/com/adyen/checkout/core/old/internal/data/model/ModelUtils.kt, core/src/main/java/com/adyen/checkout/core/common/internal/model/ModelUtils.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 drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInResultContract.kt:40— `resultCode == Activity.RESULT_CANCELED && data.hasExtra(DropIn.ERROR_REASON_KEY)` appears character-identically in 2 files — drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInResultContract.kt, drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInResultContract.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 drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInResultContract.kt:48— `resultCode == Activity.RESULT_OK && data.hasExtra(DropIn.RESULT_KEY)` appears character-identically in 2 files — drop-in/src/main/java/com/adyen/checkout/dropin/old/DropInResultContract.kt, drop-in/src/main/java/com/adyen/checkout/dropin/old/SessionDropInResultContract.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 bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt:293— `rootView.findFocus() === view && view != null` appears character-identically in 2 files — bacs/src/main/java/com/adyen/checkout/bacs/internal/ui/view/BacsDirectDebitInputView.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardView.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 await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt:197— `statusResponse != null && StatusResponseUtils.isFinalResult(statusResponse)` appears character-identically in 2 files — await/src/main/java/com/adyen/checkout/await/old/internal/ui/DefaultAwaitDelegate.kt, qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/DefaultQRCodeDelegate.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 await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt:127— `supportedActionTypes.contains(action.type) && PAYMENT_METHODS.contains(action.paymentMethodType)` appears character-identically in 4 files — await/src/main/java/com/adyen/checkout/await/old/internal/provider/AwaitComponentProvider.kt, twint-action/src/main/java/com/adyen/checkout/twint/action/internal/provider/TwintActionComponentProvider.kt, voucher/src/main/java/com/adyen/checkout/voucher/internal/provider/VoucherComponentProvider.kt, wechatpay/src/main/java/com/adyen/checkout/wechatpay/internal/provider/WeChatPayActionComponentProvider.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 checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt:31— `tag.length <= MAX_TAG_LENGTH || Build.VERSION.SDK_INT >= Build.VERSION_CODES.O` appears character-identically in 2 files — checkout-core/src/main/java/com/adyen/checkout/core/old/internal/util/LogcatLogger.kt, core/src/main/java/com/adyen/checkout/core/common/internal/helper/LogcatLogger.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 scripts/generate_release_notes.py:133— `id not in dependency_list['excluded'] and id not in dependency_list['included']` appears character-identically in 2 files — scripts/generate_release_notes.py, scripts/validate_dependencies_for_release_notes.py. 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.
D8 · Code Coverage· Tests reach code only in some runs · ×7
Tests reach code only in some runs: build-logic/convention/src/main/kotlin/com/adyen/checkout/ProjectExtensions.kt build-logic/convention/src/main/kotlin/com/adyen/checkout/ProjectExtensions.kt:16— 1 line(s) (16) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: lint/src/main/java/com/adyen/checkout/lint/ContextGetString.kt lint/src/main/java/com/adyen/checkout/lint/ContextGetString.kt:22— 29 line(s) (22-24, 27-32, 35, 37-39, 42, 44, 46, 48-49, 51-59, 63, 66) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: lint/src/main/java/com/adyen/checkout/lint/JSONOptFunctions.kt lint/src/main/java/com/adyen/checkout/lint/JSONOptFunctions.kt:21— 37 line(s) (21-23, 28-33, 36, 38-40, 43-50, 53-59, 62-69, 72) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: lint/src/main/java/com/adyen/checkout/lint/NotAdyenLog.kt lint/src/main/java/com/adyen/checkout/lint/NotAdyenLog.kt:21— 19 line(s) (21-28, 31, 33-35, 38-43, 46) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: lint/src/main/java/com/adyen/checkout/lint/NotDispatcherProvider.kt lint/src/main/java/com/adyen/checkout/lint/NotDispatcherProvider.kt:23— 27 line(s) (23-30, 33, 35-37, 40-53, 57) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: lint/src/main/java/com/adyen/checkout/lint/ObjectInPublicSealedClass.kt lint/src/main/java/com/adyen/checkout/lint/ObjectInPublicSealedClass.kt:23— 36 line(s) (23-25, 29-33, 36, 38-40, 42, 44, 46, 48, 50-61, 65, 68, 72, 76-77, 79, 83, 85) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: lint/src/main/java/com/adyen/checkout/lint/TextInLayoutXml.kt lint/src/main/java/com/adyen/checkout/lint/TextInLayoutXml.kt:21— 22 line(s) (21-23, 26-31, 34, 36-39, 42, 44-48, 50, 53) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×5
Projects may be oversized for their cohesion core/build.gradle:1— `core` (14812 LoC, 817 module-visible types across 48 directories) overshoots its size bounds. 5 of 58 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.4/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 components-core/build.gradle:1— `components-core` (9507 LoC, 494 module-visible types across 14 directories) overshoots its size bounds. 5 of 58 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.4/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 card/build.gradle:1— `card` (12474 LoC, 412 module-visible types across 21 directories) overshoots its size bounds. 5 of 58 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.4/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 drop-in/build.gradle:1— `drop-in` (11585 LoC, 299 module-visible types across 17 directories) overshoots its size bounds. 5 of 58 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.4/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 googlepay/build.gradle:1— `googlepay` (4956 LoC, 137 module-visible types across 14 directories) overshoots its size bounds. 5 of 58 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.4/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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 20 significant file(s) lose their only recent owner: authentication/src/main/java/com/adyen/checkout/authentication/internal/ui/AuthenticationComponent.kt, drop-in/src/main/java/com/adyen/checkout/dropin/internal/manage/StoredPaymentMethodManagementScreen.kt, drop-in/src/main/java/com/adyen/checkout/dropin/internal/ui/DropInViewModel.kt, twint/src/main/java/com/adyen/checkout/twint/internal/ui/DefaultTwintDelegate.kt, qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/SimpleQRCodeView.kt, build-logic/convention/src/main/kotlin/ResolveDependenciesPlugin.kt, drop-in/src/main/java/com/adyen/checkout/dropin/internal/manage/StoredPaymentMethodManagementViewModel.kt, drop-in/src/main/java/com/adyen/checkout/dropin/internal/data/PaymentMethodRepository.kt (+12 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 17 significant file(s) lose their only recent owner: payto/src/main/java/com/adyen/checkout/payto/internal/ui/view/PayToView.kt, drop-in-compose/src/main/java/com/adyen/checkout/dropin/compose/ComposeExtensions.kt, payto/src/main/java/com/adyen/checkout/payto/internal/ui/DefaultPayToDelegate.kt, ui-core/src/main/java/com/adyen/checkout/ui/core/old/internal/util/ImageSaver.kt, address/src/main/java/com/adyen/checkout/address/internal/ui/state/AddressComponentStateReducer.kt, address/src/main/java/com/adyen/checkout/address/internal/ui/state/AddressComponentState.kt, payto/src/main/java/com/adyen/checkout/payto/internal/ui/model/PayToOutputData.kt, core/src/main/java/com/adyen/checkout/core/components/internal/data/api/StatusRepository.kt (+9 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 6 significant file(s) lose their only recent owner: example-app/src/main/java/com/adyen/checkout/example/ui/settings/composable/SettingsScreen.kt, card/src/main/java/com/adyen/checkout/card/internal/ui/view/CardBrands.kt, example-app/src/main/java/com/adyen/checkout/example/ui/card/compose/SessionsCardScreen.kt, card/src/main/java/com/adyen/checkout/card/internal/ui/state/CardComponentStatePostProcessor.kt, card-scanning/src/main/java/com/adyen/checkout/card/scanning/internal/CardScannerInitializer.kt, core/src/main/java/com/adyen/checkout/core/common/internal/ui/ScreenHeader.kt. Pair on, review, or document these before any departure.
Fat interface: Protocol (18 abstract methods) drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/DropInBottomSheetDialogFragment.kt:97— `Protocol` declares 18 abstract methods: `showPreselectedDialog`, `showPaymentMethodsDialog`, `showStoredComponentDialog`, `showComponentDialog`, `requestPaymentsCall`, `requestDetailsCall`, `showError`, `terminateDropIn`, `requestBalanceCall`, `requestPartialPayment`, `requestOrderCancellation`, `finishWithAction`, `removeStoredPaymentMethod`, `onRedirect`, `onBinValue`, `onBinLookup`, `onAddressLookupQuery`, `onAddressLookupCompletion`. 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: KeyValueStorage (34 abstract methods) example-app/src/main/java/com/adyen/checkout/example/data/storage/KeyValueStorage.kt:33— `KeyValueStorage` declares 34 abstract methods: `getShopperReference`, `setShopperReference`, `getOldAmount`, `getAmount`, `setAmount`, `setCurrency`, `getCountry`, `setCountry`, `getShopperLocale`, `setShopperLocale`, `getThreeDSMode`, `setThreeDSMode`, `getShopperEmail`, `setShopperEmail`, `getMerchantAccount`, `setMerchantAccount`, `isSplitCardFundingSources`, `setSplitCardFundingSources`, `getCardAddressMode`, `setCardAddressMode`, `isRemoveStoredPaymentMethodEnabled`, `setRemoveStoredPaymentMethodEnabled`, `getInstantPaymentMethodType`, `setInstantPaymentMethodType`, `getInstallmentOptionsMode`, `setInstallmentOptionsMode`, `isInstallmentAmountShown`, `setInstallmentAmountShown`, `getIntegrationFlow`, `setIntegrationFlow`, `getAnalyticsMode`, `setAnalyticsMode`, `getOnBeforeSubmitMode`, `setOnBeforeSubmitMode`. 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.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 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 (47 single-owned of 639 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; 639 of the 1819 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (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: card/src/main/java/com/adyen/checkout/card/internal/ui/model/InstallmentsParamsMapper.kt, card/src/main/java/com/adyen/checkout/card/InstallmentConfiguration.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/CardBrandAdapter.kt, example-app/src/main/java/com/adyen/checkout/example/data/storage/ExternalConfigurationReader.kt.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 37 of 639 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 639 of the 1819 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: ach/src/main/java/com/adyen/checkout/ach/internal/ui/DefaultACHDirectDebitDelegate.kt, sepa/src/main/java/com/adyen/checkout/sepa/internal/ui/model/Iban.kt, boleto/src/main/java/com/adyen/checkout/boleto/internal/ui/DefaultBoletoDelegate.kt, drop-in/src/main/java/com/adyen/checkout/dropin/old/internal/ui/PaymentMethodsListViewModel.kt, ach/src/main/java/com/adyen/checkout/ach/ACHDirectDebitConfiguration.kt, ach/src/main/java/com/adyen/checkout/ach/internal/ui/StoredACHDirectDebitDelegate.kt, card/src/main/java/com/adyen/checkout/card/old/internal/ui/view/StoredCardView.kt, qr-code/src/main/java/com/adyen/checkout/qrcode/internal/ui/view/FullQRCodeView.kt (and 29 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
M2 · Architecture documentation· Architecture diagram out of date · ×1
Architecture diagram out of date dependency-graph/project.dot:1— `dependency-graph/project.dot` draws the system's parts, and the drawing no longer matches the code: it leaves out `3ds2`, `address`, `authentication`, `card-scanning`, `core`, `lint`, `meal-voucher-fr`, `paybybank-us`, `payto`, `twint`, `twint-action`, `ui`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
X2 · Cancellation propagation· Not all suspend functions that make a request accept the coroutine's cancellation · ×1
Not all suspend functions that make a request accept the coroutine's cancellation — Only 1/2 suspend functions that make a cancellable request (Ktor, OkHttp newCall, URL streams) accept the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a screen navigated away from, a disposed widget, a superseded search. In a suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 86 file(s) — `3ds2/src/main/java/com/adyen/checkout/threeds2/old/Adyen3DS2Configuration.kt`, `ach/src/main/java/com/adyen/checkout/ach/ACHDirectDebitConfiguration.kt`, `ach/src/main/java/com/adyen/checkout/ach/internal/provider/ACHDirectDebitComponentProvider.kt`, `action-core/src/main/java/com/adyen/checkout/action/core/GenericActionComponent.kt`, `await/src/main/java/com/adyen/checkout/await/old/AwaitConfiguration.kt`, … (+81 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1ea0b-2a07-716e-8990-e68c4ca773c5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 41 · Warnings: 603 · Recommendations: 85 · Info: 149 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 15:06 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.