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

micronaut-projects/micronaut-data

Measured 16 November 2026, 21:13 UTC, at code version b6ace62

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

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

CAI score 61.0out of 100 Adequate
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 188,051 lines of product code in 32 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Domain Modelling, 57.4

Findings by how serious they are

9 critical 1020 serious 129 minor

18 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

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

64of 64 dimensions measured by tools.
1143of 1158 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
64dimensions across 7 lenses, read from 188,051 lines of product code in 32 projects.
Chapters

Executive summary

micronaut-projects/micronaut-data falls short of our standard for production, held back most by its Domain Modelling lens, the way the code models the business it serves. It scores 61.0 out of 100 and is rated Adequate, and four of its nine critical findings are security problems.

Domain Modelling, at 57.4, 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.8 points. Organising the data access would lift Domain Modelling itself, worth about 2.9 points. Raising Domain Modelling to 70 would lift the score to about 63.6.

Two secrets can leak from the build pipeline. One automatic update takes new releases before a bad one can be spotted, and three packages carry licence risk. Limiting each secret to its own step, setting a waiting period for automatic updates and replacing or clearing the banned-licence packages would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code. The test that checks nothing needs to check the result it produces.

The product code is 188,051 lines, about €380,000 to rebuild.

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

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

If Domain Modelling rose from 57.4 to 70, the lowest score rated Strong, the score would rise from 61.0 to about 63.6.

