Public report of CleverTap/clevertap-android-sdk, 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, 13:58 UTC · Survey ID cd_b9f427aa447b41e2adcc083350c0aaf4
CleverTap/clevertap-android-sdk
Measured 17 November 2026, 13:57 UTC, at code version 1163e2c
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 79,497 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Security and Compliance, 56.9
Findings by how serious they are
49 critical460 serious120 minor
17 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, 13:57 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
49of 49 dimensions measured by tools.
618of 629 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
49dimensions across 6 lenses, read from 79,497 lines of product code in 7 projects.
CleverTap/clevertap-android-sdk falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 63.8 out of 100 and is rated Adequate, and 42 of its 49 critical findings are security problems in the build pipeline.
Security and Compliance, at 56.9, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 2.6 points. Adding automated security scanning comes next, worth about 4.8 points. Raising Security and Compliance to 70 would lift the score to about 67.7.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. The three parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 79,497 lines, about €220,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 56.9 to 70, the lowest score rated Strong, the score would rise from 63.8 to about 67.7.
Code composition: what the lines of code are
Product code 50%Tests 50%
Rebuild cost: about €220,000 · Estimate
Cost to rebuild
€73,000 to €360,000, for 1,210 to 3,840 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 79,497 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Raises the score by about 2.6 points · Low effort · ADR Quality
2
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €220,000 to build again, about 1.5 person-years of work. Its weakest lens is Security and Compliance, at 56.9 (checked 4 of 10). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2.6 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 25,883 lines over the last 90 days, which is about 104,970 lines a year. At that pace, the extra work comes to an estimated 5.2 to 35 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
240 modules, with 389 dependencies between them. 2 loops run through 59 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 200 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.
com.clevertap.android.sdk.inapp.data.DurationPartitionedInApps uses com.clevertap.android.sdk.inapp.data, so a change to com.clevertap.android.sdk.inapp.data can break com.clevertap.android.sdk.inapp.data.DurationPartitionedInApps, while a change to com.clevertap.android.sdk.inapp.data.DurationPartitionedInApps can't break com.clevertap.android.sdk.inapp.data.
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.
3→24 com.clevertap.android.sdk.inapp.delay uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.inapp.delay uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.inapp.delay uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inapp.delay, while a change to com.clevertap.android.sdk.inapp.delay can't break com.clevertap.android.sdk.utils.
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.
4→24 com.clevertap.android.sdk.inapp.images.memory uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
11 pairs of types, where a type in com.clevertap.android.sdk.inapp.images.memory uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.inapp.images.memory uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inapp.images.memory, while a change to com.clevertap.android.sdk.inapp.images.memory can't break com.clevertap.android.sdk.utils.
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.
com.clevertap.android.sdk.interfaces uses android.content, so a change to android.content can break com.clevertap.android.sdk.interfaces, while a change to com.clevertap.android.sdk.interfaces can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.interfaces uses a module listed above it, which is the healthy direction.
5→10 com.clevertap.android.sdk.interfaces uses com.clevertap.android.sdk.pushnotificationpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.interfaces uses a type in com.clevertap.android.sdk.pushnotification.
com.clevertap.android.sdk.interfaces uses com.clevertap.android.sdk.pushnotification, so a change to com.clevertap.android.sdk.pushnotification can break com.clevertap.android.sdk.interfaces, while a change to com.clevertap.android.sdk.interfaces can't break com.clevertap.android.sdk.pushnotification.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→31 com.clevertap.android.sdk.interfaces uses com.clevertap.android.sdkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.interfaces uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.interfaces uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.interfaces, while a change to com.clevertap.android.sdk.interfaces can't break com.clevertap.android.sdk.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→24 com.clevertap.android.sdk.pushnotification.preview uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.pushnotification.preview uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.pushnotification.preview uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.pushnotification.preview, while a change to com.clevertap.android.sdk.pushnotification.preview can't break com.clevertap.android.sdk.utils.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→35 com.clevertap.android.sdk.pushnotification.preview uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.pushnotification.preview uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.pushnotification.preview uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.pushnotification.preview, while a change to com.clevertap.android.sdk.pushnotification.preview can't break com.clevertap.android.sdk.db.
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.
7→31 com.clevertap.android.sdk.task uses com.clevertap.android.sdkpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.task uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.task uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.task, while a change to com.clevertap.android.sdk.task can't break com.clevertap.android.sdk.
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.
com.clevertap.android.sdk.events uses android.content, so a change to android.content can break com.clevertap.android.sdk.events, while a change to com.clevertap.android.sdk.events can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.events uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.events uses com.clevertap.android.sdk.task, so a change to com.clevertap.android.sdk.task can break com.clevertap.android.sdk.events, while a change to com.clevertap.android.sdk.events can't break com.clevertap.android.sdk.task.
Position
Below the diagonal: com.clevertap.android.sdk.events uses a module listed above it, which is the healthy direction.
8→31 com.clevertap.android.sdk.events uses com.clevertap.android.sdkpart of a loop✕
Connections
3 pairs of types, where a type in com.clevertap.android.sdk.events uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.events uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.events, while a change to com.clevertap.android.sdk.events can't break com.clevertap.android.sdk.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→35 com.clevertap.android.sdk.events uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.events uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.events uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.events, while a change to com.clevertap.android.sdk.events can't break com.clevertap.android.sdk.db.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→37 com.clevertap.android.sdk.events uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
3 pairs of types, where a type in com.clevertap.android.sdk.events uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.events uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.events, while a change to com.clevertap.android.sdk.events can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.inapp.data uses com.clevertap.android.sdk.inapp.data.DurationPartitionedInApps, so a change to com.clevertap.android.sdk.inapp.data.DurationPartitionedInApps can break com.clevertap.android.sdk.inapp.data, while a change to com.clevertap.android.sdk.inapp.data can't break com.clevertap.android.sdk.inapp.data.DurationPartitionedInApps.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.data uses a module listed above it, which is the healthy direction.
9→13 com.clevertap.android.sdk.inapp.data uses com.clevertap.android.sdk.inapp.customtemplatespart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.data uses a type in com.clevertap.android.sdk.inapp.customtemplates.
com.clevertap.android.sdk.inapp.data uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk.inapp.data, while a change to com.clevertap.android.sdk.inapp.data can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→37 com.clevertap.android.sdk.inapp.data uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.data uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.inapp.data uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.inapp.data, while a change to com.clevertap.android.sdk.inapp.data can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.pushnotification uses android.content, so a change to android.content can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.pushnotification uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.interfaces, so a change to com.clevertap.android.sdk.interfaces can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break com.clevertap.android.sdk.interfaces.
Position
Below the diagonal: com.clevertap.android.sdk.pushnotification uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.pushnotification.preview, so a change to com.clevertap.android.sdk.pushnotification.preview can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break com.clevertap.android.sdk.pushnotification.preview.
Position
Below the diagonal: com.clevertap.android.sdk.pushnotification uses a module listed above it, which is the healthy direction.
10→24 com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.pushnotification uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break com.clevertap.android.sdk.utils.
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→31 com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdkpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.pushnotification uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break com.clevertap.android.sdk.
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→35 com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.pushnotification uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break com.clevertap.android.sdk.db.
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→37 com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.pushnotification uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.pushnotification uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.pushnotification, while a change to com.clevertap.android.sdk.pushnotification can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.inapp.images uses com.clevertap.android.sdk.inapp.images.memory, so a change to com.clevertap.android.sdk.inapp.images.memory can break com.clevertap.android.sdk.inapp.images, while a change to com.clevertap.android.sdk.inapp.images can't break com.clevertap.android.sdk.inapp.images.memory.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.images uses com.clevertap.android.sdk.inapp.data, so a change to com.clevertap.android.sdk.inapp.data can break com.clevertap.android.sdk.inapp.images, while a change to com.clevertap.android.sdk.inapp.images can't break com.clevertap.android.sdk.inapp.data.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images uses a module listed above it, which is the healthy direction.
11→24 com.clevertap.android.sdk.inapp.images uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.images uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.inapp.images uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inapp.images, while a change to com.clevertap.android.sdk.inapp.images can't break com.clevertap.android.sdk.utils.
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→37 com.clevertap.android.sdk.inapp.images uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.inapp.images uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.inapp.images uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.inapp.images, while a change to com.clevertap.android.sdk.inapp.images can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.validation uses android.content, so a change to android.content can break com.clevertap.android.sdk.validation, while a change to com.clevertap.android.sdk.validation can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.validation uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.validation uses com.clevertap.android.sdk.pushnotification, so a change to com.clevertap.android.sdk.pushnotification can break com.clevertap.android.sdk.validation, while a change to com.clevertap.android.sdk.validation can't break com.clevertap.android.sdk.pushnotification.
Position
Below the diagonal: com.clevertap.android.sdk.validation uses a module listed above it, which is the healthy direction.
12→31 com.clevertap.android.sdk.validation uses com.clevertap.android.sdkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.validation uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.validation uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.validation, while a change to com.clevertap.android.sdk.validation can't break com.clevertap.android.sdk.
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.
com.clevertap.android.sdk.inapp.customtemplates uses com.clevertap.android.sdk.inapp.images, so a change to com.clevertap.android.sdk.inapp.images can break com.clevertap.android.sdk.inapp.customtemplates, while a change to com.clevertap.android.sdk.inapp.customtemplates can't break com.clevertap.android.sdk.inapp.images.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.customtemplates uses a module listed above it, which is the healthy direction.
13→22 com.clevertap.android.sdk.inapp.customtemplates uses com.clevertap.android.sdk.inapppart of a loop✕
Connections
5 pairs of types, where a type in com.clevertap.android.sdk.inapp.customtemplates uses a type in com.clevertap.android.sdk.inapp.
com.clevertap.android.sdk.inapp.customtemplates uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk.inapp.customtemplates, while a change to com.clevertap.android.sdk.inapp.customtemplates can't break com.clevertap.android.sdk.inapp.
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.
com.clevertap.android.sdk.inapp.pipsdk.internal.view uses com.clevertap.android.sdk.inapp.images, so a change to com.clevertap.android.sdk.inapp.images can break com.clevertap.android.sdk.inapp.pipsdk.internal.view, while a change to com.clevertap.android.sdk.inapp.pipsdk.internal.view can't break com.clevertap.android.sdk.inapp.images.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.pipsdk.internal.view uses a module listed above it, which is the healthy direction.
14→17 com.clevertap.android.sdk.inapp.pipsdk.internal.view uses com.clevertap.android.sdk.inapp.pipsdk.internal.sessionpart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.inapp.pipsdk.internal.view uses a type in com.clevertap.android.sdk.inapp.pipsdk.internal.session.
com.clevertap.android.sdk.inapp.pipsdk.internal.view uses com.clevertap.android.sdk.inapp.pipsdk.internal.session, so a change to com.clevertap.android.sdk.inapp.pipsdk.internal.session can break com.clevertap.android.sdk.inapp.pipsdk.internal.view, while a change to com.clevertap.android.sdk.inapp.pipsdk.internal.view can't break com.clevertap.android.sdk.inapp.pipsdk.internal.session.
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.
14→21 com.clevertap.android.sdk.inapp.pipsdk.internal.view uses com.clevertap.android.sdk.inapp.pipsdkpart of a loop✕
Connections
5 pairs of types, where a type in com.clevertap.android.sdk.inapp.pipsdk.internal.view uses a type in com.clevertap.android.sdk.inapp.pipsdk.
com.clevertap.android.sdk.inapp.pipsdk.internal.view uses com.clevertap.android.sdk.inapp.pipsdk, so a change to com.clevertap.android.sdk.inapp.pipsdk can break com.clevertap.android.sdk.inapp.pipsdk.internal.view, while a change to com.clevertap.android.sdk.inapp.pipsdk.internal.view can't break com.clevertap.android.sdk.inapp.pipsdk.
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.
com.clevertap.android.sdk.login uses android.content, so a change to android.content can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.login uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.events, so a change to com.clevertap.android.sdk.events can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.events.
Position
Below the diagonal: com.clevertap.android.sdk.login uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.pushnotification, so a change to com.clevertap.android.sdk.pushnotification can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.pushnotification.
Position
Below the diagonal: com.clevertap.android.sdk.login uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.validation, so a change to com.clevertap.android.sdk.validation can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.validation.
Position
Below the diagonal: com.clevertap.android.sdk.login uses a module listed above it, which is the healthy direction.
15→31 com.clevertap.android.sdk.login uses com.clevertap.android.sdkpart of a loop✕
Connections
13 pairs of types, where a type in com.clevertap.android.sdk.login uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.
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.
15→33 com.clevertap.android.sdk.login uses com.clevertap.android.sdk.inboxpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.login uses a type in com.clevertap.android.sdk.inbox.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.inbox, so a change to com.clevertap.android.sdk.inbox can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.inbox.
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.
15→35 com.clevertap.android.sdk.login uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.login uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.db.
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.
15→36 com.clevertap.android.sdk.login uses com.clevertap.android.sdk.cryptionpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.login uses a type in com.clevertap.android.sdk.cryption.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.cryption, so a change to com.clevertap.android.sdk.cryption can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.cryption.
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.
15→37 com.clevertap.android.sdk.login uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.login uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.login uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.login, while a change to com.clevertap.android.sdk.login can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.validation.pipeline uses com.clevertap.android.sdk.validation, so a change to com.clevertap.android.sdk.validation can break com.clevertap.android.sdk.validation.pipeline, while a change to com.clevertap.android.sdk.validation.pipeline can't break com.clevertap.android.sdk.validation.
Position
Below the diagonal: com.clevertap.android.sdk.validation.pipeline uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.clevertap.android.sdk.inapp.pipsdk.internal.session uses a type in com.clevertap.android.sdk.inapp.pipsdk.internal.view.
com.clevertap.android.sdk.inapp.pipsdk.internal.session uses com.clevertap.android.sdk.inapp.pipsdk.internal.view, so a change to com.clevertap.android.sdk.inapp.pipsdk.internal.view can break com.clevertap.android.sdk.inapp.pipsdk.internal.session, while a change to com.clevertap.android.sdk.inapp.pipsdk.internal.session can't break com.clevertap.android.sdk.inapp.pipsdk.internal.view.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.pipsdk.internal.session uses a module listed above it, which is the healthy direction.
17→21 com.clevertap.android.sdk.inapp.pipsdk.internal.session uses com.clevertap.android.sdk.inapp.pipsdkpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.inapp.pipsdk.internal.session uses a type in com.clevertap.android.sdk.inapp.pipsdk.
com.clevertap.android.sdk.inapp.pipsdk.internal.session uses com.clevertap.android.sdk.inapp.pipsdk, so a change to com.clevertap.android.sdk.inapp.pipsdk can break com.clevertap.android.sdk.inapp.pipsdk.internal.session, while a change to com.clevertap.android.sdk.inapp.pipsdk.internal.session can't break com.clevertap.android.sdk.inapp.pipsdk.
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.
com.clevertap.android.sdk.inapp.store.preference uses com.clevertap.android.sdk.login, so a change to com.clevertap.android.sdk.login can break com.clevertap.android.sdk.inapp.store.preference, while a change to com.clevertap.android.sdk.inapp.store.preference can't break com.clevertap.android.sdk.login.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.store.preference uses a module listed above it, which is the healthy direction.
18→31 com.clevertap.android.sdk.inapp.store.preference uses com.clevertap.android.sdkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.store.preference uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.inapp.store.preference uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.inapp.store.preference, while a change to com.clevertap.android.sdk.inapp.store.preference can't break com.clevertap.android.sdk.
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.
18→36 com.clevertap.android.sdk.inapp.store.preference uses com.clevertap.android.sdk.cryptionpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.store.preference uses a type in com.clevertap.android.sdk.cryption.
com.clevertap.android.sdk.inapp.store.preference uses com.clevertap.android.sdk.cryption, so a change to com.clevertap.android.sdk.cryption can break com.clevertap.android.sdk.inapp.store.preference, while a change to com.clevertap.android.sdk.inapp.store.preference can't break com.clevertap.android.sdk.cryption.
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.
com.clevertap.android.sdk.network.api uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk.network.api, while a change to com.clevertap.android.sdk.network.api can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Below the diagonal: com.clevertap.android.sdk.network.api uses a module listed above it, which is the healthy direction.
19→37 com.clevertap.android.sdk.network.api uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.network.api uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.network.api uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.network.api, while a change to com.clevertap.android.sdk.network.api can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.inapp.data, so a change to com.clevertap.android.sdk.inapp.data can break com.clevertap.android.sdk.inapp.evaluation, while a change to com.clevertap.android.sdk.inapp.evaluation can't break com.clevertap.android.sdk.inapp.data.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.evaluation uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk.inapp.evaluation, while a change to com.clevertap.android.sdk.inapp.evaluation can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.evaluation uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.inapp.store.preference, so a change to com.clevertap.android.sdk.inapp.store.preference can break com.clevertap.android.sdk.inapp.evaluation, while a change to com.clevertap.android.sdk.inapp.evaluation can't break com.clevertap.android.sdk.inapp.store.preference.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.evaluation uses a module listed above it, which is the healthy direction.
20→22 com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.inapppart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.inapp.evaluation uses a type in com.clevertap.android.sdk.inapp.
com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk.inapp.evaluation, while a change to com.clevertap.android.sdk.inapp.evaluation can't break com.clevertap.android.sdk.inapp.
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→24 com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.evaluation uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inapp.evaluation, while a change to com.clevertap.android.sdk.inapp.evaluation can't break com.clevertap.android.sdk.utils.
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→37 com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.inapp.evaluation uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.inapp.evaluation uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.inapp.evaluation, while a change to com.clevertap.android.sdk.inapp.evaluation can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.inapp.pipsdk uses com.clevertap.android.sdk.inapp.images, so a change to com.clevertap.android.sdk.inapp.images can break com.clevertap.android.sdk.inapp.pipsdk, while a change to com.clevertap.android.sdk.inapp.pipsdk can't break com.clevertap.android.sdk.inapp.images.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.pipsdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.pipsdk uses com.clevertap.android.sdk.inapp.pipsdk.internal.session, so a change to com.clevertap.android.sdk.inapp.pipsdk.internal.session can break com.clevertap.android.sdk.inapp.pipsdk, while a change to com.clevertap.android.sdk.inapp.pipsdk can't break com.clevertap.android.sdk.inapp.pipsdk.internal.session.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.pipsdk uses a module listed above it, which is the healthy direction.
21→22 com.clevertap.android.sdk.inapp.pipsdk uses com.clevertap.android.sdk.inapppart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp.pipsdk uses a type in com.clevertap.android.sdk.inapp.
com.clevertap.android.sdk.inapp.pipsdk uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk.inapp.pipsdk, while a change to com.clevertap.android.sdk.inapp.pipsdk can't break com.clevertap.android.sdk.inapp.
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.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.inapp.delay, so a change to com.clevertap.android.sdk.inapp.delay can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.inapp.delay.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.task, so a change to com.clevertap.android.sdk.task can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.task.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.inapp.images, so a change to com.clevertap.android.sdk.inapp.images can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.inapp.images.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.login, so a change to com.clevertap.android.sdk.login can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.login.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.inapp.store.preference, so a change to com.clevertap.android.sdk.inapp.store.preference can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.inapp.store.preference.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.inapp.evaluation, so a change to com.clevertap.android.sdk.inapp.evaluation can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.inapp.evaluation.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.inapp.pipsdk, so a change to com.clevertap.android.sdk.inapp.pipsdk can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.inapp.pipsdk.
Position
Below the diagonal: com.clevertap.android.sdk.inapp uses a module listed above it, which is the healthy direction.
22→24 com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.utilspart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.inapp uses a type in com.clevertap.android.sdk.utils.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.utils.
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.
22→31 com.clevertap.android.sdk.inapp uses com.clevertap.android.sdkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inapp uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.
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.
22→37 com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
3 pairs of types, where a type in com.clevertap.android.sdk.inapp uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.inapp uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.inapp, while a change to com.clevertap.android.sdk.inapp can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.inapp.fragment uses com.clevertap.android.sdk.inapp.images, so a change to com.clevertap.android.sdk.inapp.images can break com.clevertap.android.sdk.inapp.fragment, while a change to com.clevertap.android.sdk.inapp.fragment can't break com.clevertap.android.sdk.inapp.images.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.fragment uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.fragment uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk.inapp.fragment, while a change to com.clevertap.android.sdk.inapp.fragment can't break com.clevertap.android.sdk.inapp.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.fragment uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.utils uses android.content, so a change to android.content can break com.clevertap.android.sdk.utils, while a change to com.clevertap.android.sdk.utils can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.utils uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.utils uses com.clevertap.android.sdk.inapp.images.memory, so a change to com.clevertap.android.sdk.inapp.images.memory can break com.clevertap.android.sdk.utils, while a change to com.clevertap.android.sdk.utils can't break com.clevertap.android.sdk.inapp.images.memory.
Position
Below the diagonal: com.clevertap.android.sdk.utils uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.utils uses com.clevertap.android.sdk.validation, so a change to com.clevertap.android.sdk.validation can break com.clevertap.android.sdk.utils, while a change to com.clevertap.android.sdk.utils can't break com.clevertap.android.sdk.validation.
Position
Below the diagonal: com.clevertap.android.sdk.utils uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.utils uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk.utils, while a change to com.clevertap.android.sdk.utils can't break com.clevertap.android.sdk.inapp.
Position
Below the diagonal: com.clevertap.android.sdk.utils uses a module listed above it, which is the healthy direction.
24→31 com.clevertap.android.sdk.utils uses com.clevertap.android.sdkpart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.utils uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.utils uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.utils, while a change to com.clevertap.android.sdk.utils can't break com.clevertap.android.sdk.
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.
24→33 com.clevertap.android.sdk.utils uses com.clevertap.android.sdk.inboxpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.utils uses a type in com.clevertap.android.sdk.inbox.
com.clevertap.android.sdk.utils uses com.clevertap.android.sdk.inbox, so a change to com.clevertap.android.sdk.inbox can break com.clevertap.android.sdk.utils, while a change to com.clevertap.android.sdk.utils can't break com.clevertap.android.sdk.inbox.
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.
com.clevertap.android.sdk.featureFlags uses android.content, so a change to android.content can break com.clevertap.android.sdk.featureFlags, while a change to com.clevertap.android.sdk.featureFlags can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.featureFlags uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.featureFlags uses com.clevertap.android.sdk.task, so a change to com.clevertap.android.sdk.task can break com.clevertap.android.sdk.featureFlags, while a change to com.clevertap.android.sdk.featureFlags can't break com.clevertap.android.sdk.task.
Position
Below the diagonal: com.clevertap.android.sdk.featureFlags uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.featureFlags uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.featureFlags, while a change to com.clevertap.android.sdk.featureFlags can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.featureFlags uses a module listed above it, which is the healthy direction.
25→31 com.clevertap.android.sdk.featureFlags uses com.clevertap.android.sdkpart of a loop✕
Connections
7 pairs of types, where a type in com.clevertap.android.sdk.featureFlags uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.featureFlags uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.featureFlags, while a change to com.clevertap.android.sdk.featureFlags can't break com.clevertap.android.sdk.
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.
com.clevertap.android.sdk.inapp.images.preload uses com.clevertap.android.sdk.inapp.data, so a change to com.clevertap.android.sdk.inapp.data can break com.clevertap.android.sdk.inapp.images.preload, while a change to com.clevertap.android.sdk.inapp.images.preload can't break com.clevertap.android.sdk.inapp.data.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images.preload uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.images.preload uses com.clevertap.android.sdk.inapp.images, so a change to com.clevertap.android.sdk.inapp.images can break com.clevertap.android.sdk.inapp.images.preload, while a change to com.clevertap.android.sdk.inapp.images.preload can't break com.clevertap.android.sdk.inapp.images.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images.preload uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.images.preload uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inapp.images.preload, while a change to com.clevertap.android.sdk.inapp.images.preload can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images.preload uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network.fetch uses com.clevertap.android.sdk.network.api, so a change to com.clevertap.android.sdk.network.api can break com.clevertap.android.sdk.network.fetch, while a change to com.clevertap.android.sdk.network.fetch can't break com.clevertap.android.sdk.network.api.
Position
Below the diagonal: com.clevertap.android.sdk.network.fetch uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network.fetch uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.network.fetch, while a change to com.clevertap.android.sdk.network.fetch can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.network.fetch uses a module listed above it, which is the healthy direction.
27→37 com.clevertap.android.sdk.network.fetch uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.network.fetch uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.network.fetch uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.network.fetch, while a change to com.clevertap.android.sdk.network.fetch can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.product_config uses android.content, so a change to android.content can break com.clevertap.android.sdk.product_config, while a change to com.clevertap.android.sdk.product_config can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.product_config uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.product_config uses com.clevertap.android.sdk.task, so a change to com.clevertap.android.sdk.task can break com.clevertap.android.sdk.product_config, while a change to com.clevertap.android.sdk.product_config can't break com.clevertap.android.sdk.task.
Position
Below the diagonal: com.clevertap.android.sdk.product_config uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.product_config uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.product_config, while a change to com.clevertap.android.sdk.product_config can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.product_config uses a module listed above it, which is the healthy direction.
28→31 com.clevertap.android.sdk.product_config uses com.clevertap.android.sdkpart of a loop✕
Connections
11 pairs of types, where a type in com.clevertap.android.sdk.product_config uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.product_config uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.product_config, while a change to com.clevertap.android.sdk.product_config can't break com.clevertap.android.sdk.
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.
com.clevertap.android.sdk.inapp.images.repo uses com.clevertap.android.sdk.inapp.data, so a change to com.clevertap.android.sdk.inapp.data can break com.clevertap.android.sdk.inapp.images.repo, while a change to com.clevertap.android.sdk.inapp.images.repo can't break com.clevertap.android.sdk.inapp.data.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images.repo uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.images.repo uses com.clevertap.android.sdk.inapp.store.preference, so a change to com.clevertap.android.sdk.inapp.store.preference can break com.clevertap.android.sdk.inapp.images.repo, while a change to com.clevertap.android.sdk.inapp.images.repo can't break com.clevertap.android.sdk.inapp.store.preference.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images.repo uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inapp.images.repo uses com.clevertap.android.sdk.inapp.images.preload, so a change to com.clevertap.android.sdk.inapp.images.preload can break com.clevertap.android.sdk.inapp.images.repo, while a change to com.clevertap.android.sdk.inapp.images.repo can't break com.clevertap.android.sdk.inapp.images.preload.
Position
Below the diagonal: com.clevertap.android.sdk.inapp.images.repo uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.variables uses android.content, so a change to android.content can break com.clevertap.android.sdk.variables, while a change to com.clevertap.android.sdk.variables can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.variables uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.variables uses com.clevertap.android.sdk.inapp.images.repo, so a change to com.clevertap.android.sdk.inapp.images.repo can break com.clevertap.android.sdk.variables, while a change to com.clevertap.android.sdk.variables can't break com.clevertap.android.sdk.inapp.images.repo.
Position
Below the diagonal: com.clevertap.android.sdk.variables uses a module listed above it, which is the healthy direction.
30→31 com.clevertap.android.sdk.variables uses com.clevertap.android.sdkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.variables uses a type in com.clevertap.android.sdk.
com.clevertap.android.sdk.variables uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.variables, while a change to com.clevertap.android.sdk.variables can't break com.clevertap.android.sdk.
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.
com.clevertap.android.sdk uses android.content, so a change to android.content can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.interfaces, so a change to com.clevertap.android.sdk.interfaces can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.interfaces.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.pushnotification.preview, so a change to com.clevertap.android.sdk.pushnotification.preview can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.pushnotification.preview.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.task, so a change to com.clevertap.android.sdk.task can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.task.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.events, so a change to com.clevertap.android.sdk.events can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.events.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.pushnotification, so a change to com.clevertap.android.sdk.pushnotification can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.pushnotification.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.validation, so a change to com.clevertap.android.sdk.validation can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.validation.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.login, so a change to com.clevertap.android.sdk.login can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.login.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.validation.pipeline, so a change to com.clevertap.android.sdk.validation.pipeline can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.validation.pipeline.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.inapp.store.preference, so a change to com.clevertap.android.sdk.inapp.store.preference can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.inapp.store.preference.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.inapp.evaluation, so a change to com.clevertap.android.sdk.inapp.evaluation can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.inapp.evaluation.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.inapp.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.inapp.fragment, so a change to com.clevertap.android.sdk.inapp.fragment can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.inapp.fragment.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.featureFlags, so a change to com.clevertap.android.sdk.featureFlags can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.featureFlags.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.product_config, so a change to com.clevertap.android.sdk.product_config can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.product_config.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk uses com.clevertap.android.sdk.variables, so a change to com.clevertap.android.sdk.variables can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.variables.
Position
Below the diagonal: com.clevertap.android.sdk uses a module listed above it, which is the healthy direction.
31→33 com.clevertap.android.sdk uses com.clevertap.android.sdk.inboxpart of a loop✕
Connections
10 pairs of types, where a type in com.clevertap.android.sdk uses a type in com.clevertap.android.sdk.inbox.
com.clevertap.android.sdk uses com.clevertap.android.sdk.inbox, so a change to com.clevertap.android.sdk.inbox can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.inbox.
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.
31→35 com.clevertap.android.sdk uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
3 pairs of types, where a type in com.clevertap.android.sdk uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.db.
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.
31→36 com.clevertap.android.sdk uses com.clevertap.android.sdk.cryptionpart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk uses a type in com.clevertap.android.sdk.cryption.
com.clevertap.android.sdk uses com.clevertap.android.sdk.cryption, so a change to com.clevertap.android.sdk.cryption can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.cryption.
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.
31→37 com.clevertap.android.sdk uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
6 pairs of types, where a type in com.clevertap.android.sdk uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk, while a change to com.clevertap.android.sdk can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.response uses android.content, so a change to android.content can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.inapp.data, so a change to com.clevertap.android.sdk.inapp.data can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.inapp.data.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.validation, so a change to com.clevertap.android.sdk.validation can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.validation.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.inapp.store.preference, so a change to com.clevertap.android.sdk.inapp.store.preference can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.inapp.store.preference.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.inapp.evaluation, so a change to com.clevertap.android.sdk.inapp.evaluation can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.inapp.evaluation.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.inapp, so a change to com.clevertap.android.sdk.inapp can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.inapp.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.product_config, so a change to com.clevertap.android.sdk.product_config can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.product_config.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
35 pairs of types, where a type in com.clevertap.android.sdk.response uses a type in com.clevertap.android.sdk. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.
Position
Below the diagonal: com.clevertap.android.sdk.response uses a module listed above it, which is the healthy direction.
32→35 com.clevertap.android.sdk.response uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.response uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.db.
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.
32→37 com.clevertap.android.sdk.response uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
4 pairs of types, where a type in com.clevertap.android.sdk.response uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.response uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.response, while a change to com.clevertap.android.sdk.response can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.inbox uses android.content, so a change to android.content can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break android.content.
Position
Below the diagonal: com.clevertap.android.sdk.inbox uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.network.api, so a change to com.clevertap.android.sdk.network.api can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.network.api.
Position
Below the diagonal: com.clevertap.android.sdk.inbox uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.inbox uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.network.fetch, so a change to com.clevertap.android.sdk.network.fetch can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.network.fetch.
Position
Below the diagonal: com.clevertap.android.sdk.inbox uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.
Position
Below the diagonal: com.clevertap.android.sdk.inbox uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.response, so a change to com.clevertap.android.sdk.response can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.response.
Position
Below the diagonal: com.clevertap.android.sdk.inbox uses a module listed above it, which is the healthy direction.
33→35 com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.inbox uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.db.
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.
33→37 com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.inbox uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.inbox uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.inbox, while a change to com.clevertap.android.sdk.inbox can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.db.dao uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.db.dao, while a change to com.clevertap.android.sdk.db.dao can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.db.dao uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.db.dao uses com.clevertap.android.sdk.inbox, so a change to com.clevertap.android.sdk.inbox can break com.clevertap.android.sdk.db.dao, while a change to com.clevertap.android.sdk.db.dao can't break com.clevertap.android.sdk.inbox.
Position
Below the diagonal: com.clevertap.android.sdk.db.dao uses a module listed above it, which is the healthy direction.
34→35 com.clevertap.android.sdk.db.dao uses com.clevertap.android.sdk.dbpart of a loop✕
Connections
16 pairs of types, where a type in com.clevertap.android.sdk.db.dao uses a type in com.clevertap.android.sdk.db.
com.clevertap.android.sdk.db.dao uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.db.dao, while a change to com.clevertap.android.sdk.db.dao can't break com.clevertap.android.sdk.db.
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.
com.clevertap.android.sdk.db uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.db, while a change to com.clevertap.android.sdk.db can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.db uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.db uses com.clevertap.android.sdk.db.dao, so a change to com.clevertap.android.sdk.db.dao can break com.clevertap.android.sdk.db, while a change to com.clevertap.android.sdk.db can't break com.clevertap.android.sdk.db.dao.
Position
Below the diagonal: com.clevertap.android.sdk.db uses a module listed above it, which is the healthy direction.
35→36 com.clevertap.android.sdk.db uses com.clevertap.android.sdk.cryptionpart of a loop✕
Connections
2 pairs of types, where a type in com.clevertap.android.sdk.db uses a type in com.clevertap.android.sdk.cryption.
com.clevertap.android.sdk.db uses com.clevertap.android.sdk.cryption, so a change to com.clevertap.android.sdk.cryption can break com.clevertap.android.sdk.db, while a change to com.clevertap.android.sdk.db can't break com.clevertap.android.sdk.cryption.
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.
35→37 com.clevertap.android.sdk.db uses com.clevertap.android.sdk.networkpart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.sdk.db uses a type in com.clevertap.android.sdk.network.
com.clevertap.android.sdk.db uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.sdk.db, while a change to com.clevertap.android.sdk.db can't break com.clevertap.android.sdk.network.
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.
com.clevertap.android.sdk.cryption uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.cryption, while a change to com.clevertap.android.sdk.cryption can't break com.clevertap.android.sdk.db.
Position
Below the diagonal: com.clevertap.android.sdk.cryption uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network uses com.clevertap.android.sdk.inapp.customtemplates, so a change to com.clevertap.android.sdk.inapp.customtemplates can break com.clevertap.android.sdk.network, while a change to com.clevertap.android.sdk.network can't break com.clevertap.android.sdk.inapp.customtemplates.
Position
Below the diagonal: com.clevertap.android.sdk.network uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network uses com.clevertap.android.sdk.network.api, so a change to com.clevertap.android.sdk.network.api can break com.clevertap.android.sdk.network, while a change to com.clevertap.android.sdk.network can't break com.clevertap.android.sdk.network.api.
Position
Below the diagonal: com.clevertap.android.sdk.network uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network uses com.clevertap.android.sdk.utils, so a change to com.clevertap.android.sdk.utils can break com.clevertap.android.sdk.network, while a change to com.clevertap.android.sdk.network can't break com.clevertap.android.sdk.utils.
Position
Below the diagonal: com.clevertap.android.sdk.network uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network uses com.clevertap.android.sdk.response, so a change to com.clevertap.android.sdk.response can break com.clevertap.android.sdk.network, while a change to com.clevertap.android.sdk.network can't break com.clevertap.android.sdk.response.
Position
Below the diagonal: com.clevertap.android.sdk.network uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network uses com.clevertap.android.sdk.db, so a change to com.clevertap.android.sdk.db can break com.clevertap.android.sdk.network, while a change to com.clevertap.android.sdk.network can't break com.clevertap.android.sdk.db.
Position
Below the diagonal: com.clevertap.android.sdk.network uses a module listed above it, which is the healthy direction.
com.clevertap.android.sdk.network uses com.clevertap.android.sdk.cryption, so a change to com.clevertap.android.sdk.cryption can break com.clevertap.android.sdk.network, while a change to com.clevertap.android.sdk.network can't break com.clevertap.android.sdk.cryption.
Position
Below the diagonal: com.clevertap.android.sdk.network uses a module listed above it, which is the healthy direction.
com.clevertap.android.pushtemplates.media uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.pushtemplates.media, while a change to com.clevertap.android.pushtemplates.media can't break com.clevertap.android.sdk.network.
Position
Below the diagonal: com.clevertap.android.pushtemplates.media uses a module listed above it, which is the healthy direction.
38→39 com.clevertap.android.pushtemplates.media uses com.clevertap.android.pushtemplatespart of a loop✕
Connections
1 pair of types, where a type in com.clevertap.android.pushtemplates.media uses a type in com.clevertap.android.pushtemplates.
com.clevertap.android.pushtemplates.media uses com.clevertap.android.pushtemplates, so a change to com.clevertap.android.pushtemplates can break com.clevertap.android.pushtemplates.media, while a change to com.clevertap.android.pushtemplates.media can't break com.clevertap.android.pushtemplates.
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.
com.clevertap.android.pushtemplates uses android.content, so a change to android.content can break com.clevertap.android.pushtemplates, while a change to com.clevertap.android.pushtemplates can't break android.content.
Position
Below the diagonal: com.clevertap.android.pushtemplates uses a module listed above it, which is the healthy direction.
com.clevertap.android.pushtemplates uses com.clevertap.android.sdk.interfaces, so a change to com.clevertap.android.sdk.interfaces can break com.clevertap.android.pushtemplates, while a change to com.clevertap.android.pushtemplates can't break com.clevertap.android.sdk.interfaces.
Position
Below the diagonal: com.clevertap.android.pushtemplates uses a module listed above it, which is the healthy direction.
com.clevertap.android.pushtemplates uses com.clevertap.android.sdk.pushnotification, so a change to com.clevertap.android.sdk.pushnotification can break com.clevertap.android.pushtemplates, while a change to com.clevertap.android.pushtemplates can't break com.clevertap.android.sdk.pushnotification.
Position
Below the diagonal: com.clevertap.android.pushtemplates uses a module listed above it, which is the healthy direction.
com.clevertap.android.pushtemplates uses com.clevertap.android.sdk, so a change to com.clevertap.android.sdk can break com.clevertap.android.pushtemplates, while a change to com.clevertap.android.pushtemplates can't break com.clevertap.android.sdk.
Position
Below the diagonal: com.clevertap.android.pushtemplates uses a module listed above it, which is the healthy direction.
com.clevertap.android.pushtemplates uses com.clevertap.android.sdk.network, so a change to com.clevertap.android.sdk.network can break com.clevertap.android.pushtemplates, while a change to com.clevertap.android.pushtemplates can't break com.clevertap.android.sdk.network.
Position
Below the diagonal: com.clevertap.android.pushtemplates uses a module listed above it, which is the healthy direction.
com.clevertap.android.pushtemplates uses com.clevertap.android.pushtemplates.media, so a change to com.clevertap.android.pushtemplates.media can break com.clevertap.android.pushtemplates, while a change to com.clevertap.android.pushtemplates can't break com.clevertap.android.pushtemplates.media.
Position
Below the diagonal: com.clevertap.android.pushtemplates uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in com.clevertap.android.pushtemplates.styles uses a type in com.clevertap.android.pushtemplates. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.clevertap.android.pushtemplates.styles uses com.clevertap.android.pushtemplates, so a change to com.clevertap.android.pushtemplates can break com.clevertap.android.pushtemplates.styles, while a change to com.clevertap.android.pushtemplates.styles can't break com.clevertap.android.pushtemplates.
Position
Below the diagonal: com.clevertap.android.pushtemplates.styles 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
A05:2025 — Injection
48
High / Critical
A03:2025 — Software Supply Chain Failures
7
Medium
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 11 REDACTED finding(s) charged to Static Analysis (SAST) — the other 23 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Resolve the 11 REDACTED finding(s) charged to Static Analysis (SAST) — the other 23 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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 — 49
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 — 460
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 — 120
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 17
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 49 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 49 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, 618 of 629 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 3 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because developer.huawei.com — the registry that answers it — was asked and did not reply (the build stopped because developer.huawei.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add developer.huawei.com to the allowlist and re-run — not to build anything.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (test_shared/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. `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppActionHandler.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppNotificationInflater.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PIPShowFailureHandler.kt`, … (+8 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.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (instantapp). the Android app did not build — `./gradlew :instantapp:assembleDebug` exited 1: gcp:1.9.1.301.
Required by:
root project :
> Could not resolve com.huawei.agconnect:agcp:1.9.1.301.
> Could not get resource 'https://developer.huawei.com/repo/com/huawei/…; runtime evidence skipped (launch chosen because instantapp/build.gradle.kts applies the Android application plugin and gradlew builds it).
C1 Data Protection — 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. 'android.database.sqlite' is imported (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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.
C3 Audit Trail — 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. 'android.database.sqlite' is imported (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — 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. 'android.database.sqlite' is imported (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — 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. 'android.database.sqlite' is imported (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
X1 Async correctness — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
33 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CTIconMessageViewHolder.configureWithMessage at 53. A further 1 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 CTInAppType.fromString at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppType.kt (CTInAppType.fromString at 18). 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.
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with CTIconMessageViewHolder.configureWithMessage (cyclomatic 53), CTSimpleMessageViewHolder.configureWithMessage (cyclomatic 49), InAppController.showInApp (cyclomatic 41). — 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 Cyclomatic Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 57 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with CTIconMessageViewHolder.configureWithMessage (cognitive 119), CTSimpleMessageViewHolder.configureWithMessage (cognitive 112), NestedJsonBuilder.setValueRecursive (cognitive 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 24 TooManyMethods finding(s) in God Classes — start with Utils.java (2), CleverTapAPI.java, CoreMetaData.java. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 12 ClassTooLong finding(s) in God Classes — start with CleverTapAPI.java, InAppController.kt, AnalyticsManager.java. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 10 MethodTooLong finding(s) in God Classes — start with CleverTapFactory.kt, CTIconMessageViewHolder.java, CTSimpleMessageViewHolder.java. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
104 duplicated block group(s) detected. 8.4 % of the production lines (6,683 of 79,497) are in a reported copy. A further 118 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 9 of the 222 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.
+ 95 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Utils.java (2), CTInAppNativeCoverFragment.kt, CTInAppNativeFooterFragment.kt. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with Logger.java (2), DeviceInfo.java (2), Utils.java (2). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with InboxPendingActionsDAO.kt, CTInAppBaseFullHtmlFragment.kt, ExoplayerHandle.kt. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.9 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
7 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 5 of the 7 (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: :clevertap-core
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether 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 24 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 50 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with InAppController.kt, InAppNotificationActivity.java, PushProviders.kt. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with PushPreviewKey.kt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.6 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
12 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt. Counted over 312 of the 643 production source files in this repository: 326 are under the ~2,400-byte size floor this dimension measures over, and the remaining 5 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
22 deducted task-comment markers across 79497 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 22 TodoComment finding(s) in Explicit Debt — start with CleverTapAPI.java (5), UtilsTest.kt (3), InAppControllerTest.kt (2). — One of this dimension's main actionable groups (22 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.
2 of 2 documentation facets pass in full. 25 document(s) read across 7 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
3 naming inconsistencies among 70 declarations measured against a convention their peers follow.
`openHttpsURLConnection` spells `URL` where 42 names in the project spell it `Url`clevertap-core/src/main/java/com/clevertap/android/sdk/network/http/UrlConnectionHttpClient.kt:92
`getBitmapFromURL` spells `URL` where 17 names in the project spell it `Url`clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:168
`getWZRKFields` spells `WZRK` where 12 names in the project spell it `Wzrk`clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnit.java:240
What to do
Resolve the 1 `openHttpsURLConnection` spells `URL` where 42 names in the project… finding(s) in Naming Consistency — start with UrlConnectionHttpClient.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `getBitmapFromURL` spells `URL` where 17 names in the project spell it… finding(s) in Naming Consistency — start with Utils.java. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `getWZRKFields` spells `WZRK` where 12 names in the project spell it… finding(s) in Naming Consistency — start with CleverTapDisplayUnit.java. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion3.2 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
2 of 5 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×2clevertap-core/build.gradle:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
48 finding(s): 0 critical, 42 high, 6 medium, 0 low. 23 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt` (line 100, line 1676) — 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 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 REDACTED finding(s) charged to Static Analysis (SAST) — the other 23 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (34 issue-level, 11 of them charged here).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
82 of 317 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java. Counted over 317 of the 643 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 79 Orphaned file finding(s) in Knowledge Freshness — start with Logger.java (2), FileUtils.java (2), InAppFCManager.java. — One of this dimension's main actionable groups (79 recommendation-level).
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with CTProductConfigController.java, Utils.java, CTGeofenceAPI.java. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with CTFcmMessageHandler.java. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Change coupling finding(s) in Change Coupling — start with CTFeatureFlagsController.java, CleverTapAPI.java, FetchVariablesResponse.java. — One of this dimension's main actionable groups (3 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 7 platform declaration(s) and 95 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
`ICTPreference` declares 26 abstract methods: `readString`, `readBoolean`, `readInt`, `readLong`, `readFloat`, `readStringSet`, `readAll`, `writeString`, `writeBoolean`, `writeInt`, `writeLong`, `writeFloat`, `writeStringSet`, `writeMap`, `writeStringImmediate`, `writeBooleanImmediate`, `writeIntImmediate`, `writeLongImmediate`, `writeFloatImmediate`, `writeStringSetImmediate`, `writeMapImmediate`, `isEmpty`, `size`, `remove`, `removeImmediate`, `changePreferenceName`. 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. — clevertap-core/src/main/java/com/clevertap/android/sdk/store/preference/ICTPreference.kt:14
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.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
`build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build.gradle:12
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · 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.
`messageBundle == null` can never be true where it stands: control only reaches it when `messageBundle != null` (line 111). The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it. — clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/CTFirebaseMessagingReceiver.java:113
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.7 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`convertJSONObjectToHashMap` is not private and takes `JSONObject b` from its caller, and it calls itself at line 132 with a piece of `b` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `convertJSONObjectToHashMap` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:132
`mergeHelper` is not private and takes `Object vars` from its caller, and it calls itself at line 155 with a piece of `vars` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `mergeHelper` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:155
`listToJsonArray` is not private and takes `Iterable<?> list` from its caller, and it recurses at line 45 through `mapToJsonObject` and back with a piece of `list` (and at line 47, line 123, line 125) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `listToJsonArray` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:45
`mapFromJson` is not private and takes `JSONObject object` from its caller, and it recurses at line 68 through `listFromJsonSafe`, `listFromJson` and back with a piece of `object` (and at line 70, line 102, line 104) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `mapFromJson` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:68
`JsonFlattener.flatten` is public, takes a document from its caller (line 9) and hands it to `JsonFlattener.flattenInternal`, which calls itself at line 30 with a piece of `json` — the function is not `tailrec`, so every call is a real frame — and nowhere in `JsonFlattener.flattenInternal` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `JsonFlattener.flattenInternal` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — clevertap-core/src/main/java/com/clevertap/android/sdk/utils/JsonFlattener.kt:30
`mapArgument` is public and takes `value: Map<String, Any>` from its caller, and it calls itself at line 227 with a piece of `value` — the function is not `tailrec`, so every call is a real frame — and nowhere in `mapArgument` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `mapArgument` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/CustomTemplate.kt:227
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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 an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 1005 is called with an argument built by `inAppActivityExclude.joinToString()` (line 1007), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1005
What to do
In Kotlin, hand the logger a lambda it calls only when the level is on (`logger.debug { "rows: ${rows.joinToString()}" }` — kotlin-logging and Log4j 2's Kotlin API take one), or put the line behind `if (log.isDebugEnabled)` (`if (BuildConfig.DEBUG)` for a line only a debug build needs). A string template is not the fix on SLF4J or Timber: their message is a `String`, so every `joinToString` or `toJson` inside the `${…}` runs before the call is entered.
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.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×12) — clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:93, clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java:44, clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java:58, …
`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. (×5) — clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:589, clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:319, clevertap-core/src/main/java/com/clevertap/android/sdk/gif/GifDecoder.java:779, …
`catch (t: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressStyle.kt:471, clevertap-core/src/main/java/com/clevertap/android/sdk/NdFCManager.kt:117, clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:332
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×16) — clevertap-core/src/main/java/com/clevertap/android/sdk/CallbackManager.java:307, clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1029, clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3397, …
`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) — clevertap-core/src/main/java/com/clevertap/android/sdk/utils/ColorUtils.kt:26, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PIPConfigFactory.kt:194
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — clevertap-core/src/main/java/com/clevertap/android/sdk/utils/ColorUtils.kt:38
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D11 Test Reliability — 3 observation(s) recorded · This repository declares 3 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'android.database.sqlite' (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'android.database.sqlite' (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'android.database.sqlite' (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :instantapp:assembleDebug` exited 1: gcp:1.9.1.301.
Required by:
root project :
> Could not resolve com.huawei.agconnect:agcp:1.9.1.301.
> Could not get resource 'https://developer.huawei.com/repo/com/huawei/…; runtime evidence skipped (launch chosen because instantapp/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
C1 Data Protection — Not assessed: this repository stores data through 'android.database.sqlite' (clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:4) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~79007 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D12 Dependency Hygiene — Dependency currency not established — developer.huawei.com did not answer
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 127 value object(s); 3 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 (2 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 25 current-state document(s) make no claim of a kind M4 checks. 66 claim(s) of kinds M4 does not check were not checked (path 30, environment variable 36); M4 checks only links and versions and artefact counts.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
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
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
D11 · Test Reliability· Test declared unreliable · ×3
Test declared unreliable: test_drawableToBitmap_when_PassedDrawable_should_ReturnBitmap clevertap-core/src/test/java/com/clevertap/android/sdk/UtilsTest.kt:236— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "This test is flaky and subject to licensing + hosting of image url". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: test_getBitmapFromURL_when_CorrectImageLinkArePassed_should_ReturnImage clevertap-core/src/test/java/com/clevertap/android/sdk/UtilsTest.kt:248— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "This test is flaky and subject to licensing + hosting of image url". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: test_getBitmapFromURL_when_image_link_contains_single_or_double_slash_should_ReturnImage clevertap-core/src/test/java/com/clevertap/android/sdk/UtilsTest.kt:276— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "This test is flaky and subject to licensing + hosting of image url". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Orphaned knowledge clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceAPI.java:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Boundary-crossing change coupling: CTFcmMessageHandler.java ↔ CTHmsMessageHandler.java clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/CTFcmMessageHandler.java:1— `clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/CTFcmMessageHandler.java` (context clevertap-core) and `clevertap-hms/src/main/java/com/clevertap/android/hms/CTHmsMessageHandler.java` (context clevertap-hms) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `ef053825` docs(SDK-3672) - Replaces Push Amplification with Pull Notifications …; `876bf20f` feat(SDK-1736): update nh source key and push template version; `73b0f754` feat(SDK-1736): add nh source to push services — run `git show` on any of them.
TooManyMethods: CleverTapAPI clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:103— TooManyMethods — 226 methods. The bar is 30 methods; this is 196 over it, 7.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CoreMetaData clevertap-core/src/main/java/com/clevertap/android/sdk/CoreMetaData.java:16— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.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: InAppController clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:72— TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DeviceInfo clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:56— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.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.
TooManyMethods: CleverTapInstanceConfig clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:29— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AnalyticsManager clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:55— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: LocalDataStore clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:48— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: DBAdapter clevertap-core/src/main/java/com/clevertap/android/sdk/db/DBAdapter.kt:19— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PushProviders clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:57— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CallbackManager clevertap-core/src/main/java/com/clevertap/android/sdk/CallbackManager.java:29— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 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.
TooManyMethods: BaseCallbackManager clevertap-core/src/main/java/com/clevertap/android/sdk/BaseCallbackManager.java:18— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CTInboxMessageContent clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:18— 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: Utils clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:56— 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: CTProductConfigController clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:44— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NetworkManager clevertap-core/src/main/java/com/clevertap/android/sdk/network/NetworkManager.kt:42— 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: Utils clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:63— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Media3PlayerListener clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3PlayerListener.kt:23— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExoplayerPlayerListener clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerPlayerListener.kt:22— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EvaluationManager clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.kt:46— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 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.
TooManyMethods: TemplateDataFactory clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateDataFactory.kt:89— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 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.
TooManyMethods: ManifestInfo clevertap-core/src/main/java/com/clevertap/android/sdk/ManifestInfo.java:19— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CTInboxStyleConfig clevertap-core/src/main/java/com/clevertap/android/sdk/CTInboxStyleConfig.java:14— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ControllerManager clevertap-core/src/main/java/com/clevertap/android/sdk/ControllerManager.java:27— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InAppNotificationActivity clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java:48— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Swallowed exception (caught, then discarded) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:93— `catch (Throwable)` 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:589— `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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressStyle.kt:471— `catch (t: Throwable)` 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java:44— `catch (Throwable)` 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java:58— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3474— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:147— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:225— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:103— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:241— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:296— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:319— `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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:340— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/ManifestInfo.java:361— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:417— `catch (Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/NdFCManager.kt:117— `catch (t: Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/ColorUtils.kt:26— `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) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/ColorUtils.kt:38— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:332— `catch (t: Throwable)` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PIPConfigFactory.kt:194— `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) clevertap-core/src/main/java/com/clevertap/android/sdk/gif/GifDecoder.java:779— `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) clevertap-core/src/main/java/com/clevertap/android/sdk/gif/GifHeaderParser.java:115— `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) clevertap-core/src/main/java/com/clevertap/android/sdk/gif/GifImageView.java:213— `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.
TodoComment clevertap-core/src/test/java/com/clevertap/android/sdk/CleverTapInstanceConfigTest.kt:176— // todo : fails and was identified in the UT — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/UtilsTest.kt:196— // TODO : can't get JSONException to fire — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/UtilsTest.kt:243— // TODO write what remaining cases ?? — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/UtilsTest.kt:594— //todo : giving NPE // @ piyush — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/task/PostAsyncSafelyExecutorTest.kt:53— //TODO — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/network/NetworkManagerTest.kt:43— // todo: can verify without manipulation of shared prefs; can improve later. — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/inapp/InAppControllerTest.kt:1149— // TODO verify when multiple inApps are added to the queue only the first is discarded — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/inapp/InAppControllerTest.kt:1424— //TODO verify next in-apps will not be shown after a ttl expired in-app — 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 clevertap-core/src/test/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFragmentTest.kt:48— // todo - check InAppController companion object mock to fix issue at root cause — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3327— //todo : replace with variables — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3340— //todo: replace with variables — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3515— // todo : pass manifest info here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3518— // todo : check if these re-assignments are needed, already added in manifest parsing — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3611— //TODO: start synchronizing entire flow from here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment clevertap-core/src/main/java/com/clevertap/android/sdk/ManifestInfo.java:17— // todo lp Remove context dependency from here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapFactory.kt:104— // todo this needs to be fixed with kotlin usage+using kotlin testing libs — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/task/Task.java:180— // TODO This method does not set state of the task correctly. — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/store/preference/CTPreference.kt:194— // todo : can cache context.getSharedPreferences call — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/login/LoginInfoProvider.java:39— // todo Check if this constructor is needed at all or is it better to have static methods in a different class — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.kt:425— // todo pass correct url — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/delay/InActionStorageStrategy.kt:11— //TODO: check synchronization and map usage — 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 clevertap-core/src/main/java/com/clevertap/android/sdk/cryption/CryptHandler.kt:99— // todo remove this method and use repo in use case — 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.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/CallbackManager.java:307— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1029— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3397— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3419— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:136— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:163— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/response/ConsoleResponse.java:38— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/response/ConsoleResponse.java:52— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/response/MetadataResponse.java:51— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/response/MetadataResponse.java:61— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/response/PushAmpResponse.java:89— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/network/ArpRepo.kt:120— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:486— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventQueueManager.kt:558— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventQueueManager.kt:565— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventQueueManager.kt:578— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
ClassTooLong: CleverTapAPI clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:103— ClassTooLong — 1636 significant lines (blank, comment-only and punctuation-only lines excluded), 226 methods. The bar is 400 significant lines; this is 1236 over it, 4.09× 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: InAppController clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:72— ClassTooLong — 930 significant lines (blank, comment-only and punctuation-only lines excluded), 66 methods. The bar is 400 significant lines; this is 530 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AnalyticsManager clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:55— ClassTooLong — 760 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 360 over it, 1.90× 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: PushProviders clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:57— ClassTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 261 over it, 1.65× 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: DeviceInfo clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:56— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods. The bar is 400 significant lines; this is 152 over it, 1.38× 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: PushTemplateReceiver clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:47— ClassTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 144 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NetworkManager clevertap-core/src/main/java/com/clevertap/android/sdk/network/NetworkManager.kt:42— ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 77 over it, 1.19× 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: CTInAppNotification clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:19— ClassTooLong — 466 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 66 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CleverTapInstanceConfig clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:29— ClassTooLong — 455 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 400 significant lines; this is 55 over it, 1.14× 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: LocalDataStore clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:48— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 23 over it, 1.06× 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: CTIconMessageViewHolder clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:33— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 9 over it, 1.02× 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: Constants clevertap-core/src/main/java/com/clevertap/android/sdk/Constants.java:12— ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 2 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.
Duplicated block (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt:23— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt:23-30 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:29-36 — 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 (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:23— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:23-30 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.kt:23-30 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.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.
Duplicated block (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:249— clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:249-256 | clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:454-461 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:334— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:334-341 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:318-325 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:334` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:546— clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:546-553 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:79-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:546` 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 (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:478— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:478-485 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:518-525 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:478` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:373— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:373-380 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:401-408 — 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 `clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:373` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/ManifestInfo.java:357— clevertap-core/src/main/java/com/clevertap/android/sdk/ManifestInfo.java:357-364 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:89-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:34— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:34-41 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:36-43 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:34` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewHolder` to `CTCarouselImageViewHolder` in one and `CTCarouselMessageViewHolder` 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:135— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:135-142 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTLocationUpdateReceiver.java:98-105 — 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 (8 lines × 2) sample/src/main/java/com/clevertap/demo/CustomLiveUpdateDemo.kt:81— sample/src/main/java/com/clevertap/demo/CustomLiveUpdateDemo.kt:81-88 | sample/src/main/java/com/clevertap/demo/ProgressLiveUpdateDemo.kt:366-373 — 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.
MethodTooLong: CleverTapFactory.getCoreState clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapFactory.kt:97— MethodTooLong — getCoreState runs 488 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 388 over it, 4.88× 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: CTIconMessageViewHolder.configureWithMessage clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:78— MethodTooLong — configureWithMessage runs 377 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 277 over it, 3.77× 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: CTSimpleMessageViewHolder.configureWithMessage clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:70— MethodTooLong — configureWithMessage runs 351 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 251 over it, 3.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InAppController.showInApp clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1344— MethodTooLong — showInApp runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: PushTemplateReceiver.handleRatingNotification clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:379— MethodTooLong — handleRatingNotification runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PendingIntentFactory.getPendingIntent clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/PendingIntentFactory.kt:102— MethodTooLong — getPendingIntent runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× 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: CTInAppNativeHalfInterstitialFragment.onCreateView clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:38— MethodTooLong — onCreateView runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PushProviders.triggerNotification clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:790— MethodTooLong — triggerNotification runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× 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: TemplateRenderer.renderNotification clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:100— MethodTooLong — renderNotification runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: Companion.buildCheckersForTemplateData clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/validators/ValidatorFactory.kt:197— MethodTooLong — buildCheckersForTemplateData runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
FileTooLong: sdk/CleverTapAPI.java clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java— FileTooLong — 1730 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: CleverTapAPI (103-4128). The bar is 500 significant lines; this is 1230 over it, 3.46× 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: inapp/InAppController.kt clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt— FileTooLong — 998 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: InAppController (72-1676). The bar is 500 significant lines; this is 498 over it, 2.00× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: sdk/AnalyticsManager.java clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java— FileTooLong — 807 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: AnalyticsManager (55-1334). The bar is 500 significant lines; this is 307 over it, 1.61× 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: pushnotification/PushProviders.kt clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt— FileTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: PushProviders (57-1205). The bar is 500 significant lines; this is 215 over it, 1.43× 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: sdk/CleverTapFactory.kt clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapFactory.kt— FileTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 100 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sdk/DeviceInfo.java clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: DeviceInfo (56-995). The bar is 500 significant lines; this is 99 over it, 1.20× 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: pushtemplates/PushTemplateReceiver.java clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: PushTemplateReceiver (47-832). The bar is 500 significant lines; this is 87 over it, 1.17× 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: network/NetworkManager.kt clevertap-core/src/main/java/com/clevertap/android/sdk/network/NetworkManager.kt— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: NetworkManager (42-811). The bar is 500 significant lines; this is 16 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: pushtemplates/TemplateDataFactory.kt clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateDataFactory.kt— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×8
Edited copy of a member (10 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:105— clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:105-114 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/Logger.java:41-50 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:170— clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:170-179 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/Logger.java:108-117 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:758— clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:758-768 | clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:783-792 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:541— clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:541-553 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:77-86 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1994— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1994-2003 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:2032-2041 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:482— clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:482-493 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:265-274 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:194— clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:194-203 | clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:285-294 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/EventDAOImpl.kt:174— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/EventDAOImpl.kt:174-183 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/PushNotificationDAOImpl.kt:114-125 — 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 (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:76— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:76-84 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:135-143 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFullHtmlFragment.kt:152— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFullHtmlFragment.kt:152-160 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialHtmlFragment.kt:74-82 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:181— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:181-189 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:169-177 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlFooterFragment.kt:15— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlFooterFragment.kt:15-23 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlHeaderFragment.kt:15-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.
Duplicated block (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:337— clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:337-345 | clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:347-355 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:337` 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 (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:670— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:670-678 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:786-795 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:670` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:829— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:829-837 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:893-901 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:829` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:543— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:543-551 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:564-572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:562` calls `handleViewPagerClick` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:541` 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 (20 corresponding lines) · ×7
Edited copy of a member (20 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:155— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:155-175 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:182-201 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFullFragment.kt:107— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFullFragment.kt:107-127 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFullFragment.kt:165-184 — 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:60— clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:60-88 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:102-121 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:152— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:152-171 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:142-161 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:278— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:278-297 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:300-320 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:258— clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:258-277 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:341-362 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:112— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:112-131 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:102-121 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:380— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:380-389 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/PushNotificationDAOImpl.kt:147-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:111— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:111-120 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:100-109 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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 (10 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:473— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:473-482 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:648-657 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:473` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:116— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:116-125 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:237-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:116` 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 (10 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:251— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:251-260 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java: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. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:251` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:64— clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:64-73 | clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:98-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:78— clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:78-88 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:112-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:78` 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, `clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:98` calls `SuppressWarnings` and `clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:131` 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 (26 corresponding lines) · ×6
Edited copy of a member (26 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:147— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:147-173 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:136-161 — 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:562— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:562-589 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:592-617 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt:49— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt:49-74 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialNativeFragment.kt:51-77 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/UserProfileDAOImpl.kt:24— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/UserProfileDAOImpl.kt:24-49 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:29-57 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:168— clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:168-194 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:197-222 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataValidator.kt:129— clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataValidator.kt:129-154 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataValidator.kt:160-187 — 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 (18 corresponding lines) · ×6
Edited copy of a member (18 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/leanplum/CTWrapper.kt:49— clevertap-core/src/main/java/com/clevertap/android/sdk/leanplum/CTWrapper.kt:49-66 | clevertap-core/src/main/java/com/clevertap/android/sdk/leanplum/CTWrapper.kt:79-97 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:71— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:71-88 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:130-147 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/renderer/GifRenderer.kt:136— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/renderer/GifRenderer.kt:136-157 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/renderer/ImageRenderer.kt:93-110 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:92— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:92-109 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:81-98 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/PushNotificationDAOImpl.kt:127— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/PushNotificationDAOImpl.kt:127-145 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/UninstallTimestampDAOImpl.kt:40-57 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/PushNotificationDAOImpl.kt:87— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/PushNotificationDAOImpl.kt:87-111 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/UninstallTimestampDAOImpl.kt:20-37 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×6
Edited copy of a member (14 corresponding lines) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressPayloadParser.kt:18— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressPayloadParser.kt:18-31 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressPayloadParser.kt:34-53 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java:85— clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java:85-98 | clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java:290-307 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:548— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:548-562 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:62-75 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/CTFcmMessageHandler.java:69— clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/CTFcmMessageHandler.java:69-83 | clevertap-hms/src/main/java/com/clevertap/android/hms/CTHmsMessageHandler.java: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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/DelayedLegacyInAppDAO.kt:121— clevertap-core/src/main/java/com/clevertap/android/sdk/db/DelayedLegacyInAppDAO.kt:121-136 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/DisplayedInAppDAOImpl.kt:81-94 — 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) sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenListAdapter.kt:29— sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenListAdapter.kt:29-42 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenListAdapter.kt:60-78 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×6
Edited copy of a member (12 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:745— clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:745-756 | clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:770-781 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:224— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:224-235 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:253-265 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt:36— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt:36-47 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialNativeFragment.kt:37-49 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3877— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3877-3889 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3928-3939 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.kt:152— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.kt:152-170 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/NdEvaluationManager.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) clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/JsonComparisonUtils.kt:36— clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/JsonComparisonUtils.kt:36-49 | clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/JsonComparisonUtils.kt:55-66 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×6
Edited copy of a member (13 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:80— clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:80-92 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:346-360 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ProfileChangeTracker.kt:35— clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ProfileChangeTracker.kt:35-47 | clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ProfileChangeTracker.kt:62-74 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1816— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1816-1828 | clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/FcmSdkHandlerImpl.java:82-94 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/CoreNotificationRenderer.java:154— clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/CoreNotificationRenderer.java:154-167 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:495-507 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java:434— clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java:434-446 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxActivity.java:298-310 — 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) sample/src/main/java/com/clevertap/demo/ui/main/FileVarsData.kt:98— sample/src/main/java/com/clevertap/demo/ui/main/FileVarsData.kt:98-112 | sample/src/main/java/com/clevertap/demo/ui/main/FileVarsData.kt:117-129 — 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.
Duplicated block (11 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:162— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:162-172 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:106-116 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:162` 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 × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:135— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:135-145 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:125-135 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 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 (11 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:40— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:40-50 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/InAppGifMemoryAccessObjectV1.kt:40-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3623— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3623-3633 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3654-3664 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3623` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3698— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3698-3708 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3759-3769 — 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 (11 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTMessageDAO.java:224— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTMessageDAO.java:224-234 | clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:194-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTMessageDAO.java:224` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:193` calls `getJsonDescription` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTMessageDAO.java:223` 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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×6
Recursive walk over a caller-supplied document has no depth cap clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:132— `convertJSONObjectToHashMap` is not private and takes `JSONObject b` from its caller, and it calls itself at line 132 with a piece of `b` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `convertJSONObjectToHashMap` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:155— `mergeHelper` is not private and takes `Object vars` from its caller, and it calls itself at line 155 with a piece of `vars` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `mergeHelper` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:45— `listToJsonArray` is not private and takes `Iterable<?> list` from its caller, and it recurses at line 45 through `mapToJsonObject` and back with a piece of `list` (and at line 47, line 123, line 125) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `listToJsonArray` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:68— `mapFromJson` is not private and takes `JSONObject object` from its caller, and it recurses at line 68 through `listFromJsonSafe`, `listFromJson` and back with a piece of `object` (and at line 70, line 102, line 104) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `mapFromJson` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap clevertap-core/src/main/java/com/clevertap/android/sdk/utils/JsonFlattener.kt:30— `JsonFlattener.flatten` is public, takes a document from its caller (line 9) and hands it to `JsonFlattener.flattenInternal`, which calls itself at line 30 with a piece of `json` — the function is not `tailrec`, so every call is a real frame — and nowhere in `JsonFlattener.flattenInternal` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `JsonFlattener.flattenInternal` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
Recursive walk over a caller-supplied document has no depth cap clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/CustomTemplate.kt:227— `mapArgument` is public and takes `value: Map<String, Any>` from its caller, and it calls itself at line 227 with a piece of `value` — the function is not `tailrec`, so every call is a real frame — and nowhere in `mapArgument` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `mapArgument` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTLocalInApp.kt:69— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTLocalInApp.kt:69-79 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTLocalInApp.kt:85-95 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:250— clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:250-260 | clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:313-328 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:218— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt:218-231 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:329-339 — 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) sample/src/main/java/com/clevertap/demo/MyApplication.kt:286— sample/src/main/java/com/clevertap/demo/MyApplication.kt:286-296 | sample/src/main/java/com/clevertap/demo/WebViewActivity.kt:39-52 — 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) sample/src/main/java/com/clevertap/demo/CustomLiveUpdateDemo.kt:42— sample/src/main/java/com/clevertap/demo/CustomLiveUpdateDemo.kt:42-55 | sample/src/main/java/com/clevertap/demo/ProgressLiveUpdateDemo.kt:120-130 — 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 (13 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:209— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:209-221 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:283-295 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:209` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:222` calls `put`, `toString` and `clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:296` 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 × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:182— clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:182-194 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:210-222 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:182` 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/checkers/IntSizeChecker.kt:8— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/checkers/IntSizeChecker.kt:8-20 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/checkers/LongSizeChecker.kt:8-20 — 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceAPI.java:202— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceAPI.java:202-214 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceAPI.java:270-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. 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) sample/src/main/java/com/clevertap/demo/LiveUpdatePayloadActivity.kt:125— sample/src/main/java/com/clevertap/demo/LiveUpdatePayloadActivity.kt:125-137 | sample/src/main/java/com/clevertap/demo/ui/inbox/CustomInboxComposeActivity.kt:35-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `sample/src/main/java/com/clevertap/demo/LiveUpdatePayloadActivity.kt:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:61— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:61-67 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.kt:62-68 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:236— clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:236-242 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:266-272 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:236` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:187— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:187-193 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:262-268 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:187` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:414— clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:414-420 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java:55-61 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:226— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:226-232 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:234-240 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPCompactView.kt:200— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPCompactView.kt:200-205 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPExpandedView.kt:218-223 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:116— clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:116-122 | clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/OperationHandler.kt:140-145 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.kt:670— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.kt:670-675 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/NdEvaluationManager.kt:284-289 — 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/AutoCarouselStyle.kt:31— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/AutoCarouselStyle.kt:31-36 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ManualCarouselStyle.kt:42-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 `clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/AutoCarouselStyle.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. 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:54— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:54-59 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:56-61 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Hotspot: clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1344— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in InAppController.showInApp at line 1344. 1 of those changes was a fix/bug commit, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 20:38:09 +05:30' --until='2026-11-10 20:38:09 +05:30' --full-history --no-merges -- clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java:127— clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in InAppNotificationActivity.setUp at line 127. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 20:38:09 +05:30' --until='2026-11-10 20:38:09 +05:30' --full-history --no-merges -- clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:96— clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PushProviders._createNotification at line 96. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 20:38:09 +05:30' --until='2026-11-10 20:38:09 +05:30' --full-history --no-merges -- clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:100— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TemplateRenderer.renderNotification at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 20:38:09 +05:30' --until='2026-11-10 20:38:09 +05:30' --full-history --no-merges -- clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×4
Edited copy of a member (21 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:53— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:53-75 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:47-67 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/FileUtils.java:33— clevertap-core/src/main/java/com/clevertap/android/sdk/utils/FileUtils.java:33-53 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/FileUtils.java:24-44 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:544— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:544-564 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:55-77 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/DelayedLegacyInAppDAO.kt:139— clevertap-core/src/main/java/com/clevertap/android/sdk/db/DelayedLegacyInAppDAO.kt:139-159 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:145-165 — 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 (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:256— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:256-270 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:296-310 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:211— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:211-225 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:228-242 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:187— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:187-203 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:236-250 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/leanplum/CTWrapper.kt:24— clevertap-core/src/main/java/com/clevertap/android/sdk/leanplum/CTWrapper.kt:24-39 | clevertap-core/src/main/java/com/clevertap/android/sdk/leanplum/CTWrapper.kt:102-116 — 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 (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/NumberOperationUtils.kt:22— clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/NumberOperationUtils.kt:22-29 | clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/NumberOperationUtils.kt:44-51 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:263— clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:263-270 | clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:471-479 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:191— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:191-198 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:179-186 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PIPInAppCallbacksBridge.kt:36— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PIPInAppCallbacksBridge.kt:36-48 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFragment.kt:171-178 — 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.
Change coupling: CTFeatureFlagsController.java ↔ CTProductConfigController.java clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java:1— `clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java` change together 76% of the time (19 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 19 shared commits counted here, the most recent 3 are `3c7abe6c` fix(SDK-5461): Replace printStackTrace() with Logger methods (#942); `bec9f5cf` [SDK-2466] mark methods , classes and variables as deprecated part 1; `89efc430` task(verbose_log): Reinitialising product config & Feature Flag contr… — run `git show` on any of them.
Change coupling: CleverTapAPI.java ↔ SessionManager.java clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1— `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/SessionManager.java` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `aa507fbc` Multi-triggers updates (#709); `b2f4e3b2` feat(multi_triggers) : deprecate getPreviousVisitTime() in favor of g…; `718e2a16` task(TDD): add unit tests for processPushNotificationViewedEvent() an… — run `git show` on any of them.
Change coupling: FetchVariablesResponse.java ↔ VarCache.java clevertap-core/src/main/java/com/clevertap/android/sdk/response/FetchVariablesResponse.java:1— `clevertap-core/src/main/java/com/clevertap/android/sdk/response/FetchVariablesResponse.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/variables/VarCache.java` 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 `1f6a9e4a` task(SDK-5380): adds A/B test variants support; `d38c72d9` Comment hardcoded server response. Fix naming of PE public interface.…; `40bcc38f` [SDK-2422] all things working code + sample (at that commit the file was still `clevertap-core/src/main/java/com/clevertap/android/sdk/response/RequestVariablesResponse.java`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3613— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3613-3642 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3646-3669 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:254— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:254-277 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:304-330 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/network/api/CtApi.kt:188— clevertap-core/src/main/java/com/clevertap/android/sdk/network/api/CtApi.kt:188-211 | clevertap-core/src/main/java/com/clevertap/android/sdk/network/api/CtApi.kt:213-244 — 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) · ×3
Edited copy of a member (17 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:56— clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:56-78 | clevertap-core/src/main/java/com/clevertap/android/sdk/variables/JsonUtil.java:95-111 — 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceFactory.java:23— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceFactory.java:23-39 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTLocationFactory.java:23-43 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/StoreRegistryInAppQueue.kt:99— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/StoreRegistryInAppQueue.kt:99-115 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/StoreRegistryInAppQueue.kt:124-141 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1543— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1543-1560 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:2283-2298 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppWebView.kt:153— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppWebView.kt:153-168 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppWebView.kt:172-187 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:89— clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:89-104 | clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:134-152 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3689— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3689-3712 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3755-3773 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:246— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:246-266 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:341-359 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4065— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4065-4083 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4094-4112 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×3
Edited copy of a member (23 corresponding lines) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:276— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:276-298 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:300-324 — 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:133— clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:133-155 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleLocationAdapter.java:248-273 — 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/media/TemplateRepository.kt:32— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/media/TemplateRepository.kt:32-55 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/media/TemplateRepository.kt:57-79 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×3
Edited copies of one member (3 members, 14+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/ManifestValidator.java:107— clevertap-core/src/main/java/com/clevertap/android/sdk/validation/ManifestValidator.java:107-121 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/ManifestValidator.java:124-138 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/ManifestValidator.java:141-154 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryV2.kt:51— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryV2.kt:51-64 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/InAppGifMemoryV1.kt:52-65 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/InAppImageMemoryV1.kt:51-64 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:936— sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:936-949 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:951-965 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:967-982 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:248— clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:248-256 | clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:453-461 — 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:148— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:148-157 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:159-167 — 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:243— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:243-252 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/NdStore.kt:80-88 — 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 (23 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:372— clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:372-394 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:429-451 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:372` 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 (23 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:66— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:66-88 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:56-78 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Player` names `androidx.media3.common.Player` in one and `com.google.android.exoplayer2.Player` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:103— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:103-125 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:125-147 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:138— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:138-156 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:121-139 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:138` 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 (19 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/network/api/CtApi.kt:189— clevertap-core/src/main/java/com/clevertap/android/sdk/network/api/CtApi.kt:189-207 | clevertap-core/src/main/java/com/clevertap/android/sdk/network/api/CtApi.kt:214-232 — 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 (19 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:46— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:46-64 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:36-54 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt: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 first that the copies are not typed on the same thing: `AdaptiveTrackSelection` names `androidx.media3.exoplayer.trackselection.AdaptiveTrackSelection` in one and `com.google.android.exoplayer2.trackselection.AdaptiveTrackSelection` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt:93— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt:93-107 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverImageFragment.kt:57-71 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt:93` 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 (15 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/FileStore.kt:7— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/FileStore.kt:7-21 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppAssetsStore.kt:15-29 — 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 (15 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:512— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:512-526 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:591-605 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:512` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:590` calls `setGroup` and `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:511` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:63— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:63-74 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/InAppGifMemoryAccessObjectV1.kt:64-75 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:63` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:117— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:117-128 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:107-118 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 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. Note first that the copies are not typed on the same thing: `AspectRatioFrameLayout` names `androidx.media3.ui.AspectRatioFrameLayout` in one and `com.google.android.exoplayer2.ui.AspectRatioFrameLayout` 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) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4067— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4067-4078 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4096-4107 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:4067` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPCompactView.kt:261— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPCompactView.kt:261-265 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPExpandedView.kt:262-266 — 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 (5 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPCompactView.kt:267— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPCompactView.kt:267-271 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/view/PIPExpandedView.kt:268-272 — 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 (5 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:175— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:175-179 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:163-167 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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.
D4 · Code Duplication· Edited copy of a member (58 corresponding lines) · ×2
Edited copy of a member (58 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:87— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:87-144 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:104-166 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (58 corresponding lines) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceReceiver.java:33— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceReceiver.java:33-90 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTLocationUpdateReceiver.java:39-96 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×2
Edited copy of a member (28 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1808— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:1808-1835 | clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/FcmSdkHandlerImpl.java:73-101 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:208— clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:208-236 | clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxPendingActionsDAO.kt:282-309 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:372— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:372-397 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:400-421 — 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) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceReceiver.java:47— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceReceiver.java:47-71 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTLocationUpdateReceiver.java:52-73 — 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.
Duplicated block (22–23 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:148— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:148-170 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:137-158 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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 (22–23 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:538— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:538-559 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:1286-1308 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:538` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:158— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:158-171 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:148-161 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:158` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `MediaItem` names `androidx.media3.common.MediaItem` in one and `com.google.android.exoplayer2.MediaItem` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapInputStreamReader.kt:63— clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapInputStreamReader.kt:63-77 | clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/GzipBitmapInputStreamReader.kt:61-74 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapInputStreamReader.kt:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlCoverFragment.kt:30— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlCoverFragment.kt:30-40 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlHalfInterstitialFragment.kt:16-26 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlInterstitialFragment.kt:16-26 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlCoverFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppHtmlHalfInterstitialFragment.kt` as WHOLE FILES: 90% 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. 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 × 3) clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:133— clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:133-143 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:296-306 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:344-354 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:445— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:445-455 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:522-530 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:601-610 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:643-652 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:445` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:82— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:82-90 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:102-110 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceReceiver.java:50-58 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTLocationUpdateReceiver.java:57-65 — there are 4 copies across 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:82` 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.
CTIconMessageViewHolder.configureWithMessage (cyclomatic 53) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:78— CTIconMessageViewHolder.configureWithMessage has cyclomatic complexity 53 (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.
CTSimpleMessageViewHolder.configureWithMessage (cyclomatic 49) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:70— CTSimpleMessageViewHolder.configureWithMessage has cyclomatic complexity 49 (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.
InAppController.showInApp (cyclomatic 41) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1344— InAppController.showInApp has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PendingIntentFactory.getPendingIntent (cyclomatic 32) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/PendingIntentFactory.kt:102— PendingIntentFactory.getPendingIntent has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CTInboxMessageContent.initWithJSON (cyclomatic 31) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:479— CTInboxMessageContent.initWithJSON has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PushProviders.triggerNotification (cyclomatic 30) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:790— PushProviders.triggerNotification has cyclomatic complexity 30 (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.
TemplateRenderer.renderNotification (cyclomatic 28) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:100— TemplateRenderer.renderNotification has cyclomatic complexity 28 (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.
CTInAppNotification.configureWithJson (cyclomatic 26) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:384— CTInAppNotification.configureWithJson has cyclomatic complexity 26 (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.
CleverTapInstanceConfig.<init> (cyclomatic 26) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:246— CleverTapInstanceConfig.<init> has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CleverTapDisplayUnitContent.toContent (cyclomatic 25) clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:285— CleverTapDisplayUnitContent.toContent 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.
CTInAppNotification.legacyConfigureWithJson (cyclomatic 24) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:488— CTInAppNotification.legacyConfigureWithJson 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.
CTInboxMessage.<init> (cyclomatic 24) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessage.java:74— CTInboxMessage.<init> 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.
INotificationRenderer.setActionButtons (cyclomatic 23) REDACTED:37— INotificationRenderer.setActionButtons has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PushTemplateReceiver.handleRatingNotification (cyclomatic 23) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:379— PushTemplateReceiver.handleRatingNotification has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CTInAppNativeHalfInterstitialFragment.onCreateView (cyclomatic 22) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:38— CTInAppNativeHalfInterstitialFragment.onCreateView has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Utils.getDeviceNetworkType (cyclomatic 22) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:178— Utils.getDeviceNetworkType has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
NestedJsonBuilder.setValueRecursive (cyclomatic 20) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/NestedJsonBuilder.kt:90— NestedJsonBuilder.setValueRecursive has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventDataNormalizer.cleanMapInternal (cyclomatic 20) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:103— EventDataNormalizer.cleanMapInternal has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CTJsonConverter.from (cyclomatic 19) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:64— CTJsonConverter.from has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CTVariableUtils.mergeHelper (cyclomatic 19) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:118— CTVariableUtils.mergeHelper has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Parser.parseVariablesHelper (cyclomatic 19) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/Parser.java:83— Parser.parseVariablesHelper has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PushProviders._createNotification (cyclomatic 18) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:96— PushProviders._createNotification has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventQueueManager.pushBasicProfile (cyclomatic 17) clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventQueueManager.kt:373— EventQueueManager.pushBasicProfile has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CTInAppNotification.validateNotifBundle (cyclomatic 17) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:571— CTInAppNotification.validateNotifBundle has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CTInboxController.processV2Response (cyclomatic 17) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:314— CTInboxController.processV2Response has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LoginController._onUserLogin (cyclomatic 17) clevertap-core/src/main/java/com/clevertap/android/sdk/login/LoginController.java:236— LoginController._onUserLogin has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CleverTapAPI.onActivityCreated (cyclomatic 17) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3373— CleverTapAPI.onActivityCreated has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InAppNotificationActivity.setUp (cyclomatic 17) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java:127— InAppNotificationActivity.setUp has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PushTemplateReceiver.setKeysFromDashboard (cyclomatic 17) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:798— PushTemplateReceiver.setKeysFromDashboard has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TemplateRenderer.createActionButtonPendingIntent (cyclomatic 16) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:402— TemplateRenderer.createActionButtonPendingIntent has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CTInboxBaseMessageViewHolder.addMediaPlayer (cyclomatic 16) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxBaseMessageViewHolder.java:77— CTInboxBaseMessageViewHolder.addMediaPlayer has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CTInboxListViewFragment.refreshList (cyclomatic 16) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:265— CTInboxListViewFragment.refreshList has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PushGeofenceEventTask.pushGeofenceEvents (cyclomatic 16) clevertap-geofence/src/main/java/com/clevertap/android/geofence/PushGeofenceEventTask.java:126— PushGeofenceEventTask.pushGeofenceEvents has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Repeated repair: clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/preview/PushPreviewKey.kt clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/preview/PushPreviewKey.kt:236— clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/preview/PushPreviewKey.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is Lexer.readEscape at line 236), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(SDK-6282): close five review findings in the preview store and key”; “fix(SDK-6282): canonicalise preview JSON with a strict depth-bounded reader instead of org.json”; “fix(SDK-6282): refuse hostile preview JSON before parsing so a tap cannot crash the app”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 20:38:09 +05:30' --until='2026-11-10 20:38:09 +05:30' --full-history --no-merges -- clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/preview/PushPreviewKey.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
CTIconMessageViewHolder.configureWithMessage (cognitive 119) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:78— CTIconMessageViewHolder.configureWithMessage has cognitive complexity 119 (threshold 15). Drivers by points: if/else 43 (77 pts), error handling 13 (39 pts), match/switch 2 (3 pts) (nesting depth added 61). 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.
CTSimpleMessageViewHolder.configureWithMessage (cognitive 112) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:70— CTSimpleMessageViewHolder.configureWithMessage has cognitive complexity 112 (threshold 15). Drivers by points: if/else 40 (73 pts), error handling 11 (36 pts), match/switch 2 (3 pts) (nesting depth added 59). 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.
NestedJsonBuilder.setValueRecursive (cognitive 62) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/NestedJsonBuilder.kt:90— NestedJsonBuilder.setValueRecursive has cognitive complexity 62 (threshold 15). Drivers by points: if/else 22 (59 pts), boolean chains 2, match/switch 1 (nesting depth added 37). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PushGeofenceEventTask.pushGeofenceEvents (cognitive 55) clevertap-geofence/src/main/java/com/clevertap/android/geofence/PushGeofenceEventTask.java:126— PushGeofenceEventTask.pushGeofenceEvents has cognitive complexity 55 (threshold 15). Drivers by points: if/else 12 (43 pts), error handling 2 (7 pts), loops 2 (5 pts) (nesting depth added 39). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
INotificationRenderer.setActionButtons (cognitive 52) REDACTED:37— INotificationRenderer.setActionButtons has cognitive complexity 52 (threshold 15). Drivers by points: if/else 14 (31 pts), error handling 5 (14 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PushProviders.triggerNotification (cognitive 51) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:790— PushProviders.triggerNotification has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (32 pts), error handling 5 (13 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 21). 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.
CTInboxMessageContent.initWithJSON (cognitive 50) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:479— CTInboxMessageContent.initWithJSON has cognitive complexity 50 (threshold 15). Drivers by points: ternaries 17 (33 pts), if/else 8 (12 pts), boolean chains 4, error handling 1 (nesting depth added 20). 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.
CTInboxMessage.<init> (cognitive 42) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessage.java:74— CTInboxMessage.<init> has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 12 (17 pts), if/else 6 (15 pts), loops 3 (8 pts), boolean chains 1, error handling 1 (nesting depth added 19). 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.
CleverTapDisplayUnitContent.toContent (cognitive 41) clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:285— CleverTapDisplayUnitContent.toContent has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 16 (30 pts), if/else 7 (10 pts), error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PushTemplateReceiver.handleRatingNotification (cognitive 39) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:379— PushTemplateReceiver.handleRatingNotification has cognitive complexity 39 (threshold 15). Drivers by points: if/else 30 (36 pts), error handling 2 (3 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CTInAppNotification.legacyConfigureWithJson (cognitive 38) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:488— CTInAppNotification.legacyConfigureWithJson has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 8, match/switch 1 (3 pts), error handling 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventQueueManager.pushBasicProfile (cognitive 36) clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventQueueManager.kt:373— EventQueueManager.pushBasicProfile has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 5 (14 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 19). 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.
InAppController.showInApp (cognitive 33) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1344— InAppController.showInApp has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 5, error handling 2 (4 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CTVariableUtils.mergeHelper (cognitive 33) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:118— CTVariableUtils.mergeHelper has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 6 (10 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CTInAppNativeHalfInterstitialFragment.onCreateView (cognitive 32) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:38— CTInAppNativeHalfInterstitialFragment.onCreateView has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 7, loops 1 (2 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PushTemplateReceiver.handleInputBoxNotification (cognitive 31) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:286— PushTemplateReceiver.handleInputBoxNotification has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (24 pts), error handling 1 (4 pts), boolean chains 3 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CTInAppNotification.configureWithJson (cognitive 29) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:384— CTInAppNotification.configureWithJson has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 2 (4 pts), boolean chains 3, error handling 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CTInAppNotification.writeToParcel (cognitive 28) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:256— CTInAppNotification.writeToParcel has cognitive complexity 28 (threshold 15). Drivers by points: if/else 28. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TemplateRenderer.renderNotification (cognitive 28) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:100— TemplateRenderer.renderNotification has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CTInboxBaseMessageViewHolder.addMediaPlayer (cognitive 28) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxBaseMessageViewHolder.java:77— CTInboxBaseMessageViewHolder.addMediaPlayer has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoginController._onUserLogin (cognitive 28) clevertap-core/src/main/java/com/clevertap/android/sdk/login/LoginController.java:236— LoginController._onUserLogin has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), error handling 2 (4 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.parseVariablesHelper (cognitive 28) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/Parser.java:83— Parser.parseVariablesHelper has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (23 pts), ternaries 1 (3 pts), error handling 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CleverTapInstanceConfig.<init> (cognitive 28) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java:246— CleverTapInstanceConfig.<init> has cognitive complexity 28 (threshold 15). Drivers by points: if/else 23 (25 pts), loops 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CTInboxController.processV2Response (cognitive 27) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxController.java:314— CTInboxController.processV2Response has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TemplateRenderer.createActionButtonPendingIntent (cognitive 26) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:402— TemplateRenderer.createActionButtonPendingIntent has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (15 pts), error handling 4 (8 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DefaultXmlParser.getDefaultsFromXmlParser (cognitive 26) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/DefaultXmlParser.java:52— DefaultXmlParser.getDefaultsFromXmlParser has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (8 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppResponseAdapter.fetchMediaUrls (cognitive 23) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/data/InAppResponseAdapter.kt:136— InAppResponseAdapter.fetchMediaUrls has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 2 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EventDataNormalizer.cleanMapInternal (cognitive 23) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:103— EventDataNormalizer.cleanMapInternal has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CTJsonConverter.from (cognitive 23) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:64— CTJsonConverter.from has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (18 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PushProviders._createNotification (cognitive 22) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/PushProviders.kt:96— PushProviders._createNotification has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppNotificationActivity.setUp (cognitive 22) clevertap-core/src/main/java/com/clevertap/android/sdk/InAppNotificationActivity.java:127— InAppNotificationActivity.setUp has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 2, error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TemplateRenderer.getActionButtons (cognitive 21) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:357— TemplateRenderer.getActionButtons has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 2 (7 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgressTrackRenderer.ensureContrast (cognitive 21) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressTrackRenderer.kt:124— ProgressTrackRenderer.ensureContrast has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CleverTapAPI.onActivityCreated (cognitive 20) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3373— CleverTapAPI.onActivityCreated has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 4 (5 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
2.run (cognitive 20) clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:582— 2.run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), error handling 2 (3 pts), loops 2 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Utils.cleanupOldGIFs (cognitive 20) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:353— Utils.cleanupOldGIFs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InAppController.inAppNotificationActionTriggered (cognitive 19) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:325— InAppController.inAppNotificationActionTriggered has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProductConfigSettings.setARPValue (cognitive 19) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:201— ProductConfigSettings.setARPValue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (13 pts), error handling 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AnalyticsManager.pushInboxMessageStateEvent (cognitive 19) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:1259— AnalyticsManager.pushInboxMessageStateEvent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PushTemplateReceiver.handleManualCarouselNotification (cognitive 19) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:189— PushTemplateReceiver.handleManualCarouselNotification has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CTInAppNativeHalfInterstitialImageFragment.onCreateView (cognitive 18) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:35— CTInAppNativeHalfInterstitialImageFragment.onCreateView has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CTInAppNativeInterstitialImageFragment.onCreateView (cognitive 18) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:34— CTInAppNativeInterstitialImageFragment.onCreateView has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ManualCarouselContentView.setupCarouselNavigation (cognitive 18) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/ManualCarouselContentView.kt:116— ManualCarouselContentView.setupCarouselNavigation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
3.call (cognitive 18) clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java:228— 3.call has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CTInboxListViewFragment.refreshList (cognitive 18) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:265— CTInboxListViewFragment.refreshList has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
CTVariableUtils.convertFlatMapToNestedMaps (cognitive 18) clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:75— CTVariableUtils.convertFlatMapToNestedMaps has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Utils.getEventPropertiesFromExtras (cognitive 18) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:372— Utils.getEventPropertiesFromExtras has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CTInAppNotification.validateNotifBundle (cognitive 17) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt:571— CTInAppNotification.validateNotifBundle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DisplayUnitResponse.appLaunchedWithinWhenLimits (cognitive 17) clevertap-core/src/main/java/com/clevertap/android/sdk/response/DisplayUnitResponse.kt:310— DisplayUnitResponse.appLaunchedWithinWhenLimits has cognitive complexity 17 (threshold 15). Drivers by points: error handling 5 (8 pts), if/else 7 (8 pts), loops 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TemplateRenderer.setSound (cognitive 17) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/TemplateRenderer.kt:306— TemplateRenderer.setSound has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgressTrackRenderer.layout (cognitive 17) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ProgressTrackRenderer.kt:157— ProgressTrackRenderer.layout has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CTInboxListViewFragment.handleClick (cognitive 17) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxListViewFragment.java:516— CTInboxListViewFragment.handleClick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CTProductConfigController.getStoredValues (cognitive 17) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:723— CTProductConfigController.getStoredValues has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 3 (7 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreNotificationRenderer.setSound (cognitive 17) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/CoreNotificationRenderer.java:228— CoreNotificationRenderer.setSound has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeviceInfo.fetchGoogleAdID (cognitive 17) clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:828— DeviceInfo.fetchGoogleAdID has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Utils.deleteImageFromStorage (cognitive 17) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/Utils.java:636— Utils.deleteImageFromStorage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CleverTapDisplayUnit.getKeyValues (cognitive 16) clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnit.java:319— CleverTapDisplayUnit.getKeyValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 1 (3 pts), error handling 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CTMessageDAO.initWithJSON (cognitive 16) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTMessageDAO.java:191— CTMessageDAO.initWithJSON has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 3 (4 pts), loops 1 (3 pts), error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
5.call (cognitive 16) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:481— 5.call has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PushAmpResponse.processResponse (cognitive 16) clevertap-core/src/main/java/com/clevertap/android/sdk/response/PushAmpResponse.java:49— PushAmpResponse.processResponse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 2 (4 pts), loops 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
1.run (cognitive 16) clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:492— 1.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PushTemplateReceiver.setKeysFromDashboard (cognitive 16) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:798— PushTemplateReceiver.setKeysFromDashboard has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Near-duplicate member pair (363 shared lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:79— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:79-510 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:71-467 — These two members are variants of one another: 363 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:365— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:365-400 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:423-455 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:475-530 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:554-610 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:625-652 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:665-689 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:702-729 — These 7 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 7 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 7 times.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:36— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:36-109 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.kt:36-110 — 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 copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:253— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:253-298 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:360-400 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:45— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerHandle.kt:45-88 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3Handle.kt:35-78 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:115— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:115-157 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/CTProductConfigController.java:604-641 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:140— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:140-185 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:196-235 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:116— clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:116-142 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:226-254 | clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt:258-284 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/renderer/GifRenderer.kt:39— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/renderer/GifRenderer.kt:39-78 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/pipsdk/internal/renderer/ImageRenderer.kt:32-67 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/response/FeatureFlagResponse.java:27— clevertap-core/src/main/java/com/clevertap/android/sdk/response/FeatureFlagResponse.java:27-57 | clevertap-core/src/main/java/com/clevertap/android/sdk/response/ProductConfigResponse.java:35-67 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:364— clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:364-405 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:420-468 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/network/ArpRepo.kt:85— clevertap-core/src/main/java/com/clevertap/android/sdk/network/ArpRepo.kt:85-127 | clevertap-core/src/main/java/com/clevertap/android/sdk/network/ArpRepo.kt:133-166 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:207— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:207-236 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:403-442 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:636— clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:636-661 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceTaskManager.java:37-65 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceTaskManager.java:77-106 — 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.
D4 · Code Duplication· Edited copies of one member (6 members, 17+ corresponding lines) · ×1
Edited copies of one member (6 members, 17+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:132— clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:132-153 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:222-238 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:246-262 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:295-315 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:343-363 | clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:372-388 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:637— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:637-662 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:669-695 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:701-725 — 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, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:59— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/FileMemoryAccessObject.kt:59-74 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/InAppGifMemoryAccessObjectV1.kt:60-75 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/memory/InAppImageMemoryAccessObjectV1.kt:59-74 — 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 (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppAction.kt:80— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppAction.kt:80-93 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotificationButton.kt:59-73 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotificationMedia.kt:71-84 | clevertap-core/src/main/java/com/clevertap/android/sdk/network/DownloadedBitmap.kt:35-48 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:332— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:332-345 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTMessageDAO.java:222-234 | clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:191-204 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:95— clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:95-107 | clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:109-121 | clevertap-core/src/main/java/com/clevertap/android/sdk/utils/CTJsonConverter.java:244-254 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:113— clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:113-125 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:234-246 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:248-260 | clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:270-282 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 16+ corresponding lines) · ×1
Edited copies of one member (6 members, 16+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:182— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:182-198 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:205-220 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:221-236 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:337-353 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:374-390 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/NdStore.kt:45-60 — These 6 members are one piece of code written 6 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 6 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) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxBaseMessageViewHolder.java:244— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxBaseMessageViewHolder.java:244-249 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxBaseMessageViewHolder.java:251-255 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxBaseMessageViewHolder.java:257-263 — 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 (7 members, 8+ corresponding lines) · ×1
Edited copies of one member (7 members, 8+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:114— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:114-121 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:124-131 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:134-141 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:467-474 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:867-874 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:891-898 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:1043-1050 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:144— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:144-154 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:162-172 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:231-241 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:293-303 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 11+ corresponding lines) · ×1
Edited copies of one member (5 members, 11+ corresponding lines) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/ContentView.kt:66— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/ContentView.kt:66-77 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/ContentView.kt:79-90 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/ProductDisplayLinearBigContentView.kt:152-163 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/ProductDisplayLinearBigContentView.kt:168-179 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/VerticalImageBigContentView.kt:50-60 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) clevertap-core/src/main/java/com/clevertap/android/sdk/validation/chargedevent/ChargedEventItemsValidationPipeline.kt:30— clevertap-core/src/main/java/com/clevertap/android/sdk/validation/chargedevent/ChargedEventItemsValidationPipeline.kt:30-51 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataValidationPipeline.kt:31-52 | clevertap-core/src/main/java/com/clevertap/android/sdk/validation/propertykey/EventPropertyKeyValidationPipeline.kt:30-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 4+ corresponding lines) · ×1
Edited copies of one member (6 members, 4+ corresponding lines) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/AutoCarouselStyle.kt:51— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/AutoCarouselStyle.kt:51-54 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/BasicStyle.kt:43-46 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ManualCarouselStyle.kt:65-68 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/TimerStyle.kt:59-62 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/VerticalImageStyle.kt:62-65 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/styles/ZeroBezelStyle.kt:57-60 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
Duplicated block (69–72 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:67— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:67-135 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:62-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:75— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:75-105 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.kt:76-106 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHeaderFragment.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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeFooterFragment.kt:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28–31 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:142— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:142-169 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:55-85 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:142` 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 (26–30 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:171— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:171-196 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:87-116 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialFragment.kt:171` 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 (27–29 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/utils/NestedJsonBuilder.kt:109— clevertap-core/src/main/java/com/clevertap/android/sdk/utils/NestedJsonBuilder.kt:109-137 | clevertap-core/src/main/java/com/clevertap/android/sdk/utils/NestedJsonBuilder.kt:173-199 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/utils/NestedJsonBuilder.kt:173` 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 (27 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:61— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt:61-87 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt:50-76 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/ExoplayerHandle.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/video/inapps/Media3Handle.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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. Note first that the copies are not typed on the same thing: `AdaptiveTrackSelection` names `androidx.media3.exoplayer.trackselection.AdaptiveTrackSelection` in one and `com.google.android.exoplayer2.trackselection.AdaptiveTrackSelection` 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 (25 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:152— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:152-176 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:206-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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:152` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:177` calls `has` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.kt:231` 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 (17–21 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:255— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:255-271 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:305-325 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/store/preference/InAppStore.kt:255` 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 (20 lines × 3) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:643— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:643-662 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:676-695 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:706-725 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:643` 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–17 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/preload/FilePreloaderCoroutine.kt:44— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/preload/FilePreloaderCoroutine.kt:44-60 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/images/preload/FilePreloaderExecutors.kt:27-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (10 lines × 3) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverImageFragment.kt:19— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverImageFragment.kt:19-28 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:24-33 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:23-32 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.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 × 3) clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:57— clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:57-64 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt:52-60 | clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:50-57 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.kt` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeInterstitialImageFragment.kt:45` calls `ColorDrawable` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:52` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/PendingIntentFactory.kt:214— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/PendingIntentFactory.kt:214-219 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/PendingIntentFactory.kt:222-227 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/PendingIntentFactory.kt:230-235 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (39 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerPlayerListener.kt:23— clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/ExoplayerPlayerListener.kt:23-61 | clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3PlayerListener.kt:24-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: `AudioAttributes` names `androidx.media3.common.AudioAttributes` in one and `com.google.android.exoplayer2.audio.AudioAttributes` 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 (125 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:351— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:351-475 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:336-460 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:351` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:350` calls `setBackgroundColor`, `getImageBackgroundColor` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:335` 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 (82–84 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:239— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:239-322 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:227-308 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:239` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:323` calls `setVisibility` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:309` 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 (51–52 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:185— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:185-236 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:174-224 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:185` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:237` calls `setVisibility` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:225` 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 (28–29 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:483— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:483-511 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:562-589 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:483` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:590` calls `setGroup` and `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:512` 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 (28 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:258— clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:258-285 | clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:365-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (37–38 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:145— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:145-182 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:137-173 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:145` 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, `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:183` calls `setContentDescription`, `setScreenReaderFocusable` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:174` 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 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:89— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:89-121 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:81-113 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:89` 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 (18 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:127— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:127-144 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:149-166 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselImageViewHolder.java:127` 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–14 lines × 2) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceTaskManager.java:53— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceTaskManager.java:53-65 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceTaskManager.java:93-106 — 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 `clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceTaskManager.java:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `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 (12–13 lines × 6) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:426— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:426-437 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:478-489 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:557-568 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:628-639 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:668-679 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:705-717 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:426` 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 × 3) clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:83— clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:83-95 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java:103-115 | clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceReceiver.java:51-63 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceBootReceiver.java: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.
Duplicated block (9–10 lines × 2) clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/CTPushNotificationReceiver.java:44— clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/CTPushNotificationReceiver.java:44-52 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:349-358 — 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/CTPushNotificationReceiver.java:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–9 lines × 4) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:132— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:132-140 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:154-157 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:124-132 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:146-149 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:132` 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.
Duplicated block (8 lines × 7) clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:366— clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:366-373 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:424-431 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:476-483 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:555-562 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:626-633 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:666-673 | clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:703-710 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:366` 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) clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:427— clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:427-434 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:435-442 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:443-450 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PushTemplateReceiver.java:451-458 — 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.
Duplicated block (3–7 lines × 3) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:112— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTCarouselMessageViewHolder.java:112-114 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:80-86 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:72-78 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 (12 lines × 4) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:117— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:117-128 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:136-147 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:109-120 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:128-139 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 × 6) clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:106— clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:106-111 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:118-123 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:137-142 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:98-103 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:110-115 | clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java:129-134 — before extracting anything, compare `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java` and `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTSimpleMessageViewHolder.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 374 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 `clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTIconMessageViewHolder.java:106` 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 × 4) clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:64— clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:64-68 | clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:156-160 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PTLog.java:40-44 | clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PTLog.java:46-50 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `clevertap-core/src/main/java/com/clevertap/android/sdk/Logger.java:155` calls `SuppressWarnings` and `clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/PTLog.java:44` 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 copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:867— sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:867-886 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:888-911 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:913-934 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (12 lines × 3) sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:870— sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:870-881 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:894-905 | sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:917-928 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:906` calls `setImageUrl` and `sample/src/main/java/com/clevertap/demo/ui/main/HomeScreenViewModel.kt:882` 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.
Off the main sequence: :clevertap-core — :clevertap-core: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
X12 · Unreachable branch· Branch is unreachable · ×1
Branch is unreachable — its condition cannot hold here clevertap-core/src/main/java/com/clevertap/android/sdk/pushnotification/fcm/CTFirebaseMessagingReceiver.java:113— `messageBundle == null` can never be true where it stands: control only reaches it when `messageBundle != null` (line 111). The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/TriggersMatcher.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 clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceSettings.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleLocationAdapter.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/CallbackManager.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/variables/CTVariableUtils.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-geofence/src/main/java/com/clevertap/android/geofence/PushGeofenceEventTask.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/featureFlags/CTFeatureFlagsController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessage.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/customtemplates/JsonTemplatesProducer.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 clevertap-core/src/main/java/com/clevertap/android/sdk/variables/Var.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/login/LoginInfoProvider.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/CTInboxStyleConfig.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/task/Task.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/validation/ManifestValidator.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleGeofenceAdapter.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBaseFullFragment.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 clevertap-core/src/main/java/com/clevertap/android/sdk/login/ConfigurableIdentityRepo.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file clevertap-core/src/main/java/com/clevertap/android/sdk/store/preference/ICTPreference.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 clevertap-core/src/main/java/com/clevertap/android/sdk/PushPermissionHandler.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 clevertap-geofence/src/main/java/com/clevertap/android/geofence/GeofenceUpdateTask.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate clevertap-core/src/main/java/com/clevertap/android/sdk/ActivityLifeCycleManager.java:147— `(accountId == null && config.isDefaultInstance()) || config.getAccountId().equals(accountId)` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/ActivityLifeCycleManager.java, clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3507— `accountId == null || accountToken == null` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java, clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapInstanceConfig.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:224— `contentType != null && this.media != null && contentType.equals("image/gif")` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java, clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:213— `contentType != null && this.media != null && contentType.startsWith("audio")` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java, clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:235— `contentType != null && this.media != null && contentType.startsWith("image") && !contentType .equals("image/gif")` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java, clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:247— `contentType != null && this.media != null && contentType.startsWith("video")` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java, clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/utils/FileUtils.java:126— `jsonObject == null || TextUtils.isEmpty(dirName) || TextUtils.isEmpty(fileName)` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/utils/FileUtils.java, clevertap-geofence/src/main/java/com/clevertap/android/geofence/FileUtils.java. 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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt:92— `!inAppNotification.isTablet || !isTablet()` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/media/InAppGifHandler.kt:36— `config.clickableMedia && clickListener != null` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/media/InAppGifHandler.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/media/InAppImageHandler.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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt:38— `e1.x - e2.x > SWIPE_MIN_DISTANCE && abs(velocityX.toDouble()) > SWIPE_THRESHOLD_VELOCITY` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialNativeFragment.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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt:41— `e2.x - e1.x > SWIPE_MIN_DISTANCE && abs(velocityX.toDouble()) > SWIPE_THRESHOLD_VELOCITY` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PartialHtmlInAppGestureListener.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialNativeFragment.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 clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapInputStreamDecoder.kt:43— `fileLength != -1 && fileLength != totalBytesRead` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapInputStreamDecoder.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapInputStreamReader.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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppHtmlBannerOverlay.kt:193— `gd.onTouchEvent(event) || (event.action == MotionEvent.ACTION_MOVE)` appears character-identically in 3 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppHtmlBannerOverlay.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialHtmlFragment.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppBasePartialNativeFragment.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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt:27— `inAppNotification.isTablet && isTablet()` appears character-identically in 6 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverFragment.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeCoverImageFragment.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialFragment.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/fragment/CTInAppNativeHalfInterstitialImageFragment.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 clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt:176— `oldElement is JSONObject && newElement is JSONObject` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/ArrayOperationHandler.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/DeleteOperationHandler.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 clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/DeleteOperationHandler.kt:52— `oldValue is JSONArray && newValue is JSONArray` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/DeleteOperationHandler.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/OperationHandler.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 clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/DeleteOperationHandler.kt:44— `oldValue is JSONObject && newValue is JSONObject` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/DeleteOperationHandler.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/profile/traversal/OperationHandler.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 clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt:394— `result != original && reasons.isNotEmpty()` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/validation/eventdata/EventDataNormalizer.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/validation/propertykey/EventPropertyKeyNormalizer.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 clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1572— `templateName != null && !templatesManager.isTemplateRegistered(templateName)` appears character-identically in 2 files — clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/EvaluationManager.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 clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/validators/CarouselTemplateValidator.kt:8— `validator.validate() && super.validateKeys()` appears character-identically in 6 files — clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/validators/CarouselTemplateValidator.kt, clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/validators/InputBoxTemplateValidator.kt, clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/validators/ProductDisplayTemplateValidator.kt, clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/validators/RatingTemplateValidator.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.
Silent fallback default on parse failure clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventMediator.java:140— `getChargedEventDetails` returns `new HashMap<>()` when `JSONException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Silent fallback default on parse failure clevertap-core/src/main/java/com/clevertap/android/sdk/events/EventMediator.java:128— `getChargedEventItemDetails` returns `new ArrayList<>()` when `JSONException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Silent fallback default on parse failure clevertap-core/src/main/java/com/clevertap/android/sdk/LocalDataStore.java:721— `processProfileTree` returns `emptyMap()` when `JSONException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion clevertap-core/build.gradle:1— `clevertap-core` (61665 LoC, 931 module-visible types across 67 directories) overshoots its size bounds. 2 of 5 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 3.2/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 clevertap-pushtemplates/build.gradle:1— `clevertap-pushtemplates` (7924 LoC, 161 module-visible types across 7 directories) overshoots its size bounds. 2 of 5 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 3.2/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.
Fat interface: ICTPreference (26 abstract methods) clevertap-core/src/main/java/com/clevertap/android/sdk/store/preference/ICTPreference.kt:14— `ICTPreference` declares 26 abstract methods: `readString`, `readBoolean`, `readInt`, `readLong`, `readFloat`, `readStringSet`, `readAll`, `writeString`, `writeBoolean`, `writeInt`, `writeLong`, `writeFloat`, `writeStringSet`, `writeMap`, `writeStringImmediate`, `writeBooleanImmediate`, `writeIntImmediate`, `writeLongImmediate`, `writeFloatImmediate`, `writeStringSetImmediate`, `writeMapImmediate`, `isEmpty`, `size`, `remove`, `removeImmediate`, `changePreferenceName`. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 6 significant file(s) lose their only recent owner: clevertap-core/src/main/java/com/clevertap/android/sdk/ManifestInfo.java, clevertap-core/src/main/java/com/clevertap/android/sdk/ControllerManager.java, clevertap-core/src/main/java/com/clevertap/android/sdk/network/NetworkRepo.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/video/inbox/Media3PlayerListener.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/network/NetworkEncryptionManager.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/CTDisplayUnitController.java. Pair on, review, or document these before any departure.
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 (12 single-owned of 312 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; 312 of the 643 production source files in this repository met that bar). They are anonymized user #2 (3 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (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: clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/content/NotificationBitmapUtils.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/network/http/UrlConnectionHttpClient.kt, clevertap-pushtemplates/src/main/java/com/clevertap/android/pushtemplates/media/TemplateRepository.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/db/dao/InboxMessageDAOImpl.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/usereventlogs/UserEventLogDAOImpl.kt, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/media/InAppStreamMediaHandler.kt.
No ADRs found instantapp/build.gradle.kts:2— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `instantapp/build.gradle.kts` makes this repository a deployable product (line 2).
D21 · Naming Consistency· `openHttpsURLConnection` spells `URL` where 42 names in the project spell it `Url` · ×1
`openHttpsURLConnection` spells `URL` where 42 names in the project spell it `Url` clevertap-core/src/main/java/com/clevertap/android/sdk/network/http/UrlConnectionHttpClient.kt:92— 42 of 43 names in project clevertap-core spell the token `Url` (42 of 43; unit: names in project clevertap-core containing `Url`). Peers: BitmapDownloader.httpUrlConnectionParams (clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapDownloader.kt:14); BitmapDownloader.srcUrl (clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapDownloader.kt:25); BitmapDownloader.downloadBitmap(srcUrl) (clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/BitmapDownloader.kt:27); HttpBitmapLoader.standardGzipHttpUrlConnectionParams (clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/HttpBitmapLoader.kt:17); HttpBitmapLoader.inAppStandardHttpUrlConnectionParams (clevertap-core/src/main/java/com/clevertap/android/sdk/bitmap/HttpBitmapLoader.kt:26). Rename to `openHttpsUrlConnection`. [rule N6]
D21 · Naming Consistency· `getBitmapFromURL` spells `URL` where 17 names in the project spell it `Url` · ×1
`getBitmapFromURL` spells `URL` where 17 names in the project spell it `Url` clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:168— 17 of 18 names in project clevertap-core spell the token `Url` (17 of 18; unit: names in project clevertap-core containing `Url`). Peers: CleverTapAPI.getNotificationBitmapWithTimeoutAndSize(bitmapSrcUrl) (clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3687); CleverTapAPI.getNotificationBitmapWithTimeout(bitmapSrcUrl) (clevertap-core/src/main/java/com/clevertap/android/sdk/CleverTapAPI.java:3753); Utils.getBitmapFromURL(srcUrl) (clevertap-core/src/main/java/com/clevertap/android/sdk/Utils.java:168); CleverTapDisplayUnitContent.getActionUrl (clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:101); CleverTapDisplayUnitContent.getPosterUrl (clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnitContent.java:182). Rename to `getBitmapFromUrl`. [rule N6]
D21 · Naming Consistency· `getWZRKFields` spells `WZRK` where 12 names in the project spell it `Wzrk` · ×1
`getWZRKFields` spells `WZRK` where 12 names in the project spell it `Wzrk` clevertap-core/src/main/java/com/clevertap/android/sdk/displayunits/model/CleverTapDisplayUnit.java:240— 12 of 13 names in project clevertap-core spell the token `Wzrk` (12 of 13; unit: names in project clevertap-core containing `Wzrk`). Peers: AnalyticsManager.filterWzrkFields (clevertap-core/src/main/java/com/clevertap/android/sdk/AnalyticsManager.java:332); CoreMetaData.clearWzrkParams (clevertap-core/src/main/java/com/clevertap/android/sdk/CoreMetaData.java:170); CoreMetaData.setWzrkParams (clevertap-core/src/main/java/com/clevertap/android/sdk/CoreMetaData.java:257); CoreMetaData.getWzrkParams (clevertap-core/src/main/java/com/clevertap/android/sdk/CoreMetaData.java:263); CTInboxMessage.getWzrkParams (clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessage.java:285). Rename to `getWzrkFields`. [rule N6]
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 79 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: clevertap-core/src/main/java/com/clevertap/android/sdk/InAppFCManager.java, clevertap-core/src/main/java/com/clevertap/android/sdk/inbox/CTInboxMessageContent.java, clevertap-core/src/main/java/com/clevertap/android/sdk/CTWebInterface.java, clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/evaluation/TriggersMatcher.kt, clevertap-geofence/src/main/java/com/clevertap/android/geofence/CTGeofenceSettings.java, clevertap-geofence/src/main/java/com/clevertap/android/geofence/GoogleLocationAdapter.java, clevertap-core/src/main/java/com/clevertap/android/sdk/product_config/ProductConfigSettings.java, clevertap-geofence/src/main/java/com/clevertap/android/geofence/Utils.java (and 71 more) (82 orphaned of 317 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; 317 of the 643 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST REDACTED:3— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation build.gradle:12— `build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt:1005— `debug` at line 1005 is called with an argument built by `inAppActivityExclude.joinToString()` (line 1007), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on.
Silent fallback default in catch clevertap-core/src/main/java/com/clevertap/android/sdk/DeviceInfo.java:225— `getCountryCode` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 13 file(s) — `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/CTInAppNotification.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppActionHandler.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppController.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/InAppNotificationInflater.kt`, `clevertap-core/src/main/java/com/clevertap/android/sdk/inapp/PIPShowFailureHandler.kt`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
0
—
Run 01a1e9cc-bcac-7494-b61d-ee09488542eb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 49 · Warnings: 460 · Recommendations: 120 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 13:57 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.