Public report of airbnb/viaduct, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 15:10 UTC · Survey ID cd_4db9758c97c442cf8d46dd0ce1970339
airbnb/viaduct
Measured 16 November 2026, 15:09 UTC, at code version 5e5caaf
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 138,320 lines of product code in 92 projects, tests not counted · Estimated rebuild effort: about 3.1 person-years · Weakest lens: Production Readiness, 43.1
Findings by how serious they are
191 critical488 serious127 minor
10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 15:09 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 ▸
65of 65 dimensions measured by tools.
739of 806 findings point to an exact file and line, so you can open each one in the code. The other 67 concern the repository as a whole, such as missing documentation.
65dimensions across 7 lenses, read from 138,320 lines of product code in 92 projects.
airbnb/viaduct falls short of our standard for production because four passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 51.2 out of 100 and is rated Adequate, and 181 of its 191 critical findings are security problems.
Production Readiness, at 43.1, is the weakest lens and counts most in the score. The best first step is replacing the four exposed passwords or keys and switching the old ones off, worth about 7.3 points. Replacing the two packages under a banned licence comes next, worth about 5.2 points. Raising Production Readiness to 70 would lift the score to about 57.4.
101 passwords or keys in the code's history and four in the code are open to anyone who can read the repository. Sixty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eleven secrets can leak from the build pipeline. Replacing each exposed password or key, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command. The two controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 138,320 lines, about €450,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 43.1 to 70, the lowest score rated Strong, the score would rise from 51.2 to about 57.4.
Code composition: what the lines of code are
Product code 29%Tests 71%
Rebuild cost: about €450,000 · Estimate
Cost to rebuild
€150,000 to €760,000, for 2,517 to 7,986 hours of work, about 3.1 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 138,320 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4).
Raises the score by about 7.3 points · Low effort · REDACTED Scanning
2
Resolve the 2 Banned license finding(s) in License Compliance.
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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 €450,000 to build again, about 3.1 person-years of work. Its weakest lens is Production Readiness, at 43.1 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 7.3 points for low effort, because it clears the 4 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 442,830 lines over the last 90 days, which is about 1,795,922 lines a year. At that pace, the extra work comes to an estimated 89.8 to 598.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
746 modules, with 1438 dependencies between them. 25 loops run through 112 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 706 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.
engine.api.EngineObjectData uses engine.api, so a change to engine.api can break engine.api.EngineObjectData, while a change to engine.api.EngineObjectData can't break engine.api.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→21 engine.api.instrumentation.resolver uses engine.apipart of a loop✕
Connections
1 pair of types, where a type in engine.api.instrumentation.resolver uses a type in engine.api.
engine.api.instrumentation.resolver uses engine.api, so a change to engine.api can break engine.api.instrumentation.resolver, while a change to engine.api.instrumentation.resolver can't break engine.api.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
graphql.schema.ViaductSchema uses utils.collections, so a change to utils.collections can break graphql.schema.ViaductSchema, while a change to graphql.schema.ViaductSchema can't break utils.collections.
Position
Below the diagonal: graphql.schema.ViaductSchema uses a module listed above it, which is the healthy direction.
10→16 graphql.schema.ViaductSchema uses graphql.schemapart of a loop✕
Connections
3 pairs of types, where a type in graphql.schema.ViaductSchema uses a type in graphql.schema.
graphql.schema.ViaductSchema uses graphql.schema, so a change to graphql.schema can break graphql.schema.ViaductSchema, while a change to graphql.schema.ViaductSchema can't break graphql.schema.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
graphql.utils uses utils.collections, so a change to utils.collections can break graphql.utils, while a change to graphql.utils can't break utils.collections.
Position
Below the diagonal: graphql.utils uses a module listed above it, which is the healthy direction.
engine.api.spi.FieldResolverExecutor uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.api.spi.FieldResolverExecutor, while a change to engine.api.spi.FieldResolverExecutor can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.api.spi.FieldResolverExecutor uses a module listed above it, which is the healthy direction.
14→21 engine.api.spi.FieldResolverExecutor uses engine.apipart of a loop✕
Connections
1 pair of types, where a type in engine.api.spi.FieldResolverExecutor uses a type in engine.api.
engine.api.spi.FieldResolverExecutor uses engine.api, so a change to engine.api can break engine.api.spi.FieldResolverExecutor, while a change to engine.api.spi.FieldResolverExecutor can't break engine.api.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
engine.runtime2.model.Arguments uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.model.Arguments, while a change to engine.runtime2.model.Arguments can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.model.Arguments uses a module listed above it, which is the healthy direction.
15→31 engine.runtime2.model.Arguments uses engine.runtime2.modelpart of a loop✕
Connections
7 pairs of types, where a type in engine.runtime2.model.Arguments uses a type in engine.runtime2.model.
engine.runtime2.model.Arguments uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.model.Arguments, while a change to engine.runtime2.model.Arguments can't break engine.runtime2.model.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
graphql.schema uses utils.collections, so a change to utils.collections can break graphql.schema, while a change to graphql.schema can't break utils.collections.
Position
Below the diagonal: graphql.schema uses a module listed above it, which is the healthy direction.
47 pairs of types, where a type in graphql.schema uses a type in graphql.schema.ViaductSchema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
graphql.schema uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break graphql.schema, while a change to graphql.schema can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: graphql.schema uses a module listed above it, which is the healthy direction.
engine.api.spi uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.api.spi, while a change to engine.api.spi can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.api.spi uses a module listed above it, which is the healthy direction.
engine.api.spi uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.api.spi, while a change to engine.api.spi can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.api.spi uses a module listed above it, which is the healthy direction.
engine.api.spi uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break engine.api.spi, while a change to engine.api.spi can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: engine.api.spi uses a module listed above it, which is the healthy direction.
17→21 engine.api.spi uses engine.apipart of a loop✕
Connections
17 pairs of types, where a type in engine.api.spi uses a type in engine.api.
graphql.schema.binary uses utils.collections, so a change to utils.collections can break graphql.schema.binary, while a change to graphql.schema.binary can't break utils.collections.
Position
Below the diagonal: graphql.schema.binary uses a module listed above it, which is the healthy direction.
37 pairs of types, where a type in graphql.schema.binary uses a type in graphql.schema.ViaductSchema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
graphql.schema.binary uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break graphql.schema.binary, while a change to graphql.schema.binary can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: graphql.schema.binary uses a module listed above it, which is the healthy direction.
graphql.schema.binary uses graphql.schema, so a change to graphql.schema can break graphql.schema.binary, while a change to graphql.schema.binary can't break graphql.schema.
Position
Below the diagonal: graphql.schema.binary uses a module listed above it, which is the healthy direction.
tenant.codegen.bytecode.config uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break tenant.codegen.bytecode.config, while a change to tenant.codegen.bytecode.config can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: tenant.codegen.bytecode.config uses a module listed above it, which is the healthy direction.
tenant.codegen.bytecode.config uses graphql.schema, so a change to graphql.schema can break tenant.codegen.bytecode.config, while a change to tenant.codegen.bytecode.config can't break graphql.schema.
Position
Below the diagonal: tenant.codegen.bytecode.config uses a module listed above it, which is the healthy direction.
engine.runtime uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime, while a change to engine.runtime can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime uses a module listed above it, which is the healthy direction.
engine.runtime uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.runtime, while a change to engine.runtime can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.runtime uses a module listed above it, which is the healthy direction.
engine.runtime uses service.api.spi, so a change to service.api.spi can break engine.runtime, while a change to engine.runtime can't break service.api.spi.
Position
Below the diagonal: engine.runtime uses a module listed above it, which is the healthy direction.
engine.runtime uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break engine.runtime, while a change to engine.runtime can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: engine.runtime uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in engine.runtime uses a type in engine.api.spi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime uses engine.api.spi, so a change to engine.api.spi can break engine.runtime, while a change to engine.runtime can't break engine.api.spi.
Position
Below the diagonal: engine.runtime uses a module listed above it, which is the healthy direction.
20→21 engine.runtime uses engine.apipart of a loop✕
Connections
95 pairs of types, where a type in engine.runtime uses a type in engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.api uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.api, while a change to engine.api can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.api uses a module listed above it, which is the healthy direction.
api.internal uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break api.internal, while a change to api.internal can't break engine.api.EngineObjectData.
Position
Below the diagonal: api.internal uses a module listed above it, which is the healthy direction.
125 pairs of types, where a type in arbitrary.graphql uses a type in arbitrary.common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
arbitrary.graphql uses arbitrary.common, so a change to arbitrary.common can break arbitrary.graphql, while a change to arbitrary.graphql can't break arbitrary.common.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses service.api, so a change to service.api can break arbitrary.graphql, while a change to arbitrary.graphql can't break service.api.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break arbitrary.graphql, while a change to arbitrary.graphql can't break engine.api.EngineObjectData.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break arbitrary.graphql, while a change to arbitrary.graphql can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break arbitrary.graphql, while a change to arbitrary.graphql can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses graphql.utils, so a change to graphql.utils can break arbitrary.graphql, while a change to arbitrary.graphql can't break graphql.utils.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses service.api.spi, so a change to service.api.spi can break arbitrary.graphql, while a change to arbitrary.graphql can't break service.api.spi.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break arbitrary.graphql, while a change to arbitrary.graphql can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses graphql.schema, so a change to graphql.schema can break arbitrary.graphql, while a change to arbitrary.graphql can't break graphql.schema.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
arbitrary.graphql uses engine.api.spi, so a change to engine.api.spi can break arbitrary.graphql, while a change to arbitrary.graphql can't break engine.api.spi.
Position
Below the diagonal: arbitrary.graphql uses a module listed above it, which is the healthy direction.
53 pairs of types, where a type in arbitrary.graphql uses a type in engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime.execution.QueryPlan uses engine.runtime, so a change to engine.runtime can break engine.runtime.execution.QueryPlan, while a change to engine.runtime.execution.QueryPlan can't break engine.runtime.
Position
Below the diagonal: engine.runtime.execution.QueryPlan uses a module listed above it, which is the healthy direction.
engine.runtime.execution.QueryPlan uses engine.api, so a change to engine.api can break engine.runtime.execution.QueryPlan, while a change to engine.runtime.execution.QueryPlan can't break engine.api.
Position
Below the diagonal: engine.runtime.execution.QueryPlan uses a module listed above it, which is the healthy direction.
24→30 engine.runtime.execution.QueryPlan uses engine.runtime.executionpart of a loop✕
Connections
4 pairs of types, where a type in engine.runtime.execution.QueryPlan uses a type in engine.runtime.execution.
engine.runtime.execution.QueryPlan uses engine.runtime.execution, so a change to engine.runtime.execution can break engine.runtime.execution.QueryPlan, while a change to engine.runtime.execution.QueryPlan can't break engine.runtime.execution.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
engine.runtime.mat uses engine.api, so a change to engine.api can break engine.runtime.mat, while a change to engine.runtime.mat can't break engine.api.
Position
Below the diagonal: engine.runtime.mat uses a module listed above it, which is the healthy direction.
engine.runtime.tenantloading uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.runtime.tenantloading, while a change to engine.runtime.tenantloading can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.runtime.tenantloading uses a module listed above it, which is the healthy direction.
engine.runtime.tenantloading uses graphql.utils, so a change to graphql.utils can break engine.runtime.tenantloading, while a change to engine.runtime.tenantloading can't break graphql.utils.
Position
Below the diagonal: engine.runtime.tenantloading uses a module listed above it, which is the healthy direction.
engine.runtime.tenantloading uses service.api.spi, so a change to service.api.spi can break engine.runtime.tenantloading, while a change to engine.runtime.tenantloading can't break service.api.spi.
Position
Below the diagonal: engine.runtime.tenantloading uses a module listed above it, which is the healthy direction.
engine.runtime.tenantloading uses engine.api.spi, so a change to engine.api.spi can break engine.runtime.tenantloading, while a change to engine.runtime.tenantloading can't break engine.api.spi.
Position
Below the diagonal: engine.runtime.tenantloading uses a module listed above it, which is the healthy direction.
engine.runtime.tenantloading uses engine.runtime, so a change to engine.runtime can break engine.runtime.tenantloading, while a change to engine.runtime.tenantloading can't break engine.runtime.
Position
Below the diagonal: engine.runtime.tenantloading uses a module listed above it, which is the healthy direction.
engine.runtime.tenantloading uses engine.api, so a change to engine.api can break engine.runtime.tenantloading, while a change to engine.runtime.tenantloading can't break engine.api.
Position
Below the diagonal: engine.runtime.tenantloading uses a module listed above it, which is the healthy direction.
engine.runtime2.model.ObjectEngineResult uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.model.ObjectEngineResult, while a change to engine.runtime2.model.ObjectEngineResult can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.model.ObjectEngineResult uses a module listed above it, which is the healthy direction.
engine.runtime2.model.ObjectEngineResult uses engine.runtime2.model.Arguments, so a change to engine.runtime2.model.Arguments can break engine.runtime2.model.ObjectEngineResult, while a change to engine.runtime2.model.ObjectEngineResult can't break engine.runtime2.model.Arguments.
Position
Below the diagonal: engine.runtime2.model.ObjectEngineResult uses a module listed above it, which is the healthy direction.
engine.runtime2.model.ObjectEngineResult uses engine.api, so a change to engine.api can break engine.runtime2.model.ObjectEngineResult, while a change to engine.runtime2.model.ObjectEngineResult can't break engine.api.
Position
Below the diagonal: engine.runtime2.model.ObjectEngineResult uses a module listed above it, which is the healthy direction.
27→31 engine.runtime2.model.ObjectEngineResult uses engine.runtime2.modelpart of a loop✕
Connections
5 pairs of types, where a type in engine.runtime2.model.ObjectEngineResult uses a type in engine.runtime2.model.
engine.runtime2.model.ObjectEngineResult uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.model.ObjectEngineResult, while a change to engine.runtime2.model.ObjectEngineResult can't break engine.runtime2.model.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
java.runtime.bridge uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break java.runtime.bridge, while a change to java.runtime.bridge can't break engine.api.EngineObjectData.
Position
Below the diagonal: java.runtime.bridge uses a module listed above it, which is the healthy direction.
java.runtime.bridge uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break java.runtime.bridge, while a change to java.runtime.bridge can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: java.runtime.bridge uses a module listed above it, which is the healthy direction.
java.runtime.bridge uses service.api.spi, so a change to service.api.spi can break java.runtime.bridge, while a change to java.runtime.bridge can't break service.api.spi.
Position
Below the diagonal: java.runtime.bridge uses a module listed above it, which is the healthy direction.
java.runtime.bridge uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break java.runtime.bridge, while a change to java.runtime.bridge can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: java.runtime.bridge uses a module listed above it, which is the healthy direction.
java.runtime.bridge uses engine.api.spi, so a change to engine.api.spi can break java.runtime.bridge, while a change to java.runtime.bridge can't break engine.api.spi.
Position
Below the diagonal: java.runtime.bridge uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in java.runtime.bridge uses a type in engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
java.runtime.bridge uses engine.api, so a change to engine.api can break java.runtime.bridge, while a change to java.runtime.bridge can't break engine.api.
Position
Below the diagonal: java.runtime.bridge uses a module listed above it, which is the healthy direction.
remote uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break remote, while a change to remote can't break engine.api.EngineObjectData.
Position
Below the diagonal: remote uses a module listed above it, which is the healthy direction.
remote uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break remote, while a change to remote can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: remote uses a module listed above it, which is the healthy direction.
remote uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break remote, while a change to remote can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: remote uses a module listed above it, which is the healthy direction.
engine.runtime.execution uses arbitrary.common, so a change to arbitrary.common can break engine.runtime.execution, while a change to engine.runtime.execution can't break arbitrary.common.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
engine.runtime.execution uses utils.collections, so a change to utils.collections can break engine.runtime.execution, while a change to engine.runtime.execution can't break utils.collections.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
engine.runtime.execution uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.runtime.execution, while a change to engine.runtime.execution can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
engine.runtime.execution uses graphql.utils, so a change to graphql.utils can break engine.runtime.execution, while a change to engine.runtime.execution can't break graphql.utils.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
engine.runtime.execution uses service.api.spi, so a change to service.api.spi can break engine.runtime.execution, while a change to engine.runtime.execution can't break service.api.spi.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
engine.runtime.execution uses engine.api.spi, so a change to engine.api.spi can break engine.runtime.execution, while a change to engine.runtime.execution can't break engine.api.spi.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in engine.runtime.execution uses a type in engine.runtime. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime.execution uses engine.runtime, so a change to engine.runtime can break engine.runtime.execution, while a change to engine.runtime.execution can't break engine.runtime.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
65 pairs of types, where a type in engine.runtime.execution uses a type in engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime.execution uses engine.api, so a change to engine.api can break engine.runtime.execution, while a change to engine.runtime.execution can't break engine.api.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
35 pairs of types, where a type in engine.runtime.execution uses a type in engine.runtime.execution.QueryPlan. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime.execution uses engine.runtime.execution.QueryPlan, so a change to engine.runtime.execution.QueryPlan can break engine.runtime.execution, while a change to engine.runtime.execution can't break engine.runtime.execution.QueryPlan.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in engine.runtime.execution uses a type in engine.runtime.mat. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime.execution uses engine.runtime.mat, so a change to engine.runtime.mat can break engine.runtime.execution, while a change to engine.runtime.execution can't break engine.runtime.mat.
Position
Below the diagonal: engine.runtime.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.model uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2.model, while a change to engine.runtime2.model can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2.model uses a module listed above it, which is the healthy direction.
80 pairs of types, where a type in engine.runtime2.model uses a type in graphql.schema.ViaductSchema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.model uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.model, while a change to engine.runtime2.model can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.model uses a module listed above it, which is the healthy direction.
engine.runtime2.model uses engine.runtime2.model.Arguments, so a change to engine.runtime2.model.Arguments can break engine.runtime2.model, while a change to engine.runtime2.model can't break engine.runtime2.model.Arguments.
Position
Below the diagonal: engine.runtime2.model uses a module listed above it, which is the healthy direction.
engine.runtime2.model uses graphql.schema, so a change to graphql.schema can break engine.runtime2.model, while a change to engine.runtime2.model can't break graphql.schema.
Position
Below the diagonal: engine.runtime2.model uses a module listed above it, which is the healthy direction.
engine.runtime2.model uses engine.api, so a change to engine.api can break engine.runtime2.model, while a change to engine.runtime2.model can't break engine.api.
Position
Below the diagonal: engine.runtime2.model uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in engine.runtime2.model uses a type in engine.runtime2.model.ObjectEngineResult. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.model uses engine.runtime2.model.ObjectEngineResult, so a change to engine.runtime2.model.ObjectEngineResult can break engine.runtime2.model, while a change to engine.runtime2.model can't break engine.runtime2.model.ObjectEngineResult.
Position
Below the diagonal: engine.runtime2.model uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses api.context, so a change to api.context can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break api.context.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break engine.api.EngineObjectData.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses service.api.spi, so a change to service.api.spi can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break service.api.spi.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses engine.api.spi, so a change to engine.api.spi can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break engine.api.spi.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses engine.api, so a change to engine.api can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break engine.api.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
tenant.runtime.execution uses api.internal, so a change to api.internal can break tenant.runtime.execution, while a change to tenant.runtime.execution can't break api.internal.
Position
Below the diagonal: tenant.runtime.execution uses a module listed above it, which is the healthy direction.
engine uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine, while a change to engine can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine uses a module listed above it, which is the healthy direction.
engine uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine, while a change to engine can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine uses a module listed above it, which is the healthy direction.
engine uses engine.runtime.execution.QueryPlan, so a change to engine.runtime.execution.QueryPlan can break engine, while a change to engine can't break engine.runtime.execution.QueryPlan.
Position
Below the diagonal: engine uses a module listed above it, which is the healthy direction.
engine uses engine.runtime.execution, so a change to engine.runtime.execution can break engine, while a change to engine can't break engine.runtime.execution.
Position
Below the diagonal: engine uses a module listed above it, which is the healthy direction.
engine.runtime2.model.registry uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in engine.runtime2.model.registry uses a type in graphql.schema.ViaductSchema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.model.registry uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
engine.runtime2.model.registry uses engine.runtime2.model.Arguments, so a change to engine.runtime2.model.Arguments can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break engine.runtime2.model.Arguments.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
engine.runtime2.model.registry uses graphql.schema, so a change to graphql.schema can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break graphql.schema.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
engine.runtime2.model.registry uses engine.api, so a change to engine.api can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break engine.api.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
engine.runtime2.model.registry uses engine.runtime2.model.ObjectEngineResult, so a change to engine.runtime2.model.ObjectEngineResult can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break engine.runtime2.model.ObjectEngineResult.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
49 pairs of types, where a type in engine.runtime2.model.registry uses a type in engine.runtime2.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.model.registry uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.model.registry, while a change to engine.runtime2.model.registry can't break engine.runtime2.model.
Position
Below the diagonal: engine.runtime2.model.registry uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses graphql.schema, so a change to graphql.schema can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break graphql.schema.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses engine.api.spi, so a change to engine.api.spi can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.api.spi.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses engine.runtime, so a change to engine.runtime can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.runtime.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in engine.runtime2.execution uses a type in engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.execution uses engine.api, so a change to engine.api can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.api.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.runtime2.model.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.execution uses engine.runtime2.model.registry, so a change to engine.runtime2.model.registry can break engine.runtime2.execution, while a change to engine.runtime2.execution can't break engine.runtime2.model.registry.
Position
Below the diagonal: engine.runtime2.execution uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution.framework uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution.framework uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution.framework uses engine.runtime2.model.Arguments, so a change to engine.runtime2.model.Arguments can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break engine.runtime2.model.Arguments.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution.framework uses engine.api, so a change to engine.api can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break engine.api.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution.framework uses engine.runtime2.model.ObjectEngineResult, so a change to engine.runtime2.model.ObjectEngineResult can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break engine.runtime2.model.ObjectEngineResult.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
54 pairs of types, where a type in engine.runtime2.resolution.framework uses a type in engine.runtime2.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.resolution.framework uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break engine.runtime2.model.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution.framework uses engine.runtime2.model.registry, so a change to engine.runtime2.model.registry can break engine.runtime2.resolution.framework, while a change to engine.runtime2.resolution.framework can't break engine.runtime2.model.registry.
Position
Below the diagonal: engine.runtime2.resolution.framework uses a module listed above it, which is the healthy direction.
service.runtime uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break service.runtime, while a change to service.runtime can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: service.runtime uses a module listed above it, which is the healthy direction.
service.runtime uses service.api.spi, so a change to service.api.spi can break service.runtime, while a change to service.runtime can't break service.api.spi.
Position
Below the diagonal: service.runtime uses a module listed above it, which is the healthy direction.
service.runtime uses engine.api.spi, so a change to engine.api.spi can break service.runtime, while a change to service.runtime can't break engine.api.spi.
Position
Below the diagonal: service.runtime uses a module listed above it, which is the healthy direction.
service.runtime uses engine.runtime, so a change to engine.runtime can break service.runtime, while a change to service.runtime can't break engine.runtime.
Position
Below the diagonal: service.runtime uses a module listed above it, which is the healthy direction.
service.runtime uses engine.runtime.tenantloading, so a change to engine.runtime.tenantloading can break service.runtime, while a change to service.runtime can't break engine.runtime.tenantloading.
Position
Below the diagonal: service.runtime uses a module listed above it, which is the healthy direction.
service.runtime uses engine.runtime.execution, so a change to engine.runtime.execution can break service.runtime, while a change to service.runtime can't break engine.runtime.execution.
Position
Below the diagonal: service.runtime uses a module listed above it, which is the healthy direction.
engine.runtime2 uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2, while a change to engine.runtime2 can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2 uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.runtime2, while a change to engine.runtime2 can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2 uses service.api.spi, so a change to service.api.spi can break engine.runtime2, while a change to engine.runtime2 can't break service.api.spi.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2 uses engine.api.spi, so a change to engine.api.spi can break engine.runtime2, while a change to engine.runtime2 can't break engine.api.spi.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2 uses engine.runtime, so a change to engine.runtime can break engine.runtime2, while a change to engine.runtime2 can't break engine.runtime.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2 uses engine.runtime2.model.registry, so a change to engine.runtime2.model.registry can break engine.runtime2, while a change to engine.runtime2 can't break engine.runtime2.model.registry.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2 uses engine.runtime2.execution, so a change to engine.runtime2.execution can break engine.runtime2, while a change to engine.runtime2 can't break engine.runtime2.execution.
Position
Below the diagonal: engine.runtime2 uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution uses engine.runtime2.model.Arguments, so a change to engine.runtime2.model.Arguments can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.runtime2.model.Arguments.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution uses graphql.schema, so a change to graphql.schema can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break graphql.schema.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution uses engine.api, so a change to engine.api can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.api.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
engine.runtime2.resolution uses engine.runtime2.model.ObjectEngineResult, so a change to engine.runtime2.model.ObjectEngineResult can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.runtime2.model.ObjectEngineResult.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
99 pairs of types, where a type in engine.runtime2.resolution uses a type in engine.runtime2.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.resolution uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.runtime2.model.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
59 pairs of types, where a type in engine.runtime2.resolution uses a type in engine.runtime2.model.registry. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.resolution uses engine.runtime2.model.registry, so a change to engine.runtime2.model.registry can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.runtime2.model.registry.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
67 pairs of types, where a type in engine.runtime2.resolution uses a type in engine.runtime2.resolution.framework. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.resolution uses engine.runtime2.resolution.framework, so a change to engine.runtime2.resolution.framework can break engine.runtime2.resolution, while a change to engine.runtime2.resolution can't break engine.runtime2.resolution.framework.
Position
Below the diagonal: engine.runtime2.resolution uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.api.EngineObjectData, so a change to engine.api.EngineObjectData can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.api.EngineObjectData.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.api.instrumentation.resolver, so a change to engine.api.instrumentation.resolver can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.api.instrumentation.resolver.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in engine.runtime2.bootstrap uses a type in graphql.schema.ViaductSchema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.bootstrap uses graphql.schema.ViaductSchema, so a change to graphql.schema.ViaductSchema can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break graphql.schema.ViaductSchema.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.api.spi.FieldResolverExecutor, so a change to engine.api.spi.FieldResolverExecutor can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.api.spi.FieldResolverExecutor.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.runtime2.model.Arguments, so a change to engine.runtime2.model.Arguments can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.runtime2.model.Arguments.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses graphql.schema, so a change to graphql.schema can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break graphql.schema.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.api.spi, so a change to engine.api.spi can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.api.spi.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.runtime, so a change to engine.runtime can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.runtime.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.api, so a change to engine.api can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.api.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.runtime2.model.ObjectEngineResult, so a change to engine.runtime2.model.ObjectEngineResult can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.runtime2.model.ObjectEngineResult.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.runtime2.model, so a change to engine.runtime2.model can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.runtime2.model.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
52 pairs of types, where a type in engine.runtime2.bootstrap uses a type in engine.runtime2.model.registry. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.runtime2.bootstrap uses engine.runtime2.model.registry, so a change to engine.runtime2.model.registry can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.runtime2.model.registry.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
engine.runtime2.bootstrap uses engine.runtime2.resolution, so a change to engine.runtime2.resolution can break engine.runtime2.bootstrap, while a change to engine.runtime2.bootstrap can't break engine.runtime2.resolution.
Position
Below the diagonal: engine.runtime2.bootstrap uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
106
High / Critical
A05:2025 — Injection
77
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
Top priorities: Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4); Resolve the 2 Banned license finding(s) in License Compliance; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4).
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.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Per-file score 0–10 — a quality signature. Of 256 files carrying findings, judged against the Production bar: 2% slop · 46% mixed · 52% near-clean.
File
Score
Band
Worst signal
REDACTED
2.3
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
2.3
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
2.3
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
2.3
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
4.4
Mixed
Secrets (history): REDACTED: REDACTED
REDACTED
4.4
Mixed
Secrets (history): REDACTED: REDACTED
REDACTED
4.4
Mixed
Secrets (history): REDACTED: REDACTED
REDACTED
4.4
Mixed
Secrets (history): REDACTED: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 191
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 — 488
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 — 127
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 65 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 — 65 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 739 of 806 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`jacocoTestReport`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.kt, .java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
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 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt, .java), 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (publications/test-fixtures/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D30 Dependency Vulnerabilities — 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. Osv-scanner exited 1 with no findings — dependency CVEs were not measured. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
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. `core/engine/api/src/main/kotlin/viaduct/engine/api/InputValueReader.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/ParentManagedValue.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/StandardResolutionValue.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/bootstrap/executionregistry/ModuleConfigFactory.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/resolver/ViaductResolverInstrumentation.kt`, … (+83 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.
D43 Malicious Dependencies — 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. Osv-scanner exited 1 with no findings — dependency CVEs were not measured. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
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 Guice and 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.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 9 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
52 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InclusionConditionKt.pruneContradictions at 74. A further 8 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 Builder.mk at 24 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/TypeMapper.java (TypeMapper.mapScalarOrCustomType at 24), core/tenant/api/src/main/kotlin/viaduct/api/internal/EngineValueConv.kt (Builder.mk at 24), core/tenant/api/src/main/kotlin/viaduct/api/internal/JsonConv.kt (Builder.mk at 24), core/shared/mapping/src/main/kotlin/viaduct/mapping/graphql/GJValueConv.kt (Builder.mk at 21), core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt (GraphQLJavaSchemaBuilder.convertDirectiveLocation at 20), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with InclusionConditionKt.pruneContradictions (cyclomatic 74), graph.init (cyclomatic 74). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.3 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.
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.
+ 77 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with InclusionConditionKt.pruneContradictions (cognitive 153). — Refactoring it lifts Cognitive Complexity from 5.6 to about 5.8/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.3 / 10Stronggated by 30 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 FileTooLong finding(s) in God Classes — start with FieldResolver.kt, ExecutorRegistryInputs.kt, QueryPlanFactory.kt. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 6 ClassTooLong finding(s) in God Classes — start with FieldResolver.kt, ObjectBase.java, FailureCollector.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 TooManyMethods finding(s) in God Classes — start with FailureCollector.kt, ObjectBase.java, FieldResolver.kt. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
95 duplicated block group(s) detected. 4.7 % of the production lines (6,452 of 138,320) are in a reported copy. A further 147 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 6 of the 242 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (8 corresponding lines) · ×12core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:52
Edited copy of a member (11 corresponding lines) · ×10core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:222
Edited copy of a member (12 corresponding lines) · ×8core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:38
+ 91 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with analyze-materialization.py, format_coverage_summary.py, IdentityKeys.kt. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 10 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with TypeDefinitionRegistryDecoder.kt, ViaductModuleSupport.kt, SchemaScopeDefinitions.kt. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 10 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ArgumentGrounding.kt, ConstructionDemandClosure.kt, FieldCheckerTask.kt. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 10Stronggated by 1 serious finding✓ 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.
92 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 73 of the 92 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: gradletestapps:validation-rule-support
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ResolverRegistryImpl.kt, ChainedDataLoaderInstrumentation.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 62 artifact(s) resolved, 60 of them gradable against Maven Central, and 45 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
2 of 113 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 108 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. 38 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. 1 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 39 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt (2×74=148); core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt (9×16=144); core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt (7×18=126) Repeated repair below the complexity floor: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt (15 of 25 changes were fixes); core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt (8 of 15 changes were fixes); core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/schema/GJSelectionParser.kt (4 of 5 changes were fixes)
Resolve the 10 Repeated repair finding(s) in Churn × Complexity Hotspots — start with FieldResolver.kt, ExecutionParameters.kt, GJSelectionParser.kt. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with InclusionCondition.kt, EngineObjectDataToKeyTree.kt, CollectFields.kt. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.8 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
78 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/Selection.kt. Counted over 680 of the 1526 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×8
Further sole-owners (lower concentration)
What to do
Resolve the 8 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (8 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
29 deducted task-comment markers across 138320 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 29 TodoComment finding(s) in Explicit Debt — start with AssembleTenantModuleConfigFileTask.kt (2), FieldBatchResolverExecutorImpl.kt (2), ExerciserTests.kt (2). — One of this dimension's main actionable groups (29 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 120 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs founddemoapps/starwars-java/build.gradle.kts:49
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
3 naming inconsistencies among 95 declarations measured against a convention their peers follow.
`resolveRSSVariables` spells `RSS` where 26 names in the project spell it `Rss`core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldExecutionHelpers.kt:630
`globalIDCodec` spells `ID` where 55 names in the project spell it `Id`core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/Engine2.kt:79
`getId` spells `Id` where 18 names in the project spell it `ID`core/javaapi/api/src/main/java/viaduct/java/api/context/NodeExecutionContext.java:19
What to do
Resolve the 1 `resolveRSSVariables` spells `RSS` where 26 names in the project spell… finding(s) in Naming Consistency — start with FieldExecutionHelpers.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `globalIDCodec` spells `ID` where 55 names in the project spell it `Id` finding(s) in Naming Consistency — start with Engine2.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `getId` spells `Id` where 18 names in the project spell it `ID` finding(s) in Naming Consistency — start with NodeExecutionContext.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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
5 of 77 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×5core/engine/runtime2/build.gradle.kts:1
What to do
Resolve the 5 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts (5). — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
101 finding(s): 0 critical, 101 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 101 REDACTED finding(s) in Secrets (history) — start with REDACTED (88), REDACTED (13). — One of this dimension's main actionable groups (101 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
77 finding(s): 0 critical, 76 high, 1 medium, 0 low. 61 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 14 file(s) — `.github/copydemoapps/gradlew` (line 74, line 180), `core/engine/runtime2/run-property-test-campaign.sh`, `core/engine/runtime2/src/testFixtures/kotlin/viaduct/engine/runtime2/arbitrary/ResolutionWitness.kt` (line 57, line 432), `core/service/runtime/src/main/kotlin/viaduct/service/runtime/StandardViaduct.kt` (lines 67–710), `core/x/remoteresolvers/gradlew` (line 74, line 180), … (+9 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 9 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 61 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (63 issue-level, 2 of them charged here).
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).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
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.
8 of 680 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt. Counted over 680 of the 1526 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with ViaductJavaModulePlugin.kt, ValidationErrorCodes.kt, ViaductPluginCommon.kt. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with ViaductApplicationPlugin.kt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 247 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.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels5.9 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:201, core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:228
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. — core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:209
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:237
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — core/service/wiring/src/main/resources/graphiql/index.html:23
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — core/engine/runtime2/impldocs/website/assets/app.js:264
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — core/engine/runtime2/impldocs/website/assets/tree.js:71
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`details.collapsed-section > summary > h2::before` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/engine/runtime2/impldocs/website/deep-dives/demand-closure/assets/dc.css:127
`.alt a i` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/engine/runtime2/impldocs/website/assets/style.css:62
`a.card` moves (`transition: transform .15s, border-color .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — core/engine/runtime2/impldocs/website/assets/style.css:94, core/engine/runtime2/impldocs/animation/assets/style.css:69
`.js .reveal` moves (`transition: opacity .5s ease, transform .5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — core/engine/runtime2/impldocs/website/assets/style.css:101, core/engine/runtime2/impldocs/animation/assets/style.css:76
`.js .htree li` moves (`transition: opacity .4s ease calc(var(--d, 0) * 140ms + 60ms), transform .4s ease calc(var(--d, 0) * 140ms + 60ms)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/engine/runtime2/impldocs/website/assets/style.css:229
`.drill .opt.wrong` moves (`animation: shake .35s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/engine/runtime2/impldocs/website/assets/style.css:355
`.mob-index > summary::before` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/engine/runtime2/impldocs/website/assets/style.css:446
`.dd-list .go` moves (`transition: transform .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/engine/runtime2/impldocs/website/assets/style.css:468
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`CharacterFilmsRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characterFilmRelations; e.g. `characterFilmRelations` in `addCharacterToFilm` at line 42). — demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.kt:11
`CharacterRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characters; e.g. `characters` in `add` at line 140). — demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterRepository.kt:11
`FilmCharactersRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (filmCharacterRelations; e.g. `filmCharacterRelations` in `addCharacterToFilm` at line 17). — demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/films/models/FilmCharactersRepository.kt:6
`CharacterFilmsRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characterFilmRelations; e.g. `characterFilmRelations` in `addCharacterToFilm` at line 24). — demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.java:11
`CharacterRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characters; e.g. `characters` in `add` at line 70). — demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterRepository.java:13
`FilmCharactersRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (filmCharacterRelations; e.g. `filmCharacterRelations` in `addCharacterToFilm` at line 24). — demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/models/FilmCharactersRepository.java:11
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`EngineSelectionSet` declares 17 abstract methods: `selections`, `traversableSelections`, `toSelectionSet`, `addVariables`, `toFragment`, `toNodelikeSelectionSet`, `printAsFieldSet`, `containsField`, `containsSelection`, `resolveSelection`, `requestsType`, `selectionSetForField`, `selectionSetForSelection`, `selectionSetForType`, `isEmpty`, `isTransitivelyEmpty`, `argumentsOfSelection`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/engine/api/src/main/kotlin/viaduct/engine/api/EngineSelectionSet.kt:30
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
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.
core/engine/runtime2/impldocs/evidence/profiles/2026-09-27-f5-field-checks/README.md links to `../../../../src/support/kotlin/viaduct/engine/runtime2/resolvers/resolver23/Resolver.kt`, but `core/engine/runtime2/src/support/kotlin/viaduct/engine/runtime2/resolvers/resolver23/Resolver.kt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — core/engine/runtime2/impldocs/evidence/profiles/2026-09-27-f5-field-checks/README.md:39
What to do
Reconcile the README with reality: core/engine/runtime2/impldocs/evidence/profiles/2026-09-27-f5-field-checks/README.md links to `../../../../src/support/kotlin/viaduct/engine/runtime2/resolvers/resolver23/Resolver.kt`, but `core/engine/runtime2/src/support/kotlin/viaduct/engine/runtime2/resolvers/resolver23/Resolver.kt` does not exist.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.1 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 20/29 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `core/engine/runtime2`, `core/javaapi/codegen`, `core/shared/arbitrary-cli`, `core/tenant/codegen` and 4 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.
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 18 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. — .github/workflows/ci-trigger.yml:7
`core/engine/runtime2/impldocs/graphql-spec/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — core/engine/runtime2/impldocs/graphql-spec/package.json:4
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`provideVariables` is public and takes `arguments: Map<String, Any ?>` from its caller, and it calls itself at line 38 with a piece of `arguments` — the function is not `tailrec`, so every call is a real frame — and nowhere in `provideVariables` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `provideVariables` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/VariablesProviderExecutor.kt:38
`GroundKey.of` is public and takes `arguments: Map<String, Any ?>` from its caller, and it calls itself at line 254 with a piece of `arguments` — the function is not `tailrec`, so every call is a real frame — and nowhere in `GroundKey.of` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `GroundKey.of` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/EngineResult.kt:254
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`loadJSX` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — core/service/wiring/src/main/resources/graphiql/js/jsx-loader.js:6
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 90 is called with an argument built by `schemaFiles.joinToString("…")` (line 90), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/ViaductSchemaValidator.kt:90
What to do
In Kotlin, hand the logger a lambda it calls only when the level is on (`logger.debug { "rows: ${rows.joinToString()}" }` — kotlin-logging and Log4j 2's Kotlin API take one), or put the line behind `if (log.isDebugEnabled)` (`if (BuildConfig.DEBUG)` for a line only a debug build needs). A string template is not the fix on SLF4J or Timber: their message is a `String`, so every `joinToString` or `toJson` inside the `${…}` runs before the call is entered.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterStatsResolver.kt:65
`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. (×6) — core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/RequiredSelectionSetValidator.kt:198, core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:271, core/engine/wiring/src/main/kotlin/viaduct/engine/ViaductWiringFactory.kt:61, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — core/engine/runtime2/impldocs/animation/assets/theme.js:7
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 5 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 — 2 observation(s) recorded · This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt, .java), 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.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 47 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.
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
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~340597 lines of test source are present (.kt, .java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 88 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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 aggregate root(s) (entities that raise its domain events); 362 value object(s); 11 domain event(s); no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript, Python source (service entry point: demoapps/starwars-java/src/main/java/com/example/starwars/service/Application.java:9 (Micronaut.run())
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 12% of this repository's production lines — kotlin (123,047 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
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.
AC2 · Forms & labels· <label> that labels no control · ×2
<label> that labels no control core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:201— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:228— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
D11 · Test Reliability· Test declared unreliable · ×2
Test declared unreliable: EngineTestModule core/engine/runtime/src/test/kotlin/viaduct/engine/runtime/execution/BatchNodeResolverContractTest.kt:17— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Flaky, disabling until fix; see TODO". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: core/engine/runtime/src/test/kotlin/viaduct/engine/runtime/execution/NodeResolverContractTest.kt core/engine/runtime/src/test/kotlin/viaduct/engine/runtime/execution/NodeResolverContractTest.kt:11— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "flaky". 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.)
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.
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.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:209— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:237— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×1
Hover-only interaction on <div> core/engine/runtime2/impldocs/website/assets/app.js:264— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> core/engine/runtime2/impldocs/website/assets/tree.js:71— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
TodoComment gradle-plugins/common/src/main/kotlin/viaduct/gradle/task/AssembleTenantModuleConfigFileTask.kt:96— // TODO: Re-enable task-internal incrementality after execution-style tests cover — 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 gradle-plugins/common/src/main/kotlin/viaduct/gradle/task/AssembleTenantModuleConfigFileTask.kt:190— // TODO: Keep this routing helper for future re-enablement of true task-internal — 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 demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterHomeworldResolver.kt:68— // TODO: Validate homeworld 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 demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/mutations/CreateCharacterMutation.kt:33— // TODO: Validate homeworld and species are valid ids — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/runtime/src/test/kotlin/viaduct/tenant/runtime/execution/idof/KotlinIdOfContractTest.kt:168— // TODO: relax bounds of ref (https://app.asana.com/1/150975571430/task/1211504668132957)
TodoComment core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldBatchResolverExecutorImpl.kt:64— // TODO - get rid of this argument — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldUnbatchedResolverExecutorImpl.kt:67— // TODO - get rid of this argument — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldBatchResolverExecutorImpl.kt:104— // TODO: the pass through here for `ErroneousFieldException` is not our long-term — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/NodeBatchResolverExecutorImpl.kt:79— // TODO: the pass through here for `ErroneousFieldException` is not our long-term — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/codegen/src/test/kotlin/viaduct/tenant/codegen/bytecode/exercise/ExerciserTests.kt:84— // TODO v2 exercise tests — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/codegen/src/test/kotlin/viaduct/tenant/codegen/bytecode/exercise/ExerciserTests.kt:114— // TODO v2 tests — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/ViaductGenerator.kt:84— // TODO(jimmy): Remove this global mutable state, see https://docs.google.com/document/d/18FKs13huMY3JyslnO11_V_WtYPcSA7Xb_vNQAf79yP0/edit?tab=t.0#heading=h.a24h0oe8myl2
TodoComment core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/ViaductGenerator.kt:137— // TODO(https://app.asana.com/1/150975571430/project/1207604899751448/task/1210764159508822?focus=true): Remove this global mutable state, see https://docs.google.com/document/d/18FKs13huMY3JyslnO11_V_WtYPcSA7Xb_vNQAf79yP0/edit?tab=t.0#heading=h.a24h0oe8myl2
TodoComment core/tenant/api/src/test/kotlin/viaduct/api/internal/JsonConvTest.kt:224— // TODO: support BackingData https://app.asana.com/1/150975571430/project/1211295233988904/task/1211525978501301
TodoComment core/tenant/api/src/main/kotlin/viaduct/api/FieldValue.kt:50— // TODO (https://app.asana.com/1/150975571430/task/1210815621831967?focus=true): Think through the following:
TodoComment core/tenant/api/src/main/kotlin/viaduct/api/internal/EngineValueConv.kt:194— // TODO: support BackingData in object mapping — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/shared/viaductschema/src/test/kotlin/viaduct/graphql/schema/graphqljava/FilteredSchemaTest.kt:21— // TODO - Gradle doesn't seem to like this -- strange!! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLExtensions.kt:6— // todo(diwas): remove this class eventually — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/shared/graphql/src/testFixtures/kotlin/viaduct/graphql/test/ExecutionResultAssertions.kt:118— // TODO - Why is this inline? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/shared/graphql/src/test/kotlin/viaduct/graphql/utils/ViaductQueryTraverserTest.kt:280— // TODO: Figure out why this isn't getting set — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/shared/graphql/src/test/kotlin/viaduct/graphql/utils/ViaductQueryTraverserTest.kt:290— // TODO: Figure out why this isn't getting set — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/GraphQLDocuments.kt:541— // TODO: deeply insert variable values into values (ie inside list items, or input fields) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/service/runtime/src/test/kotlin/viaduct/service/runtime/EngineRegistryTest.kt:791— // TODO: Remove these tests when registerSchema() is deleted — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/Runtime2ResolverSelectionProjector.kt:21— // TODO: After integrating engine2 into Treehouse, consolidate this with runtime's pre-existing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/engine/runtime/src/test/kotlin/viaduct/engine/runtime/execution/Conformer.kt:550— // TODO: viaduct does not call the completedValue hook with the correct value — 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.
FileTooLong: execution/FieldResolver.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt— FileTooLong — 1104 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: FieldResolver (100-1705). The bar is 500 significant lines; this is 604 over it, 2.21× 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: bootstrap/ExecutorRegistryInputs.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt— FileTooLong — 890 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 390 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: execution/QueryPlanFactory.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/QueryPlanFactory.kt— FileTooLong — 765 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 265 over it, 1.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: model/EngineResult.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/EngineResult.kt— FileTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 187 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bootstrap/ResolverRegistryImpl.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ResolverRegistryImpl.kt— FileTooLong — 675 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 175 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: utils/DefaultSchemaFactory.kt core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/DefaultSchemaFactory.kt— FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 167 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: resolution/ConstructionDemandClosure.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 78 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: execution/ExecutionParameters.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: ExecutionParameters (158-969). The bar is 500 significant lines; this is 58 over it, 1.12× 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: execution/FieldExecutionHelpers.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldExecutionHelpers.kt— FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 52 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: internal/ObjectBase.java core/javaapi/api/src/main/java/viaduct/java/api/internal/ObjectBase.java— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ObjectBase (62-927). The bar is 500 significant lines; this is 49 over it, 1.10× 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: invariants/FailureCollector.kt core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: FailureCollector (9-697). The bar is 500 significant lines; this is 45 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: execution/ExecutionSelectionSet.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ExecutionSelectionSet (40-674). The bar is 500 significant lines; this is 16 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: select/EngineSelectionSetImpl.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: EngineSelectionSetImpl (92-780). The bar is 500 significant lines; this is 10 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: graphql/ViaductDescriptor.kt core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×12
Edited copy of a member (8 corresponding lines) core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:52— core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:52-59 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/initial-analyze-materialization.py: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) .github/scripts/format_coverage_summary.py:32— .github/scripts/format_coverage_summary.py:32-39 | .github/scripts/generate_coverage_index.py:28-35 — 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) core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt:48— core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt:48-55 | core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt:63-71 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:234— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:234-244 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:247-254 — 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) core/tenant/shared/src/main/kotlin/viaduct/tenant/runtime/jvm/ConnectionArgumentsSupport.kt:141— core/tenant/shared/src/main/kotlin/viaduct/tenant/runtime/jvm/ConnectionArgumentsSupport.kt:141-148 | core/tenant/shared/src/main/kotlin/viaduct/tenant/runtime/jvm/ConnectionArgumentsSupport.kt:157-165 — 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) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.kt:22— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.kt:22-35 | demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/queries/CharacterSummaryByNameQueryResolver.kt:21-28 — 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) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/GraphQLOperationValidator.kt:84— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/GraphQLOperationValidator.kt:84-91 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/NamedFragmentValidator.kt:82-89 — 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) core/x/remoteresolvers/starwars/main-server/src/main/kotlin/com/example/main/service/viaduct/ViaductRestController.kt:42— core/x/remoteresolvers/starwars/main-server/src/main/kotlin/com/example/main/service/viaduct/ViaductRestController.kt:42-49 | demoapps/starwars/src/main/kotlin/com/example/starwars/service/viaduct/ViaductRestController.kt:64-71 — 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) core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/InternalContextImpl.kt:35— core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/InternalContextImpl.kt:35-42 | core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/JavaEngineContextDelegate.kt:71-79 — 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) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.kt:45— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.kt:45-52 | demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/films/models/FilmCharactersRepository.kt:20-27 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/exceptions/FieldFetchingException.kt:24— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/exceptions/FieldFetchingException.kt:24-31 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/InternalEngineException.kt:28-35 — 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) core/tenant/api/src/main/kotlin/viaduct/api/internal/EngineValueConv.kt:79— core/tenant/api/src/main/kotlin/viaduct/api/internal/EngineValueConv.kt:79-88 | core/tenant/api/src/main/kotlin/viaduct/api/internal/JsonConv.kt:246-253 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×10
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/deep-dives/demand-closure/assets/dc.css:127— `details.collapsed-section > summary > h2::before` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:62— `.alt a i` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:94— `a.card` moves (`transition: transform .15s, border-color .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:101— `.js .reveal` moves (`transition: opacity .5s ease, transform .5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:229— `.js .htree li` moves (`transition: opacity .4s ease calc(var(--d, 0) * 140ms + 60ms), transform .4s ease calc(var(--d, 0) * 140ms + 60ms)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:355— `.drill .opt.wrong` moves (`animation: shake .35s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:446— `.mob-index > summary::before` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/website/assets/style.css:468— `.dd-list .go` moves (`transition: transform .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/animation/assets/style.css:69— `a.card` moves (`transition: transform .15s, border-color .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard core/engine/runtime2/impldocs/animation/assets/style.css:76— `.js .reveal` moves (`transition: opacity .5s ease, transform .5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Repeated repair: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt:791— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt changed 25 times in last 90 days and 15 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is FieldResolver.buildFieldResolutionResult at line 791), 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: Keep mat field consumption scoped to its query (AIRBNB)”; “fix(engine): Mat can lose supplied fields when list items contain nested objects of different concrete GraphQL types. It then reruns the parent resolver; if results reorder, indexed reads can fail with a type mismatch. This PR fixes this by aggregating coverage by concrete type at every depth, requiring fields on every observed object of that type. (AIRBNB)”; “fix(viaduct): cancel request scope on fatal CompletionStage failures (AIRBNB)”; “fix(engine): let a resolver's value supply nested fields that have their own resolvers (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt:607— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt changed 15 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ExecutionParameters.childPlanExecutionTarget at line 607), 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(engine): skip the query plan cache for documents rewritten per request (AIRBNB)”; “fix(engine): allow sibling progress during composite list traversal (AIRBNB)”; “fix: respect parent-supplied values during selective resolution (AIRBNB)”; “fix: revert parent-managed selective result refetching (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/schema/GJSelectionParser.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/schema/GJSelectionParser.kt:346— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/schema/GJSelectionParser.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is LiteralArgumentDecoder.decodeCondition at line 346), 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(engine): Allow directives on operations in engine2 (AIRBNB)”; “fix(engine): Support Engine2 instrumentation and introspection safely. (AIRBNB)”; “fix(engine): Allow directives on engine2 fragment definitions (AIRBNB)”; “fix(engine): Reuse compiled resolver selections for engine2 variables (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/schema/GJSelectionParser.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/MatSource.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/MatSource.kt:59— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/MatSource.kt changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is MatSourceKt.suppliesField at line 59), 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(engine): let a resolver's value supply nested fields that have their own resolvers (AIRBNB)”; “fix: respect parent-supplied values during selective resolution (AIRBNB)”; “fix: revert parent-managed selective result refetching (AIRBNB)”; “fix: refetch parent-managed selective results through their parent (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/MatSource.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldUnbatchedResolverExecutorImpl.kt core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldUnbatchedResolverExecutorImpl.kt:83— core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldUnbatchedResolverExecutorImpl.kt changed 5 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 5 (its worst body is FieldUnbatchedResolverExecutorImpl.unwrapFieldResolverResult at line 83), 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: “Revert "Prevent required-selection GRTs from being returne... (AIRBNB)”; “fix(tenant-api): This PR rejects GRTs which are passed into modern resolver as resolved input RSS fragment values, both for object and query RSS. The background is that an input requirement is very often not the same as the required output and in order to prevent an accidental reuse of input values as output, Viaduct will start rejecting RSS GRTs which are reused as the result of a resolver. (AIRBNB)”; “fix: populate field variable definitions during bootstrap (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldUnbatchedResolverExecutorImpl.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:171— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt changed 5 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 6 (its worst body is ScopedSchemaBuilder.replaceChildrenWithTypeReferences at line 171), 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: prevent clients from using bypassPolicyCheck in client-facing schemas (AIRBNB)”; “Revert "fix(viaduct): prevent client bypassPolicyCheck acc... (AIRBNB)”; “fix: hide bypassPolicyCheck from restricted schema views (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:379— core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt changed 5 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 14 (its worst body is DeferredExtensionsKt.asDeferred at line 379), 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(viaduct): keep nested execution cancellation out of field fetch instrumentation (AIRBNB)”; “fix(viaduct): keep nested execution cancellation out of field errors (AIRBNB)”; “fix(viaduct): cancel request scope on fatal CompletionStage failures (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/mat/KeyTree.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/mat/KeyTree.kt:119— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/mat/KeyTree.kt changed 5 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 11 (its worst body is KeyTree.intersectUncached at line 119), 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: respect parent-supplied values during selective resolution (AIRBNB)”; “fix: revert parent-managed selective result refetching (AIRBNB)”; “fix: refetch parent-managed selective results through their parent (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/mat/KeyTree.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/MatParameters.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/MatParameters.kt:133— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/MatParameters.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is MatParametersKt.routeFor at line 133), 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: respect parent-supplied values during selective resolution (AIRBNB)”; “fix: revert parent-managed selective result refetching (AIRBNB)”; “fix: refetch parent-managed selective results through their parent (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/MatParameters.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/SchemaScopeTransformer.kt core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/SchemaScopeTransformer.kt:80— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/SchemaScopeTransformer.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is SchemaScopeTransformer.buildTransformations at line 80), 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: prevent clients from using bypassPolicyCheck in client-facing schemas (AIRBNB)”; “Revert "fix(viaduct): prevent client bypassPolicyCheck acc... (AIRBNB)”; “fix: hide bypassPolicyCheck from restricted schema views (AIRBNB)”. 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/SchemaScopeTransformer.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×10
Edited copy of a member (11 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:222— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:222-234 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:240-250 — 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) gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductModuleSupport.kt:106— gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductModuleSupport.kt:106-119 | gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductModuleSupport.kt:125-135 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/shared/scoping/src/main/kotlin/viaduct/scoping/SchemaScopeDefinitions.kt:78— core/shared/scoping/src/main/kotlin/viaduct/scoping/SchemaScopeDefinitions.kt:78-88 | core/shared/scoping/src/main/kotlin/viaduct/scoping/SchemaScopeDefinitions.kt:93-103 — 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) gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt:119— gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt:119-129 | gradle-plugins/module/src/main/kotlin/viaduct/gradle/ViaductModulePlugin.kt: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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:413— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:413-423 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:429-439 — 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) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.kt:28— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.kt:28-38 | demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/films/resolvers/FilmSpeciesResolver.kt:27-38 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:166— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:166-176 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:112-122 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:609— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:609-619 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:296-306 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/JavaFieldResolverExecutorImpl.kt:72— core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/JavaFieldResolverExecutorImpl.kt:72-84 | core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/JavaNodeResolverExecutorImpl.kt:44-54 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/correctresolution/CorrectResolutionBenchmark.kt:71— core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/correctresolution/CorrectResolutionBenchmark.kt:71-81 | core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/resolution/PropertyTestBenchmark.kt: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.
Duplicated block (9 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:60— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:60-68 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:100-108 — 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:60` 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) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt:430— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt:430-438 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt:445-453 — 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 (9 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:204— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:204-212 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:134-142 — before extracting anything, compare `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt` and `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:45— core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:45-53 | core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:58-66 — 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 `core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:45` 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 (9 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:334— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:334-342 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:384-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:334` 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:92— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:92-100 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:118-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.
Duplicated block (9 lines × 2) core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/EngineCallbackServiceImpl.kt:69— core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/EngineCallbackServiceImpl.kt:69-77 | core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteResolverServiceImpl.kt:204-212 — 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 `context` to `EngineExecutionContext ): EngineSelectionSet = if (proto.document.isBlank()` in one and `RemoteEngineExecutionContext ): EngineSelectionSet = if (proto.document.isBlank()` 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) core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:444— core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:444-452 | core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:470-478 — 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 `core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:444` 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 (9 lines × 2) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:233— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:233-241 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:277-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.java:24— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.java:24-32 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/models/FilmCharactersRepository.java:24-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:241— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:241-247 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:286-292 — 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:241` 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 × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:327— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:327-333 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:387-393 — 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:327` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:184— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:184-190 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:126-132 — before extracting anything, compare `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt` and `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCt.kt:62— core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCt.kt:62-68 | core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCt.kt:71-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (7 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:65— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:65-71 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:56-62 — before extracting anything, compare `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt` and `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.java:31— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.java:31-37 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmSpeciesResolver.java:31-37 — 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 `demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.java:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:30— demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:30-36 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/VehicleBuilder.java:27-33 — 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 `demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:30` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:27` calls `hyperdriveRating`, `doubleValue`, `MGLT` and `demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/VehicleBuilder.java:26` 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) demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:20— demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:20-26 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/VehicleBuilder.java:20-26 — 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 `demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:20` 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, `demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:27` calls `hyperdriveRating`, `doubleValue`, `MGLT` and `demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/VehicleBuilder.java:27` 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) core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-cycle-check/run-diagnostics.py:8— core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-cycle-check/run-diagnostics.py:8-14 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-deferred-cycle-detection/run-counters.py:8-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×8
Edited copy of a member (12 corresponding lines) core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:38— core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:38-53 | core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:55-66 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/TenantModuleConfigAssembler.kt:222— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/TenantModuleConfigAssembler.kt:222-233 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/TenantModuleConfigAssembler.kt:279-290 — 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) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterBuilder.kt:15— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterBuilder.kt:15-26 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/models/PlanetBuilder.kt:12-23 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/FieldArgumentsRequireResolverRule.kt:23— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/FieldArgumentsRequireResolverRule.kt:23-36 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/NoResolverOnInterfaceFieldsRule.kt:24-35 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteResolverBatchResolution.kt:102— core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteResolverBatchResolution.kt:102-113 | core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteResolverServiceImpl.kt:252-263 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:133— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:133-144 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputGen.kt:198-209 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:91— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:91-102 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputGen.kt:156-167 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/ChainedInstrumentation.kt:255— core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/ChainedInstrumentation.kt:255-266 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/OptimizedChainedInstrumentation.kt:124-135 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×7
Edited copy of a member (20 corresponding lines) demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:14— demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipBuilder.java:14-36 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/VehicleBuilder.java:14-33 — 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) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/GRTClassFilesBuilderBase.kt:87— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/GRTClassFilesBuilderBase.kt:87-109 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/kotlingen/bytecode/KotlinGRTFilesBuilder.kt:71-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) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:579— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:579-598 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/ProjectedEngineSelectionSet.kt:106-130 — 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) build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:17— build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:17-36 | build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt:17-36 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:154— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:154-175 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:388-407 — 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) core/engine/wiring/src/main/kotlin/viaduct/engine/ViaductWiringFactory.kt:55— core/engine/wiring/src/main/kotlin/viaduct/engine/ViaductWiringFactory.kt:55-74 | core/engine/wiring/src/main/kotlin/viaduct/engine/ViaductWiringFactory.kt:80-101 — 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) gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductScopesYaml.kt:77— gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductScopesYaml.kt:77-96 | gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductScopesYaml.kt:100-119 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×7
Edited copy of a member (18 corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterStatsResolver.java:14— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterStatsResolver.java:14-35 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/ProfileFieldResolver.java:24-41 — 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) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetExtensionsOSS.kt:47— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetExtensionsOSS.kt:47-64 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetExtensionsOSS.kt:71-89 — 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) core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:238— core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:238-255 | core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:391-408 — 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) gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/ViaductJavaApplicationPlugin.kt:25— gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/ViaductJavaApplicationPlugin.kt:25-42 | gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/ViaductKotlinApplicationPlugin.kt:20-37 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsEncoder.kt:286— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsEncoder.kt:286-303 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsEncoder.kt:358-378 — 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) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:284— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:284-302 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ObjectBuilderGen.kt:223-240 — 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) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/FieldModel.java:46— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/FieldModel.java:46-63 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/ResolverModel.java:85-102 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×7
Edited copy of a member (14 corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterHomeworldResolver.java:28— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterHomeworldResolver.java:28-41 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterSpeciesResolver.java:28-41 — 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) core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:439— core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:439-452 | core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:465-478 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:173— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:173-186 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:118-131 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:338— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:338-351 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:356-369 — 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) core/engine/api/src/main/kotlin/viaduct/engine/api/bootstrap/executionregistry/RequiredSelectionSetSupport.kt:102— core/engine/api/src/main/kotlin/viaduct/engine/api/bootstrap/executionregistry/RequiredSelectionSetSupport.kt:102-118 | core/tenant/ksp/src/main/kotlin/viaduct/ksp/validation/ResolverSelectionSetProcessor.kt:205-218 — 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) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/RegistryExtractorExtensions.kt:428— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/RegistryExtractorExtensions.kt:428-445 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/RegistryExtractorExtensions.kt:447-460 — 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) core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:207— core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:207-222 | core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:313-326 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:152— build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:152-164 | build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:171-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:152` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:104— build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:104-116 | build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:123-135 — 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 `build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ResolverDataFetcher.kt:81— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ResolverDataFetcher.kt:81-93 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ResolverDataFetcher.kt:108-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.
Duplicated block (13 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:46— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:46-58 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:86-98 — 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:124— core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:124-136 | core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:147-159 — 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) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:178— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:178-190 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:243-255 — 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 `core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:178` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:239— core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:239-251 | core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:392-404 — 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 `core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:239` 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) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:649— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:649-659 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/FieldSelectionDirectives.kt:21-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:649` 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) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TypeRemovalVisitor.kt:59— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TypeRemovalVisitor.kt:59-69 | core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TypeRemovalVisitor.kt:77-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:239— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:239-249 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:291-301 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:239` 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:108— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:108-118 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:121-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:176— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:176-186 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:121-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:176` 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 (11 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/NamespaceTypeConstraintsRule.kt:79— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/NamespaceTypeConstraintsRule.kt:79-89 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ParentFieldConstraintsRule.kt:83-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/NamespaceTypeConstraintsRule.kt:79` 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 (11 lines × 2) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.java:25— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.java:25-35 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/queries/CharacterSummaryByNameQueryResolver.java:22-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.java:25` 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.
Swallowed exception (caught, then discarded) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterStatsResolver.kt:65— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/RequiredSelectionSetValidator.kt:198— `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) core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:271— `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) core/engine/wiring/src/main/kotlin/viaduct/engine/ViaductWiringFactory.kt:61— `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) core/engine/wiring/src/main/kotlin/viaduct/engine/ViaductWiringFactory.kt:88— `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) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/execution/Runtime2WiringFactory.kt:313— `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) core/engine/api/src/main/kotlin/viaduct/engine/api/spi/MaterializedFieldValueReader.kt:58— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Stateful singleton: CharacterFilmsRepository demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.kt:11— `CharacterFilmsRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characterFilmRelations; e.g. `characterFilmRelations` in `addCharacterToFilm` at line 42).
Stateful singleton: CharacterRepository demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterRepository.kt:11— `CharacterRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characters; e.g. `characters` in `add` at line 140).
Stateful singleton: FilmCharactersRepository demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/films/models/FilmCharactersRepository.kt:6— `FilmCharactersRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (filmCharacterRelations; e.g. `filmCharacterRelations` in `addCharacterToFilm` at line 17).
Stateful singleton: CharacterFilmsRepository demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterFilmsRepository.java:11— `CharacterFilmsRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characterFilmRelations; e.g. `characterFilmRelations` in `addCharacterToFilm` at line 24).
Stateful singleton: CharacterRepository demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterRepository.java:13— `CharacterRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (characters; e.g. `characters` in `add` at line 70).
Stateful singleton: FilmCharactersRepository demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/models/FilmCharactersRepository.java:11— `FilmCharactersRepository` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (filmCharacterRelations; e.g. `filmCharacterRelations` in `addCharacterToFilm` at line 24).
Hotspot: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:183— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in InclusionConditionKt.pruneContradictions at line 183. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt:55— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in EngineObjectDataKeyTreeBuilder.build at line 55. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt:166— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in DefaultCollectFields.collect at line 166. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/InclusionConditionActivation.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/InclusionConditionActivation.kt:33— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/InclusionConditionActivation.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in InclusionConditionActivationKt.includeAnyReadyAlternative at line 33. 1 of those changes was a fix/bug commit, and the other 1 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 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/InclusionConditionActivation.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/SchemaConformance.kt core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/SchemaConformance.kt:64— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/SchemaConformance.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in SchemaConformanceKt.conformsToOutputSchemaType at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/SchemaConformance.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: .github/scripts/format_alert.py .github/scripts/format_alert.py:151— .github/scripts/format_alert.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in format_alert.main at line 151. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 07:20:13 +00:00' --until='2026-11-16 07:20:13 +00:00' --full-history --no-merges -- .github/scripts/format_alert.py`: 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.
ClassTooLong: FieldResolver core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt:100— ClassTooLong — 1039 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 639 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.
ClassTooLong: ObjectBase core/javaapi/api/src/main/java/viaduct/java/api/internal/ObjectBase.java:62— ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 113 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: FailureCollector core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:9— ClassTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 112 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: ExecutionParameters core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionParameters.kt:158— ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 91 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExecutionSelectionSet core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:40— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EngineSelectionSetImpl core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:92— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (8 lines × 2) build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:18— build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:18-25 | build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt:18-25 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:201— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:201-208 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:246-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:38— build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:38-45 | build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt:38-45 — 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) build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:51— build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:51-58 | build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt:51-58 — 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) build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:138— build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:138-145 | build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:90-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/ChainedModernGJInstrumentation.kt:65— core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/ChainedModernGJInstrumentation.kt:65-72 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/OptimizedChainedInstrumentation.kt:170-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/ChainedModernGJInstrumentation.kt: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.
Duplicated block (6 lines × 2) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/queries/AllCharactersConnectionQueryResolver.kt:45— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/queries/AllCharactersConnectionQueryResolver.kt:45-50 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/queries/AllPlanetsConnectionQueryResolver.kt:54-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. 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: `QueryResolvers` names `com.example.starwars.filmography.resolverbases.QueryResolvers` in one and `com.example.starwars.universe.resolverbases.QueryResolvers` 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 (6 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:202— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:202-207 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:295-300 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterStatsResolver.java:25— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterStatsResolver.java:25-30 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/ProfileFieldResolver.java:31-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) core/javaapi/api/src/main/java/viaduct/java/api/types/BackwardConnectionArguments.java:50— core/javaapi/api/src/main/java/viaduct/java/api/types/BackwardConnectionArguments.java:50-55 | core/javaapi/api/src/main/java/viaduct/java/api/types/ForwardConnectionArguments.java:34-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/javaapi/api/src/main/java/viaduct/java/api/types/BackwardConnectionArguments.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. 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) .github/scripts/generate_changelog.py:299— .github/scripts/generate_changelog.py:299-304 | .github/scripts/generate_changelog.py:311-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:72— core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:72-77 | core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt:71-76 — before extracting anything, compare `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt` and `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×5
Edited copy of a member (21 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:238— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:238-258 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:290-310 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:100— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:100-120 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:125-159 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:122— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:122-143 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:147-167 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:71— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:71-91 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt:95-118 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt:412— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt:412-432 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt:440-460 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×5
Edited copies of one member (3 members, 16+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:394— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:394-412 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:415-430 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:433-449 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:170— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:170-193 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:197-212 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/FilteredSchema.kt:216-231 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) core/tenant/api/src/main/kotlin/viaduct/api/internal/DynamicValueBuilderTypeChecker.kt:46— core/tenant/api/src/main/kotlin/viaduct/api/internal/DynamicValueBuilderTypeChecker.kt:46-62 | core/tenant/api/src/main/kotlin/viaduct/api/internal/EODBuilderWrapper.kt:67-90 | core/tenant/api/src/main/kotlin/viaduct/api/internal/ObjectBase.kt:141-156 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:172— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:172-187 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:359-375 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:377-395 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) core/shared/mapping/src/main/kotlin/viaduct/mapping/graphql/GJValueConv.kt:135— core/shared/mapping/src/main/kotlin/viaduct/mapping/graphql/GJValueConv.kt:135-151 | core/tenant/api/src/main/kotlin/viaduct/api/internal/EngineValueConv.kt:61-76 | core/tenant/api/src/main/kotlin/viaduct/api/internal/JsonConv.kt:256-272 — 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.
Duplicated block (12 lines × 2) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:68— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:68-80 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:89-100 — 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 `core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:182— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:182-193 | core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:219-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:182` 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, `core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:194` calls `replaceDirectives` and `core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:231` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:198— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:198-209 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:228-239 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:198` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:90— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:90-101 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:107-118 — 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 `actual` to `GraphQLObjectType` in one and `GraphQLInterfaceType` 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) core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/DefaultSchemaFactory.kt:94— core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/DefaultSchemaFactory.kt:94-105 | core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/DefaultSchemaFactory.kt:157-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/DefaultSchemaFactory.kt:169` calls `directiveLocation`, `DirectiveLocation` and `core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/DefaultSchemaFactory.kt:106` 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 (5 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:270— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:270-274 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:200-204 — before extracting anything, compare `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt` and `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 (5 lines × 2) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/FieldResolvers.kt:43— core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/FieldResolvers.kt:43-47 | core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/NodeResolvers.kt:30-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:585— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:585-589 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:590-595 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:585` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:76— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:76-80 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/MaterializeResult.kt:83-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:80— core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:80-84 | core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt:79-83 — before extracting anything, compare `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt` and `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 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.
TooManyMethods: FailureCollector core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:9— 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: ObjectBase core/javaapi/api/src/main/java/viaduct/java/api/internal/ObjectBase.java:62— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: FieldResolver core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldResolver.kt:100— 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: GraphQLTypesGen core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/GraphQLTypes.kt:111— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
MethodTooLong: InclusionConditionKt.pruneContradictions core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:183— MethodTooLong — pruneContradictions runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× 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: TransformationsVisitor.modifyElement core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TransformationsVisitor.kt:87— MethodTooLong — modifyElement 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: Builder.mk core/tenant/api/src/main/kotlin/viaduct/api/internal/DefaultGRTConvFactory.kt:241— MethodTooLong — mk runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: RemoteFieldProxyExecutor.batchResolve core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteFieldProxyExecutor.kt:77— MethodTooLong — batchResolve runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change coupling: ViaductJavaModulePlugin.kt ↔ ViaductModulePlugin.kt gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt:1— `gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt` and `gradle-plugins/module/src/main/kotlin/viaduct/gradle/ViaductModulePlugin.kt` change together 91% of the time (10 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `b5b5115b` feat(oss-build): introduce viaduct-metamodule to: (AIRBNB); `442c8816` refactor(gradle-plugins): remove project-level package DSL (AIRBNB); `e1fa23d0` fix(viaduct): validate direct module deps from topology paths (AIRBNB) — run `git show` on any of them.
Change coupling: ValidationErrorCodes.kt ↔ DefaultSchemaValidator.kt core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/ValidationErrorCodes.kt:1— `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/ValidationErrorCodes.kt` and `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/DefaultSchemaValidator.kt` change together 89% of the time (16 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `20eee5ec` feat(viaductschema): restrict @resolver to Node types at the type lev…; `a87a3bf6` fix: enforce tenant-local field constraints across Viaduct (AIRBNB); `369c21ff` feat(viaduct-oss): add NodeInterfaceIdConsistencyRule for schema vali… — run `git show` on any of them.
Change coupling: ViaductPluginCommon.kt ↔ ViaductModulePlugin.kt gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductPluginCommon.kt:1— `gradle-plugins/common/src/main/kotlin/viaduct/gradle/ViaductPluginCommon.kt` and `gradle-plugins/module/src/main/kotlin/viaduct/gradle/ViaductModulePlugin.kt` change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `b8606d27` feat(viaduct): add module viaduct application bucket (AIRBNB); `9a1499a0` feat(viaduct): wire projects through topology (AIRBNB); `6aa74cad` feat(viaduct-gradle): Require settings topology for project plugins (… — run `git show` on any of them.
Change coupling: EngineExecutionContextExtensions.kt ↔ FieldExecutionHelpers.kt core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/EngineExecutionContextExtensions.kt:1— `core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/EngineExecutionContextExtensions.kt` and `core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldExecutionHelpers.kt` change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `c209bf22` feat(engine): collect defer usages (AIRBNB); `6e9e0b8e` refactor(engine)!: remove selective OER keys (AIRBNB); `cfdcf463` feat(engine): selective field resolvers (AIRBNB) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×4
Edited copy of a member (27 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:275— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:275-302 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:322-348 — 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) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:224— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:224-250 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:259-300 — 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) gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/task/GenerateGRTClassFilesTask.kt:55— gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/task/GenerateGRTClassFilesTask.kt:55-81 | gradle-plugins/module/src/main/kotlin/viaduct/gradle/task/GenerateResolverBasesTask.kt:63-91 — 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) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:104— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:104-130 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputGen.kt:169-195 — 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 (32 corresponding lines) · ×4
Edited copy of a member (32 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:233— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:233-264 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:274-305 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt:21— gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt:21-55 | gradle-plugins/module/src/main/kotlin/viaduct/gradle/ViaductModulePlugin.kt:24-55 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ReflectedTypeGen.kt:210— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ReflectedTypeGen.kt:210-241 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ReflectedTypeGen.kt:248-284 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:541— core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:541-572 | core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollectorExtension.kt:13-44 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×4
Edited copy of a member (17 corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.java:30— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmPlanetsResolver.java:30-46 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmSpeciesResolver.java:30-46 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaResolverParamsExtractor.kt:223— core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaResolverParamsExtractor.kt:223-239 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/RegistryExtractorExtensions.kt:347-366 — 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) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.java:15— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/mutations/RenameCharacterSummaryMutation.java:15-35 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/queries/CharacterSummaryByNameQueryResolver.java:16-32 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:267— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:267-283 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/graphql/schema/ViaductSchemaExtensions.kt:24-40 — 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 (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:210— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:210-222 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:303-315 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaNodeResolverGenerator.java:246— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaNodeResolverGenerator.java:246-258 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaResolverGenerator.java:323-335 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:248— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:248-260 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/graphql/schema/ViaductSchemaExtensions.kt:5-22 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:293— core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:293-305 | core/javaapi/api/src/main/java/viaduct/java/api/internal/InputBase.java:337-350 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/ConstantsDecoder.kt:112— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/ConstantsDecoder.kt:112-118 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/ConstantsDecoder.kt:201-207 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/ResolverSelectionProjector.kt:132— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/ResolverSelectionProjector.kt:132-140 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/Runtime2ResolverSelectionProjector.kt:119-125 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:311— core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bootstrap/ViaductJavaExecutorFactory.kt:311-317 | core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/bootstrap/FieldAPIData.kt:13-19 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/SharedOperationContext.kt:45— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/SharedOperationContext.kt:45-51 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/ViaductSchema.kt:310-317 — 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) · ×4
Edited copy of a member (10 corresponding lines) demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/queries/PlanetFilmsQueryResolver.java:25— demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/queries/PlanetFilmsQueryResolver.java:25-34 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/queries/PlanetResidentsQueryResolver.java:25-35 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:311— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:311-320 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:357-366 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ApplicationOnlyDefinitionsRule.kt:30— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ApplicationOnlyDefinitionsRule.kt:30-39 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ApplicationOnlyDefinitionsRule.kt:44-53 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ViaductExecutionStrategy.kt:248— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ViaductExecutionStrategy.kt:248-257 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ViaductExecutionStrategy.kt:271-281 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:91— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:91-110 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:117-131 — 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) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/ResolverSelectionProjector.kt:69— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/ResolverSelectionProjector.kt:69-94 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/Runtime2ResolverSelectionProjector.kt:65-79 — 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) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentExpressions.kt:237— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentExpressions.kt:237-251 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentExpressions.kt:316-334 — 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 (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/OptimizedChainedInstrumentation.kt:194— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/OptimizedChainedInstrumentation.kt:194-212 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/OptimizedChainedInstrumentation.kt:217-235 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:85— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:85-105 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:309-327 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:647— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:647-665 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/FieldSelectionDirectives.kt:19-37 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) docs/hooks/copy_markdown.py:49— docs/hooks/copy_markdown.py:49-59 | docs/hooks/copy_markdown.py:230-238 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) core/shared/utils/src/main/kotlin/viaduct/utils/collections/BitVector.kt:89— core/shared/utils/src/main/kotlin/viaduct/utils/collections/BitVector.kt:89-97 | core/shared/utils/src/main/kotlin/viaduct/utils/collections/BitVector.kt:99-107 — 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) demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/resolvers/StarshipNodeResolver.java:24— demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/resolvers/StarshipNodeResolver.java:24-32 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/resolvers/VehicleNodeResolver.java:24-32 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×3
Edited copy of a member (1 corresponding lines) core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt:46— core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt:46-46 | core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt:61-61 — 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.
Edited copy of a member (1 corresponding lines) core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:6— core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:6-6 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/initial-analyze-materialization.py:6-6 — 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.
Edited copy of a member (1 corresponding lines) core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:4— core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:4-4 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/initial-analyze-materialization.py:4-4 — 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· Edited copy of a member (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) core/javaapi/api/src/main/java/viaduct/java/api/types/BackwardConnectionArguments.java:69— core/javaapi/api/src/main/java/viaduct/java/api/types/BackwardConnectionArguments.java:69-74 | core/javaapi/api/src/main/java/viaduct/java/api/types/MultidirectionalConnectionArguments.java:55-60 — 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) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:158— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:158-163 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:104-109 — 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) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:164— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:164-169 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/MaterializeResult.kt:191-200 — 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 (3 corresponding lines) · ×3
Edited copy of a member (3 corresponding lines) core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaDocumentParamsExtractor.kt:112— core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaDocumentParamsExtractor.kt:112-114 | core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaResolverParamsExtractor.kt:346-348 — 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) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:708— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:708-710 | core/shared/graphql/src/main/kotlin/viaduct/graphql/utils/ParsedSelections.kt:140-145 — 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) core/tenant/api/src/main/kotlin/viaduct/api/types/BackwardConnectionArguments.kt:64— core/tenant/api/src/main/kotlin/viaduct/api/types/BackwardConnectionArguments.kt:64-66 | core/tenant/api/src/main/kotlin/viaduct/api/types/MultidirectionalConnectionArguments.kt:54-56 — 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.
Duplicated block (18 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:306— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:306-323 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:357-374 — 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:377` calls `conflictsDirectlyWith` and `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:324` 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 (18 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/ResolverSupport.kt:213— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/ResolverSupport.kt:213-230 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/ResolverSupport.kt:245-262 — 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 (18 lines × 2) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:106— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:106-123 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputGen.kt:171-188 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:106` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:94— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:94-107 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/MaterializeResult.kt:107-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. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:94` 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 (14 lines × 2) core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForObjects.kt:52— core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForObjects.kt:52-65 | core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForObjects.kt:109-122 — 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 `core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForObjects.kt:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/EnumTypeBuilder.kt:13— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/EnumTypeBuilder.kt:13-39 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/EnumTypeExtensionBuilder.kt:12-25 — 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 (10 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:400— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:400-409 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:424-433 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:400` 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) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/FilterChildrenVisitor.kt:24— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/FilterChildrenVisitor.kt:24-33 | core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/FilterTenantLocalFieldsVisitor.kt:16-25 — 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) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/ValidateRequiredScopesVisitor.kt:19— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/ValidateRequiredScopesVisitor.kt:19-28 | core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/ValidateScopesVisitor.kt:22-31 — 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.
GJSchemaCheck.checkAgreement (cyclomatic 17) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:56— GJSchemaCheck.checkAgreement 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. This shape REPEATS in the file: one other method here (GJSchemaCheck.checkAgreement) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GJSchemaCheck.checkAgreement (cyclomatic 17) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt:58— GJSchemaCheck.checkAgreement 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. This shape REPEATS in the file: one other method here (GJSchemaCheck.checkAgreement) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
FunctionTooLong: global-id-plugin.GlobalIdPluginContent core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:62— FunctionTooLong — GlobalIdPluginContent runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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.
FunctionTooLong: graph.init core/engine/runtime2/impldocs/website/assets/graph.js:26— FunctionTooLong — init runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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 (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:75— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/MaterializeResolverInput.kt:75-107 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/MaterializeResult.kt:82-120 — 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.
Edited copy of a member (33 corresponding lines) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:182— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:182-216 | core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/ScopedSchemaBuilder.kt:219-251 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterBuilder.java:14— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterBuilder.java:14-27 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/models/PlanetBuilder.java:14-27 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/models/SpeciesBuilder.java:14-29 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterNodeResolver.java:29— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/resolvers/CharacterNodeResolver.java:29-43 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/resolvers/PlanetNodeResolver.java:28-41 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/queries/SpeciesNodeQueryResolver.java:28-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/starships/models/StarshipBuilder.kt:16— demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/starships/models/StarshipBuilder.kt:16-33 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/vehicles/models/VehicleBuilder.kt:14-29 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:63— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:63-80 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/instrumentation/TaggedMetricInstrumentation.kt:85-100 — 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 copies of one member (3 members, 13+ corresponding lines) · ×2
Edited copies of one member (3 members, 13+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:205— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:205-217 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:243-255 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilder.kt:368-380 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:123— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:123-135 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:140-152 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:157-182 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×2
Edited copies of one member (3 members, 18+ corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentExpressions.kt:116— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentExpressions.kt:116-135 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentExpressions.kt:140-159 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/EngineValueData.kt:253-270 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 18+ corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/CheckerResolverBase.kt:241— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/CheckerResolverBase.kt:241-259 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/VariableMapping.kt:29-46 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/VariableMapping.kt:49-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:451— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/ExecutionSelectionSet.kt:451-455 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:637-641 — 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) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:133— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BInputStream.kt:133-137 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/BOutputStream.kt:71-76 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (32 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchema.kt:136— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchema.kt:136-167 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:59-90 — 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 (32 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt:14— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt:14-45 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt:14-45 — before extracting anything, compare `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt` and `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 128 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 (17 lines × 2) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TransformationsVisitor.kt:94— core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TransformationsVisitor.kt:94-110 | core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TransformationsVisitor.kt:126-142 — 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 `core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TransformationsVisitor.kt:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) core/javaapi/api/src/main/java/viaduct/java/api/documents/MutationFromAnnotation.java:1— core/javaapi/api/src/main/java/viaduct/java/api/documents/MutationFromAnnotation.java:1-17 | core/javaapi/api/src/main/java/viaduct/java/api/documents/QueryFromAnnotation.java:1-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/javaapi/api/src/main/java/viaduct/java/api/documents/MutationFromAnnotation.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 (21 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ScalarTypeBuilder.kt:11— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ScalarTypeBuilder.kt:11-31 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/UnionTypeBuilder.kt:13-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (21 lines × 2) core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:8— core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py:8-33 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/initial-analyze-materialization.py:8-28 — before extracting anything, compare `core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/analyze-materialization.py` and `core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/initial-analyze-materialization.py` 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. 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 (5 lines × 3) demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/queries/AllPlanetsQueryResolver.kt:25— demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/queries/AllPlanetsQueryResolver.kt:25-34 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/queries/AllSpeciesQueryResolver.kt:25-29 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/vehicles/queries/AllVehiclesQueryResolver.kt:32-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaGRTGenerator.java:88— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaGRTGenerator.java:88-92 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaNodeResolverGenerator.java:250-254 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaResolverGenerator.java:327-331 — 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.
Low cohesion: ResolverRegistryImpl (LCOM4 4) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ResolverRegistryImpl.kt:406— ResolverRegistryImpl'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: ChainedDataLoaderInstrumentation (LCOM4 4) core/shared/dataloader/src/main/kotlin/viaduct/dataloader/ChainedDataLoaderInstrumentation.kt:7— ChainedDataLoaderInstrumentation'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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/VariablesProviderExecutor.kt:38— `provideVariables` is public and takes `arguments: Map<String, Any ?>` from its caller, and it calls itself at line 38 with a piece of `arguments` — the function is not `tailrec`, so every call is a real frame — and nowhere in `provideVariables` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `provideVariables` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
Recursive walk over a caller-supplied document has no depth cap core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/EngineResult.kt:254— `GroundKey.of` is public and takes `arguments: Map<String, Any ?>` from its caller, and it calls itself at line 254 with a piece of `arguments` — the function is not `tailrec`, so every call is a real frame — and nowhere in `GroundKey.of` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `GroundKey.of` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark core/service/wiring/src/main/resources/graphiql/index.html:23— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
InclusionConditionKt.pruneContradictions (cyclomatic 74) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:183— InclusionConditionKt.pruneContradictions has cyclomatic complexity 74 (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.
graph.init (cyclomatic 74) core/engine/runtime2/impldocs/website/assets/graph.js:26— graph.init has cyclomatic complexity 74 (threshold 15). Most of this is not in the body itself: 8 of the 74 points are its own statements and the rest belongs to 28 function items inside it that branch (setPanel, a function literal at line 97, focus, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
animate.caption (cyclomatic 51) core/engine/runtime2/impldocs/animation/animate.py:782— animate.caption has cyclomatic complexity 51 (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.
motion.initScene (cyclomatic 49) core/engine/runtime2/impldocs/website/assets/motion.js:130— motion.initScene has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 8 of the 49 points are its own statements and the rest belongs to 13 function items inside it that branch (render, frame, a function literal at line 257, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
animate.task_track (cyclomatic 45) core/engine/runtime2/impldocs/animation/animate.py:352— animate.task_track has cyclomatic complexity 45 (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.
motion.apply (cyclomatic 43) core/engine/runtime2/impldocs/animation/assets/motion.js:98— motion.apply has cyclomatic complexity 43 (threshold 15). Of this number, 34 points are the body's own statements and 9 belong to 4 function literals inside it that branch. 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.
motion.apply (cyclomatic 37) core/engine/runtime2/impldocs/website/assets/motion.js:77— motion.apply has cyclomatic complexity 37 (threshold 15). Of this number, 29 points are the body's own statements and 8 belong to 3 function literals inside it that branch. 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.
animate.oer_frames (cyclomatic 34) core/engine/runtime2/impldocs/animation/animate.py:525— animate.oer_frames 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.
animate.demand_frames (cyclomatic 33) core/engine/runtime2/impldocs/animation/animate.py:597— animate.demand_frames 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.
InclusionConditionActivationKt.includeAnyReadyAlternative (cyclomatic 31) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/InclusionConditionActivation.kt:33— InclusionConditionActivationKt.includeAnyReadyAlternative has cyclomatic complexity 31 (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.
app.chrome (cyclomatic 30) core/engine/runtime2/impldocs/website/assets/app.js:78— app.chrome has cyclomatic complexity 30 (threshold 15). Of this number, 19 points are the body's own statements and 11 belong to 4 function items inside it that branch. 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.
animate.oer_progress (cyclomatic 26) core/engine/runtime2/impldocs/animation/animate.py:457— animate.oer_progress 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.
IRGen.genValue (cyclomatic 25) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ArbIR.kt:276— IRGen.genValue has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app.codeHeaders (cyclomatic 25) core/engine/runtime2/impldocs/website/assets/app.js:338— app.codeHeaders has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 339, 366, 363). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
global-id-plugin.GlobalIdPluginContent (cyclomatic 25) core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:62— global-id-plugin.GlobalIdPluginContent has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 111, 69, 97, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
motion.initScene::render (cyclomatic 24) core/engine/runtime2/impldocs/animation/assets/motion.js:361— motion.initScene::render 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.
SchemaDeprecatedDirectiveVisitor.validate (cyclomatic 23) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/SchemaDeprecatedDirectiveVisitor.kt:42— SchemaDeprecatedDirectiveVisitor.validate 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.
ValueInCtSyntaxKt.valueInCtSyntax (cyclomatic 23) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ValueInCtSyntax.kt:42— ValueInCtSyntaxKt.valueInCtSyntax 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.
validate.check_scenes (cyclomatic 23) core/engine/runtime2/impldocs/website/tools/validate.py:332— validate.check_scenes 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.
app.initGlossaryPops (cyclomatic 23) core/engine/runtime2/impldocs/website/assets/app.js:248— app.initGlossaryPops has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (out, a function literal at line 260, show, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ConditionEvaluation.nextRequirement (cyclomatic 22) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:450— ConditionEvaluation.nextRequirement 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.
motion.prepare (cyclomatic 22) core/engine/runtime2/impldocs/animation/assets/motion.js:36— motion.prepare has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
tree.init (cyclomatic 21) core/engine/runtime2/impldocs/website/assets/tree.js:26— tree.init has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 28, 75, 31, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
InvariantsKt.checkMiscInvariants (cyclomatic 20) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/Invariants.kt:351— InvariantsKt.checkMiscInvariants has cyclomatic complexity 20 (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.
ResolverValueGen.genValue (cyclomatic 19) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ResolverValueGen.kt:215— ResolverValueGen.genValue 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.
check.check_case (cyclomatic 19) demoapps/plugin-compatibility/check.py:210— check.check_case 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.
drill.sort (cyclomatic 19) core/engine/runtime2/impldocs/website/assets/drill.js:78— drill.sort has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 97, hold, a function literal at line 107, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DefaultCollectFields.collect (cyclomatic 18) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt:166— DefaultCollectFields.collect 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.
Builder.mk (cyclomatic 18) core/tenant/api/src/main/kotlin/viaduct/api/internal/DefaultGRTConvFactory.kt:241— Builder.mk 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.
ValueInCtSyntaxKt.typeToCtSyntax (cyclomatic 18) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ValueInCtSyntax.kt:111— ValueInCtSyntaxKt.typeToCtSyntax 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.
SchemaConformanceKt.conformsToOutputSchemaType (cyclomatic 17) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/SchemaConformance.kt:64— SchemaConformanceKt.conformsToOutputSchemaType 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.
CycleGroups.buildScc (cyclomatic 17) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/CycleGroups.kt:87— CycleGroups.buildScc 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.
FoundationFieldSelectionRule.validateField (cyclomatic 17) core/x/federation/validation/src/main/kotlin/viaduct/x/federation/validation/FoundationFieldSelectionRule.kt:128— FoundationFieldSelectionRule.validateField 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.
format_sbom_summary.format_summary (cyclomatic 17) .github/scripts/format_sbom_summary.py:109— format_sbom_summary.format_summary 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.
animate.animation_steps (cyclomatic 17) core/engine/runtime2/impldocs/animation/animate.py:251— animate.animation_steps 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.
validate.check_links (cyclomatic 17) core/engine/runtime2/impldocs/website/tools/validate.py:259— validate.check_links 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.
motion.prepare (cyclomatic 17) core/engine/runtime2/impldocs/website/assets/motion.js:34— motion.prepare has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
EngineObjectDataKeyTreeBuilder.build (cyclomatic 16) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt:55— EngineObjectDataKeyTreeBuilder.build 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.
KmPropertyBuilder.build (cyclomatic 16) core/shared/codegen/src/main/kotlin/viaduct/codegen/km/KmPropertyBuilder.kt:151— KmPropertyBuilder.build 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.
TypeRemovalVisitor.maybeRemove (cyclomatic 16) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TypeRemovalVisitor.kt:47— TypeRemovalVisitor.maybeRemove has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FailureCollector.containsExactlyElementsIn (cyclomatic 16) core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:486— FailureCollector.containsExactlyElementsIn has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DefinitionsDecoderKt.validateAppliedDirectives (cyclomatic 16) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:546— DefinitionsDecoderKt.validateAppliedDirectives has cyclomatic complexity 16 (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.
GJSchemaRawKt.gjSchemaRawFromRegistry (cyclomatic 16) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaRaw.kt:72— GJSchemaRawKt.gjSchemaRawFromRegistry has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
format_alert.main (cyclomatic 16) .github/scripts/format_alert.py:151— format_alert.main has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
validate_release_state.validate_release_state (cyclomatic 16) .github/scripts/validate_release_state.py:80— validate_release_state.validate_release_state 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.
animate.render (cyclomatic 16) core/engine/runtime2/impldocs/animation/animate.py:890— animate.render has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
validate.check_graphs (cyclomatic 16) core/engine/runtime2/impldocs/website/tools/validate.py:371— validate.check_graphs 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.
InclusionConditionKt.pruneContradictions (cognitive 153) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:183— InclusionConditionKt.pruneContradictions has cognitive complexity 153 (threshold 15). Drivers by points: if/else 51 (118 pts), match/switch 6 (14 pts), boolean chains 11, loops 6 (10 pts) (nesting depth added 79). 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.
animate.oer_frames (cognitive 97) core/engine/runtime2/impldocs/animation/animate.py:525— animate.oer_frames has cognitive complexity 97 (threshold 15). Drivers by points: ternaries 14 (59 pts), if/else 7 (19 pts), loops 5 (12 pts), boolean chains 7 (nesting depth added 64). 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.
animate.caption (cognitive 89) core/engine/runtime2/impldocs/animation/animate.py:782— animate.caption has cognitive complexity 89 (threshold 15). Drivers by points: if/else 26 (52 pts), ternaries 12 (27 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 42). 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.
animate.task_track (cognitive 82) core/engine/runtime2/impldocs/animation/animate.py:352— animate.task_track has cognitive complexity 82 (threshold 15). Drivers by points: if/else 20 (40 pts), ternaries 9 (23 pts), boolean chains 11, loops 6 (8 pts) (nesting depth added 36). 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.
animate.demand_frames (cognitive 74) core/engine/runtime2/impldocs/animation/animate.py:597— animate.demand_frames has cognitive complexity 74 (threshold 15). Drivers by points: if/else 12 (40 pts), loops 8 (15 pts), ternaries 5 (14 pts), boolean chains 5 (nesting depth added 44). 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.
animate.oer_progress (cognitive 64) core/engine/runtime2/impldocs/animation/animate.py:457— animate.oer_progress has cognitive complexity 64 (threshold 15). Drivers by points: if/else 9 (36 pts), loops 5 (11 pts), ternaries 2 (10 pts), boolean chains 7 (nesting depth added 41). 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.
apply (cognitive 63) core/engine/runtime2/impldocs/animation/assets/motion.js:98— apply has cognitive complexity 63 (threshold 15). Drivers by points: if/else 19 (32 pts), ternaries 9 (19 pts), boolean chains 9, loops 1 (2 pts), match/switch 1 (nesting depth added 24). Of this number, 43 points are the body's own statements and 20 belong to 4 function literals inside it that branch. 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.
graph.init (cognitive 59) core/engine/runtime2/impldocs/website/assets/graph.js:26— graph.init has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 28, if/else 18 (19 pts), ternaries 12 (nesting depth added 1). Most of this is not in the body itself: 6 of the 59 points are its own statements and the rest belongs to 28 function items inside it that branch (setPanel, a function literal at line 97, resumeFlow, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
validate.check_scenes (cognitive 50) core/engine/runtime2/impldocs/website/tools/validate.py:332— validate.check_scenes has cognitive complexity 50 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 6 (13 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 28). 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.
motion.apply (cognitive 48) core/engine/runtime2/impldocs/website/assets/motion.js:77— motion.apply has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (31 pts), boolean chains 6, ternaries 3 (6 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 18). Of this number, 30 points are the body's own statements and 18 belong to 3 function literals inside it that branch. 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.
motion.initScene (cognitive 45) core/engine/runtime2/impldocs/website/assets/motion.js:130— motion.initScene has cognitive complexity 45 (threshold 15). Drivers by points: if/else 23 (28 pts), boolean chains 12, ternaries 4 (5 pts) (nesting depth added 6). Most of this is not in the body itself: 8 of the 45 points are its own statements and the rest belongs to 13 function items inside it that branch (frame, render, run, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
validate.check_graphs (cognitive 42) core/engine/runtime2/impldocs/website/tools/validate.py:371— validate.check_graphs has cognitive complexity 42 (threshold 15). Drivers by points: if/else 8 (27 pts), loops 5 (13 pts), boolean chains 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConditionEvaluation.nextRequirement (cognitive 37) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/InclusionCondition.kt:450— ConditionEvaluation.nextRequirement has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (24 pts), match/switch 3 (8 pts), boolean chains 4, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InclusionConditionActivationKt.includeAnyReadyAlternative (cognitive 35) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/InclusionConditionActivation.kt:33— InclusionConditionActivationKt.includeAnyReadyAlternative has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 10, match/switch 3 (7 pts), loops 3, 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.
GraphQLSchemaParser.extractObjects (cognitive 35) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:126— GraphQLSchemaParser.extractObjects has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 3 (7 pts), boolean chains 1 (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.
initScene::render (cognitive 34) core/engine/runtime2/impldocs/animation/assets/motion.js:361— initScene::render has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 5 (11 pts), boolean chains 10 (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.
WorkGraph.processPendingGroups (cognitive 30) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/WorkGraph.kt:245— WorkGraph.processPendingGroups has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 4 (9 pts), boolean chains 3 (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.
KeyTree.intersectUncached (cognitive 30) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/mat/KeyTree.kt:119— KeyTree.intersectUncached has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 2 (3 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.
validate.check_links (cognitive 30) core/engine/runtime2/impldocs/website/tools/validate.py:259— validate.check_links has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (3 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.
global-id-plugin.GlobalIdPluginContent (cognitive 30) core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx:62— global-id-plugin.GlobalIdPluginContent has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 7, ternaries 4, error handling 2 (3 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 111, 69, 150, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RequiredSelectionSetGraph.getAbstractEdges (cognitive 29) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/tenantloading/RequiredSelectionSetGraph.kt:326— RequiredSelectionSetGraph.getAbstractEdges has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IRGen.genValue (cognitive 28) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ArbIR.kt:276— IRGen.genValue has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 9, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DeferredExtensionsKt.waitAllDeferreds (cognitive 27) core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:474— DeferredExtensionsKt.waitAllDeferreds has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (12 pts), error handling 3 (9 pts), match/switch 2 (6 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.
ValueInCtSyntaxKt.valueInCtSyntax (cognitive 27) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ValueInCtSyntax.kt:42— ValueInCtSyntaxKt.valueInCtSyntax has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (26 pts), match/switch 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.
animate.simple_passive_steps (cognitive 27) core/engine/runtime2/impldocs/animation/animate.py:330— animate.simple_passive_steps has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 6, loops 2 (3 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.
prepare (cognitive 27) core/engine/runtime2/impldocs/animation/assets/motion.js:36— prepare has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), ternaries 5 (7 pts), error handling 2 (4 pts) (nesting depth added 6). Of this number, 23 points are the body's own statements and 4 belong to 5 function literals inside it that branch. 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.
check.check_case (cognitive 26) demoapps/plugin-compatibility/check.py:210— check.check_case has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (14 pts), loops 10 (11 pts), if/else 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.
DefaultCollectFields.collect (cognitive 25) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CollectFields.kt:166— DefaultCollectFields.collect has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 6, match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteResolverServiceImpl.batchResolveFieldInternal (cognitive 25) core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteResolverServiceImpl.kt:82— RemoteResolverServiceImpl.batchResolveFieldInternal has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 6 (10 pts), loops 1, match/switch 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.
EngineObjectDataKeyTreeBuilder.build (cognitive 24) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/EngineObjectDataToKeyTree.kt:55— EngineObjectDataKeyTreeBuilder.build has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (5 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolverValueGen.genValue (cognitive 24) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ResolverValueGen.kt:215— ResolverValueGen.genValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 2, match/switch 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.
Builder.mk (cognitive 24) core/tenant/api/src/main/kotlin/viaduct/api/internal/DefaultGRTConvFactory.kt:241— Builder.mk has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (19 pts), match/switch 2 (3 pts), boolean chains 2 (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.
format_sbom_summary.format_summary (cognitive 24) .github/scripts/format_sbom_summary.py:109— format_sbom_summary.format_summary has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 8 (9 pts), error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CycleGroups.buildScc (cognitive 23) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/CycleGroups.kt:87— CycleGroups.buildScc has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 6 (9 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.
SchemaDeprecatedDirectiveVisitor.validate (cognitive 23) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/SchemaDeprecatedDirectiveVisitor.kt:42— SchemaDeprecatedDirectiveVisitor.validate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefinitionsDecoderKt.validateAppliedDirectives (cognitive 23) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:546— DefinitionsDecoderKt.validateAppliedDirectives has cognitive complexity 23 (threshold 15). Drivers by points: loops 9 (22 pts), match/switch 1 (nesting depth added 13). 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.
animate.animation_steps (cognitive 23) core/engine/runtime2/impldocs/animation/animate.py:251— animate.animation_steps has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (8 pts), ternaries 2 (6 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Covers.covers (cognitive 21) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/Covers.kt:34— Covers.covers has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (3 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.
KmToCtForClassesKt.useDefaultImpls (cognitive 21) core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForClasses.kt:168— KmToCtForClassesKt.useDefaultImpls has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, 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.
DeferredExtensionsKt.asDeferred (cognitive 21) core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:379— DeferredExtensionsKt.asDeferred has cognitive complexity 21 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 6, match/switch 2 (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.
ConstantsEncoder.encodeCompoundValues (cognitive 21) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/ConstantsEncoder.kt:100— ConstantsEncoder.encodeCompoundValues has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 3 (7 pts), match/switch 1 (2 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.
ValueInCtSyntaxKt.typeToCtSyntax (cognitive 21) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ValueInCtSyntax.kt:111— ValueInCtSyntaxKt.typeToCtSyntax has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 1, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
GraphQLSchemaParser.extractResolvers (cognitive 21) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:443— GraphQLSchemaParser.extractResolvers has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (6 pts), ternaries 2 (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.
WorkQueue.run (cognitive 20) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/CreateWorkQueue.kt:45— WorkQueue.run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (5 pts) (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.
KmPropertyBuilder.build (cognitive 20) core/shared/codegen/src/main/kotlin/viaduct/codegen/km/KmPropertyBuilder.kt:151— KmPropertyBuilder.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8 (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.
DeferredExtensionsKt.exceptionallyCompose (cognitive 20) core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:274— DeferredExtensionsKt.exceptionallyCompose has cognitive complexity 20 (threshold 15). Drivers by points: error handling 5 (10 pts), if/else 7 (9 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.
TypeInfo.checkType (cognitive 20) core/shared/utils/src/main/kotlin/viaduct/utils/invariants/ClassTypeInvariant.kt:11— TypeInfo.checkType has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FoundationFieldSelectionRule.validateField (cognitive 20) core/x/federation/validation/src/main/kotlin/viaduct/x/federation/validation/FoundationFieldSelectionRule.kt:128— FoundationFieldSelectionRule.validateField has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 6 (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.
copy_markdown._walk_nav (cognitive 20) docs/hooks/copy_markdown.py:212— copy_markdown._walk_nav has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 2 (4 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.
app.chrome (cognitive 20) core/engine/runtime2/impldocs/website/assets/app.js:78— app.chrome has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, ternaries 2 (5 pts) (nesting depth added 6). Of this number, 11 points are the body's own statements and 9 belong to 4 function items inside it that branch. 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.
SchemaConformanceKt.conformsToOutputSchemaType (cognitive 19) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/SchemaConformance.kt:64— SchemaConformanceKt.conformsToOutputSchemaType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SelectionKt.visitWhile (cognitive 19) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/Selection.kt:765— SelectionKt.visitWhile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InvariantsKt.checkMiscInvariants (cognitive 19) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/Invariants.kt:351— InvariantsKt.checkMiscInvariants has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, match/switch 2 (3 pts), loops 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.
animate.passive_resolution_spans (cognitive 19) core/engine/runtime2/impldocs/animation/animate.py:313— animate.passive_resolution_spans has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (13 pts), boolean chains 3, loops 2 (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.
app.codeHeaders (cognitive 19) core/engine/runtime2/impldocs/website/assets/app.js:338— app.codeHeaders has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 3 (6 pts), if/else 4 (5 pts) (nesting depth added 4). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 339, 366, 363). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
InspectIntrospections.inspectIntrospection (cognitive 18) core/engine/wiring/src/main/kotlin/viaduct/engine/InspectIntrospections.kt:50— InspectIntrospections.inspectIntrospection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 6, match/switch 1 (2 pts), 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.
DefinitionsDecoder.decodeAppliedDirectives (cognitive 18) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:341— DefinitionsDecoder.decodeAppliedDirectives has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 3 (7 pts), match/switch 1 (4 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.
SchemaDefinitionReconciler.semanticallyEqual (cognitive 18) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/SchemaDefinitionReconciler.kt:130— SchemaDefinitionReconciler.semanticallyEqual has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6 (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.
ViaductSchemaExtensionsKt.kmType (cognitive 18) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/config/ViaductSchemaExtensions.kt:42— ViaductSchemaExtensionsKt.kmType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate_changelog.get_commits_between_tags (cognitive 18) .github/scripts/generate_changelog.py:260— generate_changelog.get_commits_between_tags has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate.scene_times (cognitive 18) core/engine/runtime2/impldocs/website/tools/validate.py:312— validate.scene_times has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (7 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.
saved_suite_line_overlap.main (cognitive 18) core/engine/runtime2/scripts/saved_suite_line_overlap.py:67— saved_suite_line_overlap.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3, ternaries 2 (3 pts), boolean chains 2 (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.
drill.sort (cognitive 18) core/engine/runtime2/impldocs/website/assets/drill.js:78— drill.sort has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, boolean chains 5, ternaries 2 (3 pts) (nesting depth added 1). None of this is in the body itself: all 18 points belong to 9 function items inside it that branch (a function literal at line 107, a function literal at line 97, hold, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SyncEngineObjectDataFactory.unwrap (cognitive 17) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/SyncEngineObjectDataFactory.kt:198— SyncEngineObjectDataFactory.unwrap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RequiredSelectionSetGraph.computeAncestors (cognitive 17) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/tenantloading/RequiredSelectionSetGraph.kt:250— RequiredSelectionSetGraph.computeAncestors has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2, 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.
FailureCollector.containsExactlyElementsIn (cognitive 17) core/shared/invariants/src/main/kotlin/viaduct/invariants/FailureCollector.kt:486— FailureCollector.containsExactlyElementsIn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, loops 3 (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.
format_alert.main (cognitive 17) .github/scripts/format_alert.py:151— format_alert.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 2, error handling 1, 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.
validate_release_state.validate_release_state (cognitive 17) .github/scripts/validate_release_state.py:80— validate_release_state.validate_release_state has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 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.
check.generated_snapshot (cognitive 17) demoapps/plugin-compatibility/check.py:194— check.generated_snapshot has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (7 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.
app.initGlossaryPops (cognitive 17) core/engine/runtime2/impldocs/website/assets/app.js:248— app.initGlossaryPops has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 8. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 7 function items inside it that branch (out, show, a function literal at line 287, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
KeyTree.minusUncached (cognitive 16) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/mat/KeyTree.kt:44— KeyTree.minusUncached has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArgumentGroundingKt.fetchGroundWithBindings (cognitive 16) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:82— ArgumentGroundingKt.fetchGroundWithBindings has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (7 pts), if/else 5, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParentConstructionDemandKt.findParentDemandInObjectSelection (cognitive 16) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ParentConstructionDemand.kt:221— ParentConstructionDemandKt.findParentDemandInObjectSelection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3 (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.
DeferredExtensionsKt.exceptionally (cognitive 16) core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:236— DeferredExtensionsKt.exceptionally has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 3 (7 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.
TypeRemovalVisitor.maybeRemove (cognitive 16) core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/visitors/TypeRemovalVisitor.kt:47— TypeRemovalVisitor.maybeRemove has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DefinitionsDecoder.decodeExtensionListWithSupers (cognitive 16) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:459— DefinitionsDecoder.decodeExtensionListWithSupers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CharacterFormattedDescriptionResolver.resolve (cognitive 16) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterFormattedDescriptionResolver.kt:62— CharacterFormattedDescriptionResolver.resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
compare_cve_findings.parse_trivy_json (cognitive 16) .github/scripts/compare_cve_findings.py:89— compare_cve_findings.parse_trivy_json has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 2 (4 pts), loops 2 (3 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
verify_published_signatures.fetch (cognitive 16) .github/scripts/verify_published_signatures.py:131— verify_published_signatures.fetch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verify_published_signatures.main (cognitive 16) .github/scripts/verify_published_signatures.py:202— verify_published_signatures.main has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (6 pts), error handling 3 (4 pts), if/else 4, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
inspect-stacks.inspect (cognitive 16) core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-algorithms/inspect-stacks.py:33— inspect-stacks.inspect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 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.
validate.main (cognitive 16) core/engine/runtime2/impldocs/website/tools/validate.py:496— validate.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 4 (6 pts), boolean chains 2, ternaries 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.
Change-coupling hub: ViaductApplicationPlugin.kt → AssembleCentralSchemaTask.kt, ViaductJavaModulePlugin.kt, ViaductModulePlugin.kt, GenerateResolverBasesTask.kt gradle-plugins/application/src/main/kotlin/viaduct/gradle/ViaductApplicationPlugin.kt— `gradle-plugins/application/src/main/kotlin/viaduct/gradle/ViaductApplicationPlugin.kt` changes together with 4 other files — `gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/task/AssembleCentralSchemaTask.kt`, `gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/ViaductJavaModulePlugin.kt`, `gradle-plugins/module/src/main/kotlin/viaduct/gradle/ViaductModulePlugin.kt`, `gradle-plugins/module/src/main/kotlin/viaduct/gradle/task/GenerateResolverBasesTask.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Near-duplicate member pair (53 shared lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:178— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:178-262 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:124-192 — These two members are variants of one another: 53 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:150— build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:150-164 | build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:169-183 | build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:102-116 | build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:121-135 — 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:45— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:45-80 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ArgumentGrounding.kt:85-120 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:333— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:333-379 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:383-427 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:170— core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:170-234 | core/shared/deferred/src/main/kotlin/viaduct/deferred/DeferredExtensions.kt:274-340 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:195— core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:195-228 | core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:238-269 | core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:286-317 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:272— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:272-312 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:314-357 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:424— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:424-457 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:463-511 — 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:159— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:159-195 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/ksp/ResolverParamsExtractor.kt:216-264 — 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/SuccessorDemand.kt:324— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/SuccessorDemand.kt:324-353 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/SuccessorDemand.kt:474-496 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:252— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputBuilderGen.kt:252-282 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ObjectBuilderGen.kt:194-221 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 25+ corresponding lines) · ×1
Edited copies of one member (5 members, 25+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:88— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:88-113 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:121-145 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:147-172 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:181-209 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt:211-239 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:244— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:244-271 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:276-301 — 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/ResolverSupport.kt:209— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/ResolverSupport.kt:209-237 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/ResolverSupport.kt:239-271 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/task/GenerateJavaGRTSourcesTask.kt:43— gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/task/GenerateJavaGRTSourcesTask.kt:43-72 | gradle-plugins/module-java/src/main/kotlin/viaduct/gradle/task/GenerateJavaResolverBasesTask.kt:52-84 — 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, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/SchemaWithData.kt:332— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/SchemaWithData.kt:332-353 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/SchemaWithData.kt:399-421 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/SchemaWithData.kt:481-505 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:144— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:144-170 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:221-252 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:397-426 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:148— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:148-168 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:267-287 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:344-364 — 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 copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterHomeworldResolver.kt:59— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterHomeworldResolver.kt:59-88 | demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterSpeciesResolver.kt:33-56 — 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 copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:197— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:197-207 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:290-300 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:367-376 — 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 (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterNodeResolver.kt:27— demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/resolvers/CharacterNodeResolver.kt:27-46 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/resolvers/PlanetNodeResolver.kt:25-44 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/queries/SpeciesNodeQueryResolver.kt:24-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:187— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:187-213 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaExtraDiff.kt:218-242 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:245— core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:245-256 | core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:280-292 | core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:329-340 — 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 copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputGen.kt:299— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/InputGen.kt:299-320 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/ObjectGen.kt:533-554 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:414— core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:414-440 | core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:442-465 | core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt:480-502 — 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 (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/queries/AllCharactersQueryResolver.java:27— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/queries/AllCharactersQueryResolver.java:27-36 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/queries/AllFilmsQueryResolver.java:27-36 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/queries/AllPlanetsQueryResolver.java:27-36 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/queries/AllSpeciesQueryResolver.java:27-36 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/queries/AllStarshipsQueryResolver.java:27-36 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/queries/AllVehiclesQueryResolver.java:27-36 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 5+ corresponding lines) · ×1
Edited copies of one member (4 members, 5+ corresponding lines) demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/resolvers/SpeciesCulturalNotesResolver.java:23— demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/resolvers/SpeciesCulturalNotesResolver.java:23-27 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/resolvers/SpeciesRarityLevelResolver.java:23-27 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/resolvers/SpeciesSpecialAbilitiesResolver.java:24-28 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/resolvers/SpeciesTechnologicalLevelResolver.java:23-27 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/resolvers/SpeciesCulturalNotesResolver.kt:21— demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/resolvers/SpeciesCulturalNotesResolver.kt:21-27 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/resolvers/SpeciesRarityLevelResolver.kt:21-27 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/resolvers/SpeciesSpecialAbilitiesResolver.kt:21-27 | demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/resolvers/SpeciesTechnologicalLevelResolver.kt:21-27 — 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 (6 members, 3+ corresponding lines) · ×1
Edited copies of one member (6 members, 3+ corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterRepository.java:46— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/CharacterRepository.java:46-51 | demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/models/FilmsRepository.java:67-69 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/models/PlanetsRepository.java:75-77 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/species/models/SpeciesRepository.java:55-57 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/StarshipsRepository.java:46-48 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/VehiclesRepository.java:29-31 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/FieldModel.java:87— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/FieldModel.java:87-103 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/ResolverModel.java:134-150 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/starships/models/Starship.java:38-56 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/vehicles/models/Vehicle.java:34-50 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmCastDataResolver.java:23— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/films/resolvers/FilmCastDataResolver.java:23-27 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/resolvers/PlanetDataSourceResolver.java:23-26 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (37 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:215— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:215-251 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt:145-181 — before extracting anything, compare `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt` and `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/TypeCheckerTask.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 `core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldCheckerTask.kt:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:277— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:277-301 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:319-343 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ToGraphQLSchema.kt:277` 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 (22 lines × 2) core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:239— core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:239-260 | core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:287-308 — 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 `core/shared/codegen/src/main/kotlin/viaduct/codegen/km/ctdiff/ClassDiff.kt:239` 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 `actual` to `List<MethodInfo>` in one and `List<ConstructorInfo>` 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 (19 lines × 2) core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/FieldBatchResolverExecutorImpl.kt:139— core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/FieldBatchResolverExecutorImpl.kt:139-157 | core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/JavaFieldResolverExecutorImpl.kt:174-192 — 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 (15–17 lines × 2) core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/GRTClassFilesBuilderBase.kt:93— core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/GRTClassFilesBuilderBase.kt:93-109 | core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/kotlingen/bytecode/KotlinGRTFilesBuilder.kt:76-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/bytecode/GRTClassFilesBuilderBase.kt:93` 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 (16 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:364— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:364-379 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:412-427 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt:364` 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–12 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:79— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:79-90 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.kt:117-127 — 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 `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/extensions/ToRegistry.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.
Duplicated block (10–11 lines × 2) core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt:337— core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt:337-347 | core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ConstructionDemandClosure.kt:410-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 4) build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:151— build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:151-160 | build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:170-179 | build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:103-112 | build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt:122-131 — 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 `build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt:151` 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–10 lines × 2) core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:583— core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:583-588 | core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/ProjectedEngineSelectionSet.kt:109-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/select/EngineSelectionSetImpl.kt:583` 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 × 3) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:228— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:228-233 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:246-251 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/binary/DefinitionsDecoder.kt:277-282 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23 lines × 2) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ArgumentBuilder.kt:16— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ArgumentBuilder.kt:16-38 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputFieldBuilder.kt:14-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 3) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ArgumentBuilder.kt:16— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ArgumentBuilder.kt:16-38 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/EnumValueBuilder.kt:12-29 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputFieldBuilder.kt:14-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (27 lines × 3) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputObjectTypeBuilder.kt:13— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputObjectTypeBuilder.kt:13-39 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt:14-45 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt:14-45 — before extracting anything, compare `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt` and `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 128 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 (14 lines × 6) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputObjectTypeBuilder.kt:13— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputObjectTypeBuilder.kt:13-39 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InputObjectTypeExtensionBuilder.kt:12-25 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt:14-45 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeExtensionBuilder.kt:13-31 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt:14-45 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeExtensionBuilder.kt:13-31 — before extracting anything, compare `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt` and `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 4) core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt:14— core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt:14-45 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeExtensionBuilder.kt:13-31 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt:14-45 | core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeExtensionBuilder.kt:13-31 — before extracting anything, compare `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/InterfaceTypeBuilder.kt` and `core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ObjectTypeBuilder.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–14 lines × 2) core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:386— core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:386-396 | core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.java:749-762 — 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 (27 lines × 2) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/FilmArchiveClient.java:1— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/FilmArchiveClient.java:1-27 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/UniverseCatalogClient.java:1-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/FilmArchiveClient.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 (15 lines × 2) demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/Character.java:30— demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/Character.java:30-44 | demoapps/starwars-java/modules/universe/src/main/java/com/example/starwars/modules/universe/planets/models/Planet.java:30-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `demoapps/starwars-java/modules/filmography/src/main/java/com/example/starwars/modules/filmography/characters/models/Character.java:30` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–13 lines × 2) .github/scripts/validate_release_inputs.py:140— .github/scripts/validate_release_inputs.py:140-152 | .github/scripts/validate_release_state.py:217-228 — 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 `.github/scripts/validate_release_inputs.py:140` 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 (14 lines × 3) core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-algorithms/analyze.py:5— core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-algorithms/analyze.py:5-18 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-demand/analyze.py:5-18 | core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-replay/analyze.py:5-18 — `core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-algorithms/analyze.py` and `core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-demand/analyze.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/runtime2/impldocs/evidence/profiles/2026-10-24-validation-algorithms/analyze.py:5` 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· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:87— core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:87-97 | core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt:86-96 | core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/ViaductSchemaBenchmark.kt:115-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (15 lines × 3) core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/correctresolution/CorrectResolutionBenchmark.kt:90— core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/correctresolution/CorrectResolutionBenchmark.kt:90-104 | core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/resolution/PropertyTestBenchmark.kt:77-91 | core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/resolution/ResolverBenchmark.kt:127-141 — 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. 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) core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:90— core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:90-97 | core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt:89-96 | core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/ViaductSchemaBenchmark.kt:118-125 — before extracting anything, compare `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt` and `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema5Benchmark.kt` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 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 `core/shared/viaductschema/src/jmh/kotlin/viaduct/graphql/schema/LargeSchema4Benchmark.kt:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Off the main sequence: gradletestapps:validation-rule-support — gradletestapps:validation-rule-support: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
P12 · CI test-gate honesty· Test failure does not fail the CI gate · ×1
Test failure does not fail the CI gate REDACTED:274— `./gradlew -p core testCodeCoverageVerification --no-configuration-cache --scan || {` runs the tests, and `|| {` discards their exit status — a failing suite leaves the check green. Let the test command's failure fail the step (re-raise it after logging).
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: loadJSX core/service/wiring/src/main/resources/graphiql/js/jsx-loader.js:6— `loadJSX` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Swallowed exception (empty catch) core/engine/runtime2/impldocs/animation/assets/theme.js:7— 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.
Duplicated predicate core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaGRTGenerator.java:90— `!packageDir.exists() && !packageDir.mkdirs()` appears character-identically in 3 files — core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaGRTGenerator.java, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaNodeResolverGenerator.java, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaResolverGenerator.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 core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/FieldModel.java:314— `compositeType || enumType || abstractType` appears character-identically in 2 files — core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/FieldModel.java, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/GraphQLSchemaParser.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 core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/EnumModel.java:27— `description != null && !description.isEmpty()` appears character-identically in 5 files — core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/EnumModel.java, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/InputModel.java, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/InterfaceModel.java, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/ObjectModel.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 core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/LocalLoopsGrowthProbe.java:23— `m.getName().equals("create$default")&&m.getParameterCount()==8` appears character-identically in 2 files — core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/LocalLoopsGrowthProbe.java, core/engine/runtime2/impldocs/evidence/profiles/2026-10-09-input-preparation/MaterializeGrowthProbe.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 core/engine/runtime2/impldocs/animation/assets/motion.js:129— `a.tin !== null && el.dataset.keep === undefined` appears character-identically in 2 files — core/engine/runtime2/impldocs/animation/assets/motion.js, core/engine/runtime2/impldocs/website/assets/motion.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/impldocs/animation/assets/motion.js:419— `curBeat >= beats.length - 1 && t >= D - 0.02` appears character-identically in 2 files — core/engine/runtime2/impldocs/animation/assets/motion.js, core/engine/runtime2/impldocs/website/assets/motion.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/impldocs/animation/assets/motion.js:511— `e.target.closest("input") || e.altKey || e.ctrlKey || e.metaKey` appears character-identically in 2 files — core/engine/runtime2/impldocs/animation/assets/motion.js, core/engine/runtime2/impldocs/website/assets/motion.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/impldocs/animation/assets/motion.js:304— `fig.dataset.duration || String(lastAt + 3)` appears character-identically in 2 files — core/engine/runtime2/impldocs/animation/assets/motion.js, core/engine/runtime2/impldocs/website/assets/motion.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/impldocs/website/assets/app.js:373— `navigator.clipboard && navigator.clipboard.writeText` appears character-identically in 2 files — core/engine/runtime2/impldocs/website/assets/app.js, core/service/wiring/src/main/resources/graphiql/js/global-id-plugin.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/impldocs/animation/assets/motion.js:447— `reduced && autoBox.checked && beats.length` appears character-identically in 2 files — core/engine/runtime2/impldocs/animation/assets/motion.js, core/engine/runtime2/impldocs/website/assets/motion.js. 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 build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:19— `!isGradleScript || node.elementType != CALL_EXPRESSION` appears character-identically in 4 files — build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt, build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt, build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/NoPrintlnInGradleRule.kt, build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/NoStringDependenciesInGradleRule.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/ResolverSelectionProjector.kt:147— `(!topLevel || resolverType != ResolverType.NODE) && isBoundary(type.name)` appears character-identically in 2 files — core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/ResolverSelectionProjector.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/Runtime2ResolverSelectionProjector.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/FieldBatchResolverExecutorImpl.kt:140— `argumentsClass == null || Arguments.isNoArgumentsClass(argumentsClass)` appears character-identically in 3 files — core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/FieldBatchResolverExecutorImpl.kt, core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/JavaFieldResolverExecutorImpl.kt, core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/VariablesProviderExecutorImpl.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/GraphQLDocuments.kt:522— `canInull && rs.sampleWeight(cfg[ImplicitNullValueWeight])` appears character-identically in 2 files — core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/GraphQLDocuments.kt, core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/GraphQLExecutionInputs.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ParentConstructionDemand.kt:239— `checked && inclusionCondition !== InclusionCondition.Never` appears character-identically in 2 files — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/ParentConstructionDemand.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/SuccessorDemand.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/PrecomputedParentConstructionDemand.kt:185— `checked && selection.inclusionCondition !== InclusionCondition.Never` appears character-identically in 2 files — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/PrecomputedParentConstructionDemand.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/SuccessorDemand.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt:54— `current is KtCallExpression && current.calleeExpression?.text == "dependencies"` appears character-identically in 2 files — build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/CoroutinesDependencyUsageRule.kt, build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldResolutionLogic.kt:94— `definition.definition == VariableDefinition.FromProvider || definition.definition is VariableDefinition.FromArgument` appears character-identically in 2 files — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldResolutionLogic.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/FieldResolverTask.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/NodeBatchResolverExecutorImpl.kt:107— `e is PassthroughException || e is ErroneousFieldException` appears character-identically in 3 files — core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/NodeBatchResolverExecutorImpl.kt, core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/FieldBatchResolverExecutorImpl.kt, core/tenant/runtime/src/main/kotlin/viaduct/tenant/runtime/execution/NodeBatchResolverExecutorImpl.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/CheckerVariablesExtraction.kt:181— `existing == null || existing == definition` appears character-identically in 2 files — core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/CheckerVariablesExtraction.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt:263— `hasAppliedDirective(TENANT_LOCAL_DIRECTIVE_NAME) || hasAppliedDirective(PARENT_DIRECTIVE_NAME) || type.baseTypeDef.name == BACKING_DATA_SCAL…` appears character-identically in 2 files — core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt, core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/graphql/schema/ScopeAndTenantLocalSchemaFilter.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/MaterializeSelection.kt:66— `key.field.type.baseTypeDef is ViaductSchema.CompositeTypeDef || subselections.isEmpty()` appears character-identically in 3 files — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/MaterializeSelection.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/MutationSelectionForest.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/Selection.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/PrecomputedParentConstructionDemand.kt:188— `nested !== PreparedParentDemand.EMPTY || fixed !== PreparedParentDemand.EMPTY` appears character-identically in 2 files — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/PrecomputedParentConstructionDemand.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/SuccessorDemand.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/TestDataGen.kt:325— `node.name == Directives.SkipDirective.name || node.name == Directives.IncludeDirective.name` appears character-identically in 2 files — core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/TestDataGen.kt, core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/tenantloading/FromFieldVariablesAreNotConditions.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/FromArgument.kt:20— `nullableTraversal || sourceType.isNullable` appears character-identically in 2 files — core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/FromArgument.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/FromField.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 19 significant file(s) lose their only recent owner: core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductDescriptor.kt, core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ArbIR.kt, core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ResolverValueGen.kt, core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/WorkGraph.kt, core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ArbIRResult.kt, core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/Defer.kt, core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/VariablesResolvers.kt, core/shared/arbitrary/src/main/kotlin/viaduct/arbitrary/graphql/ViaductSchemas.kt (+11 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 15 significant file(s) lose their only recent owner: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/Selection.kt, core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GraphQLSchemaDecoder.kt, core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/builder/ViaductSchemaBuilderFilteredCopy.kt, core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/TypeDefinitionRegistryDecoder.kt, core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/GJSchemaCheck.kt, core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/graphqljava/ValueConverter.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/Arguments.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/resolution/framework/MutationOrchestrationTask.kt (+7 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 16 significant file(s) lose their only recent owner: core/javaapi/api/src/main/java/viaduct/java/api/internal/ConnectionBuilder.java, core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaResolverParamsExtractor.kt, core/shared/codegen/src/main/kotlin/viaduct/codegen/SchemaAnalysis.kt, core/javaapi/codegen/src/main/kotlin/viaduct/x/javaapi/codegen/cli/JavaGRTsGenerator.kt, core/javaapi/registry-apt/src/main/kotlin/viaduct/java/registry/apt/JavaRegistryExtractorProcessor.kt, core/javaapi/runtime/src/main/kotlin/viaduct/java/runtime/bridge/RequiredSelectionSetFactory.kt, core/javaapi/codegen/src/main/java/viaduct/x/javaapi/codegen/JavaResolversCodegen.java, core/engine/api/src/main/kotlin/viaduct/engine/api/bootstrap/executionregistry/RequiredSelectionSetSupport.kt (+8 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 6 significant file(s) lose their only recent owner: core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/execution/Runtime2WiringFactory.kt, core/shared/viaductschema/src/main/kotlin/viaduct/graphql/schema/validation/rules/ScopeDirectivesRule.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/registry/FieldResolverDefinition.kt, core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/ViaductModernGJInstrumentation.kt, core/shared/graphql/src/main/kotlin/viaduct/graphql/scopes/utils/Utils.kt, core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/model/ScalarValues.kt. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 4 significant file(s) lose their only recent owner: core/shared/dataloader/src/main/kotlin/viaduct/dataloader/NextTickDispatcher.kt, core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/RemoteResolverStreamClient.kt, core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/CallbackDispatcher.kt, core/x/remoteresolvers/lib/src/main/kotlin/viaduct/remote/api/spi/RemoteDispatchInstrumentation.kt. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: core/shared/codegen/src/main/kotlin/viaduct/codegen/km/KmPropertyBuilder.kt, core/shared/dataloader/src/main/kotlin/viaduct/dataloader/ChainedDataLoaderInstrumentation.kt, core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/ForbiddenSelectionDirectiveChecker.kt. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 3 significant file(s) lose their only recent owner: core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForProperties.kt, core/shared/utils/src/main/kotlin/viaduct/utils/memoize/Memoize.kt, core/shared/utils/src/main/kotlin/viaduct/utils/memoize/IdentityKeys.kt. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #8 — If anonymized user #8 becomes unavailable, 3 significant file(s) lose their only recent owner: demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/queries/AllSpeciesConnectionQueryResolver.kt, core/tenant/codegen/src/main/kotlin/viaduct/tenant/codegen/cli/FragmentSpreadCollector.kt, core/service/runtime/src/main/kotlin/viaduct/service/runtime/builtinresolvers/BuiltInModuleConfigSources.kt. Pair on, review, or document these before any departure.
Orphaned file build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.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 demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterRepository.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 build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/NoStringDependenciesInGradleRule.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 core/engine/wiring/src/main/kotlin/viaduct/engine/InspectIntrospections.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 build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.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 demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/models/PlanetsRepository.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 demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/models/SpeciesRepository.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 core/engine/wiring/src/main/kotlin/viaduct/engine/IntrospectionRestrictingPreparsedDocumentProvider.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.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×5
Projects may be oversized for their cohesion core/engine/runtime2/build.gradle.kts:1— `core/engine/runtime2` (25698 LoC, 435 module-visible types across 29 directories) overshoots its size bounds. 5 of 77 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.8/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion core/engine/runtime/build.gradle.kts:1— `core/engine/runtime` (21419 LoC, 429 module-visible types across 16 directories) overshoots its size bounds. 5 of 77 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.8/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion core/shared/arbitrary/build.gradle.kts:1— `core/shared/arbitrary` (8406 LoC, 275 module-visible types across 2 directories) overshoots its size bounds. 5 of 77 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.8/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion core/shared/viaductschema/build.gradle.kts:1— `core/shared/viaductschema` (13296 LoC, 272 module-visible types across 9 directories) overshoots its size bounds. 5 of 77 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.8/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion core/tenant/api/build.gradle.kts:1— `core/tenant/api` (5207 LoC, 138 module-visible types across 14 directories) overshoots its size bounds. 5 of 77 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.8/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.
Silent fallback default on parse failure .github/scripts/format_alert.py:56— `format_attempt_label` returns `''` when `(TypeError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure .github/scripts/report_retried_tests.py:53— `ran_before` returns `False` when `(ValueError, TypeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Fat interface: EngineSelectionSet (17 abstract methods) core/engine/api/src/main/kotlin/viaduct/engine/api/EngineSelectionSet.kt:30— `EngineSelectionSet` declares 17 abstract methods: `selections`, `traversableSelections`, `toSelectionSet`, `addVariables`, `toFragment`, `toNodelikeSelectionSet`, `printAsFieldSet`, `containsField`, `containsSelection`, `resolveSelection`, `requestsType`, `selectionSetForField`, `selectionSetForSelection`, `selectionSetForType`, `isEmpty`, `isTransitivelyEmpty`, `argumentsOfSelection`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 6 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 (78 single-owned of 680 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; 680 of the 1526 production source files in this repository met that bar). They are anonymized user #9 (2 file(s)), anonymized user #10 (2 file(s)), anonymized user #11 (2 file(s)), anonymized user #12 (1 file(s)), anonymized user #13 (1 file(s)), anonymized user #14 (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: core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/KmToCtForEnum.kt, core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/tenantloading/FromFieldVariablesAreNotConditions.kt, core/shared/utils/src/jmh/kotlin/viaduct/utils/collections/CacheKeyLookupBenchmark.kt, core/shared/codegen/src/main/kotlin/viaduct/codegen/ct/CtGenContext.kt, build-logic/src/main/kotlin/buildroot/OrchestrationRegistryService.kt, build-logic/src/main/kotlin/conventions/JacocoCoverageData.kt, build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/InvalidDependencyRule.kt, core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/tenantloading/MissingResolverValidator.kt (+1 more).
No ADRs found demoapps/starwars-java/build.gradle.kts:49— 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 `demoapps/starwars-java/build.gradle.kts` makes this repository a deployable product (line 49).
D21 · Naming Consistency· `resolveRSSVariables` spells `RSS` where 26 names in the project spell it `Rss` · ×1
`resolveRSSVariables` spells `RSS` where 26 names in the project spell it `Rss` core/engine/runtime/src/main/kotlin/viaduct/engine/runtime/execution/FieldExecutionHelpers.kt:630— 26 of 27 names in project core/engine/runtime spell the token `Rss` (26 of 27; unit: names in project core/engine/runtime containing `Rss`). Peers: viaduct.engine.runtime.execution.QueryPlanBenchmark.WideRssFixture (core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/QueryPlanBenchmark.kt:53); viaduct.engine.runtime.execution.QueryPlanBenchmark.DeepRssFixture (core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/QueryPlanBenchmark.kt:69); viaduct.engine.runtime.execution.QueryPlanBenchmark.ChainedRssFixture (core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/QueryPlanBenchmark.kt:85); QueryPlanBenchmark.wideRssChildren (core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/QueryPlanBenchmark.kt:188); QueryPlanBenchmark.deepRssChildren (core/engine/runtime/src/jmh/kotlin/viaduct/engine/runtime/execution/QueryPlanBenchmark.kt:196). Rename to `resolveRssVariables`. [rule N6]
D21 · Naming Consistency· `globalIDCodec` spells `ID` where 55 names in the project spell it `Id` · ×1
`globalIDCodec` spells `ID` where 55 names in the project spell it `Id` core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/Engine2.kt:79— 55 of 57 names in project runtime2 spell the token `Id` (55 of 57; unit: names in project runtime2 containing `Id`). Peers: ResolverBenchmarkInvocationObservation.resolverOccurrenceId (core/engine/runtime2/src/jmh/kotlin/viaduct/engine/runtime2/benchmark/CurrentProfileBenchmarkSupport.kt:68); DispatcherFieldExecutor.resolverId (core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt:856); ExecutorRegistryInputsKt.nodeReference(globalId) (core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ExecutorRegistryInputs.kt:1024); NodeResolverLowering.validateNodeIdField (core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/bootstrap/ResolverRegistryImpl.kt:354); Runtime2RequestLifetimeKey.executionId (core/engine/runtime2/src/main/kotlin/viaduct/engine/runtime2/execution/Runtime2ExecutionStrategy.kt:250). Rename to `globalIdCodec`. [rule N6]
D21 · Naming Consistency· `getId` spells `Id` where 18 names in the project spell it `ID` · ×1
`getId` spells `Id` where 18 names in the project spell it `ID` core/javaapi/api/src/main/java/viaduct/java/api/context/NodeExecutionContext.java:19— 18 of 19 names in project core/javaapi/api spell the token `ID` (18 of 19; unit: names in project core/javaapi/api containing `ID`). Peers: ExecutionContext.globalIDFor (core/javaapi/api/src/main/java/viaduct/java/api/context/ExecutionContext.java:14); ExecutionContext.globalIDFor(internalID) (core/javaapi/api/src/main/java/viaduct/java/api/context/ExecutionContext.java:14); ExecutionContext.serialize(globalID) (core/javaapi/api/src/main/java/viaduct/java/api/context/ExecutionContext.java:16); ResolverExecutionContext.globalIDStringFor (core/javaapi/api/src/main/java/viaduct/java/api/context/ResolverExecutionContext.java:61); ResolverExecutionContext.globalIDStringFor(internalID) (core/javaapi/api/src/main/java/viaduct/java/api/context/ResolverExecutionContext.java:61). Rename to `getID`. [rule N6]
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 8 of 680 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; 680 of the 1526 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: build-logic/common/src/main/kotlin/detekt/ApiStabilityAnnotationRequiredRule.kt, demoapps/starwars/modules/filmography/src/main/kotlin/com/example/starwars/modules/filmography/characters/models/CharacterRepository.kt, build-logic/gradle-only/ktlint/src/main/kotlin/ktlint/NoStringDependenciesInGradleRule.kt, core/engine/wiring/src/main/kotlin/viaduct/engine/InspectIntrospections.kt, build-logic/common/src/main/kotlin/detekt/FactoryMethodNamingRule.kt, demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/planets/models/PlanetsRepository.kt, demoapps/starwars/modules/universe/src/main/kotlin/com/example/starwars/modules/universe/species/models/SpeciesRepository.kt, core/engine/wiring/src/main/kotlin/viaduct/engine/IntrospectionRestrictingPreparsedDocumentProvider.kt. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift core/engine/runtime2/impldocs/evidence/profiles/2026-09-27-f5-field-checks/README.md:39— core/engine/runtime2/impldocs/evidence/profiles/2026-09-27-f5-field-checks/README.md links to `../../../../src/support/kotlin/viaduct/engine/runtime2/resolvers/resolver23/Resolver.kt`, but `core/engine/runtime2/src/support/kotlin/viaduct/engine/runtime2/resolvers/resolver23/Resolver.kt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 20/29 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `core/engine/runtime2`, `core/javaapi/codegen`, `core/shared/arbitrary-cli`, `core/tenant/codegen` and 4 more.
No SAST .github/workflows/ci-trigger.yml:7— 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 18 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation core/engine/runtime2/impldocs/graphql-spec/package.json:4— `core/engine/runtime2/impldocs/graphql-spec/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted gradle-plugins/conventions/src/main/kotlin/viaduct/gradle/ViaductSchemaValidator.kt:90— `debug` at line 90 is called with an argument built by `schemaFiles.joinToString("…")` (line 90), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on.
Hand-rolled JSON/XML parsing via regex core/engine/runtime2/impldocs/website/assets/app.js:198— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 88 file(s) — `core/engine/api/src/main/kotlin/viaduct/engine/api/InputValueReader.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/ParentManagedValue.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/StandardResolutionValue.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/bootstrap/executionregistry/ModuleConfigFactory.kt`, `core/engine/api/src/main/kotlin/viaduct/engine/api/instrumentation/resolver/ViaductResolverInstrumentation.kt`, … (+83 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e4e8-3602-76ca-941a-bb49790bc2b3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 191 · Warnings: 488 · Recommendations: 82 · Info: 45 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 15:09 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.