Code composition: what the lines of code are
Product code 73%Tests 27%
Rebuild cost: about €380,000 · Estimate
Cost to rebuild€130,000 to €630,000, for 2,093 to 6,640 hours of work, about 2.6 person-years for 1 to 5 engineers
Difficulty of the problemHigh, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 188,051 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.
Raises the score by about 2.8 points · Low effort · ADR Quality
2
Resolve the 1 `AuthorDTO` spells `DTO` where 19 names in the project spell it `Dto` finding(s) in Naming Consistency — start with AuthorDTO.java.
Raises the score by about 1.5 points · Low effort · Naming Consistency
3
Resolve the 1 `SaleDTO` spells `DTO` where 19 names in the project spell it `Dto` finding(s) in Naming Consistency — start with SaleDTO.java.
Raises the score by about 1.5 points · Low effort · Naming Consistency

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €380,000 to build again, about 2.6 person-years of work. Its weakest lens is Domain Modelling, at 57.4 (Adequate). Domain Modelling is about whether the code protects the rules the business depends on. Because the weakest lens counts most in the score, work on Domain Modelling also moves the score most.
Based on: the rebuild estimate · the Domain Modelling grade · how much each lens counts
What to do: Start with the Domain Modelling actions in Top priorities.
One cause behind 27 Domain Modelling findings · Common cause
27 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (8 findings) · Rich vs anemic model (19 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 1 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.8 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 98,724 lines over the last 90 days, which is about 400,381 lines a year. At that pace, the extra work comes to an estimated 27 to 161.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

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

218 modules, with 716 dependencies between them. 7 loops run through 43 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 core.annotation2 data.intercept3 data.connection4 data.event5 data.model.query.builder6 data.connection.reactive7 data.model.query8 data.runtime.convert9 data.connection.support10 data.model.jpa.criteria.impl11 data.runtime.mapper12 data.model.jpa.criteria13 transaction.support14 data.model.query.builder.sql15 transaction16 data.model.runtime.convert17 data.model.runtime18 data.model19 data.document.model.query.builder20 data.operations21 data.runtime.mapper.sql22 data.tck.repositories23 data.annotation24 data.operations.async25 data.operations.reactive26 data.runtime.query27 data.model.runtime.convert.vector.impl28 data.processor.visitors.finders.criteria29 data.runtime.operations30 data.runtime.operations.internal31 data.hibernate.operations32 data.mongodb.operations33 data.processor.visitors.finders34 data.runtime.operations.internal.sql35 data.cosmos.operations36 data.hibernate.reactive.operations37 data.jdbc.operations38 data.processor.visitors39 data.r2dbc.operations40 data.processor.model.criteria.impl
1 core.annotation
2 data.intercept
3 data.connection2
4 data.event3
5 data.model.query.builder1912
6 data.connection.reactive8
7 data.model.query131
8 data.runtime.convert2544
9 data.connection.support112
10 data.model.jpa.criteria.impl418638262
11 data.runtime.mapper126
12 data.model.jpa.criteria126132
13 transaction.support113220
14 data.model.query.builder.sql1028118124548
15 transaction21
16 data.model.runtime.convert12
17 data.model.runtime4113243
18 data.model31122
19 data.document.model.query.builder26716113
20 data.operations121
21 data.runtime.mapper.sql237782
22 data.tck.repositories21
23 data.annotation21161
24 data.operations.async811
25 data.operations.reactive3445
26 data.runtime.query22161
27 data.model.runtime.convert.vector.impl21291
28 data.processor.visitors.finders.criteria1111122113
29 data.runtime.operations2324544
30 data.runtime.operations.internal6171128311
31 data.hibernate.operations21211205212222
32 data.mongodb.operations413146132142112
33 data.processor.visitors.finders121143932282
34 data.runtime.operations.internal.sql1322222252511121
35 data.cosmos.operations1311313112154163
36 data.hibernate.reactive.operations1432122142124211
37 data.jdbc.operations5152111627125121714
38 data.processor.visitors551192
39 data.r2dbc.operations11511262442425714
40 data.processor.model.criteria.impl5214272611
Uses a module listed above itPart of a loopThe module itself
1 core.annotation2 data.intercept3 data.connection4 data.event5 data.model.query.builder6 data.connection.reactive7 data.model.query8 data.runtime.convert9 data.connection.support10 data.model.jpa.criteria.impl11 data.runtime.mapper12 data.model.jpa.criteria13 transaction.support14 data.model.query.builder.sql15 transaction16 data.model.runtime.convert17 data.model.runtime18 data.model19 data.document.model.query.builder20 data.operations21 data.runtime.mapper.sql22 data.tck.repositories23 data.annotation24 data.operations.async25 data.operations.reactive26 data.runtime.query27 data.model.runtime.convert.vector.impl28 data.processor.visitors.finders.criteria29 data.runtime.operations30 data.runtime.operations.internal31 data.hibernate.operations32 data.mongodb.operations33 data.processor.visitors.finders34 data.runtime.operations.internal.sql35 data.cosmos.operations36 data.hibernate.reactive.operations37 data.jdbc.operations38 data.processor.visitors39 data.r2dbc.operations40 data.processor.model.criteria.implcore.annotation1data.intercept2data.connection3data.event4data.model.query.builder5data.connection.reactive6data.model.query7data.runtime.convert8data.connection.support9data.model.jpa.criteria.impl10data.runtime.mapper11data.model.jpa.criteria12transaction.support13data.model.query.builder.sql14transaction15data.model.runtime.convert16data.model.runtime17data.model18data.document.model.query.builder19data.operations20data.runtime.mapper.sql21data.tck.repositories22data.annotation23data.operations.async24data.operations.reactive25data.runtime.query26data.model.runtime.convert.vector.impl27data.processor.visitors.finders.criteria28data.runtime.operations29data.runtime.operations.internal30data.hibernate.operations31data.mongodb.operations32data.processor.visitors.finders33data.runtime.operations.internal.sql34data.cosmos.operations35data.hibernate.reactive.operations36data.jdbc.operations37data.processor.visitors38data.r2dbc.operations39data.processor.model.criteria.impl40231912813125441124186382621261261321132201028118124548211241132433112226716113121237782212116181134452216121291111112211323245446171128311212112052122224131461321421121211439322821322222252511121131131311215416314321221421242115152111627125121714551192115112624424257145214272611+178 more modules (most-connected shown)

At a glance — Code Health · 64.3 · Adequate · gated by X5 ·

At a glance — Architecture · 70.9 · Strong ·

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

At a glance — Readiness · 66.3 · Adequate · gated by P3 ·

At a glance — Security · 87.5 · Strong ·

At a glance — Domain Modelling · 57.4 · Adequate · gated by DM7 ·

At a glance — Performance · 91.4 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures12Medium
A05:2025 — Injection4High / Critical

Roadmap

Top priorities: Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle; 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.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.+2.8 ptsLowADR Quality
Resolve the 1 `AuthorDTO` spells `DTO` where 19 names in the project spell it `Dto` finding(s) in Naming Consistency — start with AuthorDTO.java.+1.5 ptsLowNaming Consistency
Resolve the 1 `SaleDTO` spells `DTO` where 19 names in the project spell it `Dto` finding(s) in Naming Consistency — start with SaleDTO.java.+1.5 ptsLowNaming Consistency
Resolve the 1 `testReadDTO` spells `DTO` where 13 names in the project spell it `Dto` finding(s) in Naming Consistency — start with SQLiteAuthorRepository.java.+1.5 ptsLowNaming Consistency
Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.+2.9 ptsMediumRepository granularity
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.+2.7 ptsMediumArchitecture documentation
Resolve the 3 Banned license finding(s) in License Compliance.+1.2 ptsLowLicense Compliance
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with CohQLQueryTest.java.+1.0 ptsLowTest Quality

File quality

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

FileScoreBandWorst signal
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java5.5MixedCyclomatic Complexity: R2dbcEntitiesOperations.execute (cyclomatic 20)
data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java5.5MixedCyclomatic Complexity: JdbcEntitiesOperations.execute (cyclomatic 18)
data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java5.5MixedCognitive Complexity: HibernateJpaOperations.execute (cognitive 22)
data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java5.5MixedGod Classes: TooManyMethods: DefaultReactiveCosmosRepositoryOperations
data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java5.6MixedCognitive Complexity: AbstractQueryInterceptor.instantiateEntity (cognitive 19)
doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java5.8MixedTest Reliability: Test declared unreliable: shouldGetBooksById
data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java5.9MixedGod Classes: TooManyMethods: AbstractReactorTransactionOperations
data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java6.0MixedExplicit Debt: TodoComment
data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java6.0MixedExplicit Debt: TodoComment
data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java6.0MixedExplicit Debt: TodoComment
data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java6.0MixedExplicit Debt: TodoComment
data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java6.0MixedExplicit Debt: TodoComment
doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/query/CohQLQueryTest.java6.2MixedTest Quality: Assertions commented out: shouldThrowIfBuildingJoin
jakarta-data-tck/mongodb/src/test/java/io/micronaut/data/jakarta/tck/FilterExtension.java6.6MixedExplicit Debt: TodoComment
data-mongodb/src/main/java/io/micronaut/data/mongodb/init/AbstractMongoCollectionsCreator.java6.7MixedExplicit Debt: TodoComment
doc-examples/azure-cosmos-example-python/src/main/python/example/PersonRepository.py6.7MixedExplicit Debt: TodoComment
data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java7.0MixedCyclomatic Complexity: SqlResultEntityTypeMapper.readEntity (cyclomatic 66)
data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java7.0MixedCyclomatic Complexity: AbstractSqlLikeQueryBuilder.buildUpdateStatement (cyclomatic 44)
data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java7.0MixedCyclomatic Complexity: FindersUtils.resolveInterceptorTypeByOperationType (cyclomatic 39)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 9

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

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

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 18

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 64 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 — 64 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D19D20D21D23D26D27D28D29D31D34D35D36D37D44AX10AX2AX3AX5AX6DM1DM10DM11DM4DM5DM7DM9GD1IC1M1M2M3M4P1P2P3P4P6P8PF1PF3X16X18X19X23X25X27X28X29X3X30X4X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1e635-668d-7fe7-aed5-0ee32a25b7a0.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .py, .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.
  • D10 Test 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. The 450 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 155 test source file(s) (.py, .kt) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .py, .kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 115 Maven/Gradle manifest(s) were read, stating a version for 42 dependency(ies) and leaving 6 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (test-suite-data-jdbc-sqlite/build.gradle.kts), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • 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. `data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/CriteriaUtils.java`, `data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java`, `data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryWktConverter.java`, `data-model/src/main/java/io/micronaut/data/model/vector/BinaryVector.java`, `data-model/src/main/java/io/micronaut/data/model/vector/ByteVector.java`, … (+5 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.
  • AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Micronaut, whose lifetimes are not modelled 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.
  • AXB2 Runtime readiness — 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. The image build failed, and its output does not match a cause we recognise. (rule: unrecognised-build-failure). The renderer reported: docker build failed (exit 1) — 1 | FROM adoptopenjdk/openjdk11-openj9:jdk-11.0.1.13-alpine-slim 2 | >>> COPY build/libs/*.jar example-java.jar 3 | EXPOSE 8080 4 | CMD java -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -Dcom.sun.management.jmxremote -noverify ${JAVA_OPTS} -jar example-java.jar -------------------- ERROR: failed to solve: lstat /build/libs: no such file or directory; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped.
  • 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. Render strategy: boot via Dockerfile (benchmarks/benchmark-micronaut-data-jpa/Dockerfile). docker build failed (exit 1) — 1 | FROM adoptopenjdk/openjdk11-openj9:jdk-11.0.1.13-alpine-slim 2 | >>> COPY build/libs/*.jar example-java.jar 3 | EXPOSE 8080 4 | CMD java -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -Dcom.sun.management.jmxremote -noverify ${JAVA_OPTS} -jar example-java.jar -------------------- ERROR: failed to solve: lstat /build/libs: no such file or directory; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped.
  • 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. These personal data 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 personal data controls.
  • 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. These audit 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 audit controls.
  • 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. These retention 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 retention controls.
  • 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. These data-subject rights 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 data-subject rights controls.
  • DM11 Constructible invalid state — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
  • DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The frontend declares that it computes whether a construction is produced or passed, yet 45 of 3721 constructions arrived without the answer. Arm two skipped them; it did not clear them.
  • ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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 — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X10 Duplicated predicate — 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. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
  • X12 Unreachable branch — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

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.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • 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.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • 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.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.2 / 10Adequate✓ Tool-verified

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

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

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

54 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DataConversionServiceFactory.build at 85. A further 15 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 SqlSchemaUtils.getDbType at 33 — they are counted neither in the figure above nor in this dimension's score. 13 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java (JQCriteriaBuilderUtils.getExpression at 32), data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/R2dbcQueryStatement.java (R2dbcQueryStatement.setDynamic at 25), data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/OracleR2dbcReturningSupport.java (OracleR2dbcReturningSupport.findR2dbcType at 22), data-model/src/main/java/io/micronaut/data/model/query/impl/AdvancedPredicateVisitor.java (AdvancedPredicateVisitor.appendPredicate at 20), data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcQueryStatement.java (JdbcQueryStatement.findSqlType at 19), and 8 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

DataConversionServiceFactory.build (cyclomatic 85)data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:68
SqlColumnMapping.getSqlType (cyclomatic 83)data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:247
QueryStatement.setDynamic (cyclomatic 69)data-runtime/src/main/java/io/micronaut/data/runtime/mapper/QueryStatement.java:59
SqlResultEntityTypeMapper.readEntity (cyclomatic 66)data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:607
SqlSchemaUtils.getColumnDefinition (cyclomatic 47)data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:489

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

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with DataConversionServiceFactory.build (cyclomatic 85), SqlColumnMapping.getSqlType (cyclomatic 83), QueryStatement.setDynamic (cyclomatic 69). — 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 4 together lifts Cyclomatic Complexity from 6.2 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: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity5.2 / 10Adequate✓ Tool-verified

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

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

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

110 method(s) exceeded the cognitive complexity threshold of 15; the worst was SqlResultEntityTypeMapper.readEntity at 211.

SqlResultEntityTypeMapper.readEntity (cognitive 211)data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:607
DefaultMongoStoredQuery.replaceQueryParametersInBsonValue (cognitive 109)data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:461
SyncCascadeOperations.cascadeEntity (cognitive 99)data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/SyncCascadeOperations.java:69
DataConversionServiceFactory.build (cognitive 94)data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:68
SqlColumnMapping.getSqlType (cognitive 89)data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:247

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with SqlResultEntityTypeMapper.readEntity (cognitive 211). — Refactoring it lifts Cognitive Complexity from 5.2 to about 5.8/10.

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

D3 · God Classes8.8 / 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.

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

98 god class(es) detected.

TooManyMethods: AbstractCriteriaBuilder · ×39data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractCriteriaBuilder.java:90
ClassTooLong: AbstractSqlLikeQueryBuilder · ×23data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:142
FileTooLong: sql/AbstractSqlLikeQueryBuilder.java · ×22data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java
MethodTooLong: DataConversionServiceFactory.build · ×14data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:68

What to do

  1. Resolve the 39 TooManyMethods finding(s) in God Classes — start with AbstractSqlLikeQueryBuilder.java (3), MongoQueryBuilder.java (2), AbstractCriteriaBuilder.java. — One of this dimension's main actionable groups (39 warning-level).
  2. Resolve the 23 ClassTooLong finding(s) in God Classes — start with AbstractSqlLikeQueryBuilder.java, SqlQueryBuilder.java, DefaultJdbcRepositoryOperations.java. — One of this dimension's main actionable groups (23 warning-level).
  3. Resolve the 22 FileTooLong finding(s) in God Classes — start with AbstractSqlLikeQueryBuilder.java, SqlQueryBuilder.java, DefaultJdbcRepositoryOperations.java. — One of this dimension's main actionable groups (22 warning-level).

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

D4 · Code Duplication7.2 / 10Strong✓ Tool-verified

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

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

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

270 duplicated block group(s) detected. 7.1 % of the production lines (13,360 of 188,051) are in a reported copy. A further 270 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 37 of the 540 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.

Duplicated block (6 lines × 2) · ×28data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:283
Duplicated block (8 lines × 2) · ×24data-connection/src/main/java/io/micronaut/data/connection/sync/SynchronousConnectionOperationsFromReactiveConnectionOperations.java:65
Edited copy of a member (8 corresponding lines) · ×22data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:99
Duplicated block (7 lines × 2) · ×21data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:939
Edited copy of a member (9 corresponding lines) · ×20data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:124

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

What to do

  1. Resolve the 28 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with DefaultMongoRepositoryOperations.java (4), CosmosSqlQueryBuilder.java (3), DefaultReactiveCosmosRepositoryOperations.java (2). — One of this dimension's main actionable groups (28 warning-level).
  2. Resolve the 24 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with DefaultMongoRepositoryOperations.java (3), SourcePersistentEntityCriteriaQueryImpl.java (2), SynchronousConnectionOperationsFromReactiveConnectionOperations.java. — One of this dimension's main actionable groups (24 warning-level).
  3. Resolve the 22 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with AbstractR2dbcResultReader.java (7), PersonSuspendRepositoryService.kt (3), DefaultJdbcRepositoryOperations.java (2). — One of this dimension's main actionable groups (22 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

32 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 26 of the 32 (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).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

20 of 275 classes have LCOM4 above 3.

Low cohesion: DefaultR2dbcRepositoryOperations (LCOM4 15) · ×20data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:166

What to do

  1. Resolve the 20 Low cohesion finding(s) in Cohesion (LCOM4) — start with DefaultR2dbcRepositoryOperations.java, DefaultJdbcRepositoryOperations.java, ColumnIndexReadableResultReader.java. — One of this dimension's main actionable groups (20 warning-level).

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

D10 · Test Quality9.9 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

1 skipped (1 with a documented reason), 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 450 tests. Measured on the .java suite only — at least 155 test source file(s) (.py, .kt) went unread, so its test quality is unmeasured and is not in these counts.

Assertions commented out: shouldThrowIfBuildingJoindoc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/query/CohQLQueryTest.java:40
No assertions: shouldReturnFalseForInvalidAuthor · ×2doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java:120
Skipped (documented): testObjectIdDeserdoc-examples/mongo-jackson-example-java/src/test/java/example/Tests.java:130

What to do

  1. Resolve the 1 Assertions commented out finding(s) in Test Quality — start with CohQLQueryTest.java. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 No assertions finding(s) in Test Quality — start with GeneratedAsyncStatementsTest.java (2). — One of this dimension's main actionable groups (2 warning-level).

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

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance4.0 / 10Weak✓ Tool-verified

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

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

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

3 of 38 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 115 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. 6 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 3 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.

Banned license: org.orbisgis:h2gis · ×3

What to do

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

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

D15 · Churn × Complexity Hotspots9.8 / 10Stronggated by 8 serious findings✓ Tool-verified

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

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

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

Top hotspots: data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java (16×34=544); data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java (5×66=330); data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java (17×18=306) Repeated repair below the complexity floor: data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.java (3 of 3 changes were fixes)

Hotspot: data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java · ×7data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1497
Repeated repair: data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.javadata-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.java:325

What to do

  1. Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with SqlQueryBuilder.java, SqlResultEntityTypeMapper.java, AbstractSqlLikeQueryBuilder.java. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with DefaultTransactionDefinition.java. — 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.

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

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

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

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

20 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java. Counted over 670 of the 2648 production source files in this repository: 1973 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 · ×2
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

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

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

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

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

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

TodoComment · ×31jakarta-data-tck/mongodb/src/test/java/io/micronaut/data/jakarta/tck/FilterExtension.java:54
FixmeCommenttest-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/read/only/ReadOnlyRepository.java:10
HackCommentdata-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/SqlJsonColumnMapperProvider.java:89

What to do

  1. Resolve the 31 TodoComment finding(s) in Explicit Debt — start with FilterExtension.java (4), ReadOnlyTest.java (4), PersonRepository.py (3). — One of this dimension's main actionable groups (31 warning-level).
  2. Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with ReadOnlyRepository.java. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 HackComment finding(s) in Explicit Debt — start with SqlJsonColumnMapperProvider.java. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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.

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

No architecture decision records were found.

No ADRs foundbuildSrc/build.gradle:21

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).

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

D21 · Naming Consistency0.6 / 10Critical✓ Tool-verified

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

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

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

5 naming inconsistencies among 53 declarations measured against a convention their peers follow.

`AuthorDTO` spells `DTO` where 19 names in the project spell it `Dto`data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorDTO.java:21
`SaleDTO` spells `DTO` where 19 names in the project spell it `Dto`data-tck/src/main/java/io/micronaut/data/tck/entities/SaleDTO.java:25
`testReadDTO` spells `DTO` where 13 names in the project spell it `Dto`test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteAuthorRepository.java:44
`addressID` spells `ID` where 24 names in the project spell it `Id`doc-examples/jdbc-example-kotlin/src/main/kotlin/example/AddressSubView.kt:17
`teachID` spells `ID` where 24 names in the project spell it `Id`doc-examples/jdbc-example-kotlin/src/main/kotlin/example/TeacherSubView.kt:14

What to do

  1. Resolve the 1 `AuthorDTO` spells `DTO` where 19 names in the project spell it `Dto` finding(s) in Naming Consistency — start with AuthorDTO.java. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `SaleDTO` spells `DTO` where 19 names in the project spell it `Dto` finding(s) in Naming Consistency — start with SaleDTO.java. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `testReadDTO` spells `DTO` where 13 names in the project spell it `Dto` finding(s) in Naming Consistency — start with SQLiteAuthorRepository.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.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types leak across context boundaries (2 contexts). Contexts: data-document-tck, data-tck.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D26 · Project Cohesion6.4 / 10Adequate✓ Tool-verified

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

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

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

5 of 26 build units (Gradle) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×5data-model/build.gradle:1

What to do

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

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

D27 · Navigability8.6 / 10Strong✓ Tool-verified

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

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

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

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

47 % of calls cross a namespace and 27 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)5.0 / 10Adequate✓ Tool-verified

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

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

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

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

4 finding(s): 0 critical, 4 high, 0 medium, 0 low. semgrep hit a parse error in 11 file(s) — `data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/CriteriaUtils.java` (line 223, line 225, line 233, …), `data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java` (line 107, line 108, line 109, …), `data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryWktConverter.java` (line 71, line 72, line 73, …), `data-model/src/main/java/io/micronaut/data/model/vector/BinaryVector.java` (line 157), `data-model/src/main/java/io/micronaut/data/model/vector/ByteVector.java` (line 100), … (+6 more) — 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 4 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

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness9.9 / 10Exemplary✓ Tool-verified

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

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

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

6 of 675 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is data-model/src/main/kotlin/io/micronaut/data/repository/jpa/kotlin/KotlinJpaSpecificationExecutor.kt. Counted over 675 of the 2648 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×6data-model/src/main/kotlin/io/micronaut/data/repository/jpa/kotlin/KotlinJpaSpecificationExecutor.kt:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition4.0 / 10Weak✓ Tool-verified

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

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

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

AX2 · Stateful singletons7.0 / 10Adequate✓ Tool-verified

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

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

  • `DefaultReactiveCosmosRepositoryOperations` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (defaultCosmosSqlQueryBuilder; e.g. `defaultCosmosSqlQueryBuilder` in `decorate` at line 182). — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:127
  • `TxEventsService` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (lastEvent; e.g. `lastEvent` in `afterCommit` at line 73). — data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:29
  • `EntityEventRegistry` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (beanEventHandlers; e.g. `beanEventHandlers` in `process` at line 333). — data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:67
  • `JakartaDataTrainEventListener` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (events; e.g. `events` in `onEvent` at line 38). — data-tck/src/main/java/io/micronaut/data/tck/services/JakartaDataTrainEventListener.java:33
  • `TxEventsService` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (lastEvent, events; e.g. `lastEvent` in `afterCommit` at line 132). — data-tck/src/main/java/io/micronaut/data/tck/services/TxEventsService.java:33
  • `EventRecorder` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (eventRecords; e.g. `eventRecords` in `record` at line 16). — doc-examples/coherence-example-java/src/main/java/io/micronaut/coherence/data/util/EventRecorder.java:12
  • `BookManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (events; e.g. `events` in `onNewBook` at line 35). (×2) — doc-examples/hibernate-spring-tx-example-java/src/main/java/example/BookManager.java:14, doc-examples/jdbc-spring-tx-example-java/src/main/java/example/BookManager.java:14

What to do

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

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

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

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

  • `PersonRepository` declares 46 abstract methods: `count`, `countByAgeGreaterThan`, `countByAgeLessThan`, `deleteByNameRegex`, `findAgeByName`, `findAllByNameRegex`, `findAllByNameRegex`, `findByDateOfBirthGreaterThan`, `findByDateOfBirthGreaterThanEquals`, `findByDateOfBirthLessThan`, `findByDateOfBirthLessThanEquals`, `findByIdIn`, `findByIdNotIn`, `findByName`, `findByNameContains`, `findByNameContainsIgnoreCase`, `findByNameEndsWith`, `findByNameEndsWithIgnoreCase`, `findByNameEqualIgnoreCase`, `findByNameIn`, `findByNameLike`, `findByNameNotEqualIgnoreCase`, `findByNameRegex`, `findByNameRegex`, `findByNameRegexOrderByAge`, `findByNameRegexOrderByAgeDesc`, `findByNameStartsWith`, `findByNameStartsWithIgnoreCase`, `findMaxAgeByNameRegex`, `findMaxDateOfBirthByNameRegex`, `findMinAgeByNameRegex`, `findMinDateOfBirthByNameRegex`, `get`, `getAvgAgeByNameRegex`, `getByNameRegex`, `getSumAgeByNameRegex`, `list`, `listTop10`, `queryByNameRegex`, `readAgeByNameRegex`, and 6 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 46 declarations carry 44 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 44 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/PersonRepository.java:35
  • `PersistentEntityCriteriaBuilder` declares 27 abstract methods: `and`, `arrayContains`, `containsString`, `containsStringIgnoreCase`, `createCriteriaDelete`, `createCriteriaInsert`, `createCriteriaUpdate`, `createQuery`, `createQuery`, `createTupleQuery`, `endingWithString`, `endingWithStringIgnoreCase`, `equalStringIgnoreCase`, `equalStringIgnoreCase`, `geoIntersects`, `geoWithin`, `ilike`, `isEmptyString`, `isNotEmptyString`, `near`, `notEqualStringIgnoreCase`, `notEqualStringIgnoreCase`, `or`, `regex`, `sort`, `startsWithString`, `startsWithStringIgnoreCase`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 27 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/PersistentEntityCriteriaBuilder.java:33
  • `PersistentEntityCriteriaQuery<T>` declares 17 abstract methods under just 10 distinct name(s): `distinct`, `from`, `from`, `from`, `groupBy`, `groupBy`, `having`, `having`, `limit`, `multiselect`, `multiselect`, `offset`, `orderBy`, `orderBy`, `select`, `where`, `where`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 10 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/PersistentEntityCriteriaQuery.java:38
  • `PersistentEntityFrom<OwnerType, AssociatedEntityType>` declares 20 abstract methods under just 5 distinct name(s): `getPersistentJoins`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `joinCollection`, `joinCollection`, `joinList`, `joinList`, `joinSet`, `joinSet`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 5 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/PersistentEntityFrom.java:39
  • `AdvancedPredicateVisitor<P>` declares 19 abstract methods: `getRequiredProperty`, `visitContains`, `visitEndsWith`, `visitEquals`, `visitGreaterThan`, `visitGreaterThanOrEquals`, `visitIdEquals`, `visitIn`, `visitInBetween`, `visitIsEmpty`, `visitIsFalse`, `visitIsNotEmpty`, `visitIsNotNull`, `visitIsNull`, `visitIsTrue`, `visitLessThan`, `visitLessThanOrEquals`, `visitNotEquals`, `visitStartsWith`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — data-model/src/main/java/io/micronaut/data/model/query/impl/AdvancedPredicateVisitor.java:40
  • `PersistentEntity` declares 16 abstract methods: `findNamingStrategy`, `getAliasName`, `getCompositeIdentity`, `getIdentity`, `getName`, `getNamingStrategy`, `getParentEntity`, `getPersistentProperties`, `getPersistentPropertyNames`, `getPropertyByName`, `getPropertyByNameIgnoreCase`, `getVersion`, `hasCompositeIdentity`, `hasIdentity`, `hasVersion`, `isOwningEntity`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — data-model/src/main/java/io/micronaut/data/model/PersistentEntity.java:46
  • `AsyncRepositoryOperations` declares 16 abstract methods under just 13 distinct name(s): `count`, `delete`, `deleteAll`, `executeUpdate`, `exists`, `findAll`, `findAll`, `findOne`, `findOne`, `findOptional`, `findOptional`, `findPage`, `getExecutor`, `persist`, `persistAll`, `update`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — data-model/src/main/java/io/micronaut/data/operations/async/AsyncRepositoryOperations.java:42
  • `ReactiveRepositoryOperations` declares 16 abstract methods under just 13 distinct name(s): `count`, `delete`, `deleteAll`, `executeUpdate`, `exists`, `findAll`, `findAll`, `findOne`, `findOne`, `findOptional`, `findOptional`, `findPage`, `persist`, `persistAll`, `update`, `updateAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — data-model/src/main/java/io/micronaut/data/operations/reactive/ReactiveRepositoryOperations.java:40
  • `ReactorReactiveRepositoryOperations` declares 17 abstract methods under just 14 distinct name(s): `count`, `delete`, `deleteAll`, `executeDelete`, `executeUpdate`, `exists`, `findAll`, `findAll`, `findOne`, `findOne`, `findOptional`, `findOptional`, `findPage`, `persist`, `persistAll`, `update`, `updateAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — data-model/src/main/java/io/micronaut/data/operations/reactive/ReactorReactiveRepositoryOperations.java:37
  • `JpaSpecificationExecutor<T>` declares 19 abstract methods under just 6 distinct name(s): `count`, `count`, `deleteAll`, `deleteAll`, `deleteAll`, `exists`, `exists`, `findAll`, `findAll`, `findAll`, `findAll`, `findAll`, `findAll`, `findAll`, `findOne`, `findOne`, `findOne`, `updateAll`, `updateAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 6 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — data-model/src/main/java/io/micronaut/data/repository/jpa/JpaSpecificationExecutor.java:50
  • `AuthorRepository` declares 36 abstract methods: `countByNameContains`, `findAll`, `findAll`, `findAllByName`, `findAllByNameCustom`, `findAllByNickName`, `findByBooksTitle`, `findByBooksTotalPages`, `findById`, `findByIdIsNotNull`, `findByName`, `findByNameContains`, `findByNameContainsIgnoreCase`, `findByNameEndsWith`, `findByNameEndsWithIgnoreCase`, `findByNameIgnoreCase`, `findByNameIsNotNull`, `findByNameStartsWith`, `findByNameStartsWithIgnoreCase`, `findOne`, `findOne`, `listAll`, `queryAll`, `queryByIdIsNotNull`, `queryByName`, `queryByNameContains`, `read`, `readAll`, `readByIdIsNotNull`, `readByNameIsNotNull`, `retrieveByIdIsNotNull`, `retrieveByName`, `searchAll`, `searchByName`, `searchByNameIsNotNull`, `updateNickname`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 36 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-tck/src/main/java/io/micronaut/data/tck/repositories/AuthorRepository.java:43
  • `PersonAsyncRepository` declares 25 abstract methods: `add1`, `add1Aliased`, `count`, `deleteByNameLike`, `deleteCustom`, `deleteCustomSingle`, `deleteCustomSingleNoEntity`, `erase`, `erase`, `findByName`, `findByNameLike`, `findByNameLike`, `findPeople`, `getById`, `getByName`, `getMaxId`, `list`, `queryByName`, `remove`, `save`, `saveCustom`, `saveCustomSingle`, `updateNamesCustom`, `updatePeople`, `updatePerson`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 25 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonAsyncRepository.java:34
  • `PersonReactiveRepository` declares 25 abstract methods: `count`, `deleteByNameLike`, `deleteCustom`, `deleteCustomSingle`, `deleteCustomSingleExpression`, `deleteCustomSingleNoEntity`, `findByName`, `findByNameLike`, `findByNameLike`, `findNameByNameLike`, `findPeople`, `getById`, `getByName`, `getMaxId`, `list`, `queryByAgeGreaterThan`, `queryByName`, `save`, `saveCustom`, `saveCustomSingle`, `saveCustomSingleExpression`, `searchByNameLike`, `updateNamesCustom`, `updatePeople`, `updatePerson`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonReactiveRepository.java:35
  • `PersonRepository` declares 57 abstract methods: `count`, `countByAgeGreaterThan`, `countByAgeLessThan`, `deleteByNameLike`, `deleteCustom`, `deleteCustomSingle`, `deleteCustomSingleExpression`, `deleteCustomSingleNoEntity`, `find`, `findAgeByName`, `findAll`, `findAllByAgeInRange`, `findAllByName`, `findAllByNameLike`, `findByName`, `findByNameLike`, `findByNameLike`, `findByNameLikeOrderByAge`, `findByNameLikeOrderByAgeDesc`, `findDistinct`, `findDistinctName`, `findMaxAgeByNameLike`, `findMinAgeByNameLike`, `findOptionalByName`, `findPeople`, `get`, `getAvgAgeByNameLike`, `getByName`, `getSumAgeByNameLike`, `getTotal`, `list`, `listTop10`, `queryByNameLike`, `queryNames`, `readAgeByNameLike`, `retrieve`, `save`, `saveCustom`, `saveCustom`, `saveCustomSingle`, and 17 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 57 declarations carry 53 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 53 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:53
  • `TrainRepository` declares 60 abstract methods: `deleteAll`, `findByCapacityAtLeast`, `findByCapacityBetween`, `findByCapacityGreaterThan`, `findByCapacityGreaterThanConstrain`, `findByCapacityGreaterThanEquals`, `findByModelIn`, `findByModelInConstrain`, `findByModelIsNotNull`, `findByModelIsNull`, `findByModelNot`, `findByModelNotLike`, `findByModelNotLikeConstrain`, `findByName`, `findByNameEqualsConstrain`, `findByNameEqualsConstrain`, `findByNameEqualsConstrainAndElectricConstraint`, `findByNameEqualsConstrainWithRestriction`, `findByNameLike`, `findByNameLikeConstrain`, `findByNameNotEqualsConstrain`, `findByNameNotIn`, `findByNameNotInConstrain`, `findBySpeedAtMost`, `findBySpeedLessThan`, `findBySpeedLessThanConstrain`, `findBySpeedLessThanEquals`, `findBySpeedNotBetween`, `findFirst2TrainNamesOrderedByName`, `findFirst2TrainNamesOrderedByName`, `findFirst2Trains`, `findFirst3Trains`, `findFirst3TrainsOrderedByCapacity`, `findFirst3TrainsOrderedByCapacity`, `findFirst4TrainsOrderedByName`, `findFirst4TrainsOrderedByName`, `findFirstTrain`, `findFirstTrainOrderedBySpeed`, `findFirstTrainOrderedBySpeed`, `findTrain`, and 20 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 60 declarations carry 50 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 50 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — data-tck/src/main/java/io/micronaut/data/tck/repositories/TrainRepository.java:58
  • `Catalog` declares 25 abstract methods: `add`, `addMultiple`, `allSortedByNameAsc`, `allSortedByNameAscIgnoreCase`, `allSortedByNameDesc`, `allSortedByNameDescIgnoreCase`, `countByPriceGreaterThanEqual`, `customSave`, `deleteById`, `deleteByProductNumLike`, `findAll`, `findByNameLengthAndPriceBelow`, `findByNameLengthAndPriceBelowNameAsc`, `findByNameLengthAndPriceBelowNameDesc`, `findByNameLike`, `findByPriceNotNullAndPriceLessThanEqual`, `findByPriceNull`, `findByProductNumBetween`, `findByProductNumLike`, `get`, `modify`, `modifyMultiple`, `remove`, `removeMultiple`, `withTaxBetween`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/Catalog.java:26
  • `AsciiCharacters` declares 23 abstract methods: `all`, `alphabetic`, `countByHexadecimalNotNull`, `existsByThisCharacter`, `find`, `find`, `findAll`, `findByHexadecimalContainsAndIsControlNot`, `findByHexadecimalIgnoreCase`, `findByHexadecimalIgnoreCaseBetweenAndHexadecimalNotIn`, `findByIdBetween`, `findByIsControlTrueAndNumericValueBetween`, `findByNumericValue`, `findByNumericValueBetween`, `findByNumericValueLessThanEqualAndNumericValueGreaterThanEqual`, `findFirst3ByNumericValueGreaterThanEqualAndHexadecimalEndsWith`, `findFirstByHexadecimalStartsWithAndIsControlOrderByIdAsc`, `getABCDFO`, `hex`, `jklOr`, `reverseAlphabetic`, `saveAll`, `twentyFour`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 22 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 22 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/read/only/AsciiCharacters.java:29
  • `BookRepository` declares 23 abstract methods: `delete`, `deleteAll`, `deleteByTitleLike`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findNativeBooks`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `list`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `persist`, `retrieveByTitle`, `update`, `updateByTitle`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — benchmarks/benchmark-micronaut-data-jpa/src/main/java/example/BookRepository.java:24
  • `AsyncBookRepository` declares 28 abstract methods: `countDistinctTitleByPagesGreaterThan`, `countTitleByPagesGreaterThan`, `deleteByTitleStartingWith`, `existsByAuthor`, `findAvgPagesByAuthor`, `findByAuthor`, `findByAuthorIsNotNull`, `findByAuthorIsNull`, `findByPagesGreaterThan`, `findByPagesGreaterThanEquals`, `findByPagesLessThan`, `findByPagesLessThanEquals`, `findByPublicationYearAfter`, `findByPublicationYearBefore`, `findByPublicationYearBetween`, `findByTitleContains`, `findByTitleEndingWith`, `findByTitleIn`, `findByTitleLike`, `findByTitleStartingWith`, `findDistinctTitleByPagesGreaterThan`, `findMaxPagesByAuthor`, `findMinPagesByAuthor`, `findSumPagesByAuthor`, `insert`, `insertBooks`, `update`, `updateByTitleStartingWith`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — doc-examples/coherence-example-java/src/main/java/io/micronaut/coherence/data/repositories/AsyncBookRepository.java:34
  • `BookRepository` declares 28 abstract methods: `countDistinctTitleByPagesGreaterThan`, `countTitleByPagesGreaterThan`, `deleteByTitleStartingWith`, `existsByAuthor`, `findAvgPagesByAuthor`, `findByAuthor`, `findByAuthorIsNotNull`, `findByAuthorIsNull`, `findByPagesGreaterThan`, `findByPagesGreaterThanEquals`, `findByPagesLessThan`, `findByPagesLessThanEquals`, `findByPublicationYearAfter`, `findByPublicationYearBefore`, `findByPublicationYearBetween`, `findByTitleContains`, `findByTitleEndingWith`, `findByTitleIn`, `findByTitleLike`, `findByTitleStartingWith`, `findDistinctTitleByPagesGreaterThan`, `findMaxPagesByAuthor`, `findMinPagesByAuthor`, `findSumPagesByAuthor`, `insert`, `insertBooks`, `update`, `updateByTitleStartingWith`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — doc-examples/coherence-example-java/src/main/java/io/micronaut/coherence/data/repositories/BookRepository.java:33
  • `BookRepository` declares 33 abstract methods: `delete`, `deleteAll`, `deleteByTitleLike`, `deleteMany`, `deleteOne`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findNativeBooks`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `insertCustomExp`, `insertMany`, `insertOne`, `list`, `listAll`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `retrieveByTitle`, `save`, `update`, `update`, `updateByTitle`, `updateMany`, `updateOne`, `updatePages`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 33 declarations carry 31 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 31 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — doc-examples/hibernate-example-java/src/main/java/example/BookRepository.java:21
  • `BookRepository` declares 30 abstract methods: `calculateSum`, `delete`, `deleteAll`, `deleteByTitleLike`, `find`, `find`, `findBooks`, `findByPagesBetween`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findByTitleStartingWith`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `insertCustomExp`, `list`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `persist`, `retrieveByTitle`, `searchBooksByTitle`, `update`, `update`, `updateByTitle`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 30 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — doc-examples/jdbc-example-java/src/main/java/example/BookRepository.java:18
  • `BookRepository` declares 24 abstract methods: `delete`, `deleteAll`, `deleteByTitleLike`, `find`, `findBooks`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `list`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `persist`, `retrieveByTitle`, `update`, `update`, `updateByTitle`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 24 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — doc-examples/jdbc-example-records-java/src/main/java/example/BookRepository.java:15
  • `FamilyRepository` declares 21 abstract methods: `findById`, `updateRegistered`, `updateAddress`, `updateLastName`, `queryById`, `deleteByLastName`, `deleteById`, `deleteByRegistered`, `existsByIdAndRegistered`, `countByRegistered`, `lastOrderedLastName`, `lastOrderedRegisteredDate`, `findByAddressStateAndAddressCityOrderByAddressCity`, `updateByAddressCounty`, `findByChildrenPetsType`, `findChildrenByChildrenPetsGivenName`, `findByIdIn`, `findByIdNotIn`, `findByLastNameLike`, `findByTagsArrayContains`, `childrenArrayContainsGender`. 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. — doc-examples/azure-cosmos-example-kotlin/src/main/kotlin/example/FamilyRepository.kt:20
  • `BookRepository` declares 30 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitleLike`, `list`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `listOrderByTitle`, `listOrderByTitleDesc`, `listBooks`, `save`, `insert`, `insertOne`, `insertMany`, `persist`, `update`, `updateByTitle`, `updatePages`, `updateOne`, `updateMany`, `deleteAll`, `deleteOne`, `deleteMany`, `delete`, `deleteByTitleLike`, `findOne`, `findNativeBooks`. 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. — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookRepository.kt:12
  • `BookRepository` declares 31 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitleLike`, `list`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `listOrderByTitle`, `listOrderByTitleDesc`, `listBooks`, `save`, `insert`, `insertOne`, `insertMany`, `persist`, `update`, `updateByTitle`, `updatePages`, `updateOne`, `updateMany`, `deleteAll`, `deleteOne`, `deleteMany`, `delete`, `deleteByTitleLike`, `findOne`, `findNativeBooks`, `listAll`. 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. — doc-examples/hibernate-example-kotlin/src/main/kotlin/example/BookRepository.kt:13
  • `BookRepository` declares 25 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitleLike`, `list`, `findByPagesBetween`, `findByTitleStartingWith`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `listOrderByTitle`, `listOrderByTitleDesc`, `listBooks`, `persist`, `update`, `updateByTitle`, `deleteAll`, `delete`, `deleteByTitleLike`, `findOne`, `findBooks`, `calculateSum`, `searchBooksByTitle`. 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. — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/BookRepository.kt:18
  • `BookRepository` declares 23 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleRegex`, `findByTitleRegex`, `list`, `findTitleByPagesGreaterThan`, `findTop3ByTitleRegex`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `update`, `updateByTitle`, `deleteAll`, `delete`, `deleteByTitleRegex`, `findOne`, `customFind`, `customAggregate`, `customUpdate`, `customDelete`. 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. — doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/BookRepository.kt:15
  • `BookRepository` declares 24 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleRegex`, `findByTitleRegex`, `list`, `findTitleByPagesGreaterThan`, `findTop3ByTitleRegex`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `update`, `updateByTitle`, `deleteAll`, `delete`, `deleteByTitleRegex`, `findOne`, `customFind`, `customAggregate`, `customUpdate`, `customDelete`, `incrementPagesAfter`. 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. — doc-examples/mongo-example-kotlin/src/main/kotlin/example/BookRepository.kt:16
  • `BookRepository` declares 19 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleRegex`, `findByTitleRegex`, `list`, `findTitleByPagesGreaterThan`, `findTop3ByTitleRegex`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `update`, `updateByTitle`, `deleteAll`, `delete`, `deleteByTitleRegex`, `findOne`. 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. — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/BookRepository.kt:13
  • `BookRepository` declares 17 abstract methods: `findById`, `findAll`, `findTitleById`, `save`, `saveAll`, `customFindOne`, `findOne`, `calculateSum`, `saveReturning`, `saveReturningMany`, `saveReturningManyAsList`, `updateReturning`, `updateReturningMany`, `updateReturningManyAsList`, `deleteReturning`, `deleteReturningMany`, `deleteReturningManyAsList`. 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. — doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/BookRepository.kt:16

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
  • Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

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

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

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

DM10 · One transaction, one aggregate9.6 / 10Exemplary✓ Tool-verified

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

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

  • `OneToManyJoinColumnTest.testOneToManySaveAndLoad` saves `EmployeeRepository`, `EmployeeGroupRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/one2many/OneToManyJoinColumnTest.java:30
  • `MultipleDataSourceTest.testMultipleDataSources` saves `SQLitePersonRepository`, `OtherPersonRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/MultipleDataSourceTest.java:58
  • `SQLiteCompositePrimaryKeyTest.testCrudWithCompositeId` saves `Project`, `ProjectId` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteCompositePrimaryKeyTest.java:37
  • `SQLiteJSONTest.testSaveUpdateIterable` saves `JsonEntity`, `List` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteJSONTest.java:227
  • `SQLiteValidationTest.testSaveValidObjects` saves `SQLiteMealRepository`, `SQLiteFoodRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteValidationTest.java:42
  • `SQLiteValidationTest.testUpdateInvalidObjects` saves `Meal`, `var` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteValidationTest.java:68
  • `InitController.init` saves `Owner`, `Pet` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — doc-examples/jooq-r2dbc-postgres/src/main/java/example/InitController.java:36
  • `PessimisticLockingSpec.findMethodsForUpdate` saves `manufacturerRepository`, `productLockingRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — doc-examples/jdbc-example-python/src/test/python/example/PessimisticLockingSpec.py:47
  • `SaleRepositorySpec.testReadWriteCustomType` saves `manufacturerRepository`, `productRepository`, `saleRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. (×2) — doc-examples/jdbc-example-python/src/test/python/example/SaleRepositorySpec.py:23, doc-examples/mongo-example-python/src/test/python/example/SaleRepositorySpec.py:23
  • `BookControllerTest.setupData` saves `authorRepository`, `bookRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — doc-examples/r2dbc-example-python/src/test/python/example/BookControllerTest.py:32

What to do

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

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

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

  • `Author`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Author` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Author.kt:10
  • `Book`'s public constructor takes `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×5) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Book.kt:9, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Book.kt:9, doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Book.kt:9, …
  • `Child`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Child` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×3) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Child.kt:9, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Child.kt:10, data-tck/src/main/java/io/micronaut/data/tck/entities/Child.java:28
  • `Genre`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Genre` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Genre.kt:7
  • `Student`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Student` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×4) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Student.kt:10, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Student.kt:10, doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Student.kt:20, …
  • `User`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — doc-examples/hibernate-example-kotlin/src/main/kotlin/example/User.kt:10
  • `Person`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Person` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Person.kt:15
  • `Project`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Project` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×2) — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Project.kt:8, data-tck/src/main/java/io/micronaut/data/tck/jdbc/entities/Project.java:44
  • `Review`'s public constructor takes `reviewer`, `content` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Review` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Review.kt:17
  • `ClientCategory`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ClientCategory` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/ClientCategory.java:46
  • `Company`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Company` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/Company.java:45
  • `EmployeeFieldAccess`'s public constructor takes `name`, `salary` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmployeeFieldAccess` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/EmployeeFieldAccess.java:47
  • `EmployeeMixedAccess`'s public constructor takes `name`, `salary` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmployeeMixedAccess` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/EmployeeMixedAccess.java:36
  • `EmployeePropertyAccess`'s public constructor takes `name`, `salary` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmployeePropertyAccess` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/EmployeePropertyAccess.java:35
  • `ExampleEntity`'s public constructor takes `uppercaseColumn`, `lowercaseColumn` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ExampleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/ExampleEntity.java:24
  • `Face`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Face` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/Face.java:46
  • `Order`'s public constructor takes `customer`, `weight` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Order` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/Order.java:44
  • `Product`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Product` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×4) — data-tck/src/main/java/io/micronaut/data/tck/entities/Product.java:56, benchmarks/benchmark-micronaut-data-jpa/src/main/java/example/Product.java:30, benchmarks/benchmark-spring-data/src/main/java/example/Product.java:30, …
  • `Shipment`'s public constructor takes `field` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Shipment` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/Shipment.java:30
  • `ShipmentWithIndex`'s public constructor takes `field`, `taxCode` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ShipmentWithIndex` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/ShipmentWithIndex.java:33
  • `Train`'s public constructor takes `name`, `model`, `capacity`, `speed` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Train` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/Train.java:69
  • `TrainManufacturer`'s public constructor takes `name`, `country`, `foundedYear` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TrainManufacturer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — data-tck/src/main/java/io/micronaut/data/tck/entities/TrainManufacturer.java:41
  • `Book`'s public constructor takes `title`, `pages` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×5) — benchmarks/benchmark-micronaut-data-jdbc/src/main/java/example/Book.java:28, benchmarks/benchmark-micronaut-data-jpa/src/main/java/example/Book.java:28, benchmarks/benchmark-spring-data/src/main/java/example/Book.java:28, …

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM4 · Rich vs anemic model8.7 / 10Strong✓ Tool-verified

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

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

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

  • `Author` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Author.kt:10
  • `Book` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×4) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Book.kt:9, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Book.kt:9, doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Book.kt:9, …
  • `Child` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Child.kt:9
  • `Genre` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Genre.kt:7
  • `Student` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×3) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Student.kt:10, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Student.kt:10, doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Student.kt:10
  • `Child` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Child.kt:10
  • `User` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/hibernate-example-kotlin/src/main/kotlin/example/User.kt:10
  • `Book` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Book.kt:10
  • `Person` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Person.kt:8
  • `Project` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Project.kt:8, doc-examples/jdbc-example-java/src/main/java/example/Project.java:8
  • `Review` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Review.kt:10, doc-examples/jdbc-example-java/src/main/java/example/Review.java:18
  • `Order` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — data-tck/src/main/java/io/micronaut/data/tck/entities/Order.java:28

What to do

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

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

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

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

  • `Book` exposes publicly writable state (id, title, pages). (×3) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Book.kt:9, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Book.kt:9, doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Book.kt:9
  • `Student` exposes publicly writable state (id). (×2) — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Student.kt:10, doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Student.kt:10
  • `User` exposes publicly writable state (id, name, enabled). — doc-examples/hibernate-example-kotlin/src/main/kotlin/example/User.kt:10
  • `Student` exposes publicly writable state (id, name). — doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Student.kt:10
  • `Person` exposes publicly writable state (id, name, age). — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Person.kt:8

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM7 · Repository granularity1.7 / 10Critical✓ Tool-verified

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

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

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

  • `StudentRepository` is a repository over `Student`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Student` through its owning aggregate instead. — doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/StudentRepository.kt:8
  • `AuthorRepository` is a repository over `Author`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Author` through its owning aggregate instead. (×2) — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/AuthorRepository.kt:11, data-tck/src/main/java/io/micronaut/data/tck/repositories/AuthorRepository.java:43
  • `UserRepository` is a repository over `User`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `User` through its owning aggregate instead. — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/UserRepository.kt:10
  • `AccountRepository` is a repository over `Account`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Account` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/AccountRepository.java:25
  • `CarRepository` is a repository over `Car`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Car` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/CarRepository.java:26
  • `CategoryRepository` is a repository over `Category`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Category` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/CategoryRepository.java:28
  • `ChapterRepository` is a repository over `Chapter`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Chapter` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ChapterRepository.java:22
  • `ChildRepository` is a repository over `Child`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Child` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ChildRepository.java:24
  • `ClientCategoryRepository` is a repository over `ClientCategory`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ClientCategory` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ClientCategoryRepository.java:22
  • `ClientRepository` is a repository over `Client`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Client` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ClientRepository.java:26
  • `CompanyRepository` is a repository over `Company`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Company` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/CompanyRepository.java:25
  • `EmbeddedOwnerRepository` is a repository over `EmbeddedOwner`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmbeddedOwner` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/EmbeddedOwnerRepository.java:25
  • `EmployeeFieldAccessRepository` is a repository over `EmployeeFieldAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeeFieldAccess` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeeFieldAccessRepository.java:24
  • `EmployeeMixedAccessEmbeddedIdRepository` is a repository over `EmployeeMixedAccessEmbeddedId`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeeMixedAccessEmbeddedId` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeeMixedAccessEmbeddedIdRepository.java:26
  • `EmployeeMixedAccessRepository` is a repository over `EmployeeMixedAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeeMixedAccess` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeeMixedAccessRepository.java:24
  • `EmployeePropertyAccessRepository` is a repository over `EmployeePropertyAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeePropertyAccess` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeePropertyAccessRepository.java:24
  • `EntityWithIdClassRepository` is a repository over `EntityWithIdClass`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EntityWithIdClass` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/EntityWithIdClassRepository.java:26
  • `ExampleEntityRepository` is a repository over `ExampleEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ExampleEntity` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ExampleEntityRepository.java:22
  • `FaceRepository` is a repository over `Face`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Face` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/FaceRepository.java:22
  • `GenreRepository` is a repository over `Genre`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Genre` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/GenreRepository.java:21
  • `NoseRepository` is a repository over `Nose`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Nose` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/NoseRepository.java:21
  • `OrderRepository` is a repository over `Order`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Order` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/OrderRepository.java:21
  • `PageRepository` is a repository over `Page`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Page` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PageRepository.java:27
  • `PersonAsyncRepository` is a repository over `Person`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Person` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonAsyncRepository.java:34
  • `ProjectRepository` is a repository over `Project`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Project` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ProjectRepository.java:23
  • `PublisherRepository` is a repository over `Publisher`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Publisher` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PublisherRepository.java:22
  • `PurchaseOrderRepository` is a repository over `PurchaseOrder`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PurchaseOrder` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/PurchaseOrderRepository.java:24
  • `ShelfRepository` is a repository over `Shelf`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Shelf` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/ShelfRepository.java:24
  • `StudentReactiveRepository` is a repository over `Student`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Student` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/StudentReactiveRepository.java:25
  • `TrainRepository` is a repository over `Train`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Train` through its owning aggregate instead. — data-tck/src/main/java/io/micronaut/data/tck/repositories/TrainRepository.java:58
  • `Boxes` is a repository over `Box`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Box` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/entity/Boxes.java:11
  • `Catalog` is a repository over `CatalogProduct`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `CatalogProduct` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/Catalog.java:26
  • `AsciiCharacters` is a repository over `AsciiCharacter`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AsciiCharacter` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/read/only/AsciiCharacters.java:29
  • `NaturalNumbers` is a repository over `NaturalNumber`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `NaturalNumber` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/read/only/NaturalNumbers.java:28
  • `FooRepo` is a repository over `Foo`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Foo` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteEmbedded2Test.java:58
  • `ItemGroupRepository` is a repository over `ItemGroup`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ItemGroup` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteEmbeddedIdTest.java:346
  • `JpaEnumEntityRepository` is a repository over `JpaEnumEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `JpaEnumEntity` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteEnumsMappingTest.java:188
  • `ShipmentRepository` is a repository over `Shipment`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Shipment` through its owning aggregate instead. — test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/ShipmentRepository.java:29

What to do

  • Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • `getJoinedFields` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:532

What to do

  • Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×20) — doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java:41, doc-examples/mongo-jackson-example-java/src/test/java/example/Tests.java:128, test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/AbstractManualSchemaTest.java:121, …

What to do

  • Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

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

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

What to do

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

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

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

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

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

P2 · Observability7.3 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 24/56 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `doc-examples/azure-cosmos-example-java`, `doc-examples/azure-cosmos-example-kotlin`, `doc-examples/hibernate-multitenancy-discriminator-example-java`, `doc-examples/hibernate-reactive-example-java`, `doc-examples/hibernate-reactive-example-kotlin` and 27 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 10 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:13

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.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF1 · Benchmark discipline8.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

  • A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/benchmark-spring-data-mongodb/src/jmh/java/example/SimpleQuery.java

What to do

  • Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

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

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • 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. (×12) — data-tck/src/main/java/io/micronaut/data/tck/services/ConnectionBookService.java:82, data-tck/src/main/java/io/micronaut/data/tck/services/ConnectionBookService.java:92, data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:205, …
  • `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. (×3) — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnNameR2dbcResultReader.java:145, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:240, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:500
  • `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. (×3) — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Projections.java:48, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Restrictions.java:50, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Restrictions.java:60

What to do

  • Swallowed exception (empty catch)
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.

X4 · Structured logging6.7 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `warn` at line 393 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:393
  • `warn` at line 412 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:412
  • `warn` at line 421 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:421
  • `warn` at line 435 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:435
  • `debug` at line 421 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:421
  • `debug` at line 428 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:428
  • `error` at line 499 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:499
  • `error` at line 559 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:559

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types3.8 / 10Weak✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

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

  • 49/207 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

Reference — by lens

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

LensScoreRatingImpact
Code Health64.3Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture70.9StrongSolid.
Maturity58.8Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness66.3Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security87.5StrongSolid.
Domain Modelling57.4Adequate — gated by DM7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance91.4ExemplaryStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .py, .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 — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit 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 audit 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.
  • C4 Data Retention — Not assessed: these retention 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 retention 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.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 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 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
  • 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 — docker build failed (exit 1) — 1 | FROM adoptopenjdk/openjdk11-openj9:jdk-11.0.1.13-alpine-slim 2 | >>> COPY build/libs/*.jar example-java.jar 3 | EXPOSE 8080 4 | CMD java -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -Dcom.sun.management.jmxremote -noverify ${JAVA_OPTS} -jar example-java.jar -------------------- ERROR: failed to solve: lstat /build/libs: no such file or directory; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data 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 personal data 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.
  • 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.
  • D12 Dependency Hygiene — Not scored — 115 Maven/Gradle manifest(s) were read, stating a version for 42 dependency(ies) and leaving 6 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, .py, 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
  • 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).
  • D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • 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
  • DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
  • DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 10 event handler(s); 2 CQRS handler(s)
  • ED5 Idempotency — Not assessed, and this one is on us: 12 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 only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
  • 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
  • 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
  • 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.
  • X1 Async correctness — X1 reached only 6% of this repository's production lines — java (176,344 lines), groovy (3,963 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 6% of this repository's production lines — java (176,344 lines), groovy (3,963 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 9 finding(s)
D14 · License Compliance · Banned license · ×3
  • Banned license: org.orbisgis:h2gis — `org.orbisgis:h2gis` 2.2.5 is published on Maven Central under `LGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: org.openjdk.jmh:jmh-core — `org.openjdk.jmh:jmh-core` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
  • Banned license: org.openjdk.jmh:jmh-generator-annprocess — `org.openjdk.jmh:jmh-generator-annprocess` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · Assertions commented out · ×1
  • Assertions commented out: shouldThrowIfBuildingJoin doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/query/CohQLQueryTest.java:40 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D11 · Test Reliability · Test declared unreliable · ×1
  • Test declared unreliable: shouldGetBooksById doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java:41 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Flaky test". 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.)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 1020 finding(s)
DM11 · Constructible invalid state · Constructible in an invalid state · ×40
  • Constructible in an invalid state: Author doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Author.kt:10 — `Author`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Author` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Book doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Book.kt:9 — `Book`'s public constructor takes `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Child doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Child.kt:9 — `Child`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Child` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Genre doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Genre.kt:7 — `Genre`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Genre` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Student doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Student.kt:10 — `Student`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Student` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Book doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Book.kt:9 — `Book`'s public constructor takes `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Child doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Child.kt:10 — `Child`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Child` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Student doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Student.kt:10 — `Student`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Student` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: User doc-examples/hibernate-example-kotlin/src/main/kotlin/example/User.kt:10 — `User`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Book doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Book.kt:9 — `Book`'s public constructor takes `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Student doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Student.kt:20 — `Student`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Student` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Book doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Book.kt:17 — `Book`'s public constructor takes `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Person doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Person.kt:15 — `Person`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Person` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Project doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Project.kt:8 — `Project`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Project` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Review doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Review.kt:17 — `Review`'s public constructor takes `reviewer`, `content` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Review` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Book doc-examples/jdbc-jakarta-data-example-kotlin/src/main/kotlin/example/Book.kt:8 — `Book`'s public constructor takes `title` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Child data-tck/src/main/java/io/micronaut/data/tck/entities/Child.java:28 — `Child`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Child` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ClientCategory data-tck/src/main/java/io/micronaut/data/tck/entities/ClientCategory.java:46 — `ClientCategory`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ClientCategory` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Company data-tck/src/main/java/io/micronaut/data/tck/entities/Company.java:45 — `Company`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Company` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: EmployeeFieldAccess data-tck/src/main/java/io/micronaut/data/tck/entities/EmployeeFieldAccess.java:47 — `EmployeeFieldAccess`'s public constructor takes `name`, `salary` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmployeeFieldAccess` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: EmployeeMixedAccess data-tck/src/main/java/io/micronaut/data/tck/entities/EmployeeMixedAccess.java:36 — `EmployeeMixedAccess`'s public constructor takes `name`, `salary` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmployeeMixedAccess` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: EmployeePropertyAccess data-tck/src/main/java/io/micronaut/data/tck/entities/EmployeePropertyAccess.java:35 — `EmployeePropertyAccess`'s public constructor takes `name`, `salary` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmployeePropertyAccess` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ExampleEntity data-tck/src/main/java/io/micronaut/data/tck/entities/ExampleEntity.java:24 — `ExampleEntity`'s public constructor takes `uppercaseColumn`, `lowercaseColumn` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ExampleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Face data-tck/src/main/java/io/micronaut/data/tck/entities/Face.java:46 — `Face`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Face` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Order data-tck/src/main/java/io/micronaut/data/tck/entities/Order.java:44 — `Order`'s public constructor takes `customer`, `weight` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Order` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • + 15 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×39
  • TooManyMethods: AbstractCriteriaBuilder data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractCriteriaBuilder.java:90 — TooManyMethods — 204 methods. The bar is 30 methods; this is 174 over it, 6.80× 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: SqlQueryBuilder data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:116 — TooManyMethods — 105 methods. The bar is 30 methods; this is 75 over it, 3.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AbstractSqlLikeQueryBuilder data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:142 — TooManyMethods — 100 methods. The bar is 30 methods; this is 70 over it, 3.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: DefaultJdbcRepositoryOperations data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:164 — TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.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: HibernateJpaOperations data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:117 — TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.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: BasicTypesProjection data-tck/src/main/java/io/micronaut/data/tck/entities/BasicTypesProjection.java:35 — TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AbstractQueryInterceptor data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:109 — TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.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: DefaultMongoRepositoryOperations data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:121 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× 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: DefaultHibernateReactiveRepositoryOperations data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:78 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DefaultReactiveMongoRepositoryOperations data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:97 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 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.
  • TooManyMethods: JQCriteriaBuilderUtils data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:82 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 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.
  • TooManyMethods: ArraysDto data-tck/src/main/java/io/micronaut/data/tck/entities/ArraysDto.java:25 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: BookRepository data-tck/src/main/java/io/micronaut/data/tck/repositories/BookRepository.java:57 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: DefaultReactiveCosmosRepositoryOperations data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:127 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: DefaultR2dbcRepositoryOperations data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:166 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: AbstractPersistentEntityFrom data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityFrom.java:63 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: AbstractTransactionOperations data-tx/src/main/java/io/micronaut/transaction/support/AbstractTransactionOperations.java:55 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: MongoPredicateVisitor data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1065 — 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: QueryCriteriaMethodMatch data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:101 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SqlSelectionVisitor data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3325 — 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: RuntimePersistentEntity data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:55 — 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: TxBookService data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:33 — 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: Where data-runtime/src/main/kotlin/io/micronaut/data/runtime/criteria/KCriteriaBuilderExt.kt:249 — 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: MongoFindOptions data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoFindOptions.java:33 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AbstractHibernateOperations data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/AbstractHibernateOperations.java:96 — 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.
  • + 14 more in this group — see findings.md.
DM7 · Repository granularity · Repository for a non-root entity · ×39
  • Repository for a non-root entity: StudentRepository → Student doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/StudentRepository.kt:8 — `StudentRepository` is a repository over `Student`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Student` through its owning aggregate instead.
  • Repository for a non-root entity: AuthorRepository → Author doc-examples/jdbc-example-kotlin/src/main/kotlin/example/AuthorRepository.kt:11 — `AuthorRepository` is a repository over `Author`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Author` through its owning aggregate instead.
  • Repository for a non-root entity: UserRepository → User doc-examples/jdbc-example-kotlin/src/main/kotlin/example/UserRepository.kt:10 — `UserRepository` is a repository over `User`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `User` through its owning aggregate instead.
  • Repository for a non-root entity: AccountRepository → Account data-tck/src/main/java/io/micronaut/data/tck/repositories/AccountRepository.java:25 — `AccountRepository` is a repository over `Account`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Account` through its owning aggregate instead.
  • Repository for a non-root entity: AuthorRepository → Author data-tck/src/main/java/io/micronaut/data/tck/repositories/AuthorRepository.java:43 — `AuthorRepository` is a repository over `Author`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Author` through its owning aggregate instead.
  • Repository for a non-root entity: CarRepository → Car data-tck/src/main/java/io/micronaut/data/tck/repositories/CarRepository.java:26 — `CarRepository` is a repository over `Car`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Car` through its owning aggregate instead.
  • Repository for a non-root entity: CategoryRepository → Category data-tck/src/main/java/io/micronaut/data/tck/repositories/CategoryRepository.java:28 — `CategoryRepository` is a repository over `Category`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Category` through its owning aggregate instead.
  • Repository for a non-root entity: ChapterRepository → Chapter data-tck/src/main/java/io/micronaut/data/tck/repositories/ChapterRepository.java:22 — `ChapterRepository` is a repository over `Chapter`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Chapter` through its owning aggregate instead.
  • Repository for a non-root entity: ChildRepository → Child data-tck/src/main/java/io/micronaut/data/tck/repositories/ChildRepository.java:24 — `ChildRepository` is a repository over `Child`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Child` through its owning aggregate instead.
  • Repository for a non-root entity: ClientCategoryRepository → ClientCategory data-tck/src/main/java/io/micronaut/data/tck/repositories/ClientCategoryRepository.java:22 — `ClientCategoryRepository` is a repository over `ClientCategory`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ClientCategory` through its owning aggregate instead.
  • Repository for a non-root entity: ClientRepository → Client data-tck/src/main/java/io/micronaut/data/tck/repositories/ClientRepository.java:26 — `ClientRepository` is a repository over `Client`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Client` through its owning aggregate instead.
  • Repository for a non-root entity: CompanyRepository → Company data-tck/src/main/java/io/micronaut/data/tck/repositories/CompanyRepository.java:25 — `CompanyRepository` is a repository over `Company`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Company` through its owning aggregate instead.
  • Repository for a non-root entity: EmbeddedOwnerRepository → EmbeddedOwner data-tck/src/main/java/io/micronaut/data/tck/repositories/EmbeddedOwnerRepository.java:25 — `EmbeddedOwnerRepository` is a repository over `EmbeddedOwner`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmbeddedOwner` through its owning aggregate instead.
  • Repository for a non-root entity: EmployeeFieldAccessRepository → EmployeeFieldAccess data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeeFieldAccessRepository.java:24 — `EmployeeFieldAccessRepository` is a repository over `EmployeeFieldAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeeFieldAccess` through its owning aggregate instead.
  • Repository for a non-root entity: EmployeeMixedAccessEmbeddedIdRepository → EmployeeMixedAccessEmbeddedId data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeeMixedAccessEmbeddedIdRepository.java:26 — `EmployeeMixedAccessEmbeddedIdRepository` is a repository over `EmployeeMixedAccessEmbeddedId`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeeMixedAccessEmbeddedId` through its owning aggregate instead.
  • Repository for a non-root entity: EmployeeMixedAccessRepository → EmployeeMixedAccess data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeeMixedAccessRepository.java:24 — `EmployeeMixedAccessRepository` is a repository over `EmployeeMixedAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeeMixedAccess` through its owning aggregate instead.
  • Repository for a non-root entity: EmployeePropertyAccessRepository → EmployeePropertyAccess data-tck/src/main/java/io/micronaut/data/tck/repositories/EmployeePropertyAccessRepository.java:24 — `EmployeePropertyAccessRepository` is a repository over `EmployeePropertyAccess`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmployeePropertyAccess` through its owning aggregate instead.
  • Repository for a non-root entity: EntityWithIdClassRepository → EntityWithIdClass data-tck/src/main/java/io/micronaut/data/tck/repositories/EntityWithIdClassRepository.java:26 — `EntityWithIdClassRepository` is a repository over `EntityWithIdClass`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EntityWithIdClass` through its owning aggregate instead.
  • Repository for a non-root entity: ExampleEntityRepository → ExampleEntity data-tck/src/main/java/io/micronaut/data/tck/repositories/ExampleEntityRepository.java:22 — `ExampleEntityRepository` is a repository over `ExampleEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `ExampleEntity` through its owning aggregate instead.
  • Repository for a non-root entity: FaceRepository → Face data-tck/src/main/java/io/micronaut/data/tck/repositories/FaceRepository.java:22 — `FaceRepository` is a repository over `Face`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Face` through its owning aggregate instead.
  • Repository for a non-root entity: GenreRepository → Genre data-tck/src/main/java/io/micronaut/data/tck/repositories/GenreRepository.java:21 — `GenreRepository` is a repository over `Genre`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Genre` through its owning aggregate instead.
  • Repository for a non-root entity: NoseRepository → Nose data-tck/src/main/java/io/micronaut/data/tck/repositories/NoseRepository.java:21 — `NoseRepository` is a repository over `Nose`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Nose` through its owning aggregate instead.
  • Repository for a non-root entity: OrderRepository → Order data-tck/src/main/java/io/micronaut/data/tck/repositories/OrderRepository.java:21 — `OrderRepository` is a repository over `Order`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Order` through its owning aggregate instead.
  • Repository for a non-root entity: PageRepository → Page data-tck/src/main/java/io/micronaut/data/tck/repositories/PageRepository.java:27 — `PageRepository` is a repository over `Page`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Page` through its owning aggregate instead.
  • Repository for a non-root entity: PersonAsyncRepository → Person data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonAsyncRepository.java:34 — `PersonAsyncRepository` is a repository over `Person`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Person` through its owning aggregate instead.
  • + 14 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×31
  • TodoComment jakarta-data-tck/mongodb/src/test/java/io/micronaut/data/jakarta/tck/FilterExtension.java:54 — // 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 jakarta-data-tck/mongodb/src/test/java/io/micronaut/data/jakarta/tck/FilterExtension.java:73 — // 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 jakarta-data-tck/mongodb/src/test/java/io/micronaut/data/jakarta/tck/FilterExtension.java:78 — // 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 jakarta-data-tck/mongodb/src/test/java/io/micronaut/data/jakarta/tck/FilterExtension.java:83 — // 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 doc-examples/r2dbc-example-python/src/main/python/example/BookRepository.py:26 — # TODO(python): overriding the inherited generic `<S extends Book> Publisher<S> saveAll(Iterable<S>)` is not — 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 doc-examples/mongo-jackson-example-java/src/test/java/example/Tests.java:128 — // TODO: Implement in Micronaut Serialization — 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 doc-examples/mongo-example-python/src/main/python/example/PersonRepository.py:12 — # TODO(python): the specification methods are declared on the repository instead of extending JpaSpecificationExecutor: — 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 doc-examples/jdbc-example-python/src/main/python/example/PersonRepository.py:11 — # TODO(python): the specification methods are declared on the repository instead of extending JpaSpecificationExecutor: — 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 doc-examples/hibernate-example-python/src/main/python/example/ProductRepository.py:13 — # TODO(python): the specification methods are declared on the repository instead of extending JpaSpecificationExecutor: — 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 doc-examples/azure-cosmos-example-python/src/main/python/example/FamilyRepository.py:17 — # TODO(python): the specification methods are declared on the repository instead of extending JpaSpecificationExecutor: — 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 doc-examples/azure-cosmos-example-python/src/main/python/example/PersonRepository.py:10 — # TODO(python): the specification methods are declared on the repository instead of extending JpaSpecificationExecutor: — 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 doc-examples/jdbc-spring-tx-example-java/src/test/java/example/BookRepositorySpec.java:32 — // TODO Assertions.assertEquals(1, bookManager.getEvents().size()); — 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 doc-examples/jdbc-example-kotlin/src/test/kotlin/example/PersonSuspendRepositorySpec.kt:78 — // TODO: this should throw an exception because the type is not Kotlin nullable but context returns nullable — 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 doc-examples/hibernate-spring-tx-example-java/src/test/java/example/BookRepositorySpec.java:33 — // TODO: Assertions.assertEquals(1, bookManager.getEvents().size()); — 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 doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/query/CohQLQueryTest.java:41 — // TODO: Need to update coherence after Micronaut 5 is released and this test might be obsolete — 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 data-tx-hibernate/src/test/java/io/micronaut/transaction/hibernate6/micronaut/ReadOnlyTest.java:43 — // TODO: Fix this combination — 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 data-tx-hibernate/src/test/java/io/micronaut/transaction/hibernate6/micronaut/ReadOnlyTest.java:52 — // TODO: Fix this combination — 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 data-spring-jpa/src/test/java/io/micronaut/data/spring/hibernate/micronaut/ReadOnlyTest.java:43 — // TODO: Fix this combination — 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 data-spring-jpa/src/test/java/io/micronaut/data/spring/hibernate/micronaut/ReadOnlyTest.java:52 — // TODO: Fix this combination — 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 data-tck/src/main/java/io/micronaut/data/tck/repositories/TrainRepository.java:157 — // TODO: fix postponed compilation @OrderBy(_Train.NAME) — 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 data-spring-jpa/src/main/java/io/micronaut/data/spring/jpa/hibernate/SpringHibernateConnectionOperations.java:43 — // TODO: We should avoid using @Replaces, there should be a way to use different data sources with Micronaut and Spring TX — 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 data-spring-jdbc/src/main/java/io/micronaut/data/spring/jdbc/SpringJdbcConnectionOperations.java:47 — // TODO: We should avoid using @Replaces, there should be a way to use different data sources with Micronaut and Spring TX — 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 data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:937 — // TODO: Support adding an expression annotation value in Core — 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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:251 — // TODO: support embedded ID — 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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpdateMethodMatcher.java:287 — // TODO: support embedded ID — 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.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×28
  • Duplicated block (6 lines × 2) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:283 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:283-289 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:351-356 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:713 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:713-718 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:326-331 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:713` 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 (6 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:752 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:752-757 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:922-927 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `options` to `UpdateOptions` in one and `FindOneAndUpdateOptions` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:91 — data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:91-96 | data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:99-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:447 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:447-452 | data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/DefaultPreparedQuery.java:215-220 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Shipment.java:75 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Shipment.java:75-80 | data-tck/src/main/java/io/micronaut/data/tck/entities/Shipment.java:71-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (6 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/ShipmentId.java:74 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/ShipmentId.java:74-79 | data-tck/src/main/java/io/micronaut/data/tck/entities/ShipmentId.java:69-74 — before extracting anything, compare `data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/ShipmentId.java` and `data-tck/src/main/java/io/micronaut/data/tck/entities/ShipmentId.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (6 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/AbstractJdbcVectorConverter.java:66 — data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/AbstractJdbcVectorConverter.java:66-71 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/AbstractR2dbcVectorConverter.java:66-71 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/AbstractJdbcVectorConverter.java` and `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/AbstractR2dbcVectorConverter.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:122 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:122-127 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:193-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:122` 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 (6 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:157 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:157-162 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:140-145 — before extracting anything, compare `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:146` calls `retainAll` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:163` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor2.java:67 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor2.java:67-72 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:128-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:568 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:568-573 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/AbstractSqlRepositoryOperations.java:574-579 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/EmbeddableMapper.java:41 — data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/EmbeddableMapper.java:41-46 | data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedEntityMapper.java:41-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:359 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:359-364 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:265-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:339 — data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:339-344 | data-processor/src/main/java/io/micronaut/data/processor/model/SourcePersistentEntity.java:202-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorConnectionOperations.java:57 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorConnectionOperations.java:57-62 | data-mongodb/src/main/java/io/micronaut/data/mongodb/session/DefaultMongoReactorConnectionOperations.java:56-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. 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) data-model/src/main/java/io/micronaut/data/model/geo/LineString.java:72 — data-model/src/main/java/io/micronaut/data/model/geo/LineString.java:72-77 | data-model/src/main/java/io/micronaut/data/model/geo/MultiLineString.java:72-77 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `coords` to `List<List<Double>>` in one and `List<List<List<Double>>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) data-model/src/main/java/io/micronaut/data/model/vector/BinaryVector.java:156 — data-model/src/main/java/io/micronaut/data/model/vector/BinaryVector.java:156-161 | data-model/src/main/java/io/micronaut/data/model/vector/ByteVector.java:99-104 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/DeleteSpecification.java:46 — data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/DeleteSpecification.java:46-51 | data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/QuerySpecification.java:56-61 — 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: the declarations holding them bind `spec` to `DeleteSpecification<T>` in one and `QuerySpecification<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/DeleteSpecification.java:76 — data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/DeleteSpecification.java:76-81 | data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/QuerySpecification.java:86-91 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:605 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:605-610 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:219-224 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:613 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:613-618 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:227-232 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultInsertOneAsyncInterceptor.java:44 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultInsertOneAsyncInterceptor.java:44-49 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertOneReactiveInterceptor.java:44-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:306 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:306-311 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:503-508 — 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 `data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:306` 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 (6 lines × 2) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:165 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:165-170 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:187-192 — 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.
  • + 3 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×24
  • Duplicated block (8 lines × 2) data-connection/src/main/java/io/micronaut/data/connection/sync/SynchronousConnectionOperationsFromReactiveConnectionOperations.java:65 — data-connection/src/main/java/io/micronaut/data/connection/sync/SynchronousConnectionOperationsFromReactiveConnectionOperations.java:65-72 | data-tx/src/main/java/io/micronaut/transaction/sync/SynchronousTransactionOperationsFromReactiveTransactionOperations.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 `data-connection/src/main/java/io/micronaut/data/connection/sync/SynchronousConnectionOperationsFromReactiveConnectionOperations.java:65` 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) data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedEmbeddedIdMapper.java:46 — data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedEmbeddedIdMapper.java:46-53 | data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedIdMapper.java:45-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:297 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:297-304 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:313-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:297` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `operation` to `InsertOperation<T>` in one and `UpdateOperation<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.java:53 — data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.java:53-60 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1330-1337 — 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 `data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.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 matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:322 — data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:322-329 | data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:363-370 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:322` 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:208 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:208-215 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:407-414 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:208` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `ClientSession` names `com.mongodb.client.ClientSession` in one and `com.mongodb.reactivestreams.client.ClientSession` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:194 — data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:194-201 | data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:242-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:202` calls `requireNonNull` and `data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:250` 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 (8 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:469 — data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:469-476 | data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:503-510 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:469` 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) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:228 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:228-235 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java:155-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/DefaultVectorAttributeConverter.java:96 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/DefaultVectorAttributeConverter.java:96-103 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/DefaultVectorAttributeConverter.java:106-113 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/DeleteAllSpecificationInterceptor.java:48 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/DeleteAllSpecificationInterceptor.java:48-55 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/UpdateAllSpecificationInterceptor.java:48-55 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/DeleteAllSpecificationInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/UpdateAllSpecificationInterceptor.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/DeleteAllSpecificationInterceptor.java:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningOneReactiveInterceptor.java:44 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningOneReactiveInterceptor.java:44-51 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultUpdateReturningOneReactiveInterceptor.java:44-51 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningOneReactiveInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultUpdateReturningOneReactiveInterceptor.java` 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 (8 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:98 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:98-105 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:92-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:956 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:956-963 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1222-1229 — 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) data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/BookRepository.java:105 — data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/BookRepository.java:105-112 | data-tck/src/main/java/io/micronaut/data/tck/repositories/BookRepository.java:173-180 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Author` names `io.micronaut.data.document.tck.entities.Author` in one and `io.micronaut.data.tck.entities.Author` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentAssociationPath.java:68 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentAssociationPath.java:68-75 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentAssociationPath.java:60-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentAssociationPath.java:68` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaQueryImpl.java:71 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaQueryImpl.java:71-78 | data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntitySubqueryImpl.java:65-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaQueryImpl.java:82 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaQueryImpl.java:82-89 | data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntitySubqueryImpl.java:76-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:52 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:52-59 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor2.java:50-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:353 — data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:353-360 | data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/DataSourceTransactionManager.java:415-422 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:799 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:799-806 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:662-669 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 (8 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/CountReactiveSpecificationInterceptor.java:45 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/CountReactiveSpecificationInterceptor.java:45-52 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/ExistsReactiveSpecificationInterceptor.java:43-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `MethodInvocationContext<Object, Publisher<Number>>` in one and `MethodInvocationContext<Object, Publisher<Boolean>>` 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:165 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:165-172 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:139-146 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:165` 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: `MongoCollection` names `com.mongodb.client.MongoCollection` in one and `com.mongodb.reactivestreams.client.MongoCollection` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonRepository.kt:124 — doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonRepository.kt:124-131 | doc-examples/mongo-example-kotlin/src/main/kotlin/example/PersonRepository.kt:128-135 — before extracting anything, compare `doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonRepository.kt` and `doc-examples/mongo-example-kotlin/src/main/kotlin/example/PersonRepository.kt` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D3 · God Classes · ClassTooLong · ×23
  • ClassTooLong: AbstractSqlLikeQueryBuilder data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:142 — ClassTooLong — 2268 significant lines (blank, comment-only and punctuation-only lines excluded), 100 methods. The bar is 400 significant lines; this is 1868 over it, 5.67× 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: SqlQueryBuilder data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:116 — ClassTooLong — 1826 significant lines (blank, comment-only and punctuation-only lines excluded), 105 methods. The bar is 400 significant lines; this is 1426 over it, 4.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DefaultJdbcRepositoryOperations data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:164 — ClassTooLong — 1319 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods. The bar is 400 significant lines; this is 919 over it, 3.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DefaultR2dbcRepositoryOperations data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:166 — ClassTooLong — 1119 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 719 over it, 2.80× 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: MongoQueryBuilder data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:114 — ClassTooLong — 1065 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 665 over it, 2.66× 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: DefaultMongoStoredQuery data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:89 — ClassTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 439 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: RepositoryTypeElementVisitor data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:130 — ClassTooLong — 786 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 386 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SqlResultEntityTypeMapper data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:81 — ClassTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 358 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: JQCriteriaBuilderUtils data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:82 — ClassTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 336 over it, 1.84× 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: DefaultMongoRepositoryOperations data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:121 — ClassTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 313 over it, 1.78× 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: SqlSchemaUtils data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:103 — ClassTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 269 over it, 1.67× 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: DefaultReactiveMongoRepositoryOperations data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:97 — ClassTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 267 over it, 1.67× 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: DefaultReactiveCosmosRepositoryOperations data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:127 — ClassTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 264 over it, 1.66× 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: AbstractCriteriaBuilder data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractCriteriaBuilder.java:90 — ClassTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded), 204 methods. The bar is 400 significant lines; this is 219 over it, 1.55× 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: AbstractQueryInterceptor data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:109 — ClassTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 182 over it, 1.46× 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: HibernateJpaOperations data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:117 — ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), 71 methods. The bar is 400 significant lines; this is 178 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AbstractSqlRepositoryOperations data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/AbstractSqlRepositoryOperations.java:119 — ClassTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 170 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.
  • ClassTooLong: FindersUtils data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:127 — ClassTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 123 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DataConversionServiceFactory data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:62 — ClassTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 110 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: QueryCriteriaMethodMatch data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:101 — ClassTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 106 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.
  • ClassTooLong: AbstractCriteriaMethodMatch data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:86 — ClassTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 105 over it, 1.26× 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: AbstractSpecificationInterceptor data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:100 — ClassTooLong — 463 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 63 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Restrictions data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Restrictions.java:43 — ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 12 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FileTooLong · ×22
  • FileTooLong: sql/AbstractSqlLikeQueryBuilder.java data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java — FileTooLong — 2383 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: AbstractSqlLikeQueryBuilder (142-4028). The bar is 500 significant lines; this is 1883 over it, 4.77× 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: sql/SqlQueryBuilder.java data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java — FileTooLong — 1915 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: SqlQueryBuilder (116-2867). The bar is 500 significant lines; this is 1415 over it, 3.83× 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: operations/DefaultJdbcRepositoryOperations.java data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java — FileTooLong — 1457 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: DefaultJdbcRepositoryOperations (164-2097). The bar is 500 significant lines; this is 957 over it, 2.91× 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: operations/DefaultR2dbcRepositoryOperations.java data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java — FileTooLong — 1259 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: DefaultR2dbcRepositoryOperations (166-1806). The bar is 500 significant lines; this is 759 over it, 2.52× 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: builder/MongoQueryBuilder.java data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java — FileTooLong — 1153 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: MongoQueryBuilder (114-1723). The bar is 500 significant lines; this is 653 over it, 2.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: operations/DefaultMongoStoredQuery.java data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java — FileTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: DefaultMongoStoredQuery (89-1287). The bar is 500 significant lines; this is 401 over it, 1.80× 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: visitors/RepositoryTypeElementVisitor.java data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java — FileTooLong — 890 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: RepositoryTypeElementVisitor (130-1277). The bar is 500 significant lines; this is 390 over it, 1.78× 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: operations/DefaultMongoRepositoryOperations.java data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java — FileTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: DefaultMongoRepositoryOperations (121-1162). The bar is 500 significant lines; this is 309 over it, 1.62× 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: sql/SqlResultEntityTypeMapper.java data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java — FileTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: SqlResultEntityTypeMapper (81-1311). The bar is 500 significant lines; this is 308 over it, 1.62× 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: jq/JQCriteriaBuilderUtils.java data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java — FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: JQCriteriaBuilderUtils (82-1126). The bar is 500 significant lines; this is 293 over it, 1.59× 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: operations/DefaultReactiveCosmosRepositoryOperations.java data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java — FileTooLong — 766 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: DefaultReactiveCosmosRepositoryOperations (127-1293). The bar is 500 significant lines; this is 266 over it, 1.53× 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: sql/SqlSchemaUtils.java data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java — FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: SqlSchemaUtils (103-1091). The bar is 500 significant lines; this is 246 over it, 1.49× 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: operations/DefaultReactiveMongoRepositoryOperations.java data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java — FileTooLong — 739 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: DefaultReactiveMongoRepositoryOperations (97-1092). The bar is 500 significant lines; this is 239 over it, 1.48× 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: impl/AbstractCriteriaBuilder.java data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractCriteriaBuilder.java — FileTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: AbstractCriteriaBuilder (90-1417). The bar is 500 significant lines; this is 183 over it, 1.37× 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: operations/HibernateJpaOperations.java data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java — FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: HibernateJpaOperations (117-992). The bar is 500 significant lines; this is 169 over it, 1.34× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: intercept/AbstractQueryInterceptor.java data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java — FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: AbstractQueryInterceptor (109-1419). The bar is 500 significant lines; this is 163 over it, 1.33× 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: sql/AbstractSqlRepositoryOperations.java data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/AbstractSqlRepositoryOperations.java — FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: AbstractSqlRepositoryOperations (119-1152). The bar is 500 significant lines; this is 159 over it, 1.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: finders/FindersUtils.java data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java — FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: FindersUtils (127-927). The bar is 500 significant lines; this is 128 over it, 1.26× 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: criteria/QueryCriteriaMethodMatch.java data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java — FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: QueryCriteriaMethodMatch (101-914). The bar is 500 significant lines; this is 82 over it, 1.16× 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: finders/AbstractCriteriaMethodMatch.java data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java — FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: AbstractCriteriaMethodMatch (86-851). The bar is 500 significant lines; this is 66 over it, 1.13× 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: convert/DataConversionServiceFactory.java data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java — FileTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: DataConversionServiceFactory (62-773). The bar is 500 significant lines; this is 47 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: criteria/AbstractSpecificationInterceptor.java data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java — FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: AbstractSpecificationInterceptor (100-857). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×22
  • Edited copy of a member (8 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:99 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:99-107 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:114-121 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:330 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:330-337 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:343-352 — 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) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentPropertyPathImpl.java:62 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentPropertyPathImpl.java:62-69 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentPropertyPathImpl.java:61-68 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:457 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:457-470 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:620-627 — 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) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:100 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:100-107 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:200-207 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:71 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:71-78 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractSyncEntityOperations.java:66-74 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/convert/JakartaDataRestrictionsConverter.java:105 — data-runtime/src/main/java/io/micronaut/data/runtime/convert/JakartaDataRestrictionsConverter.java:105-114 | data-runtime/src/main/java/io/micronaut/data/runtime/convert/JakartaDataRestrictionsConverter.java:274-281 — 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:632 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:632-641 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:612-619 — 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) data-processor/src/main/java/io/micronaut/data/processor/mappers/spring/SpringRepositoryMapper.java:41 — data-processor/src/main/java/io/micronaut/data/processor/mappers/spring/SpringRepositoryMapper.java:41-48 | data-processor/src/main/java/io/micronaut/data/processor/mappers/spring/SpringTransactionalEventListenerMapper.java:40-47 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1819 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1819-1826 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractSyncEntitiesOperations.java:95-102 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:167 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:167-174 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:101-108 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:228 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:228-235 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:146-153 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:238 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:238-245 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:156-163 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:248 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:248-255 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:166-173 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:258 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:258-265 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:176-183 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:268 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:268-275 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:186-193 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:278 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:278-285 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:196-203 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ProcedureMethodMatcher.java:146 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ProcedureMethodMatcher.java:146-153 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:577-584 — 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) doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:67 — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:67-74 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:88-95 — 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) doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:57 — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:57-64 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:78-85 — 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) doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:93 — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:93-100 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:47-54 — 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) doc-examples/jdbc-example-kotlin/src/main/kotlin/example/PersonRepository.kt:109 — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/PersonRepository.kt:109-116 | doc-examples/mongo-example-kotlin/src/main/kotlin/example/PersonRepository.kt:107-114 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×21
  • Duplicated block (7 lines × 2) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:939 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:939-945 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:972-978 — 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 `data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:939` 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, `data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:946` calls `getPartitionKey`, `getItemId` and `data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:979` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:340 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:340-346 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:355-361 — 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 `data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:340` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `operation` to `UpdateBatchOperation<T>` in one and `InsertBatchOperation<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/JoinPath.java:144 — data-model/src/main/java/io/micronaut/data/model/query/JoinPath.java:144-150 | data-model/src/main/java/io/micronaut/data/model/query/JoinPath.java:162-168 — 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 (7 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1026 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1026-1032 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilderUtils.java:346-352 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1026` 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:889 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:889-895 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:974-980 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:889` 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 (7 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/JoinTableAnnotationMapper.java:55 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/JoinTableAnnotationMapper.java:55-61 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/JoinTableAnnotationMapper.java:62-68 — 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 (7 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:343 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:343-349 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:1091-1098 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:343` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `type` to `ClassElement` in one and `Class<?>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:201 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:201-207 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:263-269 — before extracting anything, compare `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/AutoPopulateUtil.java:98 — data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/AutoPopulateUtil.java:98-104 | data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/AutoPopulateUtil.java:151-157 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/AutoPopulateUtil.java:98` 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:79 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:79-85 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:79-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:79` 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:161 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:161-167 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:204-210 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:161` 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 (7 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:124 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:124-130 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:142-148 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:124` 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:360 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:360-366 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:423-429 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:360` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `ClientSession` names `com.mongodb.client.ClientSession` in one and `com.mongodb.reactivestreams.client.ClientSession` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:960 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:960-966 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:842-848 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:960` 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) data-connection/src/main/java/io/micronaut/data/connection/reactive/DefaultReactiveConnectionStatus.java:162 — data-connection/src/main/java/io/micronaut/data/connection/reactive/DefaultReactiveConnectionStatus.java:162-168 | data-connection/src/main/java/io/micronaut/data/connection/support/DefaultConnectionStatus.java:114-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `synchronization` to `ReactiveConnectionSynchronization` in one and `ConnectionSynchronization` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:245 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:245-251 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:295-301 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameByIndexCallableResultReader.java:63 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameByIndexCallableResultReader.java:63-69 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnNameByIndexR2dbcResultReader.java:63-69 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcTuple.java:60 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcTuple.java:60-66 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/R2dbcTuple.java:59-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:161 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:161-167 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:417-423 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindAllAsyncInterceptor.java:46 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindAllAsyncInterceptor.java:46-52 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultFindAllReactiveInterceptor.java:44-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:822 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:822-828 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:716-722 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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: `MongoCollection` names `com.mongodb.client.MongoCollection` in one and `com.mongodb.reactivestreams.client.MongoCollection` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×20
  • Edited copy of a member (9 corresponding lines) data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:124 — data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:124-132 | data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.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) data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToManyMapper.java:42 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToManyMapper.java:42-51 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/OneToManyMapper.java:42-50 — 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:164 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:164-172 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:175-183 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1485 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1485-1494 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1310-1318 — 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) jakarta-data-tck/support/src/main/java/io/micronaut/data/jakarta/tck/TckObserver.java:43 — jakarta-data-tck/support/src/main/java/io/micronaut/data/jakarta/tck/TckObserver.java:43-51 | jakarta-data-tck/support/src/main/java/io/micronaut/data/jakarta/tck/TckObserver.java:53-61 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningOneReactiveInterceptor.java:43 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningOneReactiveInterceptor.java:43-51 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultUpdateReturningOneReactiveInterceptor.java:43-51 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:504 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:504-512 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilderUtils.java:205-214 — 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) data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedEmbeddedIdMapper.java:45 — data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedEmbeddedIdMapper.java:45-53 | data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedIdMapper.java:44-52 — 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:391 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:391-399 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java:315-330 — 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:549 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:549-557 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:594-603 — 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) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:227 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:227-235 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java:154-162 — 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) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/DefaultVectorAttributeConverter.java:95 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/DefaultVectorAttributeConverter.java:95-103 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/DefaultVectorAttributeConverter.java:105-113 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/VersionGeneratingEntityEventListener.java:69 — data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/VersionGeneratingEntityEventListener.java:69-77 | data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/VersionGeneratingEntityEventListener.java:80-89 — 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2479 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2479-2489 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1145-1153 — 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) data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:328 — data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:328-336 | data-processor/src/main/java/io/micronaut/data/processor/model/SourcePersistentEntity.java:186-194 — 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) data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:71 — data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:71-79 | data-tx/src/main/kotlin/io/micronaut/transaction/kotlin/DefaultCoroutineTransactionOperations.kt:74-83 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntitySubquery.java:62 — data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntitySubquery.java:62-71 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaQuery.java:64-72 — 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) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:240 — data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:240-248 | data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/DataSourceTransactionManager.java:322-330 — 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) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosBinder.java:135 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosBinder.java:135-143 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:437-445 — 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) doc-examples/jooq-r2dbc-postgres/src/main/java/example/AbstractRepository.java:25 — doc-examples/jooq-r2dbc-postgres/src/main/java/example/AbstractRepository.java:25-33 | doc-examples/jooq-r2dbc-postgres/src/main/java/example/AbstractRepository.java:35-43 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D6 · Cohesion (LCOM4) · Low cohesion · ×20
  • Low cohesion: DefaultR2dbcRepositoryOperations (LCOM4 15) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:166 — DefaultR2dbcRepositoryOperations's methods fall into 15 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 15 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DefaultJdbcRepositoryOperations (LCOM4 13) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:164 — DefaultJdbcRepositoryOperations's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ColumnIndexReadableResultReader (LCOM4 11) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:47 — ColumnIndexReadableResultReader's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DefaultMongoStoredQuery (LCOM4 9) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:89 — DefaultMongoStoredQuery's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AbstractReactorTransactionOperations (LCOM4 9) data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:55 — AbstractReactorTransactionOperations's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AbstractMongoRepositoryOperations (LCOM4 8) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/AbstractMongoRepositoryOperations.java:83 — AbstractMongoRepositoryOperations's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AbstractCriteriaMethodMatch (LCOM4 8) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:86 — AbstractCriteriaMethodMatch's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: R2dbcQueryStatement (LCOM4 8) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/R2dbcQueryStatement.java:43 — R2dbcQueryStatement's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: JakartaDataRestrictionsConverter (LCOM4 7) data-runtime/src/main/java/io/micronaut/data/runtime/convert/JakartaDataRestrictionsConverter.java:73 — JakartaDataRestrictionsConverter's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SQLiteJoinFetchTest (LCOM4 7) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteJoinFetchTest.java:22 — SQLiteJoinFetchTest's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DefaultReactiveCosmosRepositoryOperations (LCOM4 6) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:127 — DefaultReactiveCosmosRepositoryOperations's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: HibernateJpaOperations (LCOM4 6) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:117 — HibernateJpaOperations's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AbstractQueryInterceptor (LCOM4 5) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:109 — AbstractQueryInterceptor's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ManyToManyJoinTableTest (LCOM4 5) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/many2many/ManyToManyJoinTableTest.java:37 — ManyToManyJoinTableTest's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SQLiteEnumsMappingTest (LCOM4 5) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteEnumsMappingTest.java:33 — SQLiteEnumsMappingTest's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: RegistrationRecoveryConfiguration (LCOM4 4) data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/oracle/OracleNotificationConfiguration.java:101 — RegistrationRecoveryConfiguration's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AbstractRepositoryOperations (LCOM4 4) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractRepositoryOperations.java:51 — AbstractRepositoryOperations's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EntityTests (LCOM4 4) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/entity/EntityTests.java:58 — EntityTests's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MultiManyToOneJoinTest (LCOM4 4) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/many2one/MultiManyToOneJoinTest.java:37 — MultiManyToOneJoinTest's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SQLiteTransactionsTest (LCOM4 4) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteTransactionsTest.java:48 — SQLiteTransactionsTest's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×19
  • Duplicated block (10 lines × 2) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1157 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1157-1166 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1186-1195 — 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) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:248 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:248-257 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:205-214 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1553 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1553-1562 | data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:1232-1241 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1013 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1013-1022 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1034-1043 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1013` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1012` calls `add` and `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1033` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:405 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:405-414 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:426-435 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:405` 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1084 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1084-1093 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:1034-1043 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1084` 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, `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:1044` calls `just` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1094` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:811 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:811-820 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:992-1001 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:931 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:931-940 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:972-981 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:105 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:105-114 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:129-138 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:105` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/http/PageableRequestArgumentBinder.java:84 — data-runtime/src/main/java/io/micronaut/data/runtime/http/PageableRequestArgumentBinder.java:84-93 | data-spring/src/main/java/io/micronaut/data/spring/runtime/http/SpringPageableRequestArgumentBinder.java:80-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: `Pageable` names `io.micronaut.data.model.Pageable` in one and `org.springframework.data.domain.Pageable` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:762 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:762-771 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:816-825 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:762` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3674 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3674-3683 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2838-2847 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3674` 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, `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2848` calls `add`, `getMappedName`, `getDataType` and `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3684` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaDelete.java:95 — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaDelete.java:95-104 | data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaUpdate.java:150-159 — 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 × 2) data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:60 — data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:60-69 | data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:117-126 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:60` 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) data-runtime/src/main/java/io/micronaut/data/runtime/multitenancy/internal/DefaultDataSourceTenantResolver.java:45 — data-runtime/src/main/java/io/micronaut/data/runtime/multitenancy/internal/DefaultDataSourceTenantResolver.java:45-54 | data-runtime/src/main/java/io/micronaut/data/runtime/multitenancy/internal/DefaultSchemaTenantResolver.java:45-54 — 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) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaDelete.java:128 — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaDelete.java:128-137 | data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaUpdate.java:177-186 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.java:68 — data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.java:68-77 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/exceptions/jakarta/data/R2dbcJakartaDataExceptionConverter.java:68-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) doc-examples/jdbc-example-java/src/main/java/example/ProjectId.java:27 — doc-examples/jdbc-example-java/src/main/java/example/ProjectId.java:27-36 | doc-examples/mongo-example-java/src/main/java/example/ProjectId.java:28-37 — before extracting anything, compare `doc-examples/jdbc-example-java/src/main/java/example/ProjectId.java` and `doc-examples/mongo-example-java/src/main/java/example/ProjectId.java` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) doc-examples/hibernate-example-java/src/main/java/example/MonthDayDateAttributeConverter.java:20 — doc-examples/hibernate-example-java/src/main/java/example/MonthDayDateAttributeConverter.java:20-29 | doc-examples/hibernate-reactive-example-java/src/main/java/example/MonthDayDateAttributeConverter.java:20-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
DM4 · Rich vs anemic model · Anemic entity · ×19
  • Anemic entity: Author doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Author.kt:10 — `Author` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Book.kt:9 — `Book` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Child doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Child.kt:9 — `Child` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Genre doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Genre.kt:7 — `Genre` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Student doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Student.kt:10 — `Student` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Book.kt:9 — `Book` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Child doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Child.kt:10 — `Child` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Student doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Student.kt:10 — `Student` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: User doc-examples/hibernate-example-kotlin/src/main/kotlin/example/User.kt:10 — `User` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Book.kt:9 — `Book` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Student doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Student.kt:10 — `Student` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Book.kt:10 — `Book` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Person doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Person.kt:8 — `Person` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Project doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Project.kt:8 — `Project` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Review doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Review.kt:10 — `Review` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book doc-examples/jdbc-jakarta-data-example-kotlin/src/main/kotlin/example/Book.kt:8 — `Book` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Order data-tck/src/main/java/io/micronaut/data/tck/entities/Order.java:28 — `Order` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Project doc-examples/jdbc-example-java/src/main/java/example/Project.java:8 — `Project` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Review doc-examples/jdbc-example-java/src/main/java/example/Review.java:18 — `Review` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×18
  • Duplicated block (5 lines × 2) data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:128 — data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:128-132 | data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:163-167 — 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 `data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:128` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoRawQueryMethodMatcher.java:149 — data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoRawQueryMethodMatcher.java:149-153 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:97-101 — 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 `data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoRawQueryMethodMatcher.java:149` 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:509 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:509-514 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:995-999 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:515` calls `getDataType`, `isEmpty` and `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:1000` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:180 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:180-184 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:190-194 — 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 (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java:65 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java:65-69 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractPublisherInterceptor.java:64-68 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/DocumentRepository.java:28 — data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/DocumentRepository.java:28-32 | doc-examples/mongo-example-java/src/main/java/example/PersonRepository.java:1-102 — 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 `doc-examples/mongo-example-java/src/main/java/example/PersonRepository.java:1` 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1286 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1286-1290 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:623-627 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultSaveAllAsyncInterceptor.java:50 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultSaveAllAsyncInterceptor.java:50-54 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultSaveAllReactiveInterceptor.java:48-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/ReactiveAsyncCriteriaRepositoryOperations.java:101 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/ReactiveAsyncCriteriaRepositoryOperations.java:101-105 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/AsyncFromReactiveAsyncRepositoryOperation.java:170-174 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/OracleVectorSqlIndexDefinitionProvider.java:47 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/OracleVectorSqlIndexDefinitionProvider.java:47-51 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/PostgresVectorSqlIndexDefinitionProvider.java:46-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindByIdAsyncInterceptor.java:42 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindByIdAsyncInterceptor.java:42-46 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultFindByIdReactiveInterceptor.java:42-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultUpdateAllAsyncEntitiesInterceptor.java:45 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultUpdateAllAsyncEntitiesInterceptor.java:45-49 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultUpdateAllEntitiesReactiveInterceptor.java:42-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosSerde.java:84 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosSerde.java:84-88 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosSerde.java:141-145 — 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 `data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosSerde.java:84` 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2623 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2623-2627 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2678-2682 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2623` 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2220 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2220-2224 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2229-2233 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2220` 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:651 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:651-655 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:657-661 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:651` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:196 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:196-200 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:399-403 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:196` 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: `ClientSession` names `com.mongodb.client.ClientSession` in one and `com.mongodb.reactivestreams.client.ClientSession` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 2) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:969 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:969-973 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:998-1002 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×16
  • Edited copy of a member (11 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java:57 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java:57-69 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractPublisherInterceptor.java:58-68 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteAllAsyncInterceptor.java:48 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteAllAsyncInterceptor.java:48-58 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteAllReactiveInterceptor.java:45-55 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:104 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:104-114 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:105-119 — 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:186 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:186-196 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/CosmosSqlQueryBuilder.java:199-209 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/CallableStatementTupleMapper.java:53 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/CallableStatementTupleMapper.java:53-67 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ReadableTupleMapper.java:53-63 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/DeleteAllSpecificationInterceptor.java:45 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/DeleteAllSpecificationInterceptor.java:45-55 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/UpdateAllSpecificationInterceptor.java:45-55 — 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) data-model/src/main/java/io/micronaut/data/model/PersistentEntityUtils.java:125 — data-model/src/main/java/io/micronaut/data/model/PersistentEntityUtils.java:125-135 | data-model/src/main/java/io/micronaut/data/model/PersistentEntityUtils.java:145-157 — 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) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorTransactionOperations.java:75 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorTransactionOperations.java:75-85 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorTransactionOperations.java:88-98 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:358 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:358-368 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:421-431 — 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) data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/BookRepository.java:83 — data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/BookRepository.java:83-97 | data-tck/src/main/java/io/micronaut/data/tck/repositories/BookRepository.java:155-165 — 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) data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataOrderByListMapper.java:43 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataOrderByListMapper.java:43-53 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataSelectListMapper.java:43-53 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:342 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:342-353 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:1090-1100 — 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) data-model/src/main/java/io/micronaut/data/model/Association.java:70 — data-model/src/main/java/io/micronaut/data/model/Association.java:70-80 | data-model/src/main/java/io/micronaut/data/model/Association.java:87-97 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:254 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:254-264 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:204-216 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataCodecRegistry.java:111 — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataCodecRegistry.java:111-121 | data-runtime/src/main/java/io/micronaut/data/runtime/support/DefaultRuntimeEntityRegistry.java:190-200 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1536 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1536-1546 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:110-120 — 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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×15
  • Edited copy of a member (12 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertAllInterceptor.java:47 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertAllInterceptor.java:47-60 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateAllEntitiesInterceptor.java:46-60 — 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) data-connection/src/main/java/io/micronaut/data/connection/sync/SynchronousConnectionOperationsFromReactiveConnectionOperations.java:61 — data-connection/src/main/java/io/micronaut/data/connection/sync/SynchronousConnectionOperationsFromReactiveConnectionOperations.java:61-72 | data-tx/src/main/java/io/micronaut/transaction/sync/SynchronousTransactionOperationsFromReactiveTransactionOperations.java:74-86 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:164 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:164-175 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:138-149 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:107 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:107-118 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/AbstractReactiveSpecificationInterceptor.java:96-107 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:156 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:156-167 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:139-151 — 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) data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:427 — data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:427-438 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:465-478 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/OracleTypeConvertersFactory.java:139 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/OracleTypeConvertersFactory.java:139-150 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/OracleTypeConvertersFactory.java:153-164 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:96 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:96-107 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:90-101 — 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) data-model/src/main/java/io/micronaut/data/model/vector/VectorArrays.java:86 — data-model/src/main/java/io/micronaut/data/model/vector/VectorArrays.java:86-97 | data-model/src/main/java/io/micronaut/data/model/vector/VectorArrays.java:99-110 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:305 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:305-316 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:327-340 — 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) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:788 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:788-799 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:498-509 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:348 — data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:348-359 | data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/StoredQueryParameter.java:146-157 — 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) data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:176 — data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:176-187 | data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:257-269 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcQueryStatement.java:252 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcQueryStatement.java:252-263 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcQueryStatement.java:384-397 — 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) data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:456 — data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:456-467 | data-tx/src/main/java/io/micronaut/transaction/support/AbstractTransactionOperations.java:418-429 — 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 · Duplicated block (9 lines × 2) · ×15
  • Duplicated block (9 lines × 2) data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedPropertyMapper.java:56 — data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedPropertyMapper.java:56-64 | data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:472-480 — 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 `data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedPropertyMapper.java:56` 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) data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:856 — data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:856-864 | data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:866-874 — 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 `data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:856` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:105 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:105-113 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.java:91-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:73 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:73-81 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java:103-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:734 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:734-742 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:784-796 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:734` 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:231 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:231-239 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/BaseOperations.java:315-323 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:231` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `beanProperty` to `BeanProperty<B, T>` in one and `BeanProperty<B, L>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 2) data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:69 — data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:69-77 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:251-259 — 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 `data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:69` 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) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:207 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:207-215 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:472-480 — 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 `data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:207` 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1308 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1308-1316 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:641-649 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:838 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:838-846 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:728-736 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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: `MongoCollection` names `com.mongodb.client.MongoCollection` in one and `com.mongodb.reactivestreams.client.MongoCollection` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 2) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1501 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1501-1509 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1693-1701 — 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 `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1501` 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1643 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1643-1651 | data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/util/Joiner.java:198-206 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1655` calls `put`, `of`, `asLiteral` and `data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/util/Joiner.java:210` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:119 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:119-127 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/OracleR2dbcJsonColumnMapper.java:121-129 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java` and `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/OracleR2dbcJsonColumnMapper.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaDelete.java:147 — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaDelete.java:147-155 | data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityCriteriaUpdate.java:215-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/JsonQueryResultMapper.java:84 — data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/JsonQueryResultMapper.java:84-92 | data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:917-925 — 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.
D3 · God Classes · MethodTooLong · ×14
  • MethodTooLong: DataConversionServiceFactory.build data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:68 — MethodTooLong — build runs 459 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 359 over it, 4.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SqlColumnMapping.getSqlType data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:247 — MethodTooLong — getSqlType runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: SqlQueryBuilder.buildInsert data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1497 — MethodTooLong — buildInsert runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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: AbstractSqlLikeQueryBuilder.buildUpdateStatement data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:964 — MethodTooLong — buildUpdateStatement runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: QueryStatement.setDynamic data-runtime/src/main/java/io/micronaut/data/runtime/mapper/QueryStatement.java:59 — MethodTooLong — setDynamic runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: SqlResultEntityTypeMapper.readEntity data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:607 — MethodTooLong — readEntity runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: RepositoryTypeElementVisitor.processMethodInfo data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:596 — MethodTooLong — processMethodInfo runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: MongoExecutorQueryMethodMatcher.match data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoExecutorQueryMethodMatcher.java:48 — MethodTooLong — match runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SourceParameterExpressionImpl.bind data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceParameterExpressionImpl.java:135 — MethodTooLong — bind runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JQCriteriaBuilderUtils.getExpression data-processor/src/main/java/io/micronaut/data/processor/jq/JQCriteriaBuilderUtils.java:772 — MethodTooLong — getExpression runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: SqlQueryBuilder.buildJoin data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2037 — MethodTooLong — buildJoin runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: DefaultBindableParametersStoredQuery.bindParameter data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/query/DefaultBindableParametersStoredQuery.java:112 — MethodTooLong — bindParameter runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: DefaultMongoStoredQuery.replaceQueryParametersInBsonValue data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:461 — MethodTooLong — replaceQueryParametersInBsonValue runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: MongoQueryBuilder.addLookups data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:355 — MethodTooLong — addLookups runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×14
  • Edited copy of a member (13 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:635 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:635-647 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:656-675 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:858 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:858-870 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:754-771 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:235 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:235-248 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:251-263 — 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) data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:79 — data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:79-91 | data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:157-169 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:227 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:227-239 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/BaseOperations.java:311-323 — 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) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:69 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:69-83 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java:100-112 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/VersionGeneratingEntityEventListener.java:102 — data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/VersionGeneratingEntityEventListener.java:102-117 | data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/VersionGeneratingEntityEventListener.java:119-131 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:339 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:339-351 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:354-366 — 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1156 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1156-1168 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1185-1197 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:84 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:84-100 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:102-114 — 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) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:86 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:86-98 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:101-113 — 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) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorTransactionOperations.java:110 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorTransactionOperations.java:110-122 | data-mongodb/src/main/java/io/micronaut/data/mongodb/transaction/DefaultMongoReactorTransactionOperations.java: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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:293 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:293-308 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:314-326 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:786 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:786-798 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:800-812 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×14
  • Edited copy of a member (6 corresponding lines) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:221 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:221-226 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:258-263 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:215 — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:215-220 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:316-321 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:281 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:281-286 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:251-256 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:672 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:672-677 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:331-336 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/ReactiveAsyncCriteriaRepositoryOperations.java:94 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/ReactiveAsyncCriteriaRepositoryOperations.java:94-99 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/AsyncFromReactiveAsyncRepositoryOperation.java:162-168 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:49 — data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:49-54 | data-tck/src/main/java/io/micronaut/data/tck/services/TxEventsService.java:88-94 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:57 — data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:57-62 | data-tck/src/main/java/io/micronaut/data/tck/services/TxEventsService.java:106-112 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:65 — data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:65-70 | data-tck/src/main/java/io/micronaut/data/tck/services/TxEventsService.java:123-129 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaQuery.java:47 — data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaQuery.java:47-52 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntitySubquery.java:49-54 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-model/src/main/java/io/micronaut/data/model/CursoredPageable.java:72 — data-model/src/main/java/io/micronaut/data/model/CursoredPageable.java:72-77 | data-model/src/main/java/io/micronaut/data/model/Pageable.java:361-366 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-model/src/main/java/io/micronaut/data/model/vector/DoubleVector.java:99 — data-model/src/main/java/io/micronaut/data/model/vector/DoubleVector.java:99-104 | data-model/src/main/java/io/micronaut/data/model/vector/FloatVector.java:99-104 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-model/src/main/java/io/micronaut/data/model/CursoredPageable.java:97 — data-model/src/main/java/io/micronaut/data/model/CursoredPageable.java:97-102 | data-model/src/main/java/io/micronaut/data/model/Pageable.java:378-383 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorConnectionOperations.java:65 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactorConnectionOperations.java:65-70 | data-mongodb/src/main/java/io/micronaut/data/mongodb/session/DefaultMongoReactorConnectionOperations.java:65-71 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) doc-examples/hibernate-example-java/src/main/java/example/ProductManager.java:29 — doc-examples/hibernate-example-java/src/main/java/example/ProductManager.java:29-35 | doc-examples/hibernate-reactive-example-java/src/main/java/example/ProductManager.java:29-34 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×13
  • Edited copy of a member (7 corresponding lines) data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:129 — data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:129-135 | data-model/src/main/java/io/micronaut/data/model/Page.java:96-102 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityFrom.java:159 — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityFrom.java:159-168 | data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/AbstractPersistentEntityFrom.java:346-352 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/support/convert/convert/jpa/JakartaAttributeConverterProvider.java:44 — data-runtime/src/main/java/io/micronaut/data/runtime/support/convert/convert/jpa/JakartaAttributeConverterProvider.java:44-50 | data-runtime/src/main/java/io/micronaut/data/runtime/support/convert/convert/jpa/JxAttributeConverterProvider.java:44-50 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1423 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1423-1429 | data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1432-1438 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:739 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:739-748 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:1176-1182 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:197 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:197-203 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:131-137 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:313 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:313-319 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:357-363 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryWktConverter.java:189 — data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryWktConverter.java:189-195 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:313-319 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:187 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:187-193 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:121-127 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:203 — data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:203-212 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1570-1576 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteAllInterceptor.java:68 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteAllInterceptor.java:68-74 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteAllReturningInterceptor.java:72-78 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:177 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:177-183 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:111-117 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) doc-examples/hibernate-example-kotlin/src/main/kotlin/example/ProductManager.kt:22 — doc-examples/hibernate-example-kotlin/src/main/kotlin/example/ProductManager.kt:22-28 | doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/ProductManager.kt:25-36 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×12
  • Edited copy of a member (10 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:555 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:555-564 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:567-576 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:354 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:354-363 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:370-380 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:459 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:459-468 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:471-480 — 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1193 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1193-1202 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1204-1213 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:230 — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:230-239 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataEncoderContext.java:167-176 — 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java:387 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java:387-398 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java:441-450 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:998 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:998-1008 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1010-1019 — 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) data-spring/src/main/java/io/micronaut/data/spring/runtime/SortDelegate.java:59 — data-spring/src/main/java/io/micronaut/data/spring/runtime/SortDelegate.java:59-68 | data-spring/src/main/java/io/micronaut/data/spring/runtime/SortDelegate.java:79-88 — 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) data-model/src/main/java/io/micronaut/data/model/query/JoinPath.java:143 — data-model/src/main/java/io/micronaut/data/model/query/JoinPath.java:143-152 | data-model/src/main/java/io/micronaut/data/model/query/JoinPath.java:161-170 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractSyncEntitiesOperations.java:129 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractSyncEntitiesOperations.java:129-144 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractSyncEntitiesOperations.java:147-156 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/exceptions/R2dbcExceptionUtils.java:43 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/exceptions/R2dbcExceptionUtils.java:43-52 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/transaction/OracleTransactionPriorityReactiveTransactionExecutionListener.java:147-159 — 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) doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:103 — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:103-112 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:98-107 — 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×12
  • Swallowed exception (empty catch) data-tck/src/main/java/io/micronaut/data/tck/services/ConnectionBookService.java:82 — 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) data-tck/src/main/java/io/micronaut/data/tck/services/ConnectionBookService.java:92 — 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) data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:205 — 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) data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:275 — 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) data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:295 — 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) data-tck/src/main/java/io/micronaut/data/tck/services/TxBookService.java:325 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:221 — 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) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:890 — 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) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:910 — 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) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxBookService.java:82 — 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) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxBookService.java:122 — 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) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxBookService.java:132 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×11
  • Duplicated block (12 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1361 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1361-1372 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1374-1385 — 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 (12 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:179 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:179-190 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:153-164 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:328 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:328-339 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:372-383 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:328` 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: `ClientSession` names `com.mongodb.client.ClientSession` in one and `com.mongodb.reactivestreams.client.ClientSession` 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:784 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:784-795 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:909-920 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:784` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataCodecRegistry.java:124 — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataCodecRegistry.java:124-135 | data-runtime/src/main/java/io/micronaut/data/runtime/support/DefaultRuntimeEntityRegistry.java:203-214 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:654 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:654-665 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:674-685 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:654` 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 (12 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:442 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:442-453 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:490-501 — 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 (12 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:182 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:182-193 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:230-241 — before extracting anything, compare `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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: the declarations holding them bind `query` to `PersistentEntityCriteriaDelete<T>` in one and `PersistentEntityCriteriaUpdate<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:90 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:90-101 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:109-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `handler` to `Function<ConnectionStatus<Connection>, Publisher<T>>` in one and `Function<ConnectionStatus<Connection>, Flux<T>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/FindPageSpecificationInterceptor.java:85 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/FindPageSpecificationInterceptor.java:85-96 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:106-117 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/FindPageSpecificationInterceptor.java:97` calls `getReturnType`, `getType`, `isInstance` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:118` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:79 — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:79-90 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:59-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:79` 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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×9
  • One operation mutates 2 aggregates: OneToManyJoinColumnTest.testOneToManySaveAndLoad test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/one2many/OneToManyJoinColumnTest.java:30 — `OneToManyJoinColumnTest.testOneToManySaveAndLoad` saves `EmployeeRepository`, `EmployeeGroupRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: MultipleDataSourceTest.testMultipleDataSources test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/MultipleDataSourceTest.java:58 — `MultipleDataSourceTest.testMultipleDataSources` saves `SQLitePersonRepository`, `OtherPersonRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: SQLiteCompositePrimaryKeyTest.testCrudWithCompositeId test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteCompositePrimaryKeyTest.java:37 — `SQLiteCompositePrimaryKeyTest.testCrudWithCompositeId` saves `Project`, `ProjectId` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: SQLiteJSONTest.testSaveUpdateIterable test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteJSONTest.java:227 — `SQLiteJSONTest.testSaveUpdateIterable` saves `JsonEntity`, `List` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: SQLiteValidationTest.testSaveValidObjects test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteValidationTest.java:42 — `SQLiteValidationTest.testSaveValidObjects` saves `SQLiteMealRepository`, `SQLiteFoodRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: SQLiteValidationTest.testUpdateInvalidObjects test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteValidationTest.java:68 — `SQLiteValidationTest.testUpdateInvalidObjects` saves `Meal`, `var` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: InitController.init doc-examples/jooq-r2dbc-postgres/src/main/java/example/InitController.java:36 — `InitController.init` saves `Owner`, `Pet` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: PessimisticLockingSpec.findMethodsForUpdate doc-examples/jdbc-example-python/src/test/python/example/PessimisticLockingSpec.py:47 — `PessimisticLockingSpec.findMethodsForUpdate` saves `manufacturerRepository`, `productLockingRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: BookControllerTest.setupData doc-examples/r2dbc-example-python/src/test/python/example/BookControllerTest.py:32 — `BookControllerTest.setupData` saves `authorRepository`, `bookRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
AX2 · Stateful singletons · Stateful singleton · ×8
  • Stateful singleton: DefaultReactiveCosmosRepositoryOperations data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:127 — `DefaultReactiveCosmosRepositoryOperations` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (defaultCosmosSqlQueryBuilder; e.g. `defaultCosmosSqlQueryBuilder` in `decorate` at line 182).
  • Stateful singleton: TxEventsService data-document-tck/src/main/java/io/micronaut/data/document/tck/services/TxEventsService.java:29 — `TxEventsService` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (lastEvent; e.g. `lastEvent` in `afterCommit` at line 73).
  • Stateful singleton: EntityEventRegistry data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:67 — `EntityEventRegistry` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (beanEventHandlers; e.g. `beanEventHandlers` in `process` at line 333).
  • Stateful singleton: JakartaDataTrainEventListener data-tck/src/main/java/io/micronaut/data/tck/services/JakartaDataTrainEventListener.java:33 — `JakartaDataTrainEventListener` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (events; e.g. `events` in `onEvent` at line 38).
  • Stateful singleton: TxEventsService data-tck/src/main/java/io/micronaut/data/tck/services/TxEventsService.java:33 — `TxEventsService` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (lastEvent, events; e.g. `lastEvent` in `afterCommit` at line 132).
  • Stateful singleton: EventRecorder doc-examples/coherence-example-java/src/main/java/io/micronaut/coherence/data/util/EventRecorder.java:12 — `EventRecorder` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (eventRecords; e.g. `eventRecords` in `record` at line 16).
  • Stateful singleton: BookManager doc-examples/hibernate-spring-tx-example-java/src/main/java/example/BookManager.java:14 — `BookManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (events; e.g. `events` in `onNewBook` at line 35).
  • Stateful singleton: BookManager doc-examples/jdbc-spring-tx-example-java/src/main/java/example/BookManager.java:14 — `BookManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (events; e.g. `events` in `onNewBook` at line 35).
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×8
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:52 — data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:52-80 | data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterSerializer.java:50-66 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:172-200 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataEncoderContext.java:129-154 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:211 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:211-234 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:207-230 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:228-251 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:262-289 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/DetachInterceptor.java:47 — data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/DetachInterceptor.java:47-68 | data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/PersistInterceptor.java:47-68 | data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/RefreshInterceptor.java:47-68 | data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/RemoveInterceptor.java:47-68 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:470 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:470-551 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:570-602 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:482-563 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:583-615 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:621 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:621-634 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:637-651 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:654-669 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:672-692 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:60 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:60-71 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:88-99 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpdateMethodMatcher.java:76-87 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.java:67-78 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:61 — data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:61-77 | data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:139-155 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:279-296 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:380-397 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:243 — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:243-259 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:261-277 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:344-360 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:362-378 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×8
  • Edited copy of a member (22 corresponding lines) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:109 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:109-132 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:209-230 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:962 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:962-983 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:987-1010 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1094 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1094-1115 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1119-1140 — 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) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/visitor/JpaMetamodelProcessorVisitor.java:99 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/visitor/JpaMetamodelProcessorVisitor.java:99-124 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:110-131 — 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) data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:267 — data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:267-288 | data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:295-316 — 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) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/AbstractSourcePersistentEntityFrom.java:67 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/AbstractSourcePersistentEntityFrom.java:67-88 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/AbstractRuntimePersistentEntityFrom.java:85-108 — 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) data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:48 — data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:48-69 | data-tx/src/main/kotlin/io/micronaut/transaction/kotlin/DefaultCoroutineTransactionOperations.kt:50-72 — 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) data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:93 — data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:93-114 | data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:171-192 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×8
  • Duplicated block (13 lines × 2) data-connection/src/main/java/io/micronaut/data/connection/DefaultConnectionOperationsRegistry.java:48 — data-connection/src/main/java/io/micronaut/data/connection/DefaultConnectionOperationsRegistry.java:48-60 | data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionOperationsRegistry.java:48-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:188 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:188-200 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:167-179 — 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 `data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/VectorSimilarityDialect.java:177 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/VectorSimilarityDialect.java:177-189 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/VectorSimilarityDialect.java:191-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:606 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:606-618 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:702-714 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:129 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:129-141 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:167-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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, `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:142` calls `dto` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:180` 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) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:259 — data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:259-271 | data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/DataSourceTransactionManager.java:341-353 — 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 `data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:259` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) doc-examples/hibernate-example-java/src/main/java/example/BookController.java:17 — doc-examples/hibernate-example-java/src/main/java/example/BookController.java:17-29 | doc-examples/hibernate-reactive-example-java/src/main/java/example/BookController.java:17-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookListeners.kt:12 — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookListeners.kt:12-24 | doc-examples/hibernate-example-kotlin/src/main/kotlin/example/BookListeners.kt:12-24 — before extracting anything, compare `doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookListeners.kt` and `doc-examples/hibernate-example-kotlin/src/main/kotlin/example/BookListeners.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
DM5 · Encapsulated state · Mutable entity · ×8
  • Mutable entity: Book doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Book.kt:9 — `Book` exposes publicly writable state (id, title, pages).
  • Mutable entity: Student doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/Student.kt:10 — `Student` exposes publicly writable state (id).
  • Mutable entity: Book doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Book.kt:9 — `Book` exposes publicly writable state (id, title, pages).
  • Mutable entity: Student doc-examples/hibernate-example-kotlin/src/main/kotlin/example/Student.kt:10 — `Student` exposes publicly writable state (id).
  • Mutable entity: User doc-examples/hibernate-example-kotlin/src/main/kotlin/example/User.kt:10 — `User` exposes publicly writable state (id, name, enabled).
  • Mutable entity: Book doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Book.kt:9 — `Book` exposes publicly writable state (id, title, pages).
  • Mutable entity: Student doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/Student.kt:10 — `Student` exposes publicly writable state (id, name).
  • Mutable entity: Person doc-examples/jdbc-example-kotlin/src/main/kotlin/example/Person.kt:8 — `Person` exposes publicly writable state (id, name, age).
D15 · Churn × Complexity Hotspots · Hotspot · ×7
  • Hotspot: data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1497 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in SqlQueryBuilder.buildInsert at line 1497. 6 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.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: data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:607 — data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in SqlResultEntityTypeMapper.readEntity at line 607. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.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: data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1460 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AbstractSqlLikeQueryBuilder.buildPropertyByName at line 1460. 8 of those changes were fix/bug commits, and the other 9 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.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: data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:596 — data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in RepositoryTypeElementVisitor.processMethodInfo at line 596. 2 of those changes were fix/bug commits, and the other 4 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.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: data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1861 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in JdbcEntitiesOperations.execute at line 1861. 3 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.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: data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1568 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in R2dbcEntitiesOperations.execute at line 1568. 3 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.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: data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:127 — data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in SchemaGenerator.createOrValidateSchema at line 127. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.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.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×7
  • Edited copy of a member (20 corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:118 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:118-137 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexReadableResultReader.java:69-90 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:871 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:871-893 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:989-1008 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:916 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:916-935 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:953-974 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:510 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:510-529 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:531-552 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:436 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:436-455 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:484-503 — 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) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:206 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:206-225 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java:126-152 — 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) data-model/src/main/java/io/micronaut/data/model/PersistentProperty.java:157 — data-model/src/main/java/io/micronaut/data/model/PersistentProperty.java:157-176 | data-processor/src/main/java/io/micronaut/data/processor/model/SourcePersistentProperty.java:81-100 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×7
  • Duplicated block (11 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:80 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:80-90 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:113-123 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/visitor/JpaMetamodelProcessorVisitor.java:111 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/visitor/JpaMetamodelProcessorVisitor.java:111-121 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:118-128 — 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 `data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/visitor/JpaMetamodelProcessorVisitor.java:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3206 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3206-3216 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3433-3443 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3206` 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) data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:44 — data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:44-54 | data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:83-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `lhs` to `QuerySpecification<T>` in one and `DeleteSpecification<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:829 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:829-839 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:1201-1211 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:829` 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningManyReactiveInterceptor.java:44 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningManyReactiveInterceptor.java:44-54 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningOneReactiveInterceptor.java:46-56 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningManyReactiveInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningOneReactiveInterceptor.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningManyReactiveInterceptor.java:44` 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) doc-examples/hibernate-example-java/src/main/java/example/ProductRepository.java:65 — doc-examples/hibernate-example-java/src/main/java/example/ProductRepository.java:65-75 | doc-examples/hibernate-reactive-example-java/src/main/java/example/ProductRepository.java:37-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/hibernate-example-java/src/main/java/example/ProductRepository.java:65` 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.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×6
  • Edited copy of a member (25 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:192 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:192-220 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:395-419 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:945 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:945-969 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1209-1236 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/oracle/OracleClientInfoCondition.java:42 — data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/oracle/OracleClientInfoCondition.java:42-67 | data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/oracle/OracleTransactionRecoveryCondition.java:38-62 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:874 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:874-903 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:978-1002 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2733 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2733-2764 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2767-2791 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:117 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:117-145 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:158-182 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×6
  • Edited copy of a member (17 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:266 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:266-282 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:285-304 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningManyReactiveInterceptor.java:43 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningManyReactiveInterceptor.java:43-59 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultDeleteReturningOneReactiveInterceptor.java:45-66 — 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) data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:102 — data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:102-118 | data-connection/src/main/java/io/micronaut/data/connection/support/AbstractReactorConnectionOperations.java:137-153 — 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) data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToOneMapper.java:43 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToOneMapper.java:43-63 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/OneToOneMapper.java:43-59 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) data-connection-hibernate/src/main/java/io/micronaut/data/hibernate/conf/AbstractHibernateCondition.java:41 — data-connection-hibernate/src/main/java/io/micronaut/data/hibernate/conf/AbstractHibernateCondition.java:41-58 | data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/support/RequestBoundaryCondition.java:38-54 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:879 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:879-896 | data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:899-915 — 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 (14 corresponding lines) · ×6
  • Edited copy of a member (14 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:55 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:55-76 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:114-127 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:211 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:211-224 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:262-283 — 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) data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:247 — data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:247-260 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2243-2257 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:590 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:590-603 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:716-729 — 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) data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java:67 — data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java:67-80 | data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java:84-98 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:77 — doc-examples/mongo-reactive-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:77-90 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:57-70 — 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 (15 corresponding lines) · ×6
  • Edited copy of a member (15 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:446 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:446-460 | data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/DefaultPreparedQuery.java:214-233 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/Utils.java:65 — data-processor/src/main/java/io/micronaut/data/processor/visitors/Utils.java:65-79 | data-processor/src/main/java/io/micronaut/data/processor/visitors/Utils.java:86-102 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:104 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:104-119 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:122-136 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:123 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:123-138 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntitiesOperations.java:141-155 — 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) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:515 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:515-529 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1456-1471 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultEntityIdentityPresenceChecker.java:34 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultEntityIdentityPresenceChecker.java:34-48 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultEntityIdentityPresenceChecker.java:67-81 — 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 (4 corresponding lines) · ×6
  • Edited copy of a member (4 corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/DefaultChangeEvent.java:56 — data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/DefaultChangeEvent.java:56-59 | data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/DeferredChangeEvent.java:84-87 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:82 — data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:82-85 | data-model/src/main/java/io/micronaut/data/model/Page.java:76-79 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/DeleteAllReactiveSpecificationInterceptor.java:44 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/DeleteAllReactiveSpecificationInterceptor.java:44-47 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindAllReactiveSpecificationInterceptor.java:44-47 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:667 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:667-670 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractPreparedQueryCriteriaRepositoryOperations.java:176-179 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindOneAsyncInterceptor.java:43 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindOneAsyncInterceptor.java:43-46 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultFindOneReactiveInterceptor.java:43-46 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/jpa/JpaQueryBuilder.java:92 — data-model/src/main/java/io/micronaut/data/model/query/builder/jpa/JpaQueryBuilder.java:92-95 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:429-432 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×6
  • Duplicated block (7 lines × 3) data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedPropertyMapper.java:56 — data-document-processor/src/main/java/io/micronaut/data/document/processor/mapper/MappedPropertyMapper.java:56-62 | data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:472-478 | data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:506-512 — 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.
  • Duplicated block (7 lines × 3) data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:321 — data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:321-327 | data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:335-341 | data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:362-368 — 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 `data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:244 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:244-250 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:228-234 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:286-292 — before extracting anything, compare `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:244` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:243` calls `getMethodElement`, `annotate`, `value` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:227` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:239 — data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:239-245 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:248-254 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:257-263 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:239` 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 (7 lines × 3) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:233 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:233-239 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:103-109 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/JdbcTupleMapper.java:46-52 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 3) data-model/src/main/java/io/micronaut/data/model/vector/SparseByteVector.java:45 — data-model/src/main/java/io/micronaut/data/model/vector/SparseByteVector.java:45-51 | data-model/src/main/java/io/micronaut/data/model/vector/SparseDoubleVector.java:45-51 | data-model/src/main/java/io/micronaut/data/model/vector/SparseFloatVector.java:45-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×6
  • Swallowed exception (caught, then discarded) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnNameR2dbcResultReader.java:145 — `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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:240 — `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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Projections.java:48 — `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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Restrictions.java:50 — `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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/Restrictions.java:60 — `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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:500 — `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.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×5
  • Edited copy of a member (27 corresponding lines) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:938 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:938-969 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:971-997 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:682 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:682-709 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/QueryCriteriaMethodMatch.java:714-740 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:148 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:148-174 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:186-217 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3124 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3124-3157 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3911-3937 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:145 — data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:145-171 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:465-498 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×5
  • Edited copy of a member (21 corresponding lines) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:942 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:942-966 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/DefaultReactiveCosmosRepositoryOperations.java:975-995 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1625 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1625-1648 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1828-1848 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteAllInterceptor.java:46 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteAllInterceptor.java:46-66 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteAllReturningInterceptor.java:49-70 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveAllInterceptor.java:67 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveAllInterceptor.java:67-87 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultSaveAllAsyncInterceptor.java:56-78 — 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) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1917 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1917-1940 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1948-1968 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×5
  • Duplicated block (14 lines × 2) data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:67 — data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:67-80 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:187-200 — 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 `data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:67` 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) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/jakarta/data/HibernateJakartaDataDeleteExceptionConverter.java:44 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/jakarta/data/HibernateJakartaDataDeleteExceptionConverter.java:44-57 | data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/jakarta/data/HibernateJakartaDataUpdateExceptionConverter.java:44-57 — before extracting anything, compare `data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/jakarta/data/HibernateJakartaDataDeleteExceptionConverter.java` and `data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/jakarta/data/HibernateJakartaDataUpdateExceptionConverter.java` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (14 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/OracleTypeConvertersFactory.java:189 — data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/OracleTypeConvertersFactory.java:189-202 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/OracleTypeConvertersFactory.java:123-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3684 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3684-3697 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2850-2863 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3684` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2848` calls `add`, `getMappedName`, `getDataType` and `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3683` 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 (14 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:140 — data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:140-153 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/config/R2dbcSchemaGenerator.java:99-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×5
  • Duplicated block (9 lines × 3) data-connection-hibernate/src/main/java/io/micronaut/data/hibernate/conf/AbstractHibernateCondition.java:47 — data-connection-hibernate/src/main/java/io/micronaut/data/hibernate/conf/AbstractHibernateCondition.java:47-55 | data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/oracle/OracleClientInfoCondition.java:48-56 | data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/oracle/OracleTransactionRecoveryCondition.java:44-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (9 lines × 3) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3575 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3575-3583 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3690-3698 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2856-2864 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3575` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `propertyPath` to `PersistentPropertyPath` in one and `QueryPropertyPath` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningManyInterceptor.java:40 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningManyInterceptor.java:40-48 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertReturningManyInterceptor.java:40-48 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateReturningManyInterceptor.java:40-48 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningManyInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertReturningManyInterceptor.java` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningManyReactiveInterceptor.java:36 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningManyReactiveInterceptor.java:36-44 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultProcedureReactiveInterceptor.java:40-48 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultUpdateReturningManyReactiveInterceptor.java:36-44 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultInsertReturningManyReactiveInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultUpdateReturningManyReactiveInterceptor.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosBinder.java:77 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosBinder.java:77-85 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1463-1471 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:416-424 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×4
  • Edited copy of a member (16 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:59 — data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:59-74 | data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/QueryResultStoredQuery.java:116-134 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:371 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:371-386 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:433-449 — 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) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:153 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java:153-170 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/MethodNameParser.java: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) data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataSerdeRegistry.java:97 — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataSerdeRegistry.java:97-112 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataSerdeRegistry.java:115-130 — 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 (18 corresponding lines) · ×4
  • Edited copy of a member (18 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:404 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:404-421 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:425-442 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:401 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:401-418 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:724-742 — 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) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:754 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:754-771 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:808-825 — 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) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnNameR2dbcResultReader.java:68 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnNameR2dbcResultReader.java:68-85 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnNameR2dbcResultReader.java:89-106 — 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 (19 corresponding lines) · ×4
  • Edited copy of a member (19 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:854 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:854-872 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:750-773 — 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) data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:221 — data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:221-239 | data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:251-271 — 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) data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.java:47 — data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/jakarta/data/JdbcJakartaDataExceptionConverter.java:47-65 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/exceptions/jakarta/data/R2dbcJakartaDataExceptionConverter.java:47-65 — 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) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:193 — data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:193-212 | data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:215-233 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 9+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningOneInterceptor.java:49 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningOneInterceptor.java:49-57 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertReturningOneInterceptor.java:49-57 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateReturningOneInterceptor.java:49-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:950 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:950-958 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1044-1052 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1056-1070 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaDelete.java:54 — data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaDelete.java:54-62 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaInsert.java:48-56 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaUpdate.java:61-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:904 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:904-912 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1361-1369 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:139-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×4
  • Edited copy of a member (3 corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1250 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1250-1252 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1197-1199 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/AbstractSqlRepositoryOperations.java:219 — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/AbstractSqlRepositoryOperations.java:219-223 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:89-91 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:421 — data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:421-423 | data-processor/src/main/java/io/micronaut/data/processor/model/SourcePersistentEntity.java:300-302 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) data-spring/src/main/java/io/micronaut/data/spring/runtime/PageDelegate.java:113 — data-spring/src/main/java/io/micronaut/data/spring/runtime/PageDelegate.java:113-115 | data-spring/src/main/java/io/micronaut/data/spring/runtime/SliceDelegate.java:93-95 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×4
  • Duplicated block (25 lines × 2) data-connection/src/main/java/io/micronaut/data/connection/async/AsyncUsingReactiveConnectionOperations.java:75 — data-connection/src/main/java/io/micronaut/data/connection/async/AsyncUsingReactiveConnectionOperations.java:75-99 | data-tx/src/main/java/io/micronaut/transaction/async/AsyncUsingReactiveTransactionOperations.java:84-108 — 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 `data-connection/src/main/java/io/micronaut/data/connection/async/AsyncUsingReactiveConnectionOperations.java: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 (25 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:385 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:385-409 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:443-467 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:385` 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 (25 lines × 2) doc-examples/jdbc-example-java/src/main/java/example/Flight.java:17 — doc-examples/jdbc-example-java/src/main/java/example/Flight.java:17-41 | doc-examples/r2dbc-example-java/src/main/java/example/Flight.java:16-40 — before extracting anything, compare `doc-examples/jdbc-example-java/src/main/java/example/Flight.java` and `doc-examples/r2dbc-example-java/src/main/java/example/Flight.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (25 lines × 2) doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/ProductRepository.kt:49 — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/ProductRepository.kt:49-73 | doc-examples/hibernate-example-kotlin/src/main/kotlin/example/ProductRepository.kt:61-85 — before extracting anything, compare `doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/ProductRepository.kt` and `doc-examples/hibernate-example-kotlin/src/main/kotlin/example/ProductRepository.kt` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/ProductRepository.kt:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×4
  • Duplicated block (18 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:765 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:765-782 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:945-962 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `from` to `UpdateOptions` in one and `FindOneAndUpdateOptions` 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 (18 lines × 2) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:148 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:148-165 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java:165-182 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoCollectionsCreator.java:59 — data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoCollectionsCreator.java:59-76 | data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoReactiveCollectionsCreator.java:60-77 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoCollectionsCreator.java:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `MongoClient` names `com.mongodb.client.MongoClient` in one and `com.mongodb.reactivestreams.client.MongoClient` 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 (18 lines × 2) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1308 — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1308-1325 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2651-2668 — 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 `data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1308` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4
  • Duplicated block (15 lines × 2) data-connection-hibernate/src/main/java/io/micronaut/data/hibernate/conf/AbstractHibernateCondition.java:42 — data-connection-hibernate/src/main/java/io/micronaut/data/hibernate/conf/AbstractHibernateCondition.java:42-56 | data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/oracle/OracleClientInfoCondition.java:43-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:820 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:820-834 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:941-955 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:820` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:118 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:118-132 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:144-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:90 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:90-104 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/AbstractReactiveSpecificationInterceptor.java:79-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:90` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×4
  • Duplicated block (6 lines × 3) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1394 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1394-1399 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:105-110 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractReactiveEntityOperations.java:123-128 — 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 `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1394` 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 (6 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:266 — data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:266-271 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:274-279 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:282-287 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:266` 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 (6 lines × 3) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1918 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1918-1923 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1949-1954 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2004-2009 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1918` 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 (6 lines × 3) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentAssociationPath.java:159 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentAssociationPath.java:159-164 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentAssociationPath.java:125-130 | data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:1243-1248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×4
  • Duplicated block (23 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/AuthorBooksDto.java:32 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/AuthorBooksDto.java:32-56 | data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorBooksDto.java:29-51 — before extracting anything, compare `data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/AuthorBooksDto.java` and `data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorBooksDto.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (23 lines × 2) data-tck/src/main/java/io/micronaut/data/tck/entities/Country.java:37 — data-tck/src/main/java/io/micronaut/data/tck/entities/Country.java:37-59 | doc-examples/jdbc-example-java/src/main/java/example/Country.java:24-46 — before extracting anything, compare `data-tck/src/main/java/io/micronaut/data/tck/entities/Country.java` and `doc-examples/jdbc-example-java/src/main/java/example/Country.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (23 lines × 2) data-tck/src/main/java/io/micronaut/data/tck/jdbc/entities/upsert/AutoPopulatedUpsertEntity.java:71 — data-tck/src/main/java/io/micronaut/data/tck/jdbc/entities/upsert/AutoPopulatedUpsertEntity.java:71-170 | data-tck/src/main/java/io/micronaut/data/tck/jdbc/entities/upsert/CompositeClinic.java:29-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (23 lines × 2) doc-examples/mongo-multitenancy-datasource-example-java/src/main/java/example/BookController.java:21 — doc-examples/mongo-multitenancy-datasource-example-java/src/main/java/example/BookController.java:21-43 | doc-examples/mongo-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:21-48 — before extracting anything, compare `doc-examples/mongo-multitenancy-datasource-example-java/src/main/java/example/BookController.java` and `doc-examples/mongo-multitenancy-discriminator-example-java/src/main/java/example/BookController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×3
  • Edited copy of a member (5 corresponding lines) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/ReactiveHibernateHelper.java:120 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/ReactiveHibernateHelper.java:120-125 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/ReactiveHibernateHelper.java:137-141 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:108 — data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:108-112 | data-model/src/main/java/io/micronaut/data/model/CursoredPage.java:115-119 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:404 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:404-408 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:274-278 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 7+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:66 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:66-74 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor2.java:66-72 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java:127-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractPreparedQueryCriteriaRepositoryOperations.java:181 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractPreparedQueryCriteriaRepositoryOperations.java:181-187 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractPreparedQueryCriteriaRepositoryOperations.java:189-195 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractPreparedQueryCriteriaRepositoryOperations.java:197-203 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/operations/DefaultDataSourceConnectionOperations.java:82 — data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/operations/DefaultDataSourceConnectionOperations.java:82-88 | data-connection-jdbc/src/main/java/io/micronaut/data/connection/jdbc/support/RequestBoundaryConnectionCustomizer.java:92-98 | data-connection/src/main/java/io/micronaut/data/connection/support/JdbcConnectionUtils.java:125-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×3
  • Duplicated block (31 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:248 — data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:248-278 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:308-338 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:247` calls `requireNonNull` and `data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:307` 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 (31 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:741 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:741-771 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:618-648 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (31 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/BookDto.java:32 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/BookDto.java:32-64 | data-tck/src/main/java/io/micronaut/data/tck/entities/BookDto.java:29-59 — before extracting anything, compare `data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/BookDto.java` and `data-tck/src/main/java/io/micronaut/data/tck/entities/BookDto.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×3
  • Duplicated block (27 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/oracle/OracleChangeNotificationOptions.java:40 — data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/oracle/OracleChangeNotificationOptions.java:40-66 | data-processor/src/main/java/io/micronaut/data/processor/visitors/OracleChangeNotificationOptions.java:40-66 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/notification/oracle/OracleChangeNotificationOptions.java` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/OracleChangeNotificationOptions.java` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/services/AbstractBookService.java:31 — data-document-tck/src/main/java/io/micronaut/data/document/tck/services/AbstractBookService.java:31-57 | data-tck/src/main/java/io/micronaut/data/tck/services/AbstractBookService.java:32-62 — before extracting anything, compare `data-document-tck/src/main/java/io/micronaut/data/document/tck/services/AbstractBookService.java` and `data-tck/src/main/java/io/micronaut/data/tck/services/AbstractBookService.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Book` names `io.micronaut.data.document.tck.entities.Book` in one and `io.micronaut.data.tck.entities.Book` 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 (27 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/OracleJdbcVectorConverter.java:48 — data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/OracleJdbcVectorConverter.java:48-74 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/OracleR2dbcVectorConverter.java:47-73 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/OracleJdbcVectorConverter.java` and `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/OracleR2dbcVectorConverter.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×3
  • Duplicated block (24 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3134 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3134-3157 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3914-3937 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3134` 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 (24 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaDeleteImpl.java:48 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaDeleteImpl.java:48-71 | data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaUpdateImpl.java:49-96 — 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 `data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourcePersistentEntityCriteriaDeleteImpl.java:48` 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. 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 (24 lines × 2) doc-examples/jdbc-example-kotlin/src/main/kotlin/example/DemoController.kt:17 — doc-examples/jdbc-example-kotlin/src/main/kotlin/example/DemoController.kt:17-40 | doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/DemoController.kt:17-40 — before extracting anything, compare `doc-examples/jdbc-example-kotlin/src/main/kotlin/example/DemoController.kt` and `doc-examples/r2dbc-example-kotlin/src/main/kotlin/example/DemoController.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×3
  • Duplicated block (21 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:81 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:81-101 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/OracleR2dbcJsonColumnMapper.java:82-102 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java` and `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/OracleR2dbcJsonColumnMapper.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `resultReader` to `ResultReader<ResultSet, String>` in one and `ResultReader<Row, String>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (21 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:263 — data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:263-283 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:473-493 — 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 (21 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:219 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:219-239 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:277-297 — before extracting anything, compare `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:219` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×3
  • Duplicated block (8 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaDelete.java:55 — data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaDelete.java:55-62 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaInsert.java:49-56 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaUpdate.java:62-69 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaDelete.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimePersistentEntityCriteriaUpdate.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (8 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningOneInterceptor.java:50 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningOneInterceptor.java:50-57 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertReturningOneInterceptor.java:50-57 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateReturningOneInterceptor.java:50-57 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultDeleteReturningOneInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertReturningOneInterceptor.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 × 3) data-model/src/main/java/io/micronaut/data/model/vector/SparseByteVector.java:158 — data-model/src/main/java/io/micronaut/data/model/vector/SparseByteVector.java:158-165 | data-model/src/main/java/io/micronaut/data/model/vector/SparseDoubleVector.java:158-165 | data-model/src/main/java/io/micronaut/data/model/vector/SparseFloatVector.java:158-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×3
  • Duplicated block (7 lines × 4) data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:62 — data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:62-68 | data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:140-146 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:280-286 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:381-387 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `data-tck/src/main/java/io/micronaut/data/tck/repositories/BookSpecifications.java:62` 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 (7 lines × 4) data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:244 — data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:244-250 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:262-268 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:345-351 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:363-369 — 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 `data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:244` 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 (7 lines × 4) data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:135 — data-model/src/main/java/io/micronaut/data/model/PersistentPropertyPath.java:135-141 | data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:598-604 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:219-225 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/BaseOperations.java:303-309 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×3
  • Duplicated block (6 lines × 4) data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/DetachInterceptor.java:56 — data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/DetachInterceptor.java:56-61 | data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/PersistInterceptor.java:56-61 | data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/RefreshInterceptor.java:56-61 | data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/RemoveInterceptor.java:56-61 — before extracting anything, compare `data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/DetachInterceptor.java` and `data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/PersistInterceptor.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-jpa/src/main/java/io/micronaut/data/jpa/repository/intercept/DetachInterceptor.java:56` 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 × 4) data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:213 — data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:213-218 | data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:220-225 | data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:320-325 | data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:327-332 — 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 `data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:213` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 4) data-mongodb/src/main/java/io/micronaut/data/mongodb/transaction/DefaultMongoReactorTransactionOperations.java:77 — data-mongodb/src/main/java/io/micronaut/data/mongodb/transaction/DefaultMongoReactorTransactionOperations.java:77-82 | data-mongodb/src/main/java/io/micronaut/data/mongodb/transaction/DefaultMongoReactorTransactionOperations.java:85-90 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/transaction/DefaultR2dbcReactorTransactionOperations.java:138-143 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/transaction/DefaultR2dbcReactorTransactionOperations.java:146-151 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `connectionStatus` to `ConnectionStatus<ClientSession>` in one and `ConnectionStatus<Connection>` 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.
D10 · Test Quality · No assertions · ×2
  • No assertions: shouldReturnFalseForInvalidAuthor doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java:120 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: shouldReturnTrueForValidAuthor doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java:112 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) data-model/src/main/java/io/micronaut/data/model/geo/GeometryCollection.java:42 — data-model/src/main/java/io/micronaut/data/model/geo/GeometryCollection.java:42-52 | data-model/src/main/java/io/micronaut/data/model/geo/MultiLineString.java:42-52 | data-model/src/main/java/io/micronaut/data/model/geo/MultiPoint.java:42-52 | data-model/src/main/java/io/micronaut/data/model/geo/MultiPolygon.java:42-52 | data-model/src/main/java/io/micronaut/data/model/geo/Polygon.java:42-63 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertEntityInterceptor.java:43 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertEntityInterceptor.java:43-52 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertOneInterceptor.java:45-56 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveEntityInterceptor.java:43-52 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveOneInterceptor.java:45-56 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateEntityInterceptor.java:43-52 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:321 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:321-355 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:365-393 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:823 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:823-851 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:1195-1223 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×2
  • Edited copy of a member (35 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3658 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3658-3698 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2830-2864 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/http/PageableRequestArgumentBinder.java:83 — data-runtime/src/main/java/io/micronaut/data/runtime/http/PageableRequestArgumentBinder.java:83-118 | data-spring/src/main/java/io/micronaut/data/spring/runtime/http/SpringPageableRequestArgumentBinder.java:79-113 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:120 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:120-143 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:125-148 — 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) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:908 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:908-937 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1038-1061 — 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 (36 corresponding lines) · ×2
  • Edited copy of a member (36 corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:109 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:109-147 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:149-184 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) data-connection/src/main/java/io/micronaut/data/connection/async/AsyncUsingReactiveConnectionOperations.java:74 — data-connection/src/main/java/io/micronaut/data/connection/async/AsyncUsingReactiveConnectionOperations.java:74-115 | data-tx/src/main/java/io/micronaut/transaction/async/AsyncUsingReactiveTransactionOperations.java:83-118 — 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 copies of one member (4 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 15+ corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:267 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:267-286 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:288-307 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:309-328 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:357-371 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:695 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:695-709 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:712-726 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:307-322 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:325-340 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 7+ corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/AbstractJdbcVectorConverter.java:49 — data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/AbstractJdbcVectorConverter.java:49-55 | data-jdbc/src/main/java/io/micronaut/data/jdbc/convert/vendor/AbstractJdbcVectorConverter.java:65-71 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/AbstractR2dbcVectorConverter.java:48-55 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/convert/vendor/AbstractR2dbcVectorConverter.java:65-71 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Shipment.java:74 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Shipment.java:74-80 | data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/ShipmentId.java:73-79 | data-tck/src/main/java/io/micronaut/data/tck/entities/Shipment.java:70-76 | data-tck/src/main/java/io/micronaut/data/tck/entities/ShipmentId.java:68-74 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:167 — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:167-177 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:179-187 | data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:189-196 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:48 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:48-56 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:77-84 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpdateMethodMatcher.java:65-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceParameterExpressionImpl.java:204 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceParameterExpressionImpl.java:204-225 | data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceParameterExpressionImpl.java:259-280 — 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 `data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceParameterExpressionImpl.java:204` 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 (22 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceEmbeddedPersistentPropertyPathImpl.java:46 — data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceEmbeddedPersistentPropertyPathImpl.java:46-67 | data-runtime/src/main/java/io/micronaut/data/runtime/criteria/RuntimeEmbeddedPersistentPropertyPathImpl.java:46-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceEmbeddedPersistentPropertyPathImpl.java:46` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `persistentProperty` to `SourceAssociation` in one and `RuntimeAssociation<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:97 — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:97-113 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:179-195 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/MongoFindOneAndUpdate.java:46 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/MongoFindOneAndUpdate.java:46-71 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/MongoUpdate.java:45-61 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `options` to `FindOneAndUpdateOptions` in one and `UpdateOptions` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×2
  • Duplicated block (14 lines × 4) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:221 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:221-234 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:217-230 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:238-251 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:276-289 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:221` 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 × 4) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteReturningOneAsyncInterceptor.java:43 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteReturningOneAsyncInterceptor.java:43-56 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultInsertReturningOneAsyncInterceptor.java:43-56 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultProcedureReturningOneAsyncInterceptor.java:44-57 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultUpdateReturningOneAsyncInterceptor.java:43-56 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteReturningOneAsyncInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultInsertReturningOneAsyncInterceptor.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:57 — data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:57-67 | data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:70-80 | data-model/src/main/java/io/micronaut/data/repository/jpa/criteria/SpecificationComposition.java:96-106 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `lhs` to `QuerySpecification<T>` in one and `UpdateSpecification<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 3) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertAllInterceptor.java:50 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertAllInterceptor.java:50-60 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveAllInterceptor.java:55-65 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateAllEntitiesInterceptor.java:50-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertAllInterceptor.java:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:90 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:90-94 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:109-113 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:127-131 — 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 `data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:90` 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 × 3) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:792 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:792-796 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:809-813 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:655-659 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×2
  • Duplicated block (41 lines × 2) data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultIdDeserializer.java:1 — data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultIdDeserializer.java:1-41 | data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultOneRelationDeserializer.java:1-41 — before extracting anything, compare `data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultIdDeserializer.java` and `data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultOneRelationDeserializer.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultIdDeserializer.java:1` 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 (41 lines × 2) data-tx/src/main/java/io/micronaut/transaction/async/AsyncTransactionStatus.java:45 — data-tx/src/main/java/io/micronaut/transaction/async/AsyncTransactionStatus.java:45-85 | data-tx/src/main/java/io/micronaut/transaction/reactive/ReactiveTransactionStatus.java:38-84 — before extracting anything, compare `data-tx/src/main/java/io/micronaut/transaction/async/AsyncTransactionStatus.java` and `data-tx/src/main/java/io/micronaut/transaction/reactive/ReactiveTransactionStatus.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-tx/src/main/java/io/micronaut/transaction/async/AsyncTransactionStatus.java:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/predicate/ConjunctionPredicate.java:35 — data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/predicate/ConjunctionPredicate.java:35-53 | data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/predicate/DisjunctionPredicate.java:35-58 — before extracting anything, compare `data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/predicate/ConjunctionPredicate.java` and `data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/predicate/DisjunctionPredicate.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (19 lines × 2) doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/ProductManager.kt:17 — doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/ProductManager.kt:17-35 | doc-examples/mongo-example-kotlin/src/main/kotlin/example/ProductManager.kt:18-36 — before extracting anything, compare `doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/ProductManager.kt` and `doc-examples/mongo-example-kotlin/src/main/kotlin/example/ProductManager.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteReturningManyAsyncInterceptor.java:43 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteReturningManyAsyncInterceptor.java:43-51 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultInsertReturningManyAsyncInterceptor.java:43-51 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultProcedureReturningManyAsyncInterceptor.java:43-51 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultUpdateReturningManyAsyncInterceptor.java:43-51 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultDeleteReturningManyAsyncInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultInsertReturningManyAsyncInterceptor.java` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 4) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:64 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:64-72 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:64-72 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:63-71 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:92-100 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `index` to `Integer` in one and `String` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×2
  • Duplicated block (5 lines × 4) data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:53 — data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterDeserializer.java:53-57 | data-document-model/src/main/java/io/micronaut/data/document/serde/defaults/DefaultCustomConverterSerializer.java:51-55 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:173-177 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataEncoderContext.java:130-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `type` to `Argument<? super Object>` in one and `Argument<?>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 4) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:622 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:622-626 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:638-642 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:655-659 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:673-677 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:622` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `operation` to `UpdateOperation<T>` in one and `UpdateBatchOperation<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
DM10 · One transaction, one aggregate · One operation mutates 3 aggregates · ×2
  • One operation mutates 3 aggregates: SaleRepositorySpec.testReadWriteCustomType doc-examples/jdbc-example-python/src/test/python/example/SaleRepositorySpec.py:23 — `SaleRepositorySpec.testReadWriteCustomType` saves `manufacturerRepository`, `productRepository`, `saleRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 3 aggregates: SaleRepositorySpec.testReadWriteCustomType doc-examples/mongo-example-python/src/test/python/example/SaleRepositorySpec.py:23 — `SaleRepositorySpec.testReadWriteCustomType` saves `manufacturerRepository`, `productRepository`, `saleRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
D1 · Cyclomatic Complexity · DataConversionServiceFactory.build (cyclomatic 85) · ×1
  • DataConversionServiceFactory.build (cyclomatic 85) data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:68 — DataConversionServiceFactory.build has cyclomatic complexity 85 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · SqlColumnMapping.getSqlType (cyclomatic 83) · ×1
  • SqlColumnMapping.getSqlType (cyclomatic 83) data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:247 — SqlColumnMapping.getSqlType has cyclomatic complexity 83 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · QueryStatement.setDynamic (cyclomatic 69) · ×1
  • QueryStatement.setDynamic (cyclomatic 69) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/QueryStatement.java:59 — QueryStatement.setDynamic has cyclomatic complexity 69 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlResultEntityTypeMapper.readEntity (cyclomatic 66) · ×1
  • SqlResultEntityTypeMapper.readEntity (cyclomatic 66) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:607 — SqlResultEntityTypeMapper.readEntity has cyclomatic complexity 66 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlSchemaUtils.getColumnDefinition (cyclomatic 47) · ×1
  • SqlSchemaUtils.getColumnDefinition (cyclomatic 47) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:489 — SqlSchemaUtils.getColumnDefinition has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · AbstractSqlLikeQueryBuilder.buildUpdateStatement (cyclomatic 44) · ×1
  • AbstractSqlLikeQueryBuilder.buildUpdateStatement (cyclomatic 44) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:964 — AbstractSqlLikeQueryBuilder.buildUpdateStatement has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DefaultBindableParametersStoredQuery.bindParameter (cyclomatic 41) · ×1
  • DefaultBindableParametersStoredQuery.bindParameter (cyclomatic 41) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/query/DefaultBindableParametersStoredQuery.java:112 — DefaultBindableParametersStoredQuery.bindParameter has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DefaultMongoStoredQuery.replaceQueryParametersInBsonValue (cyclomatic 40) · ×1
  • DefaultMongoStoredQuery.replaceQueryParametersInBsonValue (cyclomatic 40) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:461 — DefaultMongoStoredQuery.replaceQueryParametersInBsonValue has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FindersUtils.resolveInterceptorTypeByOperationType (cyclomatic 39) · ×1
  • FindersUtils.resolveInterceptorTypeByOperationType (cyclomatic 39) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:142 — FindersUtils.resolveInterceptorTypeByOperationType has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MongoExecutorQueryMethodMatcher.match (cyclomatic 37) · ×1
  • MongoExecutorQueryMethodMatcher.match (cyclomatic 37) data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoExecutorQueryMethodMatcher.java:48 — MongoExecutorQueryMethodMatcher.match has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TypeUtils.resolveDataType (cyclomatic 36) · ×1
  • TypeUtils.resolveDataType (cyclomatic 36) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:553 — TypeUtils.resolveDataType has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlQueryBuilder.buildInsert (cyclomatic 34) · ×1
  • SqlQueryBuilder.buildInsert (cyclomatic 34) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1497 — SqlQueryBuilder.buildInsert has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlQueryBuilder.addGeneratedStatementToColumn (cyclomatic 33) · ×1
  • SqlQueryBuilder.addGeneratedStatementToColumn (cyclomatic 33) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1343 — SqlQueryBuilder.addGeneratedStatementToColumn has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SyncCascadeOperations.cascadeEntity (cyclomatic 31) · ×1
  • SyncCascadeOperations.cascadeEntity (cyclomatic 31) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/SyncCascadeOperations.java:69 — SyncCascadeOperations.cascadeEntity 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.
D1 · Cyclomatic Complexity · ReactiveCascadeOperations.cascadeEntity (cyclomatic 29) · ×1
  • ReactiveCascadeOperations.cascadeEntity (cyclomatic 29) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java:72 — ReactiveCascadeOperations.cascadeEntity has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RepositoryTypeElementVisitor.processMethodInfo (cyclomatic 27) · ×1
  • RepositoryTypeElementVisitor.processMethodInfo (cyclomatic 27) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:596 — RepositoryTypeElementVisitor.processMethodInfo has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RawQueryMethodMatcher.findSqlStatement (cyclomatic 26) · ×1
  • RawQueryMethodMatcher.findSqlStatement (cyclomatic 26) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:425 — RawQueryMethodMatcher.findSqlStatement 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.
D1 · Cyclomatic Complexity · DefaultMongoRepositoryOperations.applyFindOptions (cyclomatic 24) · ×1
  • DefaultMongoRepositoryOperations.applyFindOptions (cyclomatic 24) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:470 — DefaultMongoRepositoryOperations.applyFindOptions has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DefaultReactiveMongoRepositoryOperations.applyFindOptions (cyclomatic 24) · ×1
  • DefaultReactiveMongoRepositoryOperations.applyFindOptions (cyclomatic 24) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:482 — DefaultReactiveMongoRepositoryOperations.applyFindOptions has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MappedEntityVisitor.computeMappingDefaults (cyclomatic 24) · ×1
  • MappedEntityVisitor.computeMappingDefaults (cyclomatic 24) data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:298 — MappedEntityVisitor.computeMappingDefaults has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MongoQueryBuilder.buildSelect (cyclomatic 23) · ×1
  • MongoQueryBuilder.buildSelect (cyclomatic 23) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:140 — MongoQueryBuilder.buildSelect has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EntityEventRegistry.initListeners (cyclomatic 23) · ×1
  • EntityEventRegistry.initListeners (cyclomatic 23) data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:213 — EntityEventRegistry.initListeners has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlQueryBuilder.addTableCreateStatements (cyclomatic 22) · ×1
  • SqlQueryBuilder.addTableCreateStatements (cyclomatic 22) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:989 — SqlQueryBuilder.addTableCreateStatements has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlQueryBuilder.buildJoin (cyclomatic 22) · ×1
  • SqlQueryBuilder.buildJoin (cyclomatic 22) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2037 — SqlQueryBuilder.buildJoin has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 1.buildMatchInfo (cyclomatic 22) · ×1
  • 1.buildMatchInfo (cyclomatic 22) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:306 — 1.buildMatchInfo has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlQueryBuilder.createIndexStatement (cyclomatic 21) · ×1
  • SqlQueryBuilder.createIndexStatement (cyclomatic 21) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1182 — SqlQueryBuilder.createIndexStatement has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RawQueryMethodMatcher.containsTopLevelKeywordOutsideQuotes (cyclomatic 21) · ×1
  • RawQueryMethodMatcher.containsTopLevelKeywordOutsideQuotes (cyclomatic 21) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:367 — RawQueryMethodMatcher.containsTopLevelKeywordOutsideQuotes has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuditGraph.classify_package (cyclomatic 21) · ×1
  • AuditGraph.classify_package (cyclomatic 21) .github/scripts/vulnerability-audit-filter.py:92 — AuditGraph.classify_package has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SchemaGenerator.createOrValidateSchema (cyclomatic 20) · ×1
  • SchemaGenerator.createOrValidateSchema (cyclomatic 20) data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:127 — SchemaGenerator.createOrValidateSchema 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.
D1 · Cyclomatic Complexity · SchemaGenerator.generate (cyclomatic 20) · ×1
  • SchemaGenerator.generate (cyclomatic 20) data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:227 — SchemaGenerator.generate 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.
D1 · Cyclomatic Complexity · MongoFindOptions.copyNotNullFrom (cyclomatic 20) · ×1
  • MongoFindOptions.copyNotNullFrom (cyclomatic 20) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoFindOptions.java:79 — MongoFindOptions.copyNotNullFrom has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AbstractCriteriaMethodMatch.extractPredicates (cyclomatic 20) · ×1
  • AbstractCriteriaMethodMatch.extractPredicates (cyclomatic 20) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:210 — AbstractCriteriaMethodMatch.extractPredicates 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.
D1 · Cyclomatic Complexity · OracleRawQueryReturningSupport.findKeywordOutsideQuotes (cyclomatic 20) · ×1
  • OracleRawQueryReturningSupport.findKeywordOutsideQuotes (cyclomatic 20) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:117 — OracleRawQueryReturningSupport.findKeywordOutsideQuotes 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.
D1 · Cyclomatic Complexity · R2dbcEntitiesOperations.execute (cyclomatic 20) · ×1
  • R2dbcEntitiesOperations.execute (cyclomatic 20) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1568 — R2dbcEntitiesOperations.execute has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AbstractCascadeOperations.cascade (cyclomatic 20) · ×1
  • AbstractCascadeOperations.cascade (cyclomatic 20) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:77 — AbstractCascadeOperations.cascade 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.
D1 · Cyclomatic Complexity · MongoFindOptions.isEmpty (cyclomatic 19) · ×1
  • MongoFindOptions.isEmpty (cyclomatic 19) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoFindOptions.java:139 — MongoFindOptions.isEmpty has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DefaultMongoStoredQuery.<init> (cyclomatic 19) · ×1
  • DefaultMongoStoredQuery.<init> (cyclomatic 19) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:128 — DefaultMongoStoredQuery.<init> 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.
D1 · Cyclomatic Complexity · RepositoryTypeElementVisitor.bindParameters (cyclomatic 19) · ×1
  • RepositoryTypeElementVisitor.bindParameters (cyclomatic 19) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:892 — RepositoryTypeElementVisitor.bindParameters 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.
D1 · Cyclomatic Complexity · SqlResultEntityTypeMapper.setChildrenAndTriggerPostLoad (cyclomatic 19) · ×1
  • SqlResultEntityTypeMapper.setChildrenAndTriggerPostLoad (cyclomatic 19) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:547 — SqlResultEntityTypeMapper.setChildrenAndTriggerPostLoad 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.
D1 · Cyclomatic Complexity · JdbcEntitiesOperations.execute (cyclomatic 18) · ×1
  • JdbcEntitiesOperations.execute (cyclomatic 18) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1861 — JdbcEntitiesOperations.execute 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.
D1 · Cyclomatic Complexity · AbstractSqlLikeQueryBuilder.buildPropertyByName (cyclomatic 18) · ×1
  • AbstractSqlLikeQueryBuilder.buildPropertyByName (cyclomatic 18) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1460 — AbstractSqlLikeQueryBuilder.buildPropertyByName has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MongoQueryBuilder.addLookups (cyclomatic 17) · ×1
  • MongoQueryBuilder.addLookups (cyclomatic 17) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:355 — MongoQueryBuilder.addLookups 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.
D1 · Cyclomatic Complexity · MongoQueryBuilder.findPropertyInternal (cyclomatic 17) · ×1
  • MongoQueryBuilder.findPropertyInternal (cyclomatic 17) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:648 — MongoQueryBuilder.findPropertyInternal 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.
D1 · Cyclomatic Complexity · SqlUpsertQueryBuilder.build (cyclomatic 17) · ×1
  • SqlUpsertQueryBuilder.build (cyclomatic 17) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java:79 — SqlUpsertQueryBuilder.build has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DeleteMethodMatcher.match (cyclomatic 17) · ×1
  • DeleteMethodMatcher.match (cyclomatic 17) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:75 — DeleteMethodMatcher.match 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.
D1 · Cyclomatic Complexity · BeanIntrospectionMapper.map (cyclomatic 17) · ×1
  • BeanIntrospectionMapper.map (cyclomatic 17) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/BeanIntrospectionMapper.java:51 — BeanIntrospectionMapper.map 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.
D1 · Cyclomatic Complexity · MongoQueryBuilder.buildUpdate (cyclomatic 16) · ×1
  • MongoQueryBuilder.buildUpdate (cyclomatic 16) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:701 — MongoQueryBuilder.buildUpdate 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.
D1 · Cyclomatic Complexity · DefaultJdbcRepositoryOperations.findOne (cyclomatic 16) · ×1
  • DefaultJdbcRepositoryOperations.findOne (cyclomatic 16) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:377 — DefaultJdbcRepositoryOperations.findOne 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.
D1 · Cyclomatic Complexity · NamingStrategy.mappedName (cyclomatic 16) · ×1
  • NamingStrategy.mappedName (cyclomatic 16) data-model/src/main/java/io/micronaut/data/model/naming/NamingStrategy.java:153 — NamingStrategy.mappedName 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.
D1 · Cyclomatic Complexity · SqlQueryBuilder.createJsonViewQuery (cyclomatic 16) · ×1
  • SqlQueryBuilder.createJsonViewQuery (cyclomatic 16) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:640 — SqlQueryBuilder.createJsonViewQuery 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.
D1 · Cyclomatic Complexity · PersistentEntity.getPropertyPath (cyclomatic 16) · ×1
  • PersistentEntity.getPropertyPath (cyclomatic 16) data-model/src/main/java/io/micronaut/data/model/PersistentEntity.java:371 — PersistentEntity.getPropertyPath 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.
D1 · Cyclomatic Complexity · RepositoryTypeElementVisitor.addQueryDefinition (cyclomatic 16) · ×1
  • RepositoryTypeElementVisitor.addQueryDefinition (cyclomatic 16) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:809 — RepositoryTypeElementVisitor.addQueryDefinition 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.
D1 · Cyclomatic Complexity · DefaultSqlPreparedQuery.prepare (cyclomatic 16) · ×1
  • DefaultSqlPreparedQuery.prepare (cyclomatic 16) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:210 — DefaultSqlPreparedQuery.prepare 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.
D1 · Cyclomatic Complexity · HibernateTransactionManager.doBegin (cyclomatic 16) · ×1
  • HibernateTransactionManager.doBegin (cyclomatic 16) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:100 — HibernateTransactionManager.doBegin 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.java data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.java:325 — data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.java changed 3 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 8 (its worst body is DefaultTransactionDefinition.toString at line 325), 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 bugs found in a code review across processor, query builders, runtime, backends and transactions (#4091)”; “[5.2.x] Restructure the guide, add examples for all languages and fix documentation issues (#4073)”; “Restructure the guide, add examples for all languages and fix documentation issues (#4062)”. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:26:30 +01:00' --until='2026-11-16 10:26:30 +01:00' --full-history --no-merges -- data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionDefinition.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.
D17 · Explicit Debt · FixmeComment · ×1
  • FixmeComment test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/read/only/ReadOnlyRepository.java:10 — //FIXME - Are user defined repository interfaces like this allowed via the Specification? — 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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/SqlJsonColumnMapperProvider.java:89 — // Hack to avoid using the prepared query — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · SqlResultEntityTypeMapper.readEntity (cognitive 211) · ×1
  • SqlResultEntityTypeMapper.readEntity (cognitive 211) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:607 — SqlResultEntityTypeMapper.readEntity has cognitive complexity 211 (threshold 15). Drivers by points: if/else 55 (183 pts), boolean chains 14, ternaries 4 (7 pts), loops 3 (6 pts), error handling 1 (nesting depth added 134). 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.
D2 · Cognitive Complexity · DefaultMongoStoredQuery.replaceQueryParametersInBsonValue (cognitive 109) · ×1
  • DefaultMongoStoredQuery.replaceQueryParametersInBsonValue (cognitive 109) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:461 — DefaultMongoStoredQuery.replaceQueryParametersInBsonValue has cognitive complexity 109 (threshold 15). Drivers by points: if/else 29 (99 pts), loops 2 (4 pts), error handling 1 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 75). 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.
D2 · Cognitive Complexity · SyncCascadeOperations.cascadeEntity (cognitive 99) · ×1
  • SyncCascadeOperations.cascadeEntity (cognitive 99) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/SyncCascadeOperations.java:69 — SyncCascadeOperations.cascadeEntity has cognitive complexity 99 (threshold 15). Drivers by points: if/else 23 (73 pts), loops 4 (15 pts), boolean chains 6, ternaries 1 (5 pts) (nesting depth added 65). 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.
D2 · Cognitive Complexity · DataConversionServiceFactory.build (cognitive 94) · ×1
  • DataConversionServiceFactory.build (cognitive 94) data-runtime/src/main/java/io/micronaut/data/runtime/convert/DataConversionServiceFactory.java:68 — DataConversionServiceFactory.build has cognitive complexity 94 (threshold 15). Drivers by points: loops 60 (62 pts), error handling 15, if/else 4 (9 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SqlColumnMapping.getSqlType (cognitive 89) · ×1
  • SqlColumnMapping.getSqlType (cognitive 89) data-model/src/main/java/io/micronaut/data/model/schema/sql/SqlColumnMapping.java:247 — SqlColumnMapping.getSqlType has cognitive complexity 89 (threshold 15). Drivers by points: if/else 66 (71 pts), ternaries 4 (11 pts), boolean chains 7 (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · QueryStatement.setDynamic (cognitive 88) · ×1
  • QueryStatement.setDynamic (cognitive 88) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/QueryStatement.java:59 — QueryStatement.setDynamic has cognitive complexity 88 (threshold 15). Drivers by points: if/else 41 (79 pts), match/switch 2 (6 pts), boolean chains 3 (nesting depth added 42). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · AbstractSqlLikeQueryBuilder.buildUpdateStatement (cognitive 82) · ×1
  • AbstractSqlLikeQueryBuilder.buildUpdateStatement (cognitive 82) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:964 — AbstractSqlLikeQueryBuilder.buildUpdateStatement has cognitive complexity 82 (threshold 15). Drivers by points: if/else 35 (66 pts), boolean chains 12, loops 2 (4 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultBindableParametersStoredQuery.bindParameter (cognitive 75) · ×1
  • DefaultBindableParametersStoredQuery.bindParameter (cognitive 75) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/query/DefaultBindableParametersStoredQuery.java:112 — DefaultBindableParametersStoredQuery.bindParameter has cognitive complexity 75 (threshold 15). Drivers by points: if/else 36 (67 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlQueryBuilder.buildInsert (cognitive 69) · ×1
  • SqlQueryBuilder.buildInsert (cognitive 69) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1497 — SqlQueryBuilder.buildInsert has cognitive complexity 69 (threshold 15). Drivers by points: if/else 29 (51 pts), loops 5 (12 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaGenerator.createOrValidateSchema (cognitive 59) · ×1
  • SchemaGenerator.createOrValidateSchema (cognitive 59) data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:127 — SchemaGenerator.createOrValidateSchema has cognitive complexity 59 (threshold 15). Drivers by points: if/else 15 (42 pts), error handling 2 (6 pts), loops 2 (5 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 36). 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.
D2 · Cognitive Complexity · SchemaGenerator.generate (cognitive 57) · ×1
  • SchemaGenerator.generate (cognitive 57) data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:227 — SchemaGenerator.generate has cognitive complexity 57 (threshold 15). Drivers by points: if/else 9 (31 pts), error handling 3 (11 pts), loops 3 (10 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoExecutorQueryMethodMatcher.match (cognitive 55) · ×1
  • MongoExecutorQueryMethodMatcher.match (cognitive 55) data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoExecutorQueryMethodMatcher.java:48 — MongoExecutorQueryMethodMatcher.match has cognitive complexity 55 (threshold 15). Drivers by points: if/else 20 (39 pts), boolean chains 10, match/switch 3 (6 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TypeUtils.resolveDataType (cognitive 55) · ×1
  • TypeUtils.resolveDataType (cognitive 55) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/TypeUtils.java:553 — TypeUtils.resolveDataType has cognitive complexity 55 (threshold 15). Drivers by points: if/else 33 (49 pts), boolean chains 4, error handling 1, ternaries 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.
D2 · Cognitive Complexity · AuditGraph.classify_package (cognitive 54) · ×1
  • AuditGraph.classify_package (cognitive 54) .github/scripts/vulnerability-audit-filter.py:92 — AuditGraph.classify_package has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (40 pts), loops 4 (8 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoQueryBuilder.addLookups (cognitive 51) · ×1
  • MongoQueryBuilder.addLookups (cognitive 51) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:355 — MongoQueryBuilder.addLookups has cognitive complexity 51 (threshold 15). Drivers by points: if/else 14 (46 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractCriteriaMethodMatch.extractPredicates (cognitive 51) · ×1
  • AbstractCriteriaMethodMatch.extractPredicates (cognitive 51) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:210 — AbstractCriteriaMethodMatch.extractPredicates has cognitive complexity 51 (threshold 15). Drivers by points: if/else 19 (44 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 26). 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.
D2 · Cognitive Complexity · SqlQueryBuilder.addGeneratedStatementToColumn (cognitive 49) · ×1
  • SqlQueryBuilder.addGeneratedStatementToColumn (cognitive 49) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1343 — SqlQueryBuilder.addGeneratedStatementToColumn has cognitive complexity 49 (threshold 15). Drivers by points: if/else 29 (45 pts), boolean chains 3, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PersistentEntity.getPropertyPath (cognitive 45) · ×1
  • PersistentEntity.getPropertyPath (cognitive 45) data-model/src/main/java/io/micronaut/data/model/PersistentEntity.java:371 — PersistentEntity.getPropertyPath has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (41 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 28). 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.
D2 · Cognitive Complexity · FindersUtils.resolveInterceptorTypeByOperationType (cognitive 45) · ×1
  • FindersUtils.resolveInterceptorTypeByOperationType (cognitive 45) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:142 — FindersUtils.resolveInterceptorTypeByOperationType has cognitive complexity 45 (threshold 15). Drivers by points: if/else 33 (36 pts), boolean chains 9 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ReactiveCascadeOperations.cascadeEntity (cognitive 45) · ×1
  • ReactiveCascadeOperations.cascadeEntity (cognitive 45) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java:72 — ReactiveCascadeOperations.cascadeEntity has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (35 pts), boolean chains 6, loops 3, ternaries 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlQueryBuilder.addTableCreateStatements (cognitive 43) · ×1
  • SqlQueryBuilder.addTableCreateStatements (cognitive 43) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:989 — SqlQueryBuilder.addTableCreateStatements has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (37 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
D2 · Cognitive Complexity · RawQueryMethodMatcher.findSqlStatement (cognitive 43) · ×1
  • RawQueryMethodMatcher.findSqlStatement (cognitive 43) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:425 — RawQueryMethodMatcher.findSqlStatement has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 7, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RepositoryTypeElementVisitor.processMethodInfo (cognitive 43) · ×1
  • RepositoryTypeElementVisitor.processMethodInfo (cognitive 43) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:596 — RepositoryTypeElementVisitor.processMethodInfo has cognitive complexity 43 (threshold 15). Drivers by points: if/else 26 (38 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlResultEntityTypeMapper.setChildrenAndTriggerPostLoad (cognitive 43) · ×1
  • SqlResultEntityTypeMapper.setChildrenAndTriggerPostLoad (cognitive 43) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:547 — SqlResultEntityTypeMapper.setChildrenAndTriggerPostLoad has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 2 (7 pts), boolean chains 6 (nesting depth added 23). 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.
D2 · Cognitive Complexity · SqlPredicateVisitor.visitEquals (cognitive 42) · ×1
  • SqlPredicateVisitor.visitEquals (cognitive 42) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2622 — SqlPredicateVisitor.visitEquals has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (35 pts), loops 1 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 25). 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.
D2 · Cognitive Complexity · MongoQueryBuilder.buildSelect (cognitive 41) · ×1
  • MongoQueryBuilder.buildSelect (cognitive 41) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:140 — MongoQueryBuilder.buildSelect has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (32 pts), ternaries 2 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RepositoryTypeElementVisitor.bindParameters (cognitive 41) · ×1
  • RepositoryTypeElementVisitor.bindParameters (cognitive 41) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:892 — RepositoryTypeElementVisitor.bindParameters has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (39 pts), boolean chains 1, loops 1 (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.
D2 · Cognitive Complexity · AbstractCascadeOperations.cascade (cognitive 41) · ×1
  • AbstractCascadeOperations.cascade (cognitive 41) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:77 — AbstractCascadeOperations.cascade has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (27 pts), loops 2 (6 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultSqlPreparedQuery.prepare (cognitive 40) · ×1
  • DefaultSqlPreparedQuery.prepare (cognitive 40) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:210 — DefaultSqlPreparedQuery.prepare has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (34 pts), loops 2 (6 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlQueryBuilder.buildJoin (cognitive 39) · ×1
  • SqlQueryBuilder.buildJoin (cognitive 39) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2037 — SqlQueryBuilder.buildJoin has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (28 pts), ternaries 3 (7 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.
D2 · Cognitive Complexity · MongoQueryBuilder.findPropertyInternal (cognitive 37) · ×1
  • MongoQueryBuilder.findPropertyInternal (cognitive 37) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:648 — MongoQueryBuilder.findPropertyInternal has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 20). 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.
D2 · Cognitive Complexity · AbstractMongoCollectionsCreator.initialize (cognitive 37) · ×1
  • AbstractMongoCollectionsCreator.initialize (cognitive 37) data-mongodb/src/main/java/io/micronaut/data/mongodb/init/AbstractMongoCollectionsCreator.java:86 — AbstractMongoCollectionsCreator.initialize has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (29 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 26). 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.
D2 · Cognitive Complexity · SourcePersistentEntity.<init> (cognitive 37) · ×1
  • SourcePersistentEntity.<init> (cognitive 37) data-processor/src/main/java/io/micronaut/data/processor/model/SourcePersistentEntity.java:75 — SourcePersistentEntity.<init> has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (35 pts), boolean chains 1, loops 1 (nesting depth added 19). 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.
D2 · Cognitive Complexity · AbstractCriteriaMethodMatch.extractPredicates (cognitive 37) · ×1
  • AbstractCriteriaMethodMatch.extractPredicates (cognitive 37) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:336 — AbstractCriteriaMethodMatch.extractPredicates has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (29 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 23). 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.
D2 · Cognitive Complexity · MappedEntityVisitor.computeMappingDefaults (cognitive 37) · ×1
  • MappedEntityVisitor.computeMappingDefaults (cognitive 37) data-processor/src/main/java/io/micronaut/data/processor/visitors/MappedEntityVisitor.java:298 — MappedEntityVisitor.computeMappingDefaults has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 5 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlSchemaUtils.getColumnDefinition (cognitive 35) · ×1
  • SqlSchemaUtils.getColumnDefinition (cognitive 35) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:489 — SqlSchemaUtils.getColumnDefinition has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 2 (6 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PersistentEntity.getPath (cognitive 35) · ×1
  • PersistentEntity.getPath (cognitive 35) data-model/src/main/java/io/micronaut/data/model/PersistentEntity.java:244 — PersistentEntity.getPath has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (27 pts), ternaries 2 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 22). 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.
D2 · Cognitive Complexity · PersistentEntityUtils.traversePersistentProperties (cognitive 35) · ×1
  • PersistentEntityUtils.traversePersistentProperties (cognitive 35) data-model/src/main/java/io/micronaut/data/model/PersistentEntityUtils.java:216 — PersistentEntityUtils.traversePersistentProperties has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 4 (11 pts), ternaries 2 (6 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.
D2 · Cognitive Complexity · BeanIntrospectionMapper.map (cognitive 35) · ×1
  • BeanIntrospectionMapper.map (cognitive 35) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/BeanIntrospectionMapper.java:51 — BeanIntrospectionMapper.map has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (29 pts), loops 3 (4 pts), boolean chains 1, error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlSchemaUtils.addSqlIndexMappings (cognitive 34) · ×1
  • SqlSchemaUtils.addSqlIndexMappings (cognitive 34) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.java:953 — SqlSchemaUtils.addSqlIndexMappings has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (6 pts), error handling 1 (4 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · RawQueryMethodMatcher.containsTopLevelKeywordOutsideQuotes (cognitive 34) · ×1
  • RawQueryMethodMatcher.containsTopLevelKeywordOutsideQuotes (cognitive 34) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:367 — RawQueryMethodMatcher.containsTopLevelKeywordOutsideQuotes has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 6, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlQueryBuilder.createIndexStatement (cognitive 33) · ×1
  • SqlQueryBuilder.createIndexStatement (cognitive 33) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1182 — SqlQueryBuilder.createIndexStatement has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 6, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PersistentEntity.getPropertyByPath (cognitive 33) · ×1
  • PersistentEntity.getPropertyByPath (cognitive 33) data-model/src/main/java/io/micronaut/data/model/PersistentEntity.java:310 — PersistentEntity.getPropertyByPath has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (31 pts), loops 1 (2 pts) (nesting depth added 21). 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.
D2 · Cognitive Complexity · EntityEventRegistry.initListeners (cognitive 32) · ×1
  • EntityEventRegistry.initListeners (cognitive 32) data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:213 — EntityEventRegistry.initListeners has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (22 pts), error handling 6, loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractSqlLikeQueryBuilder.buildPropertyByName (cognitive 31) · ×1
  • AbstractSqlLikeQueryBuilder.buildPropertyByName (cognitive 31) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1460 — AbstractSqlLikeQueryBuilder.buildPropertyByName has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (21 pts), loops 2 (6 pts), boolean chains 3, ternaries 1 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · OracleRawQueryReturningSupport.findKeywordOutsideQuotes (cognitive 31) · ×1
  • OracleRawQueryReturningSupport.findKeywordOutsideQuotes (cognitive 31) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:117 — OracleRawQueryReturningSupport.findKeywordOutsideQuotes has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 7, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RepositoryTypeElementVisitor.visitRepositoryMethod (cognitive 31) · ×1
  • RepositoryTypeElementVisitor.visitRepositoryMethod (cognitive 31) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:436 — RepositoryTypeElementVisitor.visitRepositoryMethod has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 3 (6 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractHibernateOperations.createGraph (cognitive 30) · ×1
  • AbstractHibernateOperations.createGraph (cognitive 30) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/AbstractHibernateOperations.java:606 — AbstractHibernateOperations.createGraph has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 1 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultMongoStoredQuery.<init> (cognitive 30) · ×1
  • DefaultMongoStoredQuery.<init> (cognitive 30) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:128 — DefaultMongoStoredQuery.<init> has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (20 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoPredicateVisitor.visitEquals (cognitive 29) · ×1
  • MongoPredicateVisitor.visitEquals (cognitive 29) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:1304 — MongoPredicateVisitor.visitEquals has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (24 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 20). 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.
D2 · Cognitive Complexity · 2.bindOne (cognitive 29) · ×1
  • 2.bindOne (cognitive 29) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/AbstractHibernateOperations.java:516 — 2.bindOne has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (21 pts), ternaries 2 (8 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 1.buildMatchInfo (cognitive 29) · ×1
  • 1.buildMatchInfo (cognitive 29) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:306 — 1.buildMatchInfo has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 6, loops 2 (3 pts), ternaries 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.
D2 · Cognitive Complexity · MappingContext.findJoinPath (cognitive 29) · ×1
  • MappingContext.findJoinPath (cognitive 29) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:1176 — MappingContext.findJoinPath has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 2 (6 pts), loops 1 (3 pts) (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.
D2 · Cognitive Complexity · JdbcEntitiesOperations.execute (cognitive 28) · ×1
  • JdbcEntitiesOperations.execute (cognitive 28) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1861 — JdbcEntitiesOperations.execute has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 3 (5 pts), boolean chains 2, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NamingStrategy.mappedName (cognitive 28) · ×1
  • NamingStrategy.mappedName (cognitive 28) data-model/src/main/java/io/micronaut/data/model/naming/NamingStrategy.java:153 — NamingStrategy.mappedName has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 2, ternaries 1 (2 pts), loops 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.
D2 · Cognitive Complexity · DeleteMethodMatcher.match (cognitive 28) · ×1
  • DeleteMethodMatcher.match (cognitive 28) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:75 — DeleteMethodMatcher.match has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AutoPopulatedEntityEventListener.supports (cognitive 27) · ×1
  • AutoPopulatedEntityEventListener.supports (cognitive 27) data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/AutoPopulatedEntityEventListener.java:45 — AutoPopulatedEntityEventListener.supports has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 1 (4 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · DefaultSqlPreparedQuery.buildCursorPagination (cognitive 27) · ×1
  • DefaultSqlPreparedQuery.buildCursorPagination (cognitive 27) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/DefaultSqlPreparedQuery.java:435 — DefaultSqlPreparedQuery.buildCursorPagination has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (8 pts), loops 4 (5 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.
D2 · Cognitive Complexity · RepositoryTypeElementVisitor.addQueryDefinition (cognitive 26) · ×1
  • RepositoryTypeElementVisitor.addQueryDefinition (cognitive 26) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:809 — RepositoryTypeElementVisitor.addQueryDefinition has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 1 (3 pts), ternaries 1 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · HibernateTransactionManager.doBegin (cognitive 26) · ×1
  • HibernateTransactionManager.doBegin (cognitive 26) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:100 — HibernateTransactionManager.doBegin has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · R2dbcEntitiesOperations.execute (cognitive 25) · ×1
  • R2dbcEntitiesOperations.execute (cognitive 25) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1568 — R2dbcEntitiesOperations.execute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 20 (22 pts), ternaries 2, loops 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.
D2 · Cognitive Complexity · AbstractSpecificationInterceptor.createSelectionForSelectingIds (cognitive 25) · ×1
  • AbstractSpecificationInterceptor.createSelectionForSelectingIds (cognitive 25) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:562 — AbstractSpecificationInterceptor.createSelectionForSelectingIds has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 5 (9 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RuntimePersistentEntity.<init> (cognitive 24) · ×1
  • RuntimePersistentEntity.<init> (cognitive 24) data-model/src/main/java/io/micronaut/data/model/runtime/RuntimePersistentEntity.java:101 — RuntimePersistentEntity.<init> has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2, ternaries 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.
D2 · Cognitive Complexity · DefaultMongoStoredQuery.getValue (cognitive 24) · ×1
  • DefaultMongoStoredQuery.getValue (cognitive 24) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:611 — DefaultMongoStoredQuery.getValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 1 (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.
D2 · Cognitive Complexity · DefaultMongoRepositoryOperations.applyFindOptions (cognitive 23) · ×1
  • DefaultMongoRepositoryOperations.applyFindOptions (cognitive 23) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:470 — DefaultMongoRepositoryOperations.applyFindOptions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 20, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DefaultReactiveMongoRepositoryOperations.applyFindOptions (cognitive 23) · ×1
  • DefaultReactiveMongoRepositoryOperations.applyFindOptions (cognitive 23) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:482 — DefaultReactiveMongoRepositoryOperations.applyFindOptions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 20, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · HibernateJpaOperations.execute (cognitive 22) · ×1
  • HibernateJpaOperations.execute (cognitive 22) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:570 — HibernateJpaOperations.execute has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 1 (3 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.
D2 · Cognitive Complexity · DefaultJdbcRepositoryOperations.findOne (cognitive 22) · ×1
  • DefaultJdbcRepositoryOperations.findOne (cognitive 22) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:377 — DefaultJdbcRepositoryOperations.findOne has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, loops 1 (3 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractSqlLikeQueryBuilder.appendPropertyRef (cognitive 22) · ×1
  • AbstractSqlLikeQueryBuilder.appendPropertyRef (cognitive 22) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1764 — AbstractSqlLikeQueryBuilder.appendPropertyRef has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlQueryBuilder.createJsonViewQuery (cognitive 22) · ×1
  • SqlQueryBuilder.createJsonViewQuery (cognitive 22) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:640 — SqlQueryBuilder.createJsonViewQuery has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 4, boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SourceParameterExpressionImpl.bind (cognitive 22) · ×1
  • SourceParameterExpressionImpl.bind (cognitive 22) data-processor/src/main/java/io/micronaut/data/processor/model/criteria/impl/SourceParameterExpressionImpl.java:135 — SourceParameterExpressionImpl.bind has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 5 (8 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · AbstractCascadeOperations.afterCascadedMany (cognitive 22) · ×1
  • AbstractCascadeOperations.afterCascadedMany (cognitive 22) data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:186 — AbstractCascadeOperations.afterCascadedMany has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 1 (2 pts) (nesting depth added 13). 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.
D2 · Cognitive Complexity · SqlSelectionVisitor.visit (cognitive 21) · ×1
  • SqlSelectionVisitor.visit (cognitive 21) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:3351 — SqlSelectionVisitor.visit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · DefaultMongoPreparedQuery.applyPageable (cognitive 21) · ×1
  • DefaultMongoPreparedQuery.applyPageable (cognitive 21) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoPreparedQuery.java:221 — DefaultMongoPreparedQuery.applyPageable has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 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.
D2 · Cognitive Complexity · MongoQueryBuilder.buildUpdate (cognitive 20) · ×1
  • MongoQueryBuilder.buildUpdate (cognitive 20) data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:701 — MongoQueryBuilder.buildUpdate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (4 pts), 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.
D2 · Cognitive Complexity · AbstractPersistentEntity.getNamingStrategy (cognitive 20) · ×1
  • AbstractPersistentEntity.getNamingStrategy (cognitive 20) data-model/src/main/java/io/micronaut/data/model/AbstractPersistentEntity.java:90 — AbstractPersistentEntity.getNamingStrategy has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 1 (2 pts), boolean chains 1, ternaries 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.
D2 · Cognitive Complexity · SqlResultEntityTypeMapper.buildIdOnlyEntity (cognitive 20) · ×1
  • SqlResultEntityTypeMapper.buildIdOnlyEntity (cognitive 20) data-runtime/src/main/java/io/micronaut/data/runtime/mapper/sql/SqlResultEntityTypeMapper.java:973 — SqlResultEntityTypeMapper.buildIdOnlyEntity has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (19 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.
D2 · Cognitive Complexity · CriteriaUtils.hasVersionPredicate (cognitive 19) · ×1
  • CriteriaUtils.hasVersionPredicate (cognitive 19) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/CriteriaUtils.java:183 — CriteriaUtils.hasVersionPredicate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · AbstractSqlLikeQueryBuilder.buildOrderBy (cognitive 19) · ×1
  • AbstractSqlLikeQueryBuilder.buildOrderBy (cognitive 19) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1382 — AbstractSqlLikeQueryBuilder.buildOrderBy has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoFindOptions.copyNotNullFrom (cognitive 19) · ×1
  • MongoFindOptions.copyNotNullFrom (cognitive 19) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoFindOptions.java:79 — MongoFindOptions.copyNotNullFrom has cognitive complexity 19 (threshold 15). Drivers by points: if/else 19. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DefaultMongoRepositoryOperations.triggerPostLoad (cognitive 19) · ×1
  • DefaultMongoRepositoryOperations.triggerPostLoad (cognitive 19) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:740 — DefaultMongoRepositoryOperations.triggerPostLoad has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), match/switch 1 (3 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.
D2 · Cognitive Complexity · DefaultReactiveMongoRepositoryOperations.triggerPostLoad (cognitive 19) · ×1
  • DefaultReactiveMongoRepositoryOperations.triggerPostLoad (cognitive 19) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:617 — DefaultReactiveMongoRepositoryOperations.triggerPostLoad has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), match/switch 1 (3 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.
D2 · Cognitive Complexity · UpdateCriteriaMethodMatch.interceptPredicate (cognitive 19) · ×1
  • UpdateCriteriaMethodMatch.interceptPredicate (cognitive 19) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:166 — UpdateCriteriaMethodMatch.interceptPredicate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractQueryInterceptor.instantiateEntity (cognitive 19) · ×1
  • AbstractQueryInterceptor.instantiateEntity (cognitive 19) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:811 — AbstractQueryInterceptor.instantiateEntity has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · vulnerability-audit-filter.main (cognitive 19) · ×1
  • vulnerability-audit-filter.main (cognitive 19) .github/scripts/vulnerability-audit-filter.py:206 — vulnerability-audit-filter.main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AbstractHibernateOperations.bindQueryHints (cognitive 18) · ×1
  • AbstractHibernateOperations.bindQueryHints (cognitive 18) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/AbstractHibernateOperations.java:572 — AbstractHibernateOperations.bindQueryHints has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (2 pts), boolean chains 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.
D2 · Cognitive Complexity · Joiner.joinAssociation (cognitive 18) · ×1
  • Joiner.joinAssociation (cognitive 18) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/util/Joiner.java:103 — Joiner.joinAssociation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (18 pts) (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.
D2 · Cognitive Complexity · SqlSelectionVisitor.selectAllColumnsFromJoinPaths (cognitive 18) · ×1
  • SqlSelectionVisitor.selectAllColumnsFromJoinPaths (cognitive 18) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:2634 — SqlSelectionVisitor.selectAllColumnsFromJoinPaths has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 3 (5 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · MongoFindOptions.isEmpty (cognitive 18) · ×1
  • MongoFindOptions.isEmpty (cognitive 18) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoFindOptions.java:139 — MongoFindOptions.isEmpty has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · R2dbcSchemaGenerator.createSchema (cognitive 18) · ×1
  • R2dbcSchemaGenerator.createSchema (cognitive 18) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/config/R2dbcSchemaGenerator.java:90 — R2dbcSchemaGenerator.createSchema has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractSpecificationInterceptor.buildCursorPagination (cognitive 18) · ×1
  • AbstractSpecificationInterceptor.buildCursorPagination (cognitive 18) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:326 — AbstractSpecificationInterceptor.buildCursorPagination has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractSpecificationInterceptor.getCriteriaQueryBuilder (cognitive 18) · ×1
  • AbstractSpecificationInterceptor.getCriteriaQueryBuilder (cognitive 18) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/AbstractSpecificationInterceptor.java:473 — AbstractSpecificationInterceptor.getCriteriaQueryBuilder has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AbstractTransactionOperations.commitInternal (cognitive 18) · ×1
  • AbstractTransactionOperations.commitInternal (cognitive 18) data-tx/src/main/java/io/micronaut/transaction/support/AbstractTransactionOperations.java:483 — AbstractTransactionOperations.commitInternal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), error handling 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CosmosSerde.serialize (cognitive 17) · ×1
  • CosmosSerde.serialize (cognitive 17) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosSerde.java:71 — CosmosSerde.serialize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractHibernateOperations.collectResults (cognitive 17) · ×1
  • AbstractHibernateOperations.collectResults (cognitive 17) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/AbstractHibernateOperations.java:378 — AbstractHibernateOperations.collectResults has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaGenerator.validate (cognitive 17) · ×1
  • SchemaGenerator.validate (cognitive 17) data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:311 — SchemaGenerator.validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultJdbcRepositoryOperations.findStream (cognitive 17) · ×1
  • DefaultJdbcRepositoryOperations.findStream (cognitive 17) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:552 — DefaultJdbcRepositoryOperations.findStream has cognitive complexity 17 (threshold 15). Drivers by points: error handling 5 (6 pts), if/else 3 (4 pts), ternaries 2 (4 pts), loops 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlPredicateVisitor.visit (cognitive 17) · ×1
  • SqlPredicateVisitor.visit (cognitive 17) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:2572 — SqlPredicateVisitor.visit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DefaultMongoStoredQuery.needsProcessingValue (cognitive 17) · ×1
  • DefaultMongoStoredQuery.needsProcessingValue (cognitive 17) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:355 — DefaultMongoStoredQuery.needsProcessingValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateReturningData.getOptions (cognitive 17) · ×1
  • UpdateReturningData.getOptions (cognitive 17) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:1004 — UpdateReturningData.getOptions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractCriteriaMethodMatch.applyJoinSpecs (cognitive 17) · ×1
  • AbstractCriteriaMethodMatch.applyJoinSpecs (cognitive 17) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/AbstractCriteriaMethodMatch.java:671 — AbstractCriteriaMethodMatch.applyJoinSpecs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SaveMethodMatcher.addPropertyUpdateQueryIfPossible (cognitive 17) · ×1
  • SaveMethodMatcher.addPropertyUpdateQueryIfPossible (cognitive 17) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:403 — SaveMethodMatcher.addPropertyUpdateQueryIfPossible has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · R2dbcEntityOperations.execute (cognitive 17) · ×1
  • R2dbcEntityOperations.execute (cognitive 17) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1419 — R2dbcEntityOperations.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, ternaries 3 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · FindPageAsyncSpecificationInterceptor.findAllAsync (cognitive 17) · ×1
  • FindPageAsyncSpecificationInterceptor.findAllAsync (cognitive 17) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:116 — FindPageAsyncSpecificationInterceptor.findAllAsync has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · FindPageReactiveSpecificationInterceptor.findAllReactive (cognitive 17) · ×1
  • FindPageReactiveSpecificationInterceptor.findAllReactive (cognitive 17) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:121 — FindPageReactiveSpecificationInterceptor.findAllReactive has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · DefaultAbstractFindPageInterceptor.intercept (cognitive 17) · ×1
  • DefaultAbstractFindPageInterceptor.intercept (cognitive 17) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultAbstractFindPageInterceptor.java:48 — DefaultAbstractFindPageInterceptor.intercept has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultConnectionStatus.forEachSynchronizations (cognitive 16) · ×1
  • DefaultConnectionStatus.forEachSynchronizations (cognitive 16) data-connection/src/main/java/io/micronaut/data/connection/support/DefaultConnectionStatus.java:122 — DefaultConnectionStatus.forEachSynchronizations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (6 pts), error handling 1 (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.
D2 · Cognitive Complexity · DefaultParameterExpression.bind (cognitive 16) · ×1
  • DefaultParameterExpression.bind (cognitive 16) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/DefaultParameterExpression.java:50 — DefaultParameterExpression.bind has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (2 pts), boolean chains 1, ternaries 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.
D2 · Cognitive Complexity · SqlQueryBuilder.processAssociation (cognitive 16) · ×1
  • SqlQueryBuilder.processAssociation (cognitive 16) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:879 — SqlQueryBuilder.processAssociation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · StaticMetamodelInitializer.initializeMetadataInternal (cognitive 16) · ×1
  • StaticMetamodelInitializer.initializeMetadataInternal (cognitive 16) data-runtime/src/main/java/io/micronaut/data/runtime/criteria/metamodel/StaticMetamodelInitializer.java:54 — StaticMetamodelInitializer.initializeMetadataInternal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (3 members, 26 shared lines) · ×1
  • Near-duplicate member family (3 members, 26 shared lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:117 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:117-159 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:367-415 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:425-485 — These 3 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:59 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/FindPageAsyncSpecificationInterceptor.java:59-102 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/reactive/FindPageReactiveSpecificationInterceptor.java:60-103 — 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 (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:196 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/DeleteCriteriaMethodMatch.java:196-251 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/criteria/UpdateCriteriaMethodMatch.java:258-319 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:53 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:53-91 | data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/JacksonNodeConverter.java:149-187 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:175 — data-jpa-metamodel-processor/src/main/java/io/micronaut/data/processor/jpa/metamodel/JpaMetamodelProcessor.java:175-212 | data-processor/src/main/java/io/micronaut/data/processor/visitors/GenerateJakartaDataMetamodelVisitor.java:153-190 — 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 (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1063 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1063-1096 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:1012-1050 — 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:867 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:867-895 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:985-1010 — 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1278 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1278-1317 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1320-1350 — 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 (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:775 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:775-812 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:897-933 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:69 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/OracleJdbcJsonColumnMapper.java:69-101 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/OracleR2dbcJsonColumnMapper.java:70-102 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1067 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:1067-1094 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:1016-1048 — 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 (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:235 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:235-277 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:231-275 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoCollectionsCreator.java:57 — data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoCollectionsCreator.java:57-86 | data-mongodb/src/main/java/io/micronaut/data/mongodb/init/MongoReactiveCollectionsCreator.java:58-87 — 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, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:879 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:879-907 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1014-1034 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1167-1195 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 20+ corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:794 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:794-813 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:838-857 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1144-1163 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 22+ corresponding lines) data-model/src/main/java/io/micronaut/data/model/vector/SparseByteVector.java:59 — data-model/src/main/java/io/micronaut/data/model/vector/SparseByteVector.java:59-80 | data-model/src/main/java/io/micronaut/data/model/vector/SparseDoubleVector.java:59-80 | data-model/src/main/java/io/micronaut/data/model/vector/SparseFloatVector.java:59-80 — 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 copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:246 — data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:246-288 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:365-406 — 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 (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:305 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/AbstractR2dbcResultReader.java:305-327 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/ColumnIndexR2dbcResultReader.java:46-68 — 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, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:629 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:629-651 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:653-671 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:673-695 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:821 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:821-830 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:837-848 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:715-724 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:727-738 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:88 — data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:88-104 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:107-122 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/connection/DefaultR2dbcReactorConnectionOperations.java:125-140 — 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, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:296 — data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:296-309 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:312-325 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:385-396 | data-hibernate-reactive/src/main/java/io/micronaut/data/hibernate/reactive/operations/DefaultHibernateReactiveRepositoryOperations.java:399-413 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:251 — data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:251-271 | data-tx-hibernate/src/main/java/io/micronaut/transaction/hibernate/HibernateTransactionManager.java:274-288 | data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/DataSourceTransactionManager.java:333-353 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:816 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:816-824 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:827-835 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:861-875 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:911-919 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:91 — data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:91-119 | data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:122-145 | data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:148-170 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 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) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/event/EventIntegrator.java:93 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/event/EventIntegrator.java:93-103 | data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/event/EventIntegrator.java:134-144 | data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/event/EventIntegrator.java:170-180 — 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 (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:682 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:682-691 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor.java:76-85 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractReactiveInterceptor.java:70-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 14+ corresponding lines) data-connection/src/main/java/io/micronaut/data/connection/DefaultConnectionOperationsRegistry.java:64 — data-connection/src/main/java/io/micronaut/data/connection/DefaultConnectionOperationsRegistry.java:64-77 | data-connection/src/main/java/io/micronaut/data/connection/DefaultConnectionOperationsRegistry.java:81-94 | data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionOperationsRegistry.java:63-76 | data-tx/src/main/java/io/micronaut/transaction/support/DefaultTransactionOperationsRegistry.java:79-92 — 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 (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:554 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:554-561 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:563-570 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:572-579 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/FindersUtils.java:581-588 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:451 — data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:451-462 | data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:466-479 | data-hibernate-jpa/src/main/java/io/micronaut/data/hibernate/operations/HibernateJpaOperations.java:524-536 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) data-connection/src/main/java/io/micronaut/data/connection/support/JdbcConnectionUtils.java:157 — data-connection/src/main/java/io/micronaut/data/connection/support/JdbcConnectionUtils.java:157-167 | data-connection/src/main/java/io/micronaut/data/connection/support/JdbcConnectionUtils.java:169-179 | data-connection/src/main/java/io/micronaut/data/connection/support/JdbcConnectionUtils.java:181-191 | data-connection/src/main/java/io/micronaut/data/connection/support/JdbcConnectionUtils.java:193-203 — 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 (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:295 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:295-300 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:319-324 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:319-324 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:343-348 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 10+ corresponding lines) data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:103 — data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:103-113 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:116-125 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:128-137 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:140-150 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:153-162 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:165-175 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:179-188 | data-runtime/src/main/java/io/micronaut/data/runtime/event/EntityEventRegistry.java:191-200 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 8+ corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataDeleteMapper.java:44 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataDeleteMapper.java:44-51 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataInsertMapper.java:44-51 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataRepositoryMapper.java:44-51 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataSaveMapper.java:44-51 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataUpdateMapper.java:44-51 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) data-model/src/main/java/io/micronaut/data/model/geo/MultiPoint.java:72 — data-model/src/main/java/io/micronaut/data/model/geo/MultiPoint.java:72-77 | data-model/src/main/java/io/micronaut/data/model/geo/MultiPolygon.java:72-77 | data-model/src/main/java/io/micronaut/data/model/geo/Polygon.java:83-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 3+ corresponding lines) data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/PersonRepository.java:145 — data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/PersonRepository.java:145-147 | data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:207-209 | doc-examples/hibernate-example-java/src/main/java/example/ProductRepository.java:85-88 | doc-examples/hibernate-reactive-example-java/src/main/java/example/ProductRepository.java:57-60 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/OracleReturningSupport.java:126 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/OracleReturningSupport.java:126-129 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:674-677 | data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/AbstractSqlRepositoryOperations.java:827-830 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 5+ corresponding lines) data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataByMapper.java:42 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataByMapper.java:42-46 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataParamsMapper.java:42-46 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataSelectMapper.java:42-46 — 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 · Duplicated block (81 lines × 2) · ×1
  • Duplicated block (81 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:471 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:471-551 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:483-563 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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: the declarations holding them bind `findIterable` to `FindIterable<MR>` in one and `FindPublisher<MR>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:571 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:571-602 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:584-615 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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: the declarations holding them bind `aggregateIterable` to `AggregateIterable<MR>` in one and `AggregatePublisher<MR>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (26–29 lines × 3) · ×1
  • Duplicated block (26–29 lines × 3) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:122 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:122-147 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:368-396 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:426-454 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:983 — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:983-1003 | data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:1533-1554 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:983` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:323 — data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:323-343 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:386-406 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:427-447 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:323` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:212 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:212-231 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:229-248 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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 `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:212` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–19 lines × 3) · ×1
  • Duplicated block (18–19 lines × 3) data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:147 — data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:147-164 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:184-202 | data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:422-440 — 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 `data-model/src/main/java/io/micronaut/data/model/query/builder/QueryResult.java:147` 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.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:95 — data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:95-111 | data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:124-140 | data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:150-166 — 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 `data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:95` 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, `data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:112` calls `onNext` and `data-tx/src/main/java/io/micronaut/transaction/support/SyncCompleteAndErrorPublisher.java:167` 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/JdbcExceptionUtils.java:75 — data-jdbc/src/main/java/io/micronaut/data/jdbc/exceptions/JdbcExceptionUtils.java:75-90 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/exceptions/R2dbcExceptionUtils.java:75-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:750 — data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:750-763 | data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:780-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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/RepositoryTypeElementVisitor.java:750` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:364 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/AbstractQueryInterceptor.java:364-378 | data-runtime/src/main/java/io/micronaut/data/runtime/query/internal/DefaultStoredQuery.java:276-289 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `MethodInvocationContext` in one and `ExecutableMethod<?, ?>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToOneMapper.java:50 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToOneMapper.java:50-63 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/OneToOneMapper.java:49-59 — 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 `data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToOneMapper.java:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/OneToOneMapper.java:48` calls `stringValue`, `ifPresent`, `member` and `data-processor/src/main/java/io/micronaut/data/processor/mappers/jpa/jx/ManyToOneMapper.java:50` 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:502 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:502-513 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java:577-588 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:514-525 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java:590-601 — before extracting anything, compare `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoRepositoryOperations.java` and `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultReactiveMongoRepositoryOperations.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 278 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: the declarations holding them bind `findIterable` to `FindIterable<MR>` in one and `FindPublisher<MR>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:102 — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:102-113 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:141-152 | data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:184-195 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:102` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:65 — data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:65-76 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:103-112 — 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 `data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/options/MongoOptionsUtils.java:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:62 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:62-71 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:90-99 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpdateMethodMatcher.java:78-87 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.java:69-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoRawQueryMethodMatcher.java:227 — data-document-processor/src/main/java/io/micronaut/data/document/processor/matchers/MongoRawQueryMethodMatcher.java:227-236 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.java:235-243 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) data-model/src/main/java/io/micronaut/data/model/geo/GeometryCollection.java:43 — data-model/src/main/java/io/micronaut/data/model/geo/GeometryCollection.java:43-51 | data-model/src/main/java/io/micronaut/data/model/geo/MultiLineString.java:43-51 | data-model/src/main/java/io/micronaut/data/model/geo/MultiPoint.java:43-51 | data-model/src/main/java/io/micronaut/data/model/geo/MultiPolygon.java:43-51 | data-model/src/main/java/io/micronaut/data/model/geo/Polygon.java:43-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1683 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1683-1690 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1950-1956 — 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 `data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1683` 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertEntityInterceptor.java:46 — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertEntityInterceptor.java:46-52 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertOneInterceptor.java:50-56 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveEntityInterceptor.java:46-52 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultSaveOneInterceptor.java:50-56 | data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultUpdateEntityInterceptor.java:46-52 — before extracting anything, compare `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertEntityInterceptor.java` and `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertOneInterceptor.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultInsertEntityInterceptor.java:46` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–6 lines × 2) · ×1
  • Duplicated block (5–6 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:309 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:309-313 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:315-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ReservationMethodMatcher.java:122 — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ReservationMethodMatcher.java:122-128 | data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpdateMethodMatcher.java:239-244 — 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 `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ReservationMethodMatcher.java:122` 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, `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpdateMethodMatcher.java:236` calls `getPersistentEntity`, `hasIdentity` and `data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ReservationMethodMatcher.java:121` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (62 lines × 2) · ×1
  • Duplicated block (62 lines × 2) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Pet.java:1 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Pet.java:1-66 | data-tck/src/main/java/io/micronaut/data/tck/entities/Pet.java:1-62 — before extracting anything, compare `data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Pet.java` and `data-tck/src/main/java/io/micronaut/data/tck/entities/Pet.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Pet.java:1` 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.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×1
  • Duplicated block (19 lines × 4) data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/QuantityAttributeConverter.java:1 — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/QuantityAttributeConverter.java:1-36 | doc-examples/jdbc-example-java/src/main/java/example/QuantityAttributeConverter.java:1-19 | doc-examples/mongo-example-java/src/main/java/example/QuantityAttributeConverter.java:1-19 | doc-examples/mongo-example-records-java/src/main/java/example/QuantityAttributeConverter.java:1-19 — before extracting anything, compare `doc-examples/jdbc-example-java/src/main/java/example/QuantityAttributeConverter.java` and `doc-examples/mongo-example-java/src/main/java/example/QuantityAttributeConverter.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/QuantityAttributeConverter.java:1` 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.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×1
  • Duplicated block (50 lines × 2) data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/OracleSqlExceptionMapper.java:1 — data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/OracleSqlExceptionMapper.java:1-53 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/OracleR2dbcExceptionMapper.java:1-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 `data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/OracleSqlExceptionMapper.java:1` 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.
D4 · Code Duplication · Duplicated block (49 lines × 5) · ×1
  • Duplicated block (49 lines × 5) data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataDetachMapper.java:1 — data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataDetachMapper.java:1-49 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataMergeStatefulMapper.java:1-49 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataPersistMapper.java:1-49 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataRefreshMapper.java:1-49 | data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataRemoveMapper.java:1-49 — before extracting anything, compare `data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataDetachMapper.java` and `data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataMergeStatefulMapper.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `data-processor/src/main/java/io/micronaut/data/processor/mappers/jakarta/data/JakartaDataDetachMapper.java:1` 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosBinder.java:89 — data-azure-cosmos/src/main/java/io/micronaut/data/cosmos/operations/CosmosBinder.java:89-96 | data-jdbc/src/main/java/io/micronaut/data/jdbc/operations/DefaultJdbcRepositoryOperations.java:1475-1482 | data-mongodb/src/main/java/io/micronaut/data/mongodb/operations/DefaultMongoStoredQuery.java:428-435 | data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:1300-1307 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:104 — data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java:104-114 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java:102-112 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameCallableResultReader.java:122-132 | data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java:155-165 — before extracting anything, compare `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexCallableResultReader.java` and `data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnIndexResultSetReader.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:51 — data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:51-60 | data-tx/src/main/kotlin/io/micronaut/transaction/kotlin/DefaultCoroutineTransactionOperations.kt:53-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `data-connection/src/main/kotlin/io/micronaut/data/connection/kotlin/DefaultCoroutineConnectionOperations.kt:51` 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.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×1
  • Edited copy of a member (1 corresponding lines) doc-examples/hibernate-example-python/src/main/python/example/StudentRepository.py:13 — doc-examples/hibernate-example-python/src/main/python/example/StudentRepository.py:13-13 | doc-examples/mongo-example-python/src/main/python/example/StudentRepository.py:15-15 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (90 lines × 2) · ×1
  • Duplicated block (90 lines × 2) doc-examples/azure-cosmos-example-java/src/main/java/example/PersonRepository.java:1 — doc-examples/azure-cosmos-example-java/src/main/java/example/PersonRepository.java:1-90 | doc-examples/mongo-example-records-java/src/main/java/example/PersonRepository.java:1-92 — before extracting anything, compare `doc-examples/azure-cosmos-example-java/src/main/java/example/PersonRepository.java` and `doc-examples/mongo-example-records-java/src/main/java/example/PersonRepository.java` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/azure-cosmos-example-java/src/main/java/example/PersonRepository.java:1` 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20 — doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20-47 | doc-examples/jdbc-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20-47 — before extracting anything, compare `doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookController.java` and `doc-examples/jdbc-multitenancy-discriminator-example-java/src/main/java/example/BookController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22 lines × 7) · ×1
  • Duplicated block (22 lines × 7) doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookDto.java:13 — doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/jdbc-multitenancy-datasource-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/jdbc-multitenancy-discriminator-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/jdbc-multitenancy-schema-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/r2dbc-multitenancy-datasource-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/r2dbc-multitenancy-discriminator-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/r2dbc-multitenancy-schema-example-java/src/main/java/example/BookDto.java:13-34 — before extracting anything, compare `doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookDto.java` and `doc-examples/jdbc-multitenancy-datasource-example-java/src/main/java/example/BookDto.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) doc-examples/hibernate-spring-tx-example-java/src/main/java/example/BookManager.java:1 — doc-examples/hibernate-spring-tx-example-java/src/main/java/example/BookManager.java:1-43 | doc-examples/jdbc-spring-tx-example-java/src/main/java/example/BookManager.java:1-43 — before extracting anything, compare `doc-examples/hibernate-spring-tx-example-java/src/main/java/example/BookManager.java` and `doc-examples/jdbc-spring-tx-example-java/src/main/java/example/BookManager.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/hibernate-spring-tx-example-java/src/main/java/example/BookManager.java:1` 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) doc-examples/jdbc-and-r2dbc-example-java/src/main/java/example/AbstractJdbcBookRepository.java:19 — doc-examples/jdbc-and-r2dbc-example-java/src/main/java/example/AbstractJdbcBookRepository.java:19-31 | doc-examples/jdbc-example-java/src/main/java/example/AbstractBookRepository.java:21-33 | doc-examples/jdbc-jakarta-data-example-java/src/main/java/example/AbstractBookRepository.java:18-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note first that the copies are not typed on the same thing: `Transactional` names `io.micronaut.transaction.annotation.Transactional` in one and `jakarta.transaction.Transactional` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (78 lines × 2) · ×1
  • Duplicated block (78 lines × 2) doc-examples/jdbc-example-java/src/main/java/example/metamodel/Client.java:1 — doc-examples/jdbc-example-java/src/main/java/example/metamodel/Client.java:1-78 | doc-examples/jdbc-jakarta-data-example-java/src/main/java/example/metamodel/Client.java:1-78 — before extracting anything, compare `doc-examples/jdbc-example-java/src/main/java/example/metamodel/Client.java` and `doc-examples/jdbc-jakarta-data-example-java/src/main/java/example/metamodel/Client.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/jdbc-example-java/src/main/java/example/metamodel/Client.java:1` 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.
D4 · Code Duplication · Duplicated block (23 lines × 4) · ×1
  • Duplicated block (23 lines × 4) doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20 — doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20-47 | doc-examples/jdbc-multitenancy-datasource-example-java/src/main/java/example/BookController.java:20-42 | doc-examples/jdbc-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20-47 | doc-examples/jdbc-multitenancy-schema-example-java/src/main/java/example/BookController.java:20-42 — before extracting anything, compare `doc-examples/hibernate-multitenancy-discriminator-example-java/src/main/java/example/BookController.java` and `doc-examples/jdbc-multitenancy-datasource-example-java/src/main/java/example/BookController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) doc-examples/mongo-example-java/src/main/java/example/ProductManager.java:22 — doc-examples/mongo-example-java/src/main/java/example/ProductManager.java:22-47 | doc-examples/mongo-example-records-java/src/main/java/example/ProductManager.java:22-47 — before extracting anything, compare `doc-examples/mongo-example-java/src/main/java/example/ProductManager.java` and `doc-examples/mongo-example-records-java/src/main/java/example/ProductManager.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `doc-examples/mongo-example-java/src/main/java/example/ProductManager.java:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) doc-examples/mongo-multitenancy-database-example-java/src/main/java/example/BookDto.java:13 — doc-examples/mongo-multitenancy-database-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/mongo-multitenancy-datasource-example-java/src/main/java/example/BookDto.java:13-34 | doc-examples/mongo-multitenancy-discriminator-example-java/src/main/java/example/BookDto.java:13-34 — before extracting anything, compare `doc-examples/mongo-multitenancy-database-example-java/src/main/java/example/BookDto.java` and `doc-examples/mongo-multitenancy-datasource-example-java/src/main/java/example/BookDto.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) doc-examples/r2dbc-multitenancy-datasource-example-java/src/main/java/example/BookController.java:18 — doc-examples/r2dbc-multitenancy-datasource-example-java/src/main/java/example/BookController.java:18-40 | doc-examples/r2dbc-multitenancy-discriminator-example-java/src/main/java/example/BookController.java:20-47 | doc-examples/r2dbc-multitenancy-schema-example-java/src/main/java/example/BookController.java:18-40 — before extracting anything, compare `doc-examples/r2dbc-multitenancy-datasource-example-java/src/main/java/example/BookController.java` and `doc-examples/r2dbc-multitenancy-discriminator-example-java/src/main/java/example/BookController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookManager.kt:14 — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookManager.kt:14-23 | doc-examples/hibernate-example-kotlin/src/main/kotlin/example/BookManager.kt:14-23 | doc-examples/hibernate-reactive-example-kotlin/src/main/kotlin/example/BookManager.kt:14-23 — before extracting anything, compare `doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookManager.kt` and `doc-examples/hibernate-example-kotlin/src/main/kotlin/example/BookManager.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (122 lines × 5) · ×1
  • Duplicated block (122 lines × 5) doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt:18 — doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt:18-139 | doc-examples/hibernate-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:18-139 | doc-examples/jdbc-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:18-161 | doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt:20-171 | doc-examples/mongo-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:20-176 — before extracting anything, compare `doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt` and `doc-examples/hibernate-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) doc-examples/jdbc-multitenancy-datasource-example-kotlin/src/main/kotlin/example/BookController.kt:17 — doc-examples/jdbc-multitenancy-datasource-example-kotlin/src/main/kotlin/example/BookController.kt:17-30 | doc-examples/jdbc-multitenancy-discriminator-example-kotlin/src/main/kotlin/example/BookController.kt:17-34 | doc-examples/jdbc-multitenancy-schema-example-kotlin/src/main/kotlin/example/BookController.kt:17-30 — before extracting anything, compare `doc-examples/jdbc-multitenancy-datasource-example-kotlin/src/main/kotlin/example/BookController.kt` and `doc-examples/jdbc-multitenancy-discriminator-example-kotlin/src/main/kotlin/example/BookController.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (152 lines × 2) · ×1
  • Duplicated block (152 lines × 2) doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt:20 — doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt:20-171 | doc-examples/mongo-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt:20-176 — before extracting anything, compare `doc-examples/mongo-example-kotlin-ksp/src/main/kotlin/example/PersonSuspendRepositoryService.kt` and `doc-examples/mongo-example-kotlin/src/main/kotlin/example/PersonSuspendRepositoryService.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (53 lines × 3) · ×1
  • Duplicated block (53 lines × 3) doc-examples/azure-cosmos-example-python/src/main/python/example/PersonRepository.py:20 — doc-examples/azure-cosmos-example-python/src/main/python/example/PersonRepository.py:20-72 | doc-examples/jdbc-example-python/src/main/python/example/PersonRepository.py:21-77 | doc-examples/mongo-example-python/src/main/python/example/PersonRepository.py:22-83 — before extracting anything, compare `doc-examples/azure-cosmos-example-python/src/main/python/example/PersonRepository.py` and `doc-examples/jdbc-example-python/src/main/python/example/PersonRepository.py` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — returns a placeholder under a TODO marker data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:532 — `getJoinedFields` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
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.
Minor — 128 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:166 — `!Character.isLetterOrDigit(c) && c != '_'` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:105 — `!TypeUtils.doesReturnVoid(methodElement) && !TypeUtils.doesMethodProducesANumber(methodElement) && !producesAnEntity` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.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 data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java:64 — `!argument.isVoid() && argument.getType() != Void.class` appears character-identically in 2 files — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractCountOrEntityPublisherInterceptor.java, data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/AbstractPublisherInterceptor.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 data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java:120 — `!hasId && (cascadeType == Relation.Cascade.PERSIST || cascadeType == Relation.Cascade.UPDATE) && (association != null && SqlQueryBuilder.isF…` appears character-identically in 2 files — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java, data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/SyncCascadeOperations.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 data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultAbstractFindPageInterceptor.java:54 — `!page.hasTotalSize() && preparedQuery.getPageable().requestTotal()` appears character-identically in 3 files — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/DefaultAbstractFindPageInterceptor.java, data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/DefaultFindCursoredPageAsyncInterceptor.java, data-runtime/src/main/java/io/micronaut/data/runtime/intercept/reactive/DefaultFindCursoredPageReactiveInterceptor.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java:121 — `!rootEntity.hasIdentity() && !rootEntity.hasCompositeIdentity()` appears character-identically in 3 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/DeleteMethodMatcher.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.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 data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java:100 — `(cascadeType == Relation.Cascade.PERSIST) && shouldPersistChildOnPersist(childPersistentEntity, child)` appears character-identically in 2 files — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java, data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/SyncCascadeOperations.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 data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/ShipmentId.java:77 — `Objects.equals(country, tableId.country) && Objects.equals(city, tableId.city)` appears character-identically in 2 files — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/ShipmentId.java, data-tck/src/main/java/io/micronaut/data/tck/entities/ShipmentId.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 data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Shipment.java:78 — `Objects.equals(shipmentId, table.shipmentId) && Objects.equals(field, table.field)` appears character-identically in 2 files — data-document-tck/src/main/java/io/micronaut/data/document/tck/entities/Shipment.java, data-tck/src/main/java/io/micronaut/data/tck/entities/Shipment.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 data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java:335 — `StringUtils.isEmpty(conflictProperty) || StringUtils.isEmpty(conflictProperty.trim())` appears character-identically in 2 files — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlUpsertQueryBuilder.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java:132 — `TypeUtils.isIterableOfEntity(p.getGenericType()) || TypeUtils.isEntity(p.getGenericType())` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/SaveMethodMatcher.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/UpsertMethodMatcher.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 data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:637 — `annotationMetadata.hasAnnotation(JsonAnyGetter.class) || annotationMetadata.hasAnnotation(JsonAnySetter.class)` appears character-identically in 2 files — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java, data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.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 data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java:1028 — `assocEntity != null && assocEntity.getIdentityProperties().contains(property)` appears character-identically in 2 files — data-model/src/main/java/io/micronaut/data/model/query/builder/sql/AbstractSqlLikeQueryBuilder.java, data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilderUtils.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 data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java:268 — `association != null && SqlQueryBuilder.isForeignKeyWithJoinTable(association)` appears character-identically in 3 files — data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/AbstractCascadeOperations.java, data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/ReactiveCascadeOperations.java, data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/SyncCascadeOperations.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 data-model/src/main/java/io/micronaut/data/model/naming/NamingStrategy.java:162 — `association.getKind() != Relation.Kind.EMBEDDED && foreignAssociation == null` appears character-identically in 2 files — data-model/src/main/java/io/micronaut/data/model/naming/NamingStrategy.java, data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlSchemaUtils.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 data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java:394 — `association.getKind() == Relation.Kind.MANY_TO_MANY || association.isForeignKey() && !inverseSide.isPresent()` appears character-identically in 2 files — data-document-model/src/main/java/io/micronaut/data/document/model/query/builder/MongoQueryBuilder.java, data-mongodb/src/main/java/io/micronaut/data/mongodb/init/AbstractMongoCollectionsCreator.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:133 — `c == '"' && (i + 1 >= query.length() || query.charAt(i + 1) != '"')` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:135 — `c == '"' && i + 1 < query.length() && query.charAt(i + 1) == '"'` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:125 — `c == '\'' && (i + 1 >= query.length() || query.charAt(i + 1) != '\'')` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.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 data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java:127 — `c == '\'' && i + 1 < query.length() && query.charAt(i + 1) == '\''` appears character-identically in 2 files — data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/OracleRawQueryReturningSupport.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/RawQueryMethodMatcher.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 data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java:235 — `codec != null && CodecUtils.shouldUseCodec(codec)` appears character-identically in 2 files — data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataDecoderContext.java, data-mongodb/src/main/java/io/micronaut/data/mongodb/serde/DataEncoderContext.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 data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java:164 — `configuration.getSchemaGenerateNames() != null && !configuration.getSchemaGenerateNames().isEmpty()` appears character-identically in 2 files — data-jdbc/src/main/java/io/micronaut/data/jdbc/config/SchemaGenerator.java, data-r2dbc/src/main/java/io/micronaut/data/r2dbc/config/R2dbcSchemaGenerator.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 data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor2.java:68 — `context.isSuspend() && !returnType.getType().getName().equals("kotlinx.coroutines.flow.Flow")` appears character-identically in 2 files — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractAsyncInterceptor2.java, data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.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 data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java:169 — `converters == null || converters.isEmpty()` appears character-identically in 2 files — data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java, data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.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 data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractConvertCompletionStageInterceptor.java:58 — `csValueArgument.isVoid() || csValueArgument.getType() == Void.class || csValueArgument.isVoid()` appears character-identically in 2 files — data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractConvertCompletionStageInterceptor.java, data-runtime/src/main/java/io/micronaut/data/runtime/intercept/async/AbstractCountConvertCompletionStageInterceptor.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.
  • + 15 more in this group — see findings.md.
AX6 · Interface segregation · Fat interface · ×31
  • Fat interface: PersonRepository (46 abstract methods) data-document-tck/src/main/java/io/micronaut/data/document/tck/repositories/PersonRepository.java:35 — `PersonRepository` declares 46 abstract methods: `count`, `countByAgeGreaterThan`, `countByAgeLessThan`, `deleteByNameRegex`, `findAgeByName`, `findAllByNameRegex`, `findAllByNameRegex`, `findByDateOfBirthGreaterThan`, `findByDateOfBirthGreaterThanEquals`, `findByDateOfBirthLessThan`, `findByDateOfBirthLessThanEquals`, `findByIdIn`, `findByIdNotIn`, `findByName`, `findByNameContains`, `findByNameContainsIgnoreCase`, `findByNameEndsWith`, `findByNameEndsWithIgnoreCase`, `findByNameEqualIgnoreCase`, `findByNameIn`, `findByNameLike`, `findByNameNotEqualIgnoreCase`, `findByNameRegex`, `findByNameRegex`, `findByNameRegexOrderByAge`, `findByNameRegexOrderByAgeDesc`, `findByNameStartsWith`, `findByNameStartsWithIgnoreCase`, `findMaxAgeByNameRegex`, `findMaxDateOfBirthByNameRegex`, `findMinAgeByNameRegex`, `findMinDateOfBirthByNameRegex`, `get`, `getAvgAgeByNameRegex`, `getByNameRegex`, `getSumAgeByNameRegex`, `list`, `listTop10`, `queryByNameRegex`, `readAgeByNameRegex`, and 6 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 46 declarations carry 44 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 44 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PersistentEntityCriteriaBuilder (27 abstract methods) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/PersistentEntityCriteriaBuilder.java:33 — `PersistentEntityCriteriaBuilder` declares 27 abstract methods: `and`, `arrayContains`, `containsString`, `containsStringIgnoreCase`, `createCriteriaDelete`, `createCriteriaInsert`, `createCriteriaUpdate`, `createQuery`, `createQuery`, `createTupleQuery`, `endingWithString`, `endingWithStringIgnoreCase`, `equalStringIgnoreCase`, `equalStringIgnoreCase`, `geoIntersects`, `geoWithin`, `ilike`, `isEmptyString`, `isNotEmptyString`, `near`, `notEqualStringIgnoreCase`, `notEqualStringIgnoreCase`, `or`, `regex`, `sort`, `startsWithString`, `startsWithStringIgnoreCase`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 27 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PersistentEntityCriteriaQuery<T> (17 abstract methods) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/PersistentEntityCriteriaQuery.java:38 — `PersistentEntityCriteriaQuery<T>` declares 17 abstract methods under just 10 distinct name(s): `distinct`, `from`, `from`, `from`, `groupBy`, `groupBy`, `having`, `having`, `limit`, `multiselect`, `multiselect`, `offset`, `orderBy`, `orderBy`, `select`, `where`, `where`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 10 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: PersistentEntityFrom<OwnerType, AssociatedEntityType> (20 abstract methods) data-model/src/main/java/io/micronaut/data/model/jpa/criteria/PersistentEntityFrom.java:39 — `PersistentEntityFrom<OwnerType, AssociatedEntityType>` declares 20 abstract methods under just 5 distinct name(s): `getPersistentJoins`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `join`, `joinCollection`, `joinCollection`, `joinList`, `joinList`, `joinSet`, `joinSet`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 5 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: AdvancedPredicateVisitor<P> (19 abstract methods) data-model/src/main/java/io/micronaut/data/model/query/impl/AdvancedPredicateVisitor.java:40 — `AdvancedPredicateVisitor<P>` declares 19 abstract methods: `getRequiredProperty`, `visitContains`, `visitEndsWith`, `visitEquals`, `visitGreaterThan`, `visitGreaterThanOrEquals`, `visitIdEquals`, `visitIn`, `visitInBetween`, `visitIsEmpty`, `visitIsFalse`, `visitIsNotEmpty`, `visitIsNotNull`, `visitIsNull`, `visitIsTrue`, `visitLessThan`, `visitLessThanOrEquals`, `visitNotEquals`, `visitStartsWith`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PersistentEntity (16 abstract methods) data-model/src/main/java/io/micronaut/data/model/PersistentEntity.java:46 — `PersistentEntity` declares 16 abstract methods: `findNamingStrategy`, `getAliasName`, `getCompositeIdentity`, `getIdentity`, `getName`, `getNamingStrategy`, `getParentEntity`, `getPersistentProperties`, `getPersistentPropertyNames`, `getPropertyByName`, `getPropertyByNameIgnoreCase`, `getVersion`, `hasCompositeIdentity`, `hasIdentity`, `hasVersion`, `isOwningEntity`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AsyncRepositoryOperations (16 abstract methods) data-model/src/main/java/io/micronaut/data/operations/async/AsyncRepositoryOperations.java:42 — `AsyncRepositoryOperations` declares 16 abstract methods under just 13 distinct name(s): `count`, `delete`, `deleteAll`, `executeUpdate`, `exists`, `findAll`, `findAll`, `findOne`, `findOne`, `findOptional`, `findOptional`, `findPage`, `getExecutor`, `persist`, `persistAll`, `update`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: ReactiveRepositoryOperations (16 abstract methods) data-model/src/main/java/io/micronaut/data/operations/reactive/ReactiveRepositoryOperations.java:40 — `ReactiveRepositoryOperations` declares 16 abstract methods under just 13 distinct name(s): `count`, `delete`, `deleteAll`, `executeUpdate`, `exists`, `findAll`, `findAll`, `findOne`, `findOne`, `findOptional`, `findOptional`, `findPage`, `persist`, `persistAll`, `update`, `updateAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: ReactorReactiveRepositoryOperations (17 abstract methods) data-model/src/main/java/io/micronaut/data/operations/reactive/ReactorReactiveRepositoryOperations.java:37 — `ReactorReactiveRepositoryOperations` declares 17 abstract methods under just 14 distinct name(s): `count`, `delete`, `deleteAll`, `executeDelete`, `executeUpdate`, `exists`, `findAll`, `findAll`, `findOne`, `findOne`, `findOptional`, `findOptional`, `findPage`, `persist`, `persistAll`, `update`, `updateAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: JpaSpecificationExecutor<T> (19 abstract methods) data-model/src/main/java/io/micronaut/data/repository/jpa/JpaSpecificationExecutor.java:50 — `JpaSpecificationExecutor<T>` declares 19 abstract methods under just 6 distinct name(s): `count`, `count`, `deleteAll`, `deleteAll`, `deleteAll`, `exists`, `exists`, `findAll`, `findAll`, `findAll`, `findAll`, `findAll`, `findAll`, `findAll`, `findOne`, `findOne`, `findOne`, `updateAll`, `updateAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 6 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: AuthorRepository (36 abstract methods) data-tck/src/main/java/io/micronaut/data/tck/repositories/AuthorRepository.java:43 — `AuthorRepository` declares 36 abstract methods: `countByNameContains`, `findAll`, `findAll`, `findAllByName`, `findAllByNameCustom`, `findAllByNickName`, `findByBooksTitle`, `findByBooksTotalPages`, `findById`, `findByIdIsNotNull`, `findByName`, `findByNameContains`, `findByNameContainsIgnoreCase`, `findByNameEndsWith`, `findByNameEndsWithIgnoreCase`, `findByNameIgnoreCase`, `findByNameIsNotNull`, `findByNameStartsWith`, `findByNameStartsWithIgnoreCase`, `findOne`, `findOne`, `listAll`, `queryAll`, `queryByIdIsNotNull`, `queryByName`, `queryByNameContains`, `read`, `readAll`, `readByIdIsNotNull`, `readByNameIsNotNull`, `retrieveByIdIsNotNull`, `retrieveByName`, `searchAll`, `searchByName`, `searchByNameIsNotNull`, `updateNickname`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 36 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PersonAsyncRepository (25 abstract methods) data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonAsyncRepository.java:34 — `PersonAsyncRepository` declares 25 abstract methods: `add1`, `add1Aliased`, `count`, `deleteByNameLike`, `deleteCustom`, `deleteCustomSingle`, `deleteCustomSingleNoEntity`, `erase`, `erase`, `findByName`, `findByNameLike`, `findByNameLike`, `findPeople`, `getById`, `getByName`, `getMaxId`, `list`, `queryByName`, `remove`, `save`, `saveCustom`, `saveCustomSingle`, `updateNamesCustom`, `updatePeople`, `updatePerson`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 25 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PersonReactiveRepository (25 abstract methods) data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonReactiveRepository.java:35 — `PersonReactiveRepository` declares 25 abstract methods: `count`, `deleteByNameLike`, `deleteCustom`, `deleteCustomSingle`, `deleteCustomSingleExpression`, `deleteCustomSingleNoEntity`, `findByName`, `findByNameLike`, `findByNameLike`, `findNameByNameLike`, `findPeople`, `getById`, `getByName`, `getMaxId`, `list`, `queryByAgeGreaterThan`, `queryByName`, `save`, `saveCustom`, `saveCustomSingle`, `saveCustomSingleExpression`, `searchByNameLike`, `updateNamesCustom`, `updatePeople`, `updatePerson`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PersonRepository (57 abstract methods) data-tck/src/main/java/io/micronaut/data/tck/repositories/PersonRepository.java:53 — `PersonRepository` declares 57 abstract methods: `count`, `countByAgeGreaterThan`, `countByAgeLessThan`, `deleteByNameLike`, `deleteCustom`, `deleteCustomSingle`, `deleteCustomSingleExpression`, `deleteCustomSingleNoEntity`, `find`, `findAgeByName`, `findAll`, `findAllByAgeInRange`, `findAllByName`, `findAllByNameLike`, `findByName`, `findByNameLike`, `findByNameLike`, `findByNameLikeOrderByAge`, `findByNameLikeOrderByAgeDesc`, `findDistinct`, `findDistinctName`, `findMaxAgeByNameLike`, `findMinAgeByNameLike`, `findOptionalByName`, `findPeople`, `get`, `getAvgAgeByNameLike`, `getByName`, `getSumAgeByNameLike`, `getTotal`, `list`, `listTop10`, `queryByNameLike`, `queryNames`, `readAgeByNameLike`, `retrieve`, `save`, `saveCustom`, `saveCustom`, `saveCustomSingle`, and 17 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 57 declarations carry 53 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 53 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: TrainRepository (60 abstract methods) data-tck/src/main/java/io/micronaut/data/tck/repositories/TrainRepository.java:58 — `TrainRepository` declares 60 abstract methods: `deleteAll`, `findByCapacityAtLeast`, `findByCapacityBetween`, `findByCapacityGreaterThan`, `findByCapacityGreaterThanConstrain`, `findByCapacityGreaterThanEquals`, `findByModelIn`, `findByModelInConstrain`, `findByModelIsNotNull`, `findByModelIsNull`, `findByModelNot`, `findByModelNotLike`, `findByModelNotLikeConstrain`, `findByName`, `findByNameEqualsConstrain`, `findByNameEqualsConstrain`, `findByNameEqualsConstrainAndElectricConstraint`, `findByNameEqualsConstrainWithRestriction`, `findByNameLike`, `findByNameLikeConstrain`, `findByNameNotEqualsConstrain`, `findByNameNotIn`, `findByNameNotInConstrain`, `findBySpeedAtMost`, `findBySpeedLessThan`, `findBySpeedLessThanConstrain`, `findBySpeedLessThanEquals`, `findBySpeedNotBetween`, `findFirst2TrainNamesOrderedByName`, `findFirst2TrainNamesOrderedByName`, `findFirst2Trains`, `findFirst3Trains`, `findFirst3TrainsOrderedByCapacity`, `findFirst3TrainsOrderedByCapacity`, `findFirst4TrainsOrderedByName`, `findFirst4TrainsOrderedByName`, `findFirstTrain`, `findFirstTrainOrderedBySpeed`, `findFirstTrainOrderedBySpeed`, `findTrain`, and 20 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 60 declarations carry 50 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 50 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Catalog (25 abstract methods) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/Catalog.java:26 — `Catalog` declares 25 abstract methods: `add`, `addMultiple`, `allSortedByNameAsc`, `allSortedByNameAscIgnoreCase`, `allSortedByNameDesc`, `allSortedByNameDescIgnoreCase`, `countByPriceGreaterThanEqual`, `customSave`, `deleteById`, `deleteByProductNumLike`, `findAll`, `findByNameLengthAndPriceBelow`, `findByNameLengthAndPriceBelowNameAsc`, `findByNameLengthAndPriceBelowNameDesc`, `findByNameLike`, `findByPriceNotNullAndPriceLessThanEqual`, `findByPriceNull`, `findByProductNumBetween`, `findByProductNumLike`, `get`, `modify`, `modifyMultiple`, `remove`, `removeMultiple`, `withTaxBetween`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AsciiCharacters (23 abstract methods) test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/read/only/AsciiCharacters.java:29 — `AsciiCharacters` declares 23 abstract methods: `all`, `alphabetic`, `countByHexadecimalNotNull`, `existsByThisCharacter`, `find`, `find`, `findAll`, `findByHexadecimalContainsAndIsControlNot`, `findByHexadecimalIgnoreCase`, `findByHexadecimalIgnoreCaseBetweenAndHexadecimalNotIn`, `findByIdBetween`, `findByIsControlTrueAndNumericValueBetween`, `findByNumericValue`, `findByNumericValueBetween`, `findByNumericValueLessThanEqualAndNumericValueGreaterThanEqual`, `findFirst3ByNumericValueGreaterThanEqualAndHexadecimalEndsWith`, `findFirstByHexadecimalStartsWithAndIsControlOrderByIdAsc`, `getABCDFO`, `hex`, `jklOr`, `reverseAlphabetic`, `saveAll`, `twentyFour`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 22 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 22 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: BookRepository (23 abstract methods) benchmarks/benchmark-micronaut-data-jpa/src/main/java/example/BookRepository.java:24 — `BookRepository` declares 23 abstract methods: `delete`, `deleteAll`, `deleteByTitleLike`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findNativeBooks`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `list`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `persist`, `retrieveByTitle`, `update`, `updateByTitle`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AsyncBookRepository (28 abstract methods) doc-examples/coherence-example-java/src/main/java/io/micronaut/coherence/data/repositories/AsyncBookRepository.java:34 — `AsyncBookRepository` declares 28 abstract methods: `countDistinctTitleByPagesGreaterThan`, `countTitleByPagesGreaterThan`, `deleteByTitleStartingWith`, `existsByAuthor`, `findAvgPagesByAuthor`, `findByAuthor`, `findByAuthorIsNotNull`, `findByAuthorIsNull`, `findByPagesGreaterThan`, `findByPagesGreaterThanEquals`, `findByPagesLessThan`, `findByPagesLessThanEquals`, `findByPublicationYearAfter`, `findByPublicationYearBefore`, `findByPublicationYearBetween`, `findByTitleContains`, `findByTitleEndingWith`, `findByTitleIn`, `findByTitleLike`, `findByTitleStartingWith`, `findDistinctTitleByPagesGreaterThan`, `findMaxPagesByAuthor`, `findMinPagesByAuthor`, `findSumPagesByAuthor`, `insert`, `insertBooks`, `update`, `updateByTitleStartingWith`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: BookRepository (28 abstract methods) doc-examples/coherence-example-java/src/main/java/io/micronaut/coherence/data/repositories/BookRepository.java:33 — `BookRepository` declares 28 abstract methods: `countDistinctTitleByPagesGreaterThan`, `countTitleByPagesGreaterThan`, `deleteByTitleStartingWith`, `existsByAuthor`, `findAvgPagesByAuthor`, `findByAuthor`, `findByAuthorIsNotNull`, `findByAuthorIsNull`, `findByPagesGreaterThan`, `findByPagesGreaterThanEquals`, `findByPagesLessThan`, `findByPagesLessThanEquals`, `findByPublicationYearAfter`, `findByPublicationYearBefore`, `findByPublicationYearBetween`, `findByTitleContains`, `findByTitleEndingWith`, `findByTitleIn`, `findByTitleLike`, `findByTitleStartingWith`, `findDistinctTitleByPagesGreaterThan`, `findMaxPagesByAuthor`, `findMinPagesByAuthor`, `findSumPagesByAuthor`, `insert`, `insertBooks`, `update`, `updateByTitleStartingWith`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: BookRepository (33 abstract methods) doc-examples/hibernate-example-java/src/main/java/example/BookRepository.java:21 — `BookRepository` declares 33 abstract methods: `delete`, `deleteAll`, `deleteByTitleLike`, `deleteMany`, `deleteOne`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findNativeBooks`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `insertCustomExp`, `insertMany`, `insertOne`, `list`, `listAll`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `retrieveByTitle`, `save`, `update`, `update`, `updateByTitle`, `updateMany`, `updateOne`, `updatePages`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 33 declarations carry 31 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 31 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: BookRepository (30 abstract methods) doc-examples/jdbc-example-java/src/main/java/example/BookRepository.java:18 — `BookRepository` declares 30 abstract methods: `calculateSum`, `delete`, `deleteAll`, `deleteByTitleLike`, `find`, `find`, `findBooks`, `findByPagesBetween`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findByTitleStartingWith`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `insertCustomExp`, `list`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `persist`, `retrieveByTitle`, `searchBooksByTitle`, `update`, `update`, `updateByTitle`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 30 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: BookRepository (24 abstract methods) doc-examples/jdbc-example-records-java/src/main/java/example/BookRepository.java:15 — `BookRepository` declares 24 abstract methods: `delete`, `deleteAll`, `deleteByTitleLike`, `find`, `findBooks`, `findByPagesGreaterThan`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitle`, `findByTitleLike`, `findOne`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `getByTitle`, `list`, `listBooks`, `listOrderByTitle`, `listOrderByTitleDesc`, `persist`, `persist`, `retrieveByTitle`, `update`, `update`, `updateByTitle`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 24 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: FamilyRepository (21 abstract methods) doc-examples/azure-cosmos-example-kotlin/src/main/kotlin/example/FamilyRepository.kt:20 — `FamilyRepository` declares 21 abstract methods: `findById`, `updateRegistered`, `updateAddress`, `updateLastName`, `queryById`, `deleteByLastName`, `deleteById`, `deleteByRegistered`, `existsByIdAndRegistered`, `countByRegistered`, `lastOrderedLastName`, `lastOrderedRegisteredDate`, `findByAddressStateAndAddressCityOrderByAddressCity`, `updateByAddressCounty`, `findByChildrenPetsType`, `findChildrenByChildrenPetsGivenName`, `findByIdIn`, `findByIdNotIn`, `findByLastNameLike`, `findByTagsArrayContains`, `childrenArrayContainsGender`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: BookRepository (30 abstract methods) doc-examples/hibernate-example-kotlin-ksp/src/main/kotlin/example/BookRepository.kt:12 — `BookRepository` declares 30 abstract methods: `findByTitle`, `getByTitle`, `retrieveByTitle`, `find`, `findByPagesGreaterThan`, `findByPagesGreaterThanOrTitleLike`, `findByTitleLike`, `list`, `findTitleByPagesGreaterThan`, `findTop3ByTitleLike`, `listOrderByTitle`, `listOrderByTitleDesc`, `listBooks`, `save`, `insert`, `insertOne`, `insertMany`, `persist`, `update`, `updateByTitle`, `updatePages`, `updateOne`, `updateMany`, `deleteAll`, `deleteOne`, `deleteMany`, `delete`, `deleteByTitleLike`, `findOne`, `findNativeBooks`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • + 6 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Disabled test · ×20
  • Disabled test doc-examples/coherence-example-java/src/test/java/io/micronaut/coherence/data/GeneratedAsyncStatementsTest.java:41 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test doc-examples/mongo-jackson-example-java/src/test/java/example/Tests.java:128 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/AbstractManualSchemaTest.java:121 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteArraysTest.java:6 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteJSONTest.java:263 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteJakartaDataTest.java:27 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteJakartaDataTest.java:33 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteManualSchemaTest.java:45 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SqliteSchemaValidationTest.java:17 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SqliteSchemaValidationTest.java:34 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/assignedid/AssignedUuidManyToManyPersistTest.java:32 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/composite/CompositeTest.java:59 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/entity/EntityTests.java:142 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/entity/EntityTests.java:244 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/entity/EntityTests.java:1588 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/PersistenceEntityTests.java:73 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/PersistenceEntityTests.java:215 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/PersistenceEntityTests.java:290 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/jakarta_data/persistence/PersistenceEntityTests.java:310 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/one2many/OneToManyHierarchicalTest.java:41 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
X4 · Structured logging · Interpolated log message defeats structured logging · ×8
  • Interpolated log message defeats structured logging data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:393 — `warn` at line 393 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:412 — `warn` at line 412 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:421 — `warn` at line 421 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-tx/src/main/java/io/micronaut/transaction/support/AbstractReactorTransactionOperations.java:435 — `warn` at line 435 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:421 — `debug` at line 421 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-r2dbc/src/main/java/io/micronaut/data/r2dbc/operations/DefaultR2dbcRepositoryOperations.java:428 — `debug` at line 428 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:499 — `error` at line 499 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging data-model/src/main/java/io/micronaut/data/model/query/builder/sql/SqlQueryBuilder.java:559 — `error` at line 559 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
D34 · Knowledge Freshness · Orphaned file · ×6
  • Orphaned file data-model/src/main/kotlin/io/micronaut/data/repository/jpa/kotlin/KotlinJpaSpecificationExecutor.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 data-model/src/main/java/io/micronaut/data/model/CursoredPage.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 data-model/src/main/java/io/micronaut/data/model/DefaultCursoredPageable.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 data-model/src/main/kotlin/io/micronaut/data/repository/kotlin/KotlinCrudRepository.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 data-model/src/main/java/io/micronaut/data/model/CursoredPageable.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 data-model/src/main/java/io/micronaut/data/model/DefaultCursoredPage.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.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×5
  • Projects may be oversized for their cohesion data-model/build.gradle:1 — `data-model` (44138 LoC, 495 module-visible types across 47 directories) overshoots its size bounds. 5 of 26 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 6.4/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion data-runtime/build.gradle:1 — `data-runtime` (31187 LoC, 255 module-visible types across 33 directories) overshoots its size bounds. 5 of 26 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 6.4/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion data-processor/build.gradle:1 — `data-processor` (20121 LoC, 210 module-visible types across 15 directories) overshoots its size bounds. 5 of 26 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 6.4/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion data-tck/build.gradle:1 — `data-tck` (14475 LoC, 300 module-visible types across 10 directories) overshoots its size bounds. 5 of 26 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 6.4/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion data-tx/build.gradle:1 — `data-tx` (7486 LoC, 73 module-visible types across 13 directories) overshoots its size bounds. 5 of 26 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 6.4/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 6 significant file(s) lose their only recent owner: data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/JakartaDataQueryMethodMatcher.java, data-jdbc/src/main/java/io/micronaut/data/jdbc/mapper/ColumnNameResultSetReader.java, data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/DefaultPersistentPropertyPath.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/MethodMatchContext.java, data-runtime/src/main/java/io/micronaut/data/runtime/intercept/criteria/async/AbstractAsyncSpecificationInterceptor.java, data-runtime/src/main/java/io/micronaut/data/runtime/mapper/AbstractDelegatingResultReader.java. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: data-tx-jdbc/src/main/java/io/micronaut/transaction/jdbc/oracle/OracleSessionlessTransactionHandler.java, data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryWktConverter.java, data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java, data-model/src/main/java/io/micronaut/data/annotation/Srid.java, data-model/src/main/java/io/micronaut/data/model/geo/Point.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 (20 single-owned of 670 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; 670 of the 2648 production source files in this repository met that bar). They are anonymized user #3 (4 file(s)), anonymized user #4 (3 file(s)), anonymized user #5 (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: data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/AbstractVectorAttributeConverter.java, data-runtime/src/main/java/io/micronaut/data/runtime/operations/internal/sql/VectorParameterBinder.java, data-runtime/src/main/java/io/micronaut/data/model/runtime/convert/vector/impl/OracleVectorSqlIndexDefinitionProvider.java, data-model/src/main/java/io/micronaut/data/model/runtime/convert/SqlIndexDefinitionProvider.java, data-processor/src/main/java/io/micronaut/data/processor/visitors/finders/ReservationMethodMatcher.java, data-runtime/src/main/java/io/micronaut/data/runtime/event/listeners/AutoPopulateUtil.java, data-r2dbc/src/main/java/io/micronaut/data/r2dbc/mapper/R2dbcLobReader.java, data-model/src/main/java/io/micronaut/data/model/AbstractPersistentEntity.java.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found buildSrc/build.gradle:21 — 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 `buildSrc/build.gradle` makes this repository a deployable product (line 21).
D21 · Naming Consistency · `AuthorDTO` spells `DTO` where 19 names in the project spell it `Dto` · ×1
  • `AuthorDTO` spells `DTO` where 19 names in the project spell it `Dto` data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorDTO.java:21 — 19 of 21 names in project data-tck spell the token `Dto` (19 of 21; unit: names in project data-tck containing `Dto`). Peers: io.micronaut.data.tck.entities.ArraysDto (data-tck/src/main/java/io/micronaut/data/tck/entities/ArraysDto.java:25); io.micronaut.data.tck.entities.AuthorBooksDto (data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorBooksDto.java:23); io.micronaut.data.tck.entities.AuthorDtoWithBookDtos (data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorDtoWithBookDtos.java:24); io.micronaut.data.tck.entities.AuthorDtoWithBooks (data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorDtoWithBooks.java:24); io.micronaut.data.tck.entities.BookDto (data-tck/src/main/java/io/micronaut/data/tck/entities/BookDto.java:23). Rename to `AuthorDto`. [rule N6]
D21 · Naming Consistency · `SaleDTO` spells `DTO` where 19 names in the project spell it `Dto` · ×1
  • `SaleDTO` spells `DTO` where 19 names in the project spell it `Dto` data-tck/src/main/java/io/micronaut/data/tck/entities/SaleDTO.java:25 — 19 of 21 names in project data-tck spell the token `Dto` (19 of 21; unit: names in project data-tck containing `Dto`). Peers: io.micronaut.data.tck.entities.ArraysDto (data-tck/src/main/java/io/micronaut/data/tck/entities/ArraysDto.java:25); io.micronaut.data.tck.entities.AuthorBooksDto (data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorBooksDto.java:23); io.micronaut.data.tck.entities.AuthorDtoWithBookDtos (data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorDtoWithBookDtos.java:24); io.micronaut.data.tck.entities.AuthorDtoWithBooks (data-tck/src/main/java/io/micronaut/data/tck/entities/AuthorDtoWithBooks.java:24); io.micronaut.data.tck.entities.BookDto (data-tck/src/main/java/io/micronaut/data/tck/entities/BookDto.java:23). Rename to `SaleDto`. [rule N6]
D21 · Naming Consistency · `testReadDTO` spells `DTO` where 13 names in the project spell it `Dto` · ×1
  • `testReadDTO` spells `DTO` where 13 names in the project spell it `Dto` test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteAuthorRepository.java:44 — 13 of 14 names in project test-suite-data-jdbc-sqlite spell the token `Dto` (13 of 14; unit: names in project test-suite-data-jdbc-sqlite containing `Dto`). Peers: AbstractManualSchemaTest.testManualInsertAndDtoRetrieval (test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/AbstractManualSchemaTest.java:122); io.micronaut.data.jdbc.sqlite.SQLiteBookDtoRepository (test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteBookDtoRepository.java:25); io.micronaut.data.jdbc.sqlite.AccountRecordDto (test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteDiscriminatorMultitenancyRecordTest.java:215); io.micronaut.data.jdbc.sqlite.SQLiteDtoTest (test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteDtoTest.java:30); io.micronaut.data.jdbc.sqlite.ThingDto (test-suite-data-jdbc-sqlite/src/test/java/io/micronaut/data/jdbc/sqlite/SQLiteDtoTest.java:147). Rename to `testReadDto`. [rule N6]
D21 · Naming Consistency · `addressID` spells `ID` where 24 names in the project spell it `Id` · ×1
  • `addressID` spells `ID` where 24 names in the project spell it `Id` doc-examples/jdbc-example-kotlin/src/main/kotlin/example/AddressSubView.kt:17 — 24 of 26 names in project jdbc-example-kotlin spell the token `Id` (24 of 26; unit: names in project jdbc-example-kotlin containing `Id`). Peers: AccountBalanceRepository.findByIdForUpdate (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/AccountBalanceRepository.kt:13); BookRepository.calculateSum(bookId) (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/BookRepository.kt:125); CartRepository.findById (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/CartRepository.kt:11); FooRepository.findById (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/FooRepository.kt:15); ParentRepository.findById (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/ParentRepository.kt:12). Rename to `addressId`. [rule N6]
D21 · Naming Consistency · `teachID` spells `ID` where 24 names in the project spell it `Id` · ×1
  • `teachID` spells `ID` where 24 names in the project spell it `Id` doc-examples/jdbc-example-kotlin/src/main/kotlin/example/TeacherSubView.kt:14 — 24 of 26 names in project jdbc-example-kotlin spell the token `Id` (24 of 26; unit: names in project jdbc-example-kotlin containing `Id`). Peers: AccountBalanceRepository.findByIdForUpdate (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/AccountBalanceRepository.kt:13); BookRepository.calculateSum(bookId) (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/BookRepository.kt:125); CartRepository.findById (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/CartRepository.kt:11); FooRepository.findById (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/FooRepository.kt:15); ParentRepository.findById (doc-examples/jdbc-example-kotlin/src/main/kotlin/example/ParentRepository.kt:12). Rename to `teachId`. [rule N6]
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 6 of 675 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 675 of the 2648 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: data-model/src/main/kotlin/io/micronaut/data/repository/jpa/kotlin/KotlinJpaSpecificationExecutor.kt, data-model/src/main/java/io/micronaut/data/model/CursoredPage.java, data-model/src/main/java/io/micronaut/data/model/DefaultCursoredPageable.java, data-model/src/main/kotlin/io/micronaut/data/repository/kotlin/KotlinCrudRepository.kt, data-model/src/main/java/io/micronaut/data/model/CursoredPageable.java, data-model/src/main/java/io/micronaut/data/model/DefaultCursoredPage.java. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 24/56 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `doc-examples/azure-cosmos-example-java`, `doc-examples/azure-cosmos-example-kotlin`, `doc-examples/hibernate-multitenancy-discriminator-example-java`, `doc-examples/hibernate-reactive-example-java`, `doc-examples/hibernate-reactive-example-kotlin` and 27 more.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:13 — 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 10 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.
PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1
  • Benchmarks don't track allocations benchmarks/benchmark-spring-data-mongodb/src/jmh/java/example/SimpleQuery.java — A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 49/207 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Minor — 1 finding(s)
D10 · Test Quality · Skipped (documented) · ×1
  • Skipped (documented): testObjectIdDeser doc-examples/mongo-jackson-example-java/src/test/java/example/Tests.java:130 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-c8d8da3fadc7483386c61a51970d621e/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-c8d8da3fadc7483386c61a51970d621e/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3008" --report-format json --report-path /tmp/watchdog-gitleaks-c8d8da3fadc7483386c61a51970d621e/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c8d8da3fadc7483386c61a51970d621e/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .4artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (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—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `data-model/src/main/java/io/micronaut/data/model/jpa/criteria/impl/CriteriaUtils.java`, `data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryJsonConverter.java`, `data-model/src/main/java/io/micronaut/data/model/runtime/convert/GeometryWktConverter.java`, `data-model/src/main/java/io/micronaut/data/model/vector/BinaryVector.java`, `data-model/src/main/java/io/micronaut/data/model/vector/ByteVector.java`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (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 01a1e635-668d-7fe7-aed5-0ee32a25b7a0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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