Public report of aehrc/pathling, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 05:17 UTC · Survey ID cd_7934357d139d47189a2e9ce7b8f8ac93
aehrc/pathling
Measured 17 November 2026, 05:14 UTC, at code version 33f98f7
First survey, so nothing to compare with yet
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 121,308 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 2.1 person-years · Weakest lens: Accessibility, 52.2
Findings by how serious they are
214 critical622 serious421 minor
12 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 05:14 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
82of 82 dimensions measured by tools.
979of 1257 findings point to an exact file and line, so you can open each one in the code. The other 278 concern the repository as a whole, such as missing documentation.
82dimensions across 7 lenses, read from 121,308 lines of product code in 12 projects.
aehrc/pathling is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has pages that don't say their language. It scores 59.3 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 52.2, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two packages under a banned licence, worth about 3.2 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 5.6 points. Raising Accessibility to 70 would lift the score to about 64.6.
113 known security holes in the packages the code depends on can be used by attackers. Seventy-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and five secrets can leak from the build pipeline. Updating the vulnerable packages, 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 pipeline step that puts outside input straight into a shell command, and the five unsafe settings in infrastructure or container files need changing to safe values. The four buttons or links with no name need a name, even when they only show an icon.
The product code is 121,308 lines, about €300,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 Accessibility rose from 52.2 to 70, the lowest score rated Strong, the score would rise from 59.3 to about 64.6.
Code composition: what the lines of code are
Product code 43%Tests 57%
Rebuild cost: about €300,000 · Estimate
Cost to rebuild
€99,000 to €500,000, for 1,652 to 5,240 hours of work, about 2.1 person-years for 1 to 4 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.8 at a score of 59. 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: 121,308 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 2 Banned license finding(s) in License Compliance.
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 5.6 points · Medium effort · Keyboard semantics
3
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 3.0 points · Medium effort · Page structure
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €300,000 to build again, about 2.1 person-years of work. Its weakest lens is Accessibility, at 52.2 (Adequate). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 3.2 points for low effort, because it clears the 2 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
221 modules, with 384 dependencies between them. 2 loops run through 52 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 181 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.
au.csiro.pathling.encoders uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.encoders, while a change to au.csiro.pathling.encoders can't break au.csiro.pathling.config.
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.
au.csiro.pathling.fhirpath.column uses au.csiro.pathling.fhirpath.definition, so a change to au.csiro.pathling.fhirpath.definition can break au.csiro.pathling.fhirpath.column, while a change to au.csiro.pathling.fhirpath.column can't break au.csiro.pathling.fhirpath.definition.
Position
Below the diagonal: au.csiro.pathling.fhirpath.column uses a module listed above it, which is the healthy direction.
8→13 au.csiro.pathling.fhirpath.function uses au.csiro.pathling.fhirpath.collectionpart of a loop✕
Connections
4 pairs of types, where a type in au.csiro.pathling.fhirpath.function uses a type in au.csiro.pathling.fhirpath.collection.
au.csiro.pathling.fhirpath.function uses au.csiro.pathling.fhirpath.collection, so a change to au.csiro.pathling.fhirpath.collection can break au.csiro.pathling.fhirpath.function, while a change to au.csiro.pathling.fhirpath.function can't break au.csiro.pathling.fhirpath.collection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→14 au.csiro.pathling.fhirpath.function uses au.csiro.pathling.fhirpathpart of a loop✕
Connections
2 pairs of types, where a type in au.csiro.pathling.fhirpath.function uses a type in au.csiro.pathling.fhirpath.
au.csiro.pathling.fhirpath.function uses au.csiro.pathling.fhirpath, so a change to au.csiro.pathling.fhirpath can break au.csiro.pathling.fhirpath.function, while a change to au.csiro.pathling.fhirpath.function can't break au.csiro.pathling.fhirpath.
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.
au.csiro.pathling.library.io.sink uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.library.io.sink, while a change to au.csiro.pathling.library.io.sink can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.library.io.sink uses a module listed above it, which is the healthy direction.
9→28 au.csiro.pathling.library.io.sink uses au.csiro.pathling.librarypart of a loop✕
Connections
5 pairs of types, where a type in au.csiro.pathling.library.io.sink uses a type in au.csiro.pathling.library.
au.csiro.pathling.library.io.sink uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.library.io.sink, while a change to au.csiro.pathling.library.io.sink can't break au.csiro.pathling.library.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ui.src.api uses ui.src.api.sqlOnFhirOperations, so a change to ui.src.api.sqlOnFhirOperations can break ui.src.api, while a change to ui.src.api can't break ui.src.api.sqlOnFhirOperations.
Position
Below the diagonal: ui.src.api uses a module listed above it, which is the healthy direction.
ui.src.components.sqlOnFhir uses ui.src.api.sqlOnFhirOperations, so a change to ui.src.api.sqlOnFhirOperations can break ui.src.components.sqlOnFhir, while a change to ui.src.components.sqlOnFhir can't break ui.src.api.sqlOnFhirOperations.
Position
Below the diagonal: ui.src.components.sqlOnFhir uses a module listed above it, which is the healthy direction.
ui.src.hooks uses ui.src.api.sqlOnFhirOperations, so a change to ui.src.api.sqlOnFhirOperations can break ui.src.hooks, while a change to ui.src.hooks can't break ui.src.api.sqlOnFhirOperations.
Position
Below the diagonal: ui.src.hooks uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.collection uses au.csiro.pathling.fhirpath.definition, so a change to au.csiro.pathling.fhirpath.definition can break au.csiro.pathling.fhirpath.collection, while a change to au.csiro.pathling.fhirpath.collection can't break au.csiro.pathling.fhirpath.definition.
Position
Below the diagonal: au.csiro.pathling.fhirpath.collection uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.collection uses au.csiro.pathling.fhirpath.column, so a change to au.csiro.pathling.fhirpath.column can break au.csiro.pathling.fhirpath.collection, while a change to au.csiro.pathling.fhirpath.collection can't break au.csiro.pathling.fhirpath.column.
Position
Below the diagonal: au.csiro.pathling.fhirpath.collection uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.collection uses au.csiro.pathling.fhirpath.function, so a change to au.csiro.pathling.fhirpath.function can break au.csiro.pathling.fhirpath.collection, while a change to au.csiro.pathling.fhirpath.collection can't break au.csiro.pathling.fhirpath.function.
Position
Below the diagonal: au.csiro.pathling.fhirpath.collection uses a module listed above it, which is the healthy direction.
13→14 au.csiro.pathling.fhirpath.collection uses au.csiro.pathling.fhirpathpart of a loop✕
Connections
49 pairs of types, where a type in au.csiro.pathling.fhirpath.collection uses a type in au.csiro.pathling.fhirpath. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
au.csiro.pathling.fhirpath.collection uses au.csiro.pathling.fhirpath, so a change to au.csiro.pathling.fhirpath can break au.csiro.pathling.fhirpath.collection, while a change to au.csiro.pathling.fhirpath.collection can't break au.csiro.pathling.fhirpath.
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.
au.csiro.pathling.fhirpath uses au.csiro.pathling.fhirpath.definition, so a change to au.csiro.pathling.fhirpath.definition can break au.csiro.pathling.fhirpath, while a change to au.csiro.pathling.fhirpath can't break au.csiro.pathling.fhirpath.definition.
Position
Below the diagonal: au.csiro.pathling.fhirpath uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath uses au.csiro.pathling.fhirpath.column, so a change to au.csiro.pathling.fhirpath.column can break au.csiro.pathling.fhirpath, while a change to au.csiro.pathling.fhirpath can't break au.csiro.pathling.fhirpath.column.
Position
Below the diagonal: au.csiro.pathling.fhirpath uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath uses au.csiro.pathling.fhirpath.function, so a change to au.csiro.pathling.fhirpath.function can break au.csiro.pathling.fhirpath, while a change to au.csiro.pathling.fhirpath can't break au.csiro.pathling.fhirpath.function.
Position
Below the diagonal: au.csiro.pathling.fhirpath uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath uses au.csiro.pathling.fhirpath.collection, so a change to au.csiro.pathling.fhirpath.collection can break au.csiro.pathling.fhirpath, while a change to au.csiro.pathling.fhirpath can't break au.csiro.pathling.fhirpath.collection.
Position
Below the diagonal: au.csiro.pathling.fhirpath uses a module listed above it, which is the healthy direction.
14→33 au.csiro.pathling.fhirpath uses au.csiro.pathling.configpart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.fhirpath uses a type in au.csiro.pathling.config.
au.csiro.pathling.fhirpath uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.fhirpath, while a change to au.csiro.pathling.fhirpath can't break au.csiro.pathling.config.
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.
au.csiro.pathling.fhirpath.encoding uses au.csiro.pathling.fhirpath, so a change to au.csiro.pathling.fhirpath can break au.csiro.pathling.fhirpath.encoding, while a change to au.csiro.pathling.fhirpath.encoding can't break au.csiro.pathling.fhirpath.
Position
Below the diagonal: au.csiro.pathling.fhirpath.encoding uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.parser uses au.csiro.pathling.fhirpath, so a change to au.csiro.pathling.fhirpath can break au.csiro.pathling.fhirpath.parser, while a change to au.csiro.pathling.fhirpath.parser can't break au.csiro.pathling.fhirpath.
Position
Below the diagonal: au.csiro.pathling.fhirpath.parser uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.fhirpath.definition, so a change to au.csiro.pathling.fhirpath.definition can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.fhirpath.definition.
Position
Below the diagonal: au.csiro.pathling.fhirpath.evaluation uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.fhirpath.evaluation uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.fhirpath.function, so a change to au.csiro.pathling.fhirpath.function can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.fhirpath.function.
Position
Below the diagonal: au.csiro.pathling.fhirpath.evaluation uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.fhirpath.collection, so a change to au.csiro.pathling.fhirpath.collection can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.fhirpath.collection.
Position
Below the diagonal: au.csiro.pathling.fhirpath.evaluation uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.fhirpath, so a change to au.csiro.pathling.fhirpath can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.fhirpath.
Position
Below the diagonal: au.csiro.pathling.fhirpath.evaluation uses a module listed above it, which is the healthy direction.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.fhirpath.parser, so a change to au.csiro.pathling.fhirpath.parser can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.fhirpath.parser.
Position
Below the diagonal: au.csiro.pathling.fhirpath.evaluation uses a module listed above it, which is the healthy direction.
17→33 au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.configpart of a loop✕
Connections
4 pairs of types, where a type in au.csiro.pathling.fhirpath.evaluation uses a type in au.csiro.pathling.config.
au.csiro.pathling.fhirpath.evaluation uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.fhirpath.evaluation, while a change to au.csiro.pathling.fhirpath.evaluation can't break au.csiro.pathling.config.
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.
au.csiro.pathling.views uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.views, while a change to au.csiro.pathling.views can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.views uses a module listed above it, which is the healthy direction.
au.csiro.pathling.views uses au.csiro.pathling.fhirpath.parser, so a change to au.csiro.pathling.fhirpath.parser can break au.csiro.pathling.views, while a change to au.csiro.pathling.views can't break au.csiro.pathling.fhirpath.parser.
Position
Below the diagonal: au.csiro.pathling.views uses a module listed above it, which is the healthy direction.
18→33 au.csiro.pathling.views uses au.csiro.pathling.configpart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.views uses a type in au.csiro.pathling.config.
au.csiro.pathling.views uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.views, while a change to au.csiro.pathling.views can't break au.csiro.pathling.config.
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.
au.csiro.pathling.search uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.search, while a change to au.csiro.pathling.search can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.search uses a module listed above it, which is the healthy direction.
au.csiro.pathling.search uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.search, while a change to au.csiro.pathling.search can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.search uses a module listed above it, which is the healthy direction.
au.csiro.pathling.search uses au.csiro.pathling.fhirpath.parser, so a change to au.csiro.pathling.fhirpath.parser can break au.csiro.pathling.search, while a change to au.csiro.pathling.search can't break au.csiro.pathling.fhirpath.parser.
Position
Below the diagonal: au.csiro.pathling.search uses a module listed above it, which is the healthy direction.
au.csiro.pathling.search uses au.csiro.pathling.fhirpath.evaluation, so a change to au.csiro.pathling.fhirpath.evaluation can break au.csiro.pathling.search, while a change to au.csiro.pathling.search can't break au.csiro.pathling.fhirpath.evaluation.
Position
Below the diagonal: au.csiro.pathling.search uses a module listed above it, which is the healthy direction.
19→22 au.csiro.pathling.search uses au.csiro.pathling.library.io.sourcepart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.search uses a type in au.csiro.pathling.library.io.source.
au.csiro.pathling.search uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.search, while a change to au.csiro.pathling.search can't break au.csiro.pathling.library.io.source.
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.
19→33 au.csiro.pathling.search uses au.csiro.pathling.configpart of a loop✕
Connections
2 pairs of types, where a type in au.csiro.pathling.search uses a type in au.csiro.pathling.config.
au.csiro.pathling.search uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.search, while a change to au.csiro.pathling.search can't break au.csiro.pathling.config.
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.
au.csiro.pathling.fhir uses au.csiro.pathling.search, so a change to au.csiro.pathling.search can break au.csiro.pathling.fhir, while a change to au.csiro.pathling.fhir can't break au.csiro.pathling.search.
Position
Below the diagonal: au.csiro.pathling.fhir uses a module listed above it, which is the healthy direction.
20→33 au.csiro.pathling.fhir uses au.csiro.pathling.configpart of a loop✕
Connections
3 pairs of types, where a type in au.csiro.pathling.fhir uses a type in au.csiro.pathling.config.
au.csiro.pathling.fhir uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.fhir, while a change to au.csiro.pathling.fhir can't break au.csiro.pathling.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→34 au.csiro.pathling.fhir uses au.csiro.pathling.cachepart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.fhir uses a type in au.csiro.pathling.cache.
au.csiro.pathling.fhir uses au.csiro.pathling.cache, so a change to au.csiro.pathling.cache can break au.csiro.pathling.fhir, while a change to au.csiro.pathling.fhir can't break au.csiro.pathling.cache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→40 au.csiro.pathling.fhir uses au.csiro.pathlingpart of a loop✕
Connections
2 pairs of types, where a type in au.csiro.pathling.fhir uses a type in au.csiro.pathling.
au.csiro.pathling.fhir uses au.csiro.pathling, so a change to au.csiro.pathling can break au.csiro.pathling.fhir, while a change to au.csiro.pathling.fhir can't break au.csiro.pathling.
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.
au.csiro.pathling.library.query uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.library.query, while a change to au.csiro.pathling.library.query can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.library.query uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library.query uses au.csiro.pathling.views, so a change to au.csiro.pathling.views can break au.csiro.pathling.library.query, while a change to au.csiro.pathling.library.query can't break au.csiro.pathling.views.
Position
Below the diagonal: au.csiro.pathling.library.query uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library.query uses au.csiro.pathling.search, so a change to au.csiro.pathling.search can break au.csiro.pathling.library.query, while a change to au.csiro.pathling.library.query can't break au.csiro.pathling.search.
Position
Below the diagonal: au.csiro.pathling.library.query uses a module listed above it, which is the healthy direction.
21→28 au.csiro.pathling.library.query uses au.csiro.pathling.librarypart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.library.query uses a type in au.csiro.pathling.library.
au.csiro.pathling.library.query uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.library.query, while a change to au.csiro.pathling.library.query can't break au.csiro.pathling.library.
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.
au.csiro.pathling.library.io.source uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.library.io.source, while a change to au.csiro.pathling.library.io.source can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.library.io.source uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library.io.source uses au.csiro.pathling.library.io.sink, so a change to au.csiro.pathling.library.io.sink can break au.csiro.pathling.library.io.source, while a change to au.csiro.pathling.library.io.source can't break au.csiro.pathling.library.io.sink.
Position
Below the diagonal: au.csiro.pathling.library.io.source uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library.io.source uses au.csiro.pathling.views, so a change to au.csiro.pathling.views can break au.csiro.pathling.library.io.source, while a change to au.csiro.pathling.library.io.source can't break au.csiro.pathling.views.
Position
Below the diagonal: au.csiro.pathling.library.io.source uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library.io.source uses au.csiro.pathling.library.query, so a change to au.csiro.pathling.library.query can break au.csiro.pathling.library.io.source, while a change to au.csiro.pathling.library.io.source can't break au.csiro.pathling.library.query.
Position
Below the diagonal: au.csiro.pathling.library.io.source uses a module listed above it, which is the healthy direction.
22→28 au.csiro.pathling.library.io.source uses au.csiro.pathling.librarypart of a loop✕
Connections
10 pairs of types, where a type in au.csiro.pathling.library.io.source uses a type in au.csiro.pathling.library.
au.csiro.pathling.library.io.source uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.library.io.source, while a change to au.csiro.pathling.library.io.source can't break au.csiro.pathling.library.
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.
au.csiro.pathling.terminology.expand uses au.csiro.pathling.fhir, so a change to au.csiro.pathling.fhir can break au.csiro.pathling.terminology.expand, while a change to au.csiro.pathling.terminology.expand can't break au.csiro.pathling.fhir.
Position
Below the diagonal: au.csiro.pathling.terminology.expand uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.compartment uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.operations.compartment, while a change to au.csiro.pathling.operations.compartment can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.compartment uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.compartment uses au.csiro.pathling.fhirpath.collection, so a change to au.csiro.pathling.fhirpath.collection can break au.csiro.pathling.operations.compartment, while a change to au.csiro.pathling.operations.compartment can't break au.csiro.pathling.fhirpath.collection.
Position
Below the diagonal: au.csiro.pathling.operations.compartment uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.compartment uses au.csiro.pathling.fhirpath.parser, so a change to au.csiro.pathling.fhirpath.parser can break au.csiro.pathling.operations.compartment, while a change to au.csiro.pathling.operations.compartment can't break au.csiro.pathling.fhirpath.parser.
Position
Below the diagonal: au.csiro.pathling.operations.compartment uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.compartment uses au.csiro.pathling.fhirpath.evaluation, so a change to au.csiro.pathling.fhirpath.evaluation can break au.csiro.pathling.operations.compartment, while a change to au.csiro.pathling.operations.compartment can't break au.csiro.pathling.fhirpath.evaluation.
Position
Below the diagonal: au.csiro.pathling.operations.compartment uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.compartment uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.operations.compartment, while a change to au.csiro.pathling.operations.compartment can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.compartment uses a module listed above it, which is the healthy direction.
au.csiro.pathling.terminology.local uses au.csiro.pathling.terminology.expand, so a change to au.csiro.pathling.terminology.expand can break au.csiro.pathling.terminology.local, while a change to au.csiro.pathling.terminology.local can't break au.csiro.pathling.terminology.expand.
Position
Below the diagonal: au.csiro.pathling.terminology.local uses a module listed above it, which is the healthy direction.
25→26 au.csiro.pathling.terminology.local uses au.csiro.pathling.terminology.conceptmappart of a loop✕
Connections
5 pairs of types, where a type in au.csiro.pathling.terminology.local uses a type in au.csiro.pathling.terminology.conceptmap.
au.csiro.pathling.terminology.local uses au.csiro.pathling.terminology.conceptmap, so a change to au.csiro.pathling.terminology.conceptmap can break au.csiro.pathling.terminology.local, while a change to au.csiro.pathling.terminology.local can't break au.csiro.pathling.terminology.conceptmap.
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.
25→27 au.csiro.pathling.terminology.local uses au.csiro.pathling.terminologypart of a loop✕
Connections
5 pairs of types, where a type in au.csiro.pathling.terminology.local uses a type in au.csiro.pathling.terminology.
au.csiro.pathling.terminology.local uses au.csiro.pathling.terminology, so a change to au.csiro.pathling.terminology can break au.csiro.pathling.terminology.local, while a change to au.csiro.pathling.terminology.local can't break au.csiro.pathling.terminology.
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.
25→33 au.csiro.pathling.terminology.local uses au.csiro.pathling.configpart of a loop✕
Connections
2 pairs of types, where a type in au.csiro.pathling.terminology.local uses a type in au.csiro.pathling.config.
au.csiro.pathling.terminology.local uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.terminology.local, while a change to au.csiro.pathling.terminology.local can't break au.csiro.pathling.config.
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.
au.csiro.pathling.terminology.conceptmap uses au.csiro.pathling.fhir, so a change to au.csiro.pathling.fhir can break au.csiro.pathling.terminology.conceptmap, while a change to au.csiro.pathling.terminology.conceptmap can't break au.csiro.pathling.fhir.
Position
Below the diagonal: au.csiro.pathling.terminology.conceptmap uses a module listed above it, which is the healthy direction.
au.csiro.pathling.terminology.conceptmap uses au.csiro.pathling.terminology.local, so a change to au.csiro.pathling.terminology.local can break au.csiro.pathling.terminology.conceptmap, while a change to au.csiro.pathling.terminology.conceptmap can't break au.csiro.pathling.terminology.local.
Position
Below the diagonal: au.csiro.pathling.terminology.conceptmap uses a module listed above it, which is the healthy direction.
au.csiro.pathling.terminology uses au.csiro.pathling.fhir, so a change to au.csiro.pathling.fhir can break au.csiro.pathling.terminology, while a change to au.csiro.pathling.terminology can't break au.csiro.pathling.fhir.
Position
Below the diagonal: au.csiro.pathling.terminology uses a module listed above it, which is the healthy direction.
au.csiro.pathling.terminology uses au.csiro.pathling.terminology.expand, so a change to au.csiro.pathling.terminology.expand can break au.csiro.pathling.terminology, while a change to au.csiro.pathling.terminology can't break au.csiro.pathling.terminology.expand.
Position
Below the diagonal: au.csiro.pathling.terminology uses a module listed above it, which is the healthy direction.
au.csiro.pathling.terminology uses au.csiro.pathling.terminology.conceptmap, so a change to au.csiro.pathling.terminology.conceptmap can break au.csiro.pathling.terminology, while a change to au.csiro.pathling.terminology can't break au.csiro.pathling.terminology.conceptmap.
Position
Below the diagonal: au.csiro.pathling.terminology uses a module listed above it, which is the healthy direction.
27→33 au.csiro.pathling.terminology uses au.csiro.pathling.configpart of a loop✕
Connections
4 pairs of types, where a type in au.csiro.pathling.terminology uses a type in au.csiro.pathling.config.
au.csiro.pathling.terminology uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.terminology, while a change to au.csiro.pathling.terminology can't break au.csiro.pathling.config.
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.
au.csiro.pathling.library uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.library, while a change to au.csiro.pathling.library can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.library uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library uses au.csiro.pathling.fhirpath.evaluation, so a change to au.csiro.pathling.fhirpath.evaluation can break au.csiro.pathling.library, while a change to au.csiro.pathling.library can't break au.csiro.pathling.fhirpath.evaluation.
Position
Below the diagonal: au.csiro.pathling.library uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.library, while a change to au.csiro.pathling.library can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.library uses a module listed above it, which is the healthy direction.
au.csiro.pathling.library uses au.csiro.pathling.terminology, so a change to au.csiro.pathling.terminology can break au.csiro.pathling.library, while a change to au.csiro.pathling.library can't break au.csiro.pathling.terminology.
Position
Below the diagonal: au.csiro.pathling.library uses a module listed above it, which is the healthy direction.
28→33 au.csiro.pathling.library uses au.csiro.pathling.configpart of a loop✕
Connections
6 pairs of types, where a type in au.csiro.pathling.library uses a type in au.csiro.pathling.config.
au.csiro.pathling.library uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.library, while a change to au.csiro.pathling.library can't break au.csiro.pathling.config.
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.
au.csiro.pathling.io uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
au.csiro.pathling.io uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
au.csiro.pathling.io uses au.csiro.pathling.library.io.sink, so a change to au.csiro.pathling.library.io.sink can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.library.io.sink.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
au.csiro.pathling.io uses au.csiro.pathling.views, so a change to au.csiro.pathling.views can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.views.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
au.csiro.pathling.io uses au.csiro.pathling.library.query, so a change to au.csiro.pathling.library.query can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.library.query.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
au.csiro.pathling.io uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
au.csiro.pathling.io uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.library.
Position
Below the diagonal: au.csiro.pathling.io uses a module listed above it, which is the healthy direction.
29→33 au.csiro.pathling.io uses au.csiro.pathling.configpart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.io uses a type in au.csiro.pathling.config.
au.csiro.pathling.io uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.io, while a change to au.csiro.pathling.io can't break au.csiro.pathling.config.
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.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.library.io.sink, so a change to au.csiro.pathling.library.io.sink can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.library.io.sink.
Position
Below the diagonal: au.csiro.pathling.operations.bulkimport uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.bulkimport uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.library.
Position
Below the diagonal: au.csiro.pathling.operations.bulkimport uses a module listed above it, which is the healthy direction.
30→33 au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.configpart of a loop✕
Connections
5 pairs of types, where a type in au.csiro.pathling.operations.bulkimport uses a type in au.csiro.pathling.config.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.config.
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.
30→34 au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.cachepart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.operations.bulkimport uses a type in au.csiro.pathling.cache.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.cache, so a change to au.csiro.pathling.cache can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.cache.
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.
30→36 au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.asyncpart of a loop✕
Connections
10 pairs of types, where a type in au.csiro.pathling.operations.bulkimport uses a type in au.csiro.pathling.async.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling.async, so a change to au.csiro.pathling.async can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.async.
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.
30→40 au.csiro.pathling.operations.bulkimport uses au.csiro.pathlingpart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.operations.bulkimport uses a type in au.csiro.pathling.
au.csiro.pathling.operations.bulkimport uses au.csiro.pathling, so a change to au.csiro.pathling can break au.csiro.pathling.operations.bulkimport, while a change to au.csiro.pathling.operations.bulkimport can't break au.csiro.pathling.
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.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.library.io.sink, so a change to au.csiro.pathling.library.io.sink can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.library.io.sink.
Position
Below the diagonal: au.csiro.pathling.operations.bulkexport uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.bulkexport uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.operations.compartment, so a change to au.csiro.pathling.operations.compartment can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.operations.compartment.
Position
Below the diagonal: au.csiro.pathling.operations.bulkexport uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.library.
Position
Below the diagonal: au.csiro.pathling.operations.bulkexport uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.io, so a change to au.csiro.pathling.io can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.io.
Position
Below the diagonal: au.csiro.pathling.operations.bulkexport uses a module listed above it, which is the healthy direction.
31→33 au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.configpart of a loop✕
Connections
4 pairs of types, where a type in au.csiro.pathling.operations.bulkexport uses a type in au.csiro.pathling.config.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→36 au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.asyncpart of a loop✕
Connections
9 pairs of types, where a type in au.csiro.pathling.operations.bulkexport uses a type in au.csiro.pathling.async.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling.async, so a change to au.csiro.pathling.async can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.async.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→40 au.csiro.pathling.operations.bulkexport uses au.csiro.pathlingpart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.operations.bulkexport uses a type in au.csiro.pathling.
au.csiro.pathling.operations.bulkexport uses au.csiro.pathling, so a change to au.csiro.pathling can break au.csiro.pathling.operations.bulkexport, while a change to au.csiro.pathling.operations.bulkexport can't break au.csiro.pathling.
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.
au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.io, so a change to au.csiro.pathling.io can break au.csiro.pathling.operations.bulksubmit, while a change to au.csiro.pathling.operations.bulksubmit can't break au.csiro.pathling.io.
Position
Below the diagonal: au.csiro.pathling.operations.bulksubmit uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.operations.bulkimport, so a change to au.csiro.pathling.operations.bulkimport can break au.csiro.pathling.operations.bulksubmit, while a change to au.csiro.pathling.operations.bulksubmit can't break au.csiro.pathling.operations.bulkimport.
Position
Below the diagonal: au.csiro.pathling.operations.bulksubmit uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.operations.bulkexport, so a change to au.csiro.pathling.operations.bulkexport can break au.csiro.pathling.operations.bulksubmit, while a change to au.csiro.pathling.operations.bulksubmit can't break au.csiro.pathling.operations.bulkexport.
Position
Below the diagonal: au.csiro.pathling.operations.bulksubmit uses a module listed above it, which is the healthy direction.
32→33 au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.configpart of a loop✕
Connections
5 pairs of types, where a type in au.csiro.pathling.operations.bulksubmit uses a type in au.csiro.pathling.config.
au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.bulksubmit, while a change to au.csiro.pathling.operations.bulksubmit can't break au.csiro.pathling.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→36 au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.asyncpart of a loop✕
Connections
2 pairs of types, where a type in au.csiro.pathling.operations.bulksubmit uses a type in au.csiro.pathling.async.
au.csiro.pathling.operations.bulksubmit uses au.csiro.pathling.async, so a change to au.csiro.pathling.async can break au.csiro.pathling.operations.bulksubmit, while a change to au.csiro.pathling.operations.bulksubmit can't break au.csiro.pathling.async.
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.
au.csiro.pathling.config uses au.csiro.pathling.operations.bulksubmit, so a change to au.csiro.pathling.operations.bulksubmit can break au.csiro.pathling.config, while a change to au.csiro.pathling.config can't break au.csiro.pathling.operations.bulksubmit.
Position
Below the diagonal: au.csiro.pathling.config uses a module listed above it, which is the healthy direction.
au.csiro.pathling.cache uses au.csiro.pathling.fhir, so a change to au.csiro.pathling.fhir can break au.csiro.pathling.cache, while a change to au.csiro.pathling.cache can't break au.csiro.pathling.fhir.
Position
Below the diagonal: au.csiro.pathling.cache uses a module listed above it, which is the healthy direction.
au.csiro.pathling.cache uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.cache, while a change to au.csiro.pathling.cache can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling.cache uses a module listed above it, which is the healthy direction.
34→36 au.csiro.pathling.cache uses au.csiro.pathling.asyncpart of a loop✕
Connections
1 pair of types, where a type in au.csiro.pathling.cache uses a type in au.csiro.pathling.async.
au.csiro.pathling.cache uses au.csiro.pathling.async, so a change to au.csiro.pathling.async can break au.csiro.pathling.cache, while a change to au.csiro.pathling.cache can't break au.csiro.pathling.async.
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.
au.csiro.pathling.operations.view uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.operations.view, while a change to au.csiro.pathling.operations.view can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.view uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.view uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.operations.view, while a change to au.csiro.pathling.operations.view can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.operations.view uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.view uses au.csiro.pathling.views, so a change to au.csiro.pathling.views can break au.csiro.pathling.operations.view, while a change to au.csiro.pathling.operations.view can't break au.csiro.pathling.views.
Position
Below the diagonal: au.csiro.pathling.operations.view uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.view uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.view, while a change to au.csiro.pathling.operations.view can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling.operations.view uses a module listed above it, which is the healthy direction.
au.csiro.pathling.async uses au.csiro.pathling.io, so a change to au.csiro.pathling.io can break au.csiro.pathling.async, while a change to au.csiro.pathling.async can't break au.csiro.pathling.io.
Position
Below the diagonal: au.csiro.pathling.async uses a module listed above it, which is the healthy direction.
au.csiro.pathling.async uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.async, while a change to au.csiro.pathling.async can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling.async uses a module listed above it, which is the healthy direction.
au.csiro.pathling.async uses au.csiro.pathling.cache, so a change to au.csiro.pathling.cache can break au.csiro.pathling.async, while a change to au.csiro.pathling.async can't break au.csiro.pathling.cache.
Position
Below the diagonal: au.csiro.pathling.async uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.views, so a change to au.csiro.pathling.views can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.views.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.terminology.expand, so a change to au.csiro.pathling.terminology.expand can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.terminology.expand.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.terminology.conceptmap, so a change to au.csiro.pathling.terminology.conceptmap can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.terminology.conceptmap.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.terminology, so a change to au.csiro.pathling.terminology can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.terminology.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.library.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.operations.view, so a change to au.csiro.pathling.operations.view can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.operations.view.
Position
Below the diagonal: au.csiro.pathling.operations.sqlquery uses a module listed above it, which is the healthy direction.
37→39 au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.operations.sqlpart of a loop✕
Connections
4 pairs of types, where a type in au.csiro.pathling.operations.sqlquery uses a type in au.csiro.pathling.operations.sql.
au.csiro.pathling.operations.sqlquery uses au.csiro.pathling.operations.sql, so a change to au.csiro.pathling.operations.sql can break au.csiro.pathling.operations.sqlquery, while a change to au.csiro.pathling.operations.sqlquery can't break au.csiro.pathling.operations.sql.
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.
au.csiro.pathling.operations.update uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.operations.update, while a change to au.csiro.pathling.operations.update can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.operations.update uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.update uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.operations.update, while a change to au.csiro.pathling.operations.update can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.update uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.update uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling.operations.update, while a change to au.csiro.pathling.operations.update can't break au.csiro.pathling.library.
Position
Below the diagonal: au.csiro.pathling.operations.update uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.update uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.update, while a change to au.csiro.pathling.operations.update can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling.operations.update uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.update uses au.csiro.pathling.cache, so a change to au.csiro.pathling.cache can break au.csiro.pathling.operations.update, while a change to au.csiro.pathling.operations.update can't break au.csiro.pathling.cache.
Position
Below the diagonal: au.csiro.pathling.operations.update uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.io.source, so a change to au.csiro.pathling.io.source can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.views, so a change to au.csiro.pathling.views can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.views.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.operations.compartment, so a change to au.csiro.pathling.operations.compartment can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.operations.compartment.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.operations.bulkexport, so a change to au.csiro.pathling.operations.bulkexport can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.operations.bulkexport.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.operations.view, so a change to au.csiro.pathling.operations.view can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.operations.view.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.async, so a change to au.csiro.pathling.async can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.async.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling.operations.sql uses au.csiro.pathling.operations.sqlquery, so a change to au.csiro.pathling.operations.sqlquery can break au.csiro.pathling.operations.sql, while a change to au.csiro.pathling.operations.sql can't break au.csiro.pathling.operations.sqlquery.
Position
Below the diagonal: au.csiro.pathling.operations.sql uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.encoders, so a change to au.csiro.pathling.encoders can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.encoders.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.search, so a change to au.csiro.pathling.search can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.search.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.fhir, so a change to au.csiro.pathling.fhir can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.fhir.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.library.io.source, so a change to au.csiro.pathling.library.io.source can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.library.io.source.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.library, so a change to au.csiro.pathling.library can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.library.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.io, so a change to au.csiro.pathling.io can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.io.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.operations.bulkimport, so a change to au.csiro.pathling.operations.bulkimport can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.operations.bulkimport.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.operations.bulkexport, so a change to au.csiro.pathling.operations.bulkexport can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.operations.bulkexport.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.operations.bulksubmit, so a change to au.csiro.pathling.operations.bulksubmit can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.operations.bulksubmit.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.config, so a change to au.csiro.pathling.config can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.config.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.cache, so a change to au.csiro.pathling.cache can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.cache.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.async, so a change to au.csiro.pathling.async can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.async.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.operations.update, so a change to au.csiro.pathling.operations.update can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.operations.update.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
au.csiro.pathling uses au.csiro.pathling.operations.sql, so a change to au.csiro.pathling.operations.sql can break au.csiro.pathling, while a change to au.csiro.pathling can't break au.csiro.pathling.operations.sql.
Position
Below the diagonal: au.csiro.pathling uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
202
High / Critical
A05:2025 — Injection
87
High / Critical
A02:2025 — Security Misconfiguration
42
High / Critical
A01:2025 — Broken Access Control
3
Medium
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 2 Banned license finding(s) in License Compliance; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Banned license finding(s) in License Compliance.
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.
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
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 — 214
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 — 622
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 — 421
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 82 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 — 82 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, 979 of 1257 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for ui/ failed in the analyzer sandbox (npm error Cannot read properties of null (reading 'edgesOut')), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`jacoco:report`) shows coverage is measured in your own CI.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 3,942 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 151 test source file(s) (.ts, .tsx, .py, .js) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for ui/ failed in the analyzer sandbox (npm error Cannot read properties of null (reading 'edgesOut')), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
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. Test reliability for the vitest suite in ui/ was NOT MEASURED: the dependency install for ui/ failed in the analyzer sandbox (npm error Cannot read properties of null (reading 'edgesOut')), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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 Maven 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.
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 REDACTED, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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 — 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. 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
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.
D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `lib/R/inst/extdata/delta/Condition.parquet/_delta_log/00000000000000000000.json`, `lib/R/inst/extdata/delta/Patient.parquet/_delta_log/00000000000000000000.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — 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. `encoders/src/main/java/au/csiro/pathling/encoders/terminology/ucum/Ucum.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathQuantity.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/Collection.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/SingleInstanceEvaluator.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/unit/FhirPathUnit.java`, … (+1 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.
D41 Kernel & Syscall Confinement — 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. Deployment/cache/chart/templates/deployment.yaml:7, REDACTED:7, REDACTED:6 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The filesystem refused the listing or the read of: fhirpath/src/test/resources/tests/sql-on-fhir. Every other path was read.
R10 Code Duplication — 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations: 13 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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 REDACTED (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.
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ViewDefinitionResource.copy (cyclomatic 48), ViewDefinitionResource.isEmpty (cyclomatic 34), dap_upload.main (cyclomatic 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 38 bodies over 15 down to 15 or less in Cognitive Complexity — start with ViewDefinitionResource.copy (cognitive 62), auth.checkServerCapabilities (cognitive 59), useServerCapabilities.parseCapabilities (cognitive 57). — 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 38 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 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 11 FunctionTooLong finding(s) in God Classes — start with SqlQueryInlineTab.tsx, SqlQueryForm.tsx, ViewDefinitionForm.tsx. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 7 TooManyMethods finding(s) in God Classes — start with ViewDefinitionResource.java, ColumnRepresentation.java, REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 FileTooLong finding(s) in God Classes — start with SnomedRf2Importer.java, ViewDefinitionResource.java, LocalTerminologyService.java. — One of this dimension's main actionable groups (7 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.
67 duplicated block group(s) detected. 2.7 % of the production lines (3,315 of 121,308) are in a reported copy. A further 85 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 152 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) · ×10server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:78
Edited copy of a member (6 corresponding lines) · ×9server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitProvider.java:351
Edited copy of a member (17 corresponding lines) · ×6server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:261
+ 58 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with PathlingServerVersion.java, VclEvaluator.java, DecimalCustomCoder.scala. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with DefaultTerminologyService.java (4), BulkSubmitProvider.java, CombineOperator.java. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with PathlingServerVersion.java, NdjsonSink.java, DefaultTerminologyClient.java. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
12 production modules (Maven+npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 10 of the 12 (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).
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 MockTerminologyService.java, BulkSubmitValidator.java. — 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.
Do you agree with this assessment?
D10 · Test Quality9.6 / 10Stronggated by 118 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
4 skipped (4 with a documented reason), 118 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3942 tests. Measured on the .java suite only — at least 151 test source file(s) (.ts, .tsx, .py, .js) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: testDesignationWithLanguage · ×118fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:745
Skipped (documented): test · ×4fhirpath/src/test/java/au/csiro/pathling/views/FhirViewTest.java:499
What to do
Resolve the 118 No assertions finding(s) in Test Quality — start with TerminologyUdfTest.java (19), SingleResourceFhirPathTest.java (8), ExportOperationIT.java (8). — One of this dimension's main actionable groups (118 warning-level).
Detailed fixes: d10_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.
263 outdated artifact(s) of 327 resolved by the build, graded against Maven Central. The poms themselves state a version for only 49 of 182 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
2 of 42 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 14 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. 133 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 6 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 REDACTED, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
Banned license: org.openjdk.jmh:jmh-core · ×2
What to do
Resolve the 2 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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: ui/src/components/sqlOnFhir/SqlQueryForm.tsx (11×28=308); server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java (11×24=264); ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx (8×21=168) Repeated repair below the complexity floor: terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java (14 of 24 changes were fixes); server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.java (5 of 8 changes were fixes); server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java (4 of 5 changes were fixes)
Resolve the 13 Repeated repair finding(s) in Churn × Complexity Hotspots — start with LocalTerminologyService.java, SqlRunProvider.java, SqlValidator.java. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with SqlQueryForm.tsx, SqlDependencyResolver.java, SqlQueryInlineTab.tsx. — One of this dimension's main actionable groups (9 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 Factor5.6 / 10Adequate✓ 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.
250 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java. Counted over 556 of the 838 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 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 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.
1 deducted task-comment markers across 121308 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 1 TodoComment finding(s) in Explicit Debt — start with RequestTagFactory.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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. 15 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — 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 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.
52 of 1425 judged comments only repeat the code they sit on (3.6 %). 6 comment(s) in another language or script were not judged.
redundant comment · ×52ui/e2e/export.spec.ts:507
doc comments repeat the namesui/src/api/jobs.ts:50
What to do
Resolve the 52 redundant comment finding(s) in Comment Value — start with import.spec.ts (4), resources.spec.ts (4), sqlOnFhir.spec.ts (4). — One of this dimension's main actionable groups (52 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
5 of 10 build units (Maven, Python, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×5REDACTED:1
What to do
Resolve the 5 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
31 % of calls cross a namespace and 5 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
87 finding(s): 0 critical, 84 high, 3 medium, 0 low. 64 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 18 file(s) — `.github/scripts/install-spark.sh` (line 12, line 13, line 14), `REDACTED`, `deployment/cache/chart/templates/service.yaml`, `REDACTED`, `deployment/fhirpath-lab-api/chart/templates/service.yaml`, … (+13 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 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 REDACTED finding(s) charged to Static Analysis (SAST) — the other 64 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 (77 issue-level, 13 of them charged here).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 99 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (50), REDACTED (47), REDACTED (2). — One of this dimension's main actionable groups (99 issue-level).
Resolve the 13 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 26 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (26 warning-level).
Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 11 Low IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (2). — One of this dimension's main actionable groups (11 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)7.3 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
3 finding(s): 0 critical, 0 high, 3 medium, 0 low. semgrep could not parse 6 file(s) — `encoders/src/main/java/au/csiro/pathling/encoders/terminology/ucum/Ucum.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathQuantity.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/Collection.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/SingleInstanceEvaluator.java`, `fhirpath/src/main/java/au/csiro/pathling/fhirpath/unit/FhirPathUnit.java`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
6 of 556 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportResultRegistry.java. Counted over 556 of the 838 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 3 Change coupling finding(s) in Change Coupling — start with SqlQueryInlineTab.tsx, ImportForm.tsx, Export.tsx. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 77 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 & labels7.7 / 10Strong✓ 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 control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — licenses/epl 2.0 - epl-2.0.html:7, licenses/epl 2.0 - epl-2.0.html:49
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — licenses/epl 2.0 - epl-2.0.html:8
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×3) — licenses/epl 2.0 - epl-2.0.html:9, licenses/epl 2.0 - epl-2.0.html:41, licenses/epl 2.0 - epl-2.0.html:42
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>. (×6) — library-api/src/main/javadoc/overview.html:20, licenses/bsd-3-clause - license.html:3, licenses/eclipse public license - v 1.0 - epl-v10.html:3, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — licenses/apache-2.0 - license-2.0.html:460
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — licenses/bsd-3-clause - license.html:3, licenses/eclipse public license - v 1.0 - epl-v10.html:3, licenses/gnu general public license (gpl), version 2, with the classpath exception - gplv2+ce.html:1
With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled. — licenses/epl 2.0 - epl-2.0.html:1
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — ui/index.html:2
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".
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×10) — licenses/apache-2.0 - license-2.0.html:255, licenses/apache-2.0 - license-2.0.html:304, licenses/apache-2.0 - license-2.0.html:310, …
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — licenses/mit - mit.html:1314
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.
`.wp-block-jetpack-search-search-input .jetpack-search-input__field:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — licenses/mit - mit.html:295
`input[type=checkbox]:checked + label:before, input[type=radio]:checked + label:before` sets color: #ffffff on background-color: #17d0f4 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — site/static/assets/css/home/main.css:2215
`.toast-viewport` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — ui/src/contexts/ToastContext.css:20
`a.arrow:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — site/static/assets/css/home/main.css:2815
`.gallery a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — site/static/assets/css/home/main.css:2890
`.gallery .modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — site/static/assets/css/home/main.css:2943
`.toast-root[data-state="open"]` moves (`animation: toast-slide-in 150ms cubic-bezier(0.16, 1, 0.3, 1)`) 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. — ui/src/contexts/ToastContext.css:36
`.toast-root[data-swipe="cancel"]` moves (`transition: transform 200ms ease-out`) 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. — ui/src/contexts/ToastContext.css:49
`.toast-root[data-swipe="end"]` moves (`animation: toast-swipe-out 100ms ease-out`) 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. — ui/src/contexts/ToastContext.css:53
`.gallery .modal:before` moves (`animation: gallery-modal-spinner 1s infinite linear`) 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. — site/static/assets/css/home/main.css:2955
`.gallery .modal .inner` moves (`transition: opacity 0.25s ease, transform 0.25s 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. — site/static/assets/css/home/main.css:3002
`.gallery .modal.loaded .inner` moves (`transition: opacity 0.5s ease, transform 0.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. — site/static/assets/css/home/main.css:3032
`#wrapper > section.intro > header` moves (`transition: transform 1s 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. — site/static/assets/css/home/main.css:3778
`#wrapper > section.intro > .content` moves (`transition: transform 1s 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. — site/static/assets/css/home/main.css:3782
`#wrapper > section.intro > header > *` moves (`transition: transform 1s ease, opacity 1s 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. — site/static/assets/css/home/main.css:3799
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 — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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.
`CacheableDatabase` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (cacheKey; e.g. `cacheKey` in `invalidate` at line 230). — server/src/main/java/au/csiro/pathling/cache/CacheableDatabase.java:56
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.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — fhirpath/src/test/java/au/csiro/pathling/views/FhirViewExperimentalComplianceTest.java:25
What to do
Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
`CONTRIBUTING.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `fhirpath-lab-api`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — CONTRIBUTING.md:49
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.
Update CONTRIBUTING.md so it draws the parts the code has today: add fhirpath-lab-api.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether 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.
Only 7/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `lib/python`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
`site/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`. — site/package.json:16
What to do
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 · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — server/src/main/java/au/csiro/pathling/security/PathlingJwtDecoderBuilder.java:106
What to do
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmark/src/main/java/au/csiro/pathling/benchmark/PathlingBenchmark.java
What to do
Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
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.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
Do you agree with this assessment?
R10 · Code Duplication4.9 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
13 duplicated blocks under ui/src/components/ have copies in at least two of the sibling directories export, import, resources, sqlOnFhir — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — ui/src/components/export/ExportCard.tsx:150
7 duplicated blocks under ui/src/ have copies in at least two of the sibling directories api, components, hooks, pages, services, types — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — ui/src/components/jobs/JobsTable.tsx:110
ui/src/components/sqlOnFhir/SqlQueryCard.tsx:69 · ui/src/components/sqlOnFhir/ViewCard.tsx:104 — the two spans are one implementation copied and then locally edited — 546 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/components/sqlOnFhir/SqlQueryCard.tsx:69
ui/src/api/bulkExport.ts:69 · ui/src/api/bulkSubmit.ts:80 — the two spans are one implementation copied and then locally edited — 366 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/api/bulkExport.ts:69
ui/src/components/sqlOnFhir/SqlQueryForm.tsx:180 · ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:117 — the two spans are one implementation copied and then locally edited — 347 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/components/sqlOnFhir/SqlQueryForm.tsx:180
ui/src/components/export/ExportCard.tsx:150 · ui/src/components/sqlOnFhir/ExportJobCard.tsx:158 — the two spans are one implementation copied and then locally edited — 272 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/components/export/ExportCard.tsx:150
ui/src/hooks/useImport.ts:57 · ui/src/hooks/useImportPnp.ts:69 — the two spans are one implementation copied and then locally edited — 203 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/hooks/useImport.ts:57
ui/src/components/import/ImportForm.tsx:99 · ui/src/components/import/ImportPnpForm.tsx:96 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/import/ImportForm.tsx:99
ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:261 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:336 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:261
ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:309 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:370 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:309
ui/src/api/bulkExport.ts:266 · ui/src/api/job.ts:63 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/api/bulkExport.ts:266
ui/src/api/sqlOnFhirOperations.ts:166 · ui/src/api/sqlOnFhirOperations.ts:293 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/api/sqlOnFhirOperations.ts:166
ui/src/api/rest.ts:196 · ui/src/api/rest.ts:236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — ui/src/api/rest.ts:196
ui/src/components/SearchParamsInput.tsx:146 · ui/src/components/import/ImportForm.tsx:163 · ui/src/components/resources/ResourceSearchForm.tsx:173 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/components/SearchParamsInput.tsx:146
ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:168 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:194 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:168
ui/src/hooks/useSqlQueryLibraries.ts:58 · ui/src/hooks/useSqlViews.ts:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/hooks/useSqlQueryLibraries.ts:58
ui/src/pages/Export.tsx:51 · ui/src/pages/Import.tsx:68 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/pages/Export.tsx:51
ui/src/api/bulkExport.ts:154 · ui/src/api/import.ts:114 · ui/src/api/import.ts:240 · ui/src/api/sqlOnFhirOperations.ts:312 — the 4 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/api/bulkExport.ts:154
ui/src/api/import.ts:109 · ui/src/api/import.ts:235 · ui/src/api/sqlOnFhirOperations.ts:307 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/api/import.ts:109
ui/src/components/export/ExportCard.tsx:239 · ui/src/components/sqlOnFhir/ExportJobCard.tsx:227 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/export/ExportCard.tsx:239
ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:365 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:472 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:365
ui/src/components/SearchParamsInput.tsx:109 · ui/src/components/resources/ResourceSearchForm.tsx:157 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/SearchParamsInput.tsx:109
ui/src/components/export/ExportForm.tsx:86 · ui/src/components/import/ImportForm.tsx:107 · ui/src/components/import/ImportPnpForm.tsx:104 — the 3 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/components/export/ExportForm.tsx:86
ui/src/components/export/ExportOptions.tsx:159 · ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:178 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/components/export/ExportOptions.tsx:159
ui/src/components/sqlOnFhir/ExportSetPanel.tsx:151 · ui/src/components/sqlOnFhir/ExportSetPanel.tsx:163 · ui/src/components/sqlOnFhir/ExportSetPanel.tsx:175 — 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. — ui/src/components/sqlOnFhir/ExportSetPanel.tsx:151
ui/src/components/import/ImportCard.tsx:127 · ui/src/components/sqlOnFhir/ViewCard.tsx:146 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/import/ImportCard.tsx:127
ui/src/components/import/ImportCard.tsx:140 · ui/src/components/sqlOnFhir/ExportJobCard.tsx:157 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ui/src/components/import/ImportCard.tsx:140
ui/src/components/export/ExportForm.tsx:88 · ui/src/components/export/ExportOptions.tsx:161 · ui/src/components/import/ImportForm.tsx:112 · ui/src/components/import/ImportPnpForm.tsx:109 · +2 more site(s) not listed — the 6 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/components/export/ExportForm.tsx:88
ui/src/components/export/ExportOptions.tsx:123 · ui/src/components/export/ExportOptions.tsx:132 — 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. — ui/src/components/export/ExportOptions.tsx:123
ui/src/components/export/ExportOptions.tsx:171 · ui/src/components/resources/ResourceSearchForm.tsx:154 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/export/ExportOptions.tsx:171
ui/src/pages/Import.tsx:43 · ui/src/pages/Import.tsx:58 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/pages/Import.tsx:43
ui/src/api/bulkSubmit.ts:136 · ui/src/api/bulkSubmit.ts:148 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/api/bulkSubmit.ts:136
ui/src/api/sqlOnFhirOperations.ts:376 · ui/src/types/export.ts:101 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — ui/src/api/sqlOnFhirOperations.ts:376
ui/src/components/SearchParamsInput.tsx:95 · ui/src/components/import/ImportForm.tsx:86 · ui/src/components/resources/ResourceSearchForm.tsx:110 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/components/SearchParamsInput.tsx:95
ui/src/components/sqlOnFhir/SqlOnFhirForm.tsx:104 · ui/src/components/sqlOnFhir/SqlQueryForm.tsx:249 · ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:157 · ui/src/pages/Import.tsx:92 — the 4 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/components/sqlOnFhir/SqlOnFhirForm.tsx:104
ui/src/hooks/useBulkExport.ts:111 · ui/src/hooks/useImport.ts:65 · ui/src/hooks/useImportPnp.ts:77 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/hooks/useBulkExport.ts:111
ui/src/hooks/useBulkSubmit.ts:174 · ui/src/hooks/useSqlExport.ts:86 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/src/hooks/useBulkSubmit.ts:174
REDACTED:222 · REDACTED:129 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:222
ui/src/components/resources/ResourceSearchForm.tsx:91 · ui/src/types/exportOptions.ts:80 — the two spans are one implementation copied and then locally edited — 67 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/components/resources/ResourceSearchForm.tsx:91
REDACTED:91 · REDACTED:139 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — REDACTED:91
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
getResourceSummary has cyclomatic complexity 41 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/resources/ResourceCard.tsx:54
parseCapabilities has cyclomatic complexity 31 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:88
checkServerCapabilities has cyclomatic complexity 29 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:126
SqlQueryForm has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/sqlOnFhir/SqlQueryForm.tsx:93
ViewDefinitionForm has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:88
ExportCard has cyclomatic complexity 20 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/export/ExportCard.tsx:84
ExportJobCard has cyclomatic complexity 16 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/sqlOnFhir/ExportJobCard.tsx:115
libraryToSummary has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/hooks/sqlQueryHelpers.ts:96
Dashboard has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/pages/Dashboard.tsx:46
buildPnpParameters has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/api/import.ts:140
SqlQueryStoredTab has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/sqlOnFhir/SqlQueryStoredTab.tsx:73
ImportCard has cyclomatic complexity 13 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/import/ImportCard.tsx:82
search has cyclomatic complexity 11 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/api/rest.ts:90
(anonymous) has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/pages/BulkSubmit.tsx:57
Do you agree with this assessment?
R3 · Large Files9.7 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code8.5 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 13 application, 5 tooling and 99 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (13 application, 5 tooling, 99 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — ui/src/types/polling.ts
Nothing imports this binding — it is safe to review for removal. (×28) — ui/src/api/asyncJob.ts:52, ui/src/api/bulkExport.ts:72, ui/src/api/bulkExport.ts:75, …
Nothing ultimately consumes this binding: its only referrer is the re-export in ui/src/utils/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ui/src/utils/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — ui/src/utils/ndjson.ts:24, ui/src/utils/ndjson.ts:60
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — ui/src/types/sqlQuery.ts:252
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://www.apachecon.com/event-images/snippet.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 41 such include(s) across the repository's markup. — licenses/apache-2.0 - license-2.0.html:34
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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/24 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.
`fetchSmartConfiguration` 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 })`. — REDACTED:55
`checkServerCapabilities` 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 })`. — REDACTED:126
`queryFn` 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 })`. — REDACTED:222
`kickOffExport` 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 })`. — ui/src/api/bulkExport.ts:140
`bulkExportStatus` 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 })`. — ui/src/api/bulkExport.ts:266
`bulkExportDownload` 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 })`. — ui/src/api/bulkExport.ts:318
`bulkSubmit` 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 })`. — ui/src/api/bulkSubmit.ts:204
`bulkSubmitStatus` 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 })`. — ui/src/api/bulkSubmit.ts:237
`bulkSubmitDownload` 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 })`. — ui/src/api/bulkSubmit.ts:313
`importKickOff` 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 })`. — ui/src/api/import.ts:94
`importPnpKickOff` 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 })`. — ui/src/api/import.ts:224
`jobStatus` 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 })`. — ui/src/api/job.ts:63
`jobCancel` 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 })`. — ui/src/api/job.ts:114
`listJobs` 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 })`. — ui/src/api/jobs.ts:148
`search` 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 })`. — ui/src/api/rest.ts:90
`read` 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 })`. — ui/src/api/rest.ts:159
`create` 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 })`. — ui/src/api/rest.ts:192
`update` 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 })`. — ui/src/api/rest.ts:232
`deleteResource` 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 })`. — ui/src/api/rest.ts:270
`sqlRun` 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 })`. — ui/src/api/sqlOnFhirOperations.ts:149
`sqlRunStored` 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 })`. — ui/src/api/sqlOnFhirOperations.ts:211
`sqlExportKickOff` 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 })`. — ui/src/api/sqlOnFhirOperations.ts:267
`sqlExportDownload` 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 })`. — ui/src/api/sqlOnFhirOperations.ts:345
`listStoredLibraries` 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 })`. — ui/src/api/sqlQuery.ts:89
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.
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` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) 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 (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java:848, fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/FhirResourceResolver.java:144
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 `REDACTED` 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 strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~3.0 `!` null assertions per 1k TypeScript source lines — 49 assertion(s) across the 16513 source line(s) of the 116 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: ui/src/api/import.ts (9), ui/src/hooks/useBulkExport.ts (8), ui/src/hooks/useBulkSubmit.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 22 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 — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 40 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.
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 24 | >>> RUN python3 -c "from pathling import PathlingContext; pc = PathlingContext.create(); pc.spark.stop()" 25 | 26 | ENV PORT=8080 -------------------- ERROR: failed to solve: process "/bin/sh -c python3 -c \"from pathling import PathlingContext; pc = PathlingContext.create(); pc.spark.stop()\"" did not complete successfully: exit code: 1; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c python3 -c \"from pathling import PathlingContext; pc = PathlingContext.create(); pc.spark.stop()\"`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c python3 -c \"from pathling import PathlingContext; pc = PathlingContext.create(); pc.spark.stop()\"`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Python surface was not measured.
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
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 214 value object(s)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
P12 CI test-gate honesty — 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.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 22% of this repository's production lines — java (94,117 lines), r (2,614 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 22% of this repository's production lines — java (94,117 lines), r (2,614 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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· Link with no accessible name · ×3
Link with no accessible name licenses/epl 2.0 - epl-2.0.html:9— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name licenses/epl 2.0 - epl-2.0.html:41— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name licenses/epl 2.0 - epl-2.0.html:42— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
<html> without a lang licenses/bsd-3-clause - license.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang licenses/eclipse public license - v 1.0 - epl-v10.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang licenses/gnu general public license (gpl), version 2, with the classpath exception - gplv2+ce.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels· <input> without a programmatic label · ×2
<input> without a programmatic label licenses/epl 2.0 - epl-2.0.html:7— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label licenses/epl 2.0 - epl-2.0.html:49— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
Banned license: org.openjdk.jmh:jmh-core — `org.openjdk.jmh:jmh-core` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: org.openjdk.jmh:jmh-generator-annprocess — `org.openjdk.jmh:jmh-generator-annprocess` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text licenses/epl 2.0 - epl-2.0.html:8— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
No assertions: testDesignationWithLanguage fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:745— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDesignationWithNoLanguageAndAlternativeDisplayName fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:784— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDesignationWithNoUse fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:804— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDesignationWithNullLanguageAndUseColumn fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:764— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDisplay fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:505— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDisplayWithLanguage fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:533— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProperty fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:564— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testPropertyWithDefaultType fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:624— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testPropertyWithLanguage fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:654— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testSubsumedBy fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:454— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testSubsumes fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:403— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTranslateCoding fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:336— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTranslateCodingArray fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:360— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidateCode fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:206— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidateCoding fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:147— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidateCodingArray fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:234— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidateCodingNullDataset fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:170— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidateCodingUnresolvableValueSet fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:189— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validateCodingArrayWithNullDataset fhirpath/src/test/java/au/csiro/pathling/sql/udf/TerminologyUdfTest.java:312— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: elementExtensionTest fhirpath/src/test/java/au/csiro/pathling/fhirpath/execution/SingleResourceFhirPathTest.java:207— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nestedExtensionTest fhirpath/src/test/java/au/csiro/pathling/fhirpath/execution/SingleResourceFhirPathTest.java:179— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nestedExtensionTraversalTest fhirpath/src/test/java/au/csiro/pathling/fhirpath/execution/SingleResourceFhirPathTest.java:195— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nullHandlingTests fhirpath/src/test/java/au/csiro/pathling/fhirpath/execution/SingleResourceFhirPathTest.java:141— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ofTypeExtensionTest fhirpath/src/test/java/au/csiro/pathling/fhirpath/execution/SingleResourceFhirPathTest.java:221— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resourceExtensionTest fhirpath/src/test/java/au/csiro/pathling/fhirpath/execution/SingleResourceFhirPathTest.java:165— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 93 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×70
X2 · Cancellation propagation· Async function without AbortSignal · ×24
Async function without AbortSignal: fetchSmartConfiguration REDACTED:55— `fetchSmartConfiguration` 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 })`.
Async function without AbortSignal: checkServerCapabilities REDACTED:126— `checkServerCapabilities` 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 })`.
Async function without AbortSignal: queryFn REDACTED:222— `queryFn` 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 })`.
Async function without AbortSignal: kickOffExport ui/src/api/bulkExport.ts:140— `kickOffExport` 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 })`.
Async function without AbortSignal: bulkExportStatus ui/src/api/bulkExport.ts:266— `bulkExportStatus` 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 })`.
Async function without AbortSignal: bulkExportDownload ui/src/api/bulkExport.ts:318— `bulkExportDownload` 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 })`.
Async function without AbortSignal: bulkSubmit ui/src/api/bulkSubmit.ts:204— `bulkSubmit` 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 })`.
Async function without AbortSignal: bulkSubmitStatus ui/src/api/bulkSubmit.ts:237— `bulkSubmitStatus` 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 })`.
Async function without AbortSignal: bulkSubmitDownload ui/src/api/bulkSubmit.ts:313— `bulkSubmitDownload` 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 })`.
Async function without AbortSignal: importKickOff ui/src/api/import.ts:94— `importKickOff` 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 })`.
Async function without AbortSignal: importPnpKickOff ui/src/api/import.ts:224— `importPnpKickOff` 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 })`.
Async function without AbortSignal: jobStatus ui/src/api/job.ts:63— `jobStatus` 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 })`.
Async function without AbortSignal: jobCancel ui/src/api/job.ts:114— `jobCancel` 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 })`.
Async function without AbortSignal: listJobs ui/src/api/jobs.ts:148— `listJobs` 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 })`.
Async function without AbortSignal: search ui/src/api/rest.ts:90— `search` 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 })`.
Async function without AbortSignal: read ui/src/api/rest.ts:159— `read` 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 })`.
Async function without AbortSignal: create ui/src/api/rest.ts:192— `create` 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 })`.
Async function without AbortSignal: update ui/src/api/rest.ts:232— `update` 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 })`.
Async function without AbortSignal: deleteResource ui/src/api/rest.ts:270— `deleteResource` 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 })`.
Async function without AbortSignal: sqlRun ui/src/api/sqlOnFhirOperations.ts:149— `sqlRun` 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 })`.
Async function without AbortSignal: sqlRunStored ui/src/api/sqlOnFhirOperations.ts:211— `sqlRunStored` 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 })`.
Async function without AbortSignal: sqlExportKickOff ui/src/api/sqlOnFhirOperations.ts:267— `sqlExportKickOff` 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 })`.
Async function without AbortSignal: sqlExportDownload ui/src/api/sqlOnFhirOperations.ts:345— `sqlExportDownload` 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 })`.
Async function without AbortSignal: listStoredLibraries ui/src/api/sqlQuery.ts:89— `listStoredLibraries` 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 })`.
Repeated repair: terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java:803— terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java changed 24 times in last 90 days and 14 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is LocalTerminologyService.buildLookup at line 803), 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: Explain why a simple map cannot be read as a concept map”; “fix: Align memberOf with the FHIR definition”; “fix: Read implicit concept maps on experimental SNOMED CT bases”; “fix: Reject a version pin in local mode only on implicit value set URLs”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.java server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.java:152— server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.java changed 8 times in last 90 days and 5 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 SqlRunProvider.run at line 152), 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: Restore test compilation and formatting after request id removal”; “fix: Confine the analysis-failure 422 to the caller's own SQL”; “fix: Report a Spark analysis failure as a 422 naming the subject”; “fix: Address review feedback on the manifest and binding errors”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java:462— server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java 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 8 (its worst body is SqlValidator.walkPlanStrict at line 462), 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: Restore test compilation and formatting after request id removal”; “Namespace temp views with server-generated random id (fixes #2770)”; “fix: Accept a subquery over a nested SQLView's own dependency”; “fix: Reject input file functions in SQL on FHIR queries”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ReferenceCollection.java fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ReferenceCollection.java:91— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ReferenceCollection.java 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 1 (its worst body is ReferenceCollection.getKeyCollection at line 91), 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: Anchor getReferenceKey type pattern to relative references”; “fix: Return empty getReferenceKey for absolute, contained and URN references”; “fix: Match reference key types exactly and support repeating references”; “fix: Strip /_history version from getReferenceKey() so versioned references join”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ReferenceCollection.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/QuantityValue.java fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/QuantityValue.java:163— fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/QuantityValue.java 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 ValueWithUnit.compare at line 163), 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: Reject bounded quantities when decoding”; “fix: Convert only representable FHIR Quantities”; “fix: Return empty when comparing bounded quantities”; “fix: Treat paths beyond the encoded nesting depth as empty”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/QuantityValue.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: server/src/main/java/au/csiro/pathling/async/JobProvider.java server/src/main/java/au/csiro/pathling/async/JobProvider.java:314— server/src/main/java/au/csiro/pathling/async/JobProvider.java 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 6 (its worst body is JobProvider.handleCompletedJob at line 314), 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: Report a failed job clean-up honestly rather than as an error”; “fix: Cancel a deleted job's Spark work within the request”; “fix: Stop job deletion racing the work it cancels”; “fix: Enforce job ownership on the delete path”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/async/JobProvider.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: server/src/main/java/au/csiro/pathling/operations/sql/SqlOperationError.java server/src/main/java/au/csiro/pathling/operations/sql/SqlOperationError.java:160— server/src/main/java/au/csiro/pathling/operations/sql/SqlOperationError.java 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 4 (its worst body is SqlOperationError.analyserMessage at line 160), 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: Confine the analysis-failure 422 to the caller's own SQL”; “fix: Report the analyser's simple message, without the logical plan”; “fix: Report a Spark analysis failure as a 422 naming the subject”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/operations/sql/SqlOperationError.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java:305— server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java 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 11 (its worst body is ResultStreamingHelper.writeFhirPart at line 305), 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: Render DATE and TIMESTAMP as ISO 8601 in $sql-run output”; “fix: Use the first row check to drive CSV streaming”; “fix: Report $sql-run evaluation failures before the CSV header is sent”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: terminology/src/main/java/au/csiro/pathling/terminology/local/index/RefsetIndex.java terminology/src/main/java/au/csiro/pathling/terminology/local/index/RefsetIndex.java:61— terminology/src/main/java/au/csiro/pathling/terminology/local/index/RefsetIndex.java 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 3 (its worst body is RefsetIndex.load at line 61), 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: Honour THO implicit concept map definitions in local translate”; “fix: Keep every target of a SNOMED CT association in local translate”; “fix: Order reverse SNOMED association translation by code”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- terminology/src/main/java/au/csiro/pathling/terminology/local/index/RefsetIndex.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: ui/src/pages/Import.tsx ui/src/pages/Import.tsx:41— ui/src/pages/Import.tsx 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 1 (its worst body is Import.Import at line 41), 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: Report a failed operation once rather than twice”; “fix: Stop an operation failure notifying itself repeatedly”; “fix: Report operation failures instead of discarding them”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/pages/Import.tsx`: 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: ui/src/pages/Export.tsx ui/src/pages/Export.tsx:46— ui/src/pages/Export.tsx 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 1 (its worst body is Export.Export at line 46), 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: Report a failed download as a download failure”; “fix: Stop an operation failure notifying itself repeatedly”; “fix: Report operation failures instead of discarding them”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/pages/Export.tsx`: 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: fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java:325— fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ConversionLogic.convertToString at line 325), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: Reject bounded quantities when decoding”; “fix: Render Coding as its literal in toString()”; “fix: Convert only representable FHIR Quantities”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: ui/src/components/auth/SessionExpiredDialog.tsx ui/src/components/auth/SessionExpiredDialog.tsx:71— ui/src/components/auth/SessionExpiredDialog.tsx changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is SessionExpiredDialog.SessionExpiredDialogBody at line 71), 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: Clear the login error when the expiry dialog is raised again”; “fix: Keep the login button's label visible while it is pending”; “fix: Give visible feedback when a login attempt is made”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/components/auth/SessionExpiredDialog.tsx`: 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.
FunctionTooLong: SqlQueryInlineTab.SqlQueryInlineTab ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:143— FunctionTooLong — SqlQueryInlineTab runs 299 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 199 over it, 2.99× 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: SqlQueryForm.SqlQueryForm ui/src/components/sqlOnFhir/SqlQueryForm.tsx:93— FunctionTooLong — SqlQueryForm runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: ViewDefinitionForm.ViewDefinitionForm ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:88— FunctionTooLong — ViewDefinitionForm runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: ExportOptions.ExportOptions ui/src/components/export/ExportOptions.tsx:61— FunctionTooLong — ExportOptions runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× 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: ExportCard.ExportCard ui/src/components/export/ExportCard.tsx:84— FunctionTooLong — ExportCard runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: Dashboard.Dashboard ui/src/pages/Dashboard.tsx:46— FunctionTooLong — Dashboard runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: SqlOnFhir.SqlOnFhir ui/src/pages/SqlOnFhir.tsx:71— FunctionTooLong — SqlOnFhir runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ExportSetPanel.ExportSetPanel ui/src/components/sqlOnFhir/ExportSetPanel.tsx:86— FunctionTooLong — ExportSetPanel runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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: SqlQueryStoredTab.SqlQueryStoredTab ui/src/components/sqlOnFhir/SqlQueryStoredTab.tsx:73— FunctionTooLong — SqlQueryStoredTab runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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: ExportJobCard.ExportJobCard ui/src/components/sqlOnFhir/ExportJobCard.tsx:115— FunctionTooLong — ExportJobCard runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ResourceSearchForm.ResourceSearchForm ui/src/components/resources/ResourceSearchForm.tsx:62— FunctionTooLong — ResourceSearchForm runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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.
AC4 · Keyboard semantics· Anchor without href · ×10
Anchor without href licenses/apache-2.0 - license-2.0.html:255— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:304— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:310— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:324— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:358— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:365— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:370— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:379— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/apache-2.0 - license-2.0.html:390— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href licenses/epl 2.0 - epl-2.0.html:12— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×10
Edited copy of a member (8 corresponding lines) server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:78— server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:78-85 | utilities/src/main/java/au/csiro/pathling/PathlingVersion.java:78-85 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) terminology/src/main/java/au/csiro/pathling/terminology/local/VclEvaluator.java:378— terminology/src/main/java/au/csiro/pathling/terminology/local/VclEvaluator.java:378-385 | terminology/src/main/java/au/csiro/pathling/terminology/local/VclEvaluator.java:432-443 — 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) encoders/src/main/scala/au/csiro/pathling/encoders/datatypes/DecimalCustomCoder.scala:81— encoders/src/main/scala/au/csiro/pathling/encoders/datatypes/DecimalCustomCoder.scala:81-88 | encoders/src/main/scala/au/csiro/pathling/encoders/datatypes/IdCustomCoder.scala:87-94 — 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) terminology/src/main/java/au/csiro/pathling/terminology/store/ConceptMapStaging.java:360— terminology/src/main/java/au/csiro/pathling/terminology/store/ConceptMapStaging.java:360-368 | terminology/src/main/java/au/csiro/pathling/terminology/store/ValueSetStaging.java:161-168 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java:545— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java:545-554 | server/src/main/java/au/csiro/pathling/operations/export/ExportFileWriter.java:96-103 — 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) terminology/src/main/java/au/csiro/pathling/config/HttpClientCachingStorageType.java:54— terminology/src/main/java/au/csiro/pathling/config/HttpClientCachingStorageType.java:54-61 | terminology/src/main/java/au/csiro/pathling/terminology/store/PackageVerification.java:67-74 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:152— fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:152-167 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathTime.java:121-128 — 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) library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:171— library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:171-178 | library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.java:162-169 — 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) server/src/main/java/au/csiro/pathling/operations/sql/SqlExportRequestParser.java:296— server/src/main/java/au/csiro/pathling/operations/sql/SqlExportRequestParser.java:296-303 | server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.java:384-391 — 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/Collection.java:180— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/Collection.java:180-187 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ResourceCollection.java:122-132 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×9
Animation without a prefers-reduced-motion guard ui/src/contexts/ToastContext.css:36— `.toast-root[data-state="open"]` moves (`animation: toast-slide-in 150ms cubic-bezier(0.16, 1, 0.3, 1)`) 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 ui/src/contexts/ToastContext.css:49— `.toast-root[data-swipe="cancel"]` moves (`transition: transform 200ms ease-out`) 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 ui/src/contexts/ToastContext.css:53— `.toast-root[data-swipe="end"]` moves (`animation: toast-swipe-out 100ms ease-out`) 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 site/static/assets/css/home/main.css:2955— `.gallery .modal:before` moves (`animation: gallery-modal-spinner 1s infinite linear`) 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 site/static/assets/css/home/main.css:3002— `.gallery .modal .inner` moves (`transition: opacity 0.25s ease, transform 0.25s 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 site/static/assets/css/home/main.css:3032— `.gallery .modal.loaded .inner` moves (`transition: opacity 0.5s ease, transform 0.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 site/static/assets/css/home/main.css:3778— `#wrapper > section.intro > header` moves (`transition: transform 1s 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 site/static/assets/css/home/main.css:3782— `#wrapper > section.intro > .content` moves (`transition: transform 1s 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 site/static/assets/css/home/main.css:3799— `#wrapper > section.intro > header > *` moves (`transition: transform 1s ease, opacity 1s 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.
Hotspot: ui/src/components/sqlOnFhir/SqlQueryForm.tsx ui/src/components/sqlOnFhir/SqlQueryForm.tsx:93— ui/src/components/sqlOnFhir/SqlQueryForm.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in SqlQueryForm.SqlQueryForm at line 93. 2 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/components/sqlOnFhir/SqlQueryForm.tsx`: 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: server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java:264— server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in SqlDependencyResolver.resolveReference at line 264. 1 of those changes was a fix/bug commit, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:143— ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in SqlQueryInlineTab.SqlQueryInlineTab at line 143. 3 of those changes were fix/bug commits, and the other 5 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx`: 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: ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:88— ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in ViewDefinitionForm.ViewDefinitionForm at line 88. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx`: 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: server/src/main/java/au/csiro/pathling/FhirServer.java server/src/main/java/au/csiro/pathling/FhirServer.java:264— server/src/main/java/au/csiro/pathling/FhirServer.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in FhirServer.initialize at line 264. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/FhirServer.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/python/pathling/cli/config.py lib/python/pathling/cli/config.py:470— lib/python/pathling/cli/config.py changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in config._resolve_tx_store at line 470. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- lib/python/pathling/cli/config.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.
Hotspot: ui/src/components/sqlOnFhir/ExportJobCard.tsx ui/src/components/sqlOnFhir/ExportJobCard.tsx:115— ui/src/components/sqlOnFhir/ExportJobCard.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ExportJobCard.ExportJobCard at line 115. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/components/sqlOnFhir/ExportJobCard.tsx`: 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: server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java:230— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ImportPnpExecutor.buildBulkExportClient at line 230. 2 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: ui/src/components/export/ExportCard.tsx ui/src/components/export/ExportCard.tsx:84— ui/src/components/export/ExportCard.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in ExportCard.ExportCard at line 84. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 22:36:45 +11:00' --until='2026-10-21 22:36:45 +11:00' --full-history --no-merges -- ui/src/components/export/ExportCard.tsx`: 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 (6 corresponding lines) · ×9
Edited copy of a member (6 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitProvider.java:351— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitProvider.java:351-362 | server/src/main/java/au/csiro/pathling/async/AsyncAspect.java:267-272 — 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/CombineOperator.java:52— fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/CombineOperator.java:52-57 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/UnionOperator.java:57-63 — 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) terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:104— terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:104-109 | terminology/src/main/java/au/csiro/pathling/terminology/caching/CachingTerminologyService.java:156-161 — 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) terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:94— terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:94-99 | terminology/src/main/java/au/csiro/pathling/terminology/caching/CachingTerminologyService.java:146-151 — 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) terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:116— terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:116-121 | terminology/src/main/java/au/csiro/pathling/terminology/caching/CachingTerminologyService.java:168-173 — 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) fhirpath/src/main/java/au/csiro/pathling/views/ConstantDeclarationTypeAdapterFactory.java:36— fhirpath/src/main/java/au/csiro/pathling/views/ConstantDeclarationTypeAdapterFactory.java:36-41 | fhirpath/src/main/java/au/csiro/pathling/views/StrictStringTypeAdapterFactory.java:36-41 — 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) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitValidator.java:324— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitValidator.java:324-329 | server/src/main/java/au/csiro/pathling/operations/sql/SqlExportRequestParser.java:284-293 — 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) terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:71— terminology/src/main/java/au/csiro/pathling/terminology/DefaultTerminologyService.java:71-76 | terminology/src/main/java/au/csiro/pathling/terminology/caching/CachingTerminologyService.java:123-128 — 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ResolvedReferenceCollection.java:96— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ResolvedReferenceCollection.java:96-101 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/mixed/MixedCollection.java:45-53 — 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.
Duplicated block (7 lines × 2) server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:79— server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:79-85 | utilities/src/main/java/au/csiro/pathling/PathlingVersion.java:79-85 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/PathlingServerVersion.java` and `utilities/src/main/java/au/csiro/pathling/PathlingVersion.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:125— library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:125-131 | library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.java:119-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.java:126` calls `getValue` and `library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:132` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:114— terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:114-120 | terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:152-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DecimalCollection.java:251— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DecimalCollection.java:251-257 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/IntegerCollection.java:256-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) server/src/main/java/au/csiro/pathling/async/JobProvider.java:368— server/src/main/java/au/csiro/pathling/async/JobProvider.java:368-374 | server/src/main/java/au/csiro/pathling/async/JobResultProvider.java:173-179 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/async/JobProvider.java` and `server/src/main/java/au/csiro/pathling/async/JobResultProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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) server/src/main/java/au/csiro/pathling/operations/sqlquery/ResolvedConceptMap.java:141— server/src/main/java/au/csiro/pathling/operations/sqlquery/ResolvedConceptMap.java:141-147 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ResolvedValueSet.java:123-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) server/src/main/java/au/csiro/pathling/read/ReadProviderFactory.java:64— server/src/main/java/au/csiro/pathling/read/ReadProviderFactory.java:64-70 | server/src/main/java/au/csiro/pathling/search/SearchProviderFactory.java:64-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `server/src/main/java/au/csiro/pathling/read/ReadProviderFactory.java:64` 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DateCollection.java:123— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DateCollection.java:123-129 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DecimalCollection.java:241-247 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) server/src/main/java/au/csiro/pathling/FhirServer.java:493— server/src/main/java/au/csiro/pathling/FhirServer.java:493-499 | server/src/main/java/au/csiro/pathling/config/SecurityConfiguration.java:149-155 — 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.
AC3 · Page structure· Page without a main landmark · ×7
Page without a main landmark library-api/src/main/javadoc/overview.html:20— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark licenses/bsd-3-clause - license.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark licenses/eclipse public license - v 1.0 - epl-v10.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark licenses/eclipse public license v2.0 - epl-v20.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark licenses/epl-2.0 - epl-v20.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark licenses/gnu general public license (gpl), version 2, with the classpath exception - gplv2+ce.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark ui/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
TooManyMethods: ViewDefinitionResource encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java:90— TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× 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: ColumnRepresentation fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/ColumnRepresentation.java:59— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PathlingContext REDACTED:85— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TypeSpecifierVisitor fhirpath/src/main/java/au/csiro/pathling/fhirpath/parser/TypeSpecifierVisitor.java:79— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LocalTerminologyService terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java:89— 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: Collection fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/Collection.java:70— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SnomedRf2Importer terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:132— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: store/SnomedRf2Importer.java terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java— FileTooLong — 924 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: SnomedRf2Importer (132-1418). The bar is 500 significant lines; this is 424 over it, 1.85× 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: encoders/ViewDefinitionResource.java encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java— FileTooLong — 790 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ViewDefinitionResource (90-1265). The bar is 500 significant lines; this is 290 over it, 1.58× 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: local/LocalTerminologyService.java terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java— FileTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 258 over it, 1.52× 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: cli/terminology.py lib/python/pathling/cli/terminology.py— FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 137 over it, 1.27× 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: encoders/Expressions.scala encoders/src/main/scala/au/csiro/pathling/encoders/Expressions.scala— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 110 over it, 1.22× 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: store/FhirTerminologyImporter.java terminology/src/main/java/au/csiro/pathling/terminology/store/FhirTerminologyImporter.java— FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: FhirTerminologyImporter (105-863). The bar is 500 significant lines; this is 34 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: bulksubmit/BulkSubmitExecutor.java server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: BulkSubmitExecutor (79-959). The bar is 500 significant lines; this is 31 over it, 1.06× 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.
Duplicated block (10 lines × 2) library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:313— library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:313-322 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ValueSetMembershipResolver.java:232-241 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:144— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:144-153 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportProvider.java:141-150 — 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 `server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:144` 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 (10 lines × 2) library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:114— library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:114-123 | library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.java:108-117 — 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 `library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:209— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:209-218 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.java:402-411 — 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/comparison/Comparable.java:59— fhirpath/src/main/java/au/csiro/pathling/fhirpath/comparison/Comparable.java:59-68 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/comparison/Equatable.java:77-86 — 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 `fhirpath/src/main/java/au/csiro/pathling/fhirpath/comparison/Comparable.java:59` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `operation` to `ComparisonOperation` in one and `EqualityOperation` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) fhirpath/src/main/java/au/csiro/pathling/sql/misc/HighBoundaryForTime.java:73— fhirpath/src/main/java/au/csiro/pathling/sql/misc/HighBoundaryForTime.java:73-82 | fhirpath/src/main/java/au/csiro/pathling/sql/misc/LowBoundaryForTime.java:73-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) terminology/src/main/java/au/csiro/pathling/terminology/lookup/LookupExecutor.java:71— terminology/src/main/java/au/csiro/pathling/terminology/lookup/LookupExecutor.java:71-80 | terminology/src/main/java/au/csiro/pathling/terminology/translate/TranslateExecutor.java:69-78 — 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 (17 corresponding lines) · ×6
Edited copy of a member (17 corresponding lines) server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:261— server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:261-277 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:139-156 — 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) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:327— terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:327-343 | terminology/src/main/java/au/csiro/pathling/terminology/store/FhirResourceScanner.java:206-227 — 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) server/src/main/java/au/csiro/pathling/security/SecurityAspect.java:106— server/src/main/java/au/csiro/pathling/security/SecurityAspect.java:106-122 | server/src/main/java/au/csiro/pathling/security/SecurityAspect.java:129-149 — 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) terminology/src/main/java/au/csiro/pathling/sql/udf/DisplayUdf.java:83— terminology/src/main/java/au/csiro/pathling/sql/udf/DisplayUdf.java:83-99 | terminology/src/main/java/au/csiro/pathling/sql/udf/PropertyUdf.java:140-156 — 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) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryResultStreamer.java:88— server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryResultStreamer.java:88-106 | server/src/main/java/au/csiro/pathling/operations/view/ViewExecutionHelper.java:167-183 — 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) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitValidator.java:163— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitValidator.java:163-179 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitValidator.java:207-228 — 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 (9 corresponding lines) · ×6
Edited copy of a member (9 corresponding lines) server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java:175— server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java:175-186 | server/src/main/java/au/csiro/pathling/operations/view/ResultStreamingHelper.java:395-403 — 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) terminology/src/main/java/au/csiro/pathling/ecl/EclToVclTranslator.java:120— terminology/src/main/java/au/csiro/pathling/ecl/EclToVclTranslator.java:120-128 | terminology/src/main/java/au/csiro/pathling/ecl/EclToVclTranslator.java:131-139 — 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) server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:120— server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:120-128 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ValueSetMembershipResolver.java:94-103 — 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) terminology/src/main/java/au/csiro/pathling/ecl/EclToVclTranslator.java:255— terminology/src/main/java/au/csiro/pathling/ecl/EclToVclTranslator.java:255-263 | terminology/src/main/java/au/csiro/pathling/ecl/EclToVclTranslator.java:277-285 — 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) terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1380— terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1380-1389 | terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1392-1400 — 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) server/src/main/java/au/csiro/pathling/async/AsyncAspect.java:368— server/src/main/java/au/csiro/pathling/async/AsyncAspect.java:368-381 | server/src/main/java/au/csiro/pathling/async/JobProvider.java:449-457 — 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 (7 corresponding lines) · ×6
Edited copy of a member (7 corresponding lines) server/src/main/java/au/csiro/pathling/operations/sqlquery/ResolvedConceptMap.java:88— server/src/main/java/au/csiro/pathling/operations/sqlquery/ResolvedConceptMap.java:88-94 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ResolvedValueSet.java:78-84 — 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) fhirpath/src/main/java/au/csiro/pathling/projection/GroupingSelection.java:38— fhirpath/src/main/java/au/csiro/pathling/projection/GroupingSelection.java:38-44 | fhirpath/src/main/java/au/csiro/pathling/projection/UnionSelection.java:38-45 — 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/DefaultRepresentation.java:163— fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/DefaultRepresentation.java:163-171 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/column/ResourceRepresentation.java:230-236 — 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) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationHelper.java:70— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationHelper.java:70-76 | server/src/main/java/au/csiro/pathling/operations/sql/SqlExportSupport.java:97-104 — 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) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:81— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:81-87 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportProvider.java:84-91 — 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) encoders/src/main/scala/au/csiro/pathling/encoders/SchemaConverter.scala:66— encoders/src/main/scala/au/csiro/pathling/encoders/SchemaConverter.scala:66-72 | encoders/src/main/scala/au/csiro/pathling/encoders/SerializerBuilder.scala:122-128 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:159— library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:159-166 | library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.java:150-157 — 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 `library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) terminology/src/main/java/au/csiro/pathling/terminology/local/ComposeTranslator.java:93— terminology/src/main/java/au/csiro/pathling/terminology/local/ComposeTranslator.java:93-100 | terminology/src/main/java/au/csiro/pathling/terminology/local/ComposeTranslator.java:167-174 — 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 `terminology/src/main/java/au/csiro/pathling/terminology/local/ComposeTranslator.java: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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:200— terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:200-207 | terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:239-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:343— library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:343-350 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewRegistrationService.java:301-308 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:180— server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:180-187 | server/src/main/java/au/csiro/pathling/operations/view/ViewExecutionHelper.java:222-231 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportFormat.java:64— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportFormat.java:64-71 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/SubmissionState.java:59-66 — 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×5
Focus outline removed in CSS without a :focus replacement licenses/mit - mit.html:295— `.wp-block-jetpack-search-search-input .jetpack-search-input__field:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement ui/src/contexts/ToastContext.css:20— `.toast-viewport` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement site/static/assets/css/home/main.css:2815— `a.arrow:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement site/static/assets/css/home/main.css:2890— `.gallery a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement site/static/assets/css/home/main.css:2943— `.gallery .modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×5
Edited copy of a member (10 corresponding lines) fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/SingleInstanceEvaluator.java:318— fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/SingleInstanceEvaluator.java:318-334 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/SingleInstanceEvaluator.java:518-527 — 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) library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:402— library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:402-411 | server/src/main/java/au/csiro/pathling/operations/sqlquery/CanonicalReference.java:68-78 — 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) terminology/src/main/java/au/csiro/pathling/terminology/translate/TranslateExecutor.java:82— terminology/src/main/java/au/csiro/pathling/terminology/translate/TranslateExecutor.java:82-95 | terminology/src/main/java/au/csiro/pathling/terminology/validatecode/ValidateCodeExecutor.java:79-88 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) REDACTED:457— REDACTED:457-466 | REDACTED:568-577 — 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) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java:613— server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java:613-622 | server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java:640-649 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) server/src/main/java/au/csiro/pathling/async/JobProvider.java:165— server/src/main/java/au/csiro/pathling/async/JobProvider.java:165-176 | server/src/main/java/au/csiro/pathling/async/JobResultProvider.java:117-128 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/async/JobProvider.java` and `server/src/main/java/au/csiro/pathling/async/JobResultProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:133— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:133-144 | server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java: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.
Duplicated block (12 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitAuthProvider.java:217— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitAuthProvider.java:217-228 | terminology/src/main/java/au/csiro/pathling/fhir/ClientAuthInterceptor.java:125-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:280— server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:280-291 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ValueSetMembershipResolver.java:302-313 — 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 `server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:280` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/AsOperator.java:47— fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/AsOperator.java:47-59 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/IsOperator.java:40-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `fhirpath/src/main/java/au/csiro/pathling/fhirpath/operator/AsOperator.java:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `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.
ClassTooLong: SnomedRf2Importer terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:132— ClassTooLong — 827 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 427 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ViewDefinitionResource encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java:90— ClassTooLong — 745 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods. The bar is 400 significant lines; this is 345 over it, 1.86× 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: BulkSubmitExecutor server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:79— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 79 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: FhirTerminologyImporter terminology/src/main/java/au/csiro/pathling/terminology/store/FhirTerminologyImporter.java:105— ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 70 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) server/src/main/java/au/csiro/pathling/FhirServer.java:492— server/src/main/java/au/csiro/pathling/FhirServer.java:492-506 | server/src/main/java/au/csiro/pathling/config/SecurityConfiguration.java:148-160 — 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) library-api/src/main/java/au/csiro/pathling/library/io/sink/DeltaSink.java:329— library-api/src/main/java/au/csiro/pathling/library/io/sink/DeltaSink.java:329-341 | server/src/main/java/au/csiro/pathling/io/SchemaDrift.java:106-118 — 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) fhirpath/src/main/java/au/csiro/pathling/views/ansi/AnsiSqlToSparkDataTypeVisitor.java:63— fhirpath/src/main/java/au/csiro/pathling/views/ansi/AnsiSqlToSparkDataTypeVisitor.java:63-75 | fhirpath/src/main/java/au/csiro/pathling/views/ansi/AnsiSqlToSparkDataTypeVisitor.java:117-129 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ValidationLogic.java:225— fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ValidationLogic.java:225-237 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ValidationLogic.java:318-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.
Duplicated block (13 lines × 2) server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:49— server/src/main/java/au/csiro/pathling/PathlingServerVersion.java:49-61 | utilities/src/main/java/au/csiro/pathling/PathlingVersion.java:49-61 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/PathlingServerVersion.java` and `utilities/src/main/java/au/csiro/pathling/PathlingVersion.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:385— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:385-397 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:637-649 — 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 `server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:385` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:336— server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:336-348 | server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:355-367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:249— server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:249-261 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ValueSetMembershipResolver.java:272-284 — 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 `server/src/main/java/au/csiro/pathling/operations/sqlquery/ConceptMapResolver.java:249` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `cause` to `ConceptMapLimitExceededException` in one and `ExpansionLimitExceededException` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:77— terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:77-83 | terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:117-123 | terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:188-194 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:125` calls `addParameter`, `setName`, `setValue` and `terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DateCollection.java:108— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DateCollection.java:108-114 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DateTimeCollection.java:138-144 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/TimeCollection.java:102-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) server/src/main/java/au/csiro/pathling/operations/create/CreateProviderFactory.java:73— server/src/main/java/au/csiro/pathling/operations/create/CreateProviderFactory.java:73-79 | server/src/main/java/au/csiro/pathling/operations/delete/DeleteProviderFactory.java:72-78 | server/src/main/java/au/csiro/pathling/operations/update/UpdateProviderFactory.java:72-78 — 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 (7 lines × 3) server/src/main/java/au/csiro/pathling/operations/create/CreateProviderFactory.java:89— server/src/main/java/au/csiro/pathling/operations/create/CreateProviderFactory.java:89-95 | server/src/main/java/au/csiro/pathling/operations/delete/DeleteProviderFactory.java:88-94 | server/src/main/java/au/csiro/pathling/operations/update/UpdateProviderFactory.java:88-94 — 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 × 2) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:440— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:440-444 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:483-490 — 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 `server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:440` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:353— terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:353-358 | terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:433-437 — 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 `terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:353` 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) server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:344— server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:344-348 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:167-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) fhirpath/src/main/java/au/csiro/pathling/fhirpath/definition/defaults/DefaultDefinitionContext.java:44— fhirpath/src/main/java/au/csiro/pathling/fhirpath/definition/defaults/DefaultDefinitionContext.java:44-48 | library-api/src/main/java/au/csiro/pathling/library/io/source/DatasetSource.java:82-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2 locations) ui/src/api/bulkSubmit.ts:136— ui/src/api/bulkSubmit.ts:136 · ui/src/api/bulkSubmit.ts:148 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) ui/src/api/sqlOnFhirOperations.ts:376— ui/src/api/sqlOnFhirOperations.ts:376 · ui/src/types/export.ts:101 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (8 lines × 2 locations) ui/src/hooks/useBulkSubmit.ts:174— ui/src/hooks/useBulkSubmit.ts:174 · ui/src/hooks/useSqlExport.ts:86 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) REDACTED:222— REDACTED:222 · REDACTED:129 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Change coupling: SqlQueryInlineTab.tsx ↔ sqlQueryFormHelpers.ts ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:1— `ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx` and `ui/src/components/sqlOnFhir/sqlQueryFormHelpers.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `89bd35d8` feat: Let admin UI queries depend on value sets and concept maps; `3731922d` feat: Add shared parameter value control and completeness checks; `7bdcc078` feat: Author SQL on FHIR view references by canonical URL in the admi… — run `git show` on any of them.
Change coupling: ImportForm.tsx ↔ ImportPnpForm.tsx ui/src/components/import/ImportForm.tsx:1— `ui/src/components/import/ImportForm.tsx` and `ui/src/components/import/ImportPnpForm.tsx` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3e6167df` refactor: Extract FieldLabel component for form field labels; `337bac4b` refactor: Extract FieldGuidance component for form helper text; `29cbc789` refactor: Reorder import form fields and clean up URL schemes — run `git show` on any of them.
Change coupling: Export.tsx ↔ Import.tsx ui/src/pages/Export.tsx:1— `ui/src/pages/Export.tsx` and `ui/src/pages/Import.tsx` change together 52% of the time (11 of the 21 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise 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 `fbfd2ead` fix: Stop an operation failure notifying itself repeatedly; `8a01dc27` refactor: Move request state into useAsyncJob hook; `47cd88dd` refactor: Remove duplicate progress state from page components — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1210— terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1210-1230 | terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1403-1417 — 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) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportResponse.java:176— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportResponse.java:176-194 | server/src/main/java/au/csiro/pathling/operations/export/ExportManifest.java:161-175 — 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) encoders/src/main/java/au/csiro/pathling/encoders/ColumnFunctions.java:49— encoders/src/main/java/au/csiro/pathling/encoders/ColumnFunctions.java:49-63 | encoders/src/main/java/au/csiro/pathling/encoders/ColumnFunctions.java:75-89 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×3
Edited copies of one member (3 members, 6+ corresponding lines) server/src/main/java/au/csiro/pathling/operations/sql/SqlRunFormat.java:171— server/src/main/java/au/csiro/pathling/operations/sql/SqlRunFormat.java:171-178 | server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryOutputFormat.java:94-99 | server/src/main/java/au/csiro/pathling/operations/view/ViewOutputFormat.java:83-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) server/src/main/java/au/csiro/pathling/operations/delete/DeleteProvider.java:72— server/src/main/java/au/csiro/pathling/operations/delete/DeleteProvider.java:72-77 | server/src/main/java/au/csiro/pathling/read/ReadProvider.java:70-75 | server/src/main/java/au/csiro/pathling/search/SearchProvider.java:90-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:571— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:571-580 | server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:337-342 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:194-199 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (11 lines × 2) library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:354— library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:354-364 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewRegistrationService.java:287-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:131— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:131-141 | server/src/main/java/au/csiro/pathling/operations/sql/SqlExportSupport.java:120-130 — 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 (11 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:664— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:664-674 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:823-833 — 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 `server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:664` 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, `server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:675` calls `debug` and `server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:834` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) encoders/src/main/java/au/csiro/pathling/encoders/ColumnFunctions.java:51— encoders/src/main/java/au/csiro/pathling/encoders/ColumnFunctions.java:51-56 | encoders/src/main/java/au/csiro/pathling/encoders/ColumnFunctions.java:77-82 — 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) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitResultBuilder.java:108— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitResultBuilder.java:108-113 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitResultBuilder.java:131-136 — 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 `server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitResultBuilder.java:108` 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) server/src/main/java/au/csiro/pathling/operations/create/CreateProvider.java:75— server/src/main/java/au/csiro/pathling/operations/create/CreateProvider.java:75-80 | server/src/main/java/au/csiro/pathling/operations/update/UpdateProvider.java:74-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `server/src/main/java/au/csiro/pathling/operations/create/CreateProvider.java:75` 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 (16 lines × 2 locations) ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:168— ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:168 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:194 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (16 lines × 2 locations) ui/src/hooks/useSqlQueryLibraries.ts:58— ui/src/hooks/useSqlQueryLibraries.ts:58 · ui/src/hooks/useSqlViews.ts:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (16 lines × 2 locations) ui/src/pages/Export.tsx:51— ui/src/pages/Export.tsx:51 · ui/src/pages/Import.tsx:68 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) ui/src/components/export/ExportOptions.tsx:123— ui/src/components/export/ExportOptions.tsx:123 · ui/src/components/export/ExportOptions.tsx:132 — 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 locations) ui/src/components/export/ExportOptions.tsx:171— ui/src/components/export/ExportOptions.tsx:171 · ui/src/components/resources/ResourceSearchForm.tsx:154 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) ui/src/pages/Import.tsx:43— ui/src/pages/Import.tsx:43 · ui/src/pages/Import.tsx:58 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×2
Edited copy of a member (44 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:132— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:132-175 | server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:227-273 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (44 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:434— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:434-477 | server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:506-553 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) server/src/main/java/au/csiro/pathling/io/DynamicDeltaSource.java:242— server/src/main/java/au/csiro/pathling/io/DynamicDeltaSource.java:242-263 | server/src/main/java/au/csiro/pathling/io/SchemaMigrator.java:191-210 — 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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/encoding/QuantityEncoding.java:268— fhirpath/src/main/java/au/csiro/pathling/fhirpath/encoding/QuantityEncoding.java:268-287 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/encoding/QuantityEncoding.java:334-356 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) server/src/main/java/au/csiro/pathling/async/JobProvider.java:104— server/src/main/java/au/csiro/pathling/async/JobProvider.java:104-119 | server/src/main/java/au/csiro/pathling/async/JobProvider.java:145-161 | server/src/main/java/au/csiro/pathling/async/JobResultProvider.java:95-112 — 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) server/src/main/java/au/csiro/pathling/operations/create/CreateProvider.java:98— server/src/main/java/au/csiro/pathling/operations/create/CreateProvider.java:98-118 | server/src/main/java/au/csiro/pathling/operations/delete/DeleteProvider.java:94-109 | server/src/main/java/au/csiro/pathling/operations/update/UpdateProvider.java:98-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:531— terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:531-549 | terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:564-579 — 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) lib/python/pathling/cli/fhirpath.py:59— lib/python/pathling/cli/fhirpath.py:59-74 | lib/python/pathling/cli/sparkconf.py:44-63 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:150— library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:150-163 | library-api/src/main/java/au/csiro/pathling/library/terminology/TerminologyRelations.java:216-229 — 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) server/src/main/java/au/csiro/pathling/async/JobProvider.java:163— server/src/main/java/au/csiro/pathling/async/JobProvider.java:163-176 | server/src/main/java/au/csiro/pathling/async/JobResultProvider.java:115-128 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:177— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:177-188 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:190-201 — 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) library-api/src/main/java/au/csiro/pathling/library/io/source/DeltaSource.java:68— library-api/src/main/java/au/csiro/pathling/library/io/source/DeltaSource.java:68-79 | library-api/src/main/java/au/csiro/pathling/library/io/source/NdjsonSource.java:86-97 — 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 (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryOutputFormat.java:75— server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryOutputFormat.java:75-86 | server/src/main/java/au/csiro/pathling/operations/view/ViewOutputFormat.java:65-75 — 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) terminology/src/main/java/au/csiro/pathling/terminology/store/ConceptMapStaging.java:271— terminology/src/main/java/au/csiro/pathling/terminology/store/ConceptMapStaging.java:271-282 | terminology/src/main/java/au/csiro/pathling/terminology/store/ValueSetStaging.java:117-127 — 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 (15–16 lines × 2) server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:382— server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:382-396 | server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:462-477 — 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 `server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:382` 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, `server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:379` calls `addSearchParameters` and `server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:459` 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 (15–16 lines × 2) server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:200— server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:200-215 | server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:229-243 — 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 `server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:243` calls `getAuth`, `isEnabled`, `checkHasAuthority` and `server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:215` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) server/src/main/java/au/csiro/pathling/async/JobProvider.java:146— server/src/main/java/au/csiro/pathling/async/JobProvider.java:146-159 | server/src/main/java/au/csiro/pathling/async/JobResultProvider.java:96-109 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/async/JobProvider.java` and `server/src/main/java/au/csiro/pathling/async/JobResultProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:536— terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:536-549 | terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:566-579 — 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 `terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:536` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Path` names `java.nio.file.Path` in one and `org.apache.hadoop.fs.Path` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStageLoader.java:375— terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStageLoader.java:375-383 | terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:1211-1219 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) encoders/src/main/scala/au/csiro/pathling/encoders/SerializerBuilder.scala:211— encoders/src/main/scala/au/csiro/pathling/encoders/SerializerBuilder.scala:211-219 | encoders/src/main/scala/au/csiro/pathling/encoders/datatypes/DataTypeMappings.scala:60-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Low cohesion: MockTerminologyService (LCOM4 5) terminology/src/main/java/au/csiro/pathling/terminology/mock/MockTerminologyService.java:58— MockTerminologyService's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BulkSubmitValidator (LCOM4 4) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitValidator.java:48— BulkSubmitValidator'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.
Duplicated block (19 lines × 2 locations) ui/src/api/bulkExport.ts:266— ui/src/api/bulkExport.ts:266 · ui/src/api/job.ts:63 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) ui/src/api/sqlOnFhirOperations.ts:166— ui/src/api/sqlOnFhirOperations.ts:166 · ui/src/api/sqlOnFhirOperations.ts:293 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) ui/src/components/export/ExportCard.tsx:239— ui/src/components/export/ExportCard.tsx:239 · ui/src/components/sqlOnFhir/ExportJobCard.tsx:227 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:365— ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:365 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:472 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (10 lines × 2 locations) ui/src/components/import/ImportCard.tsx:127— ui/src/components/import/ImportCard.tsx:127 · ui/src/components/sqlOnFhir/ViewCard.tsx:146 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) ui/src/components/import/ImportCard.tsx:140— ui/src/components/import/ImportCard.tsx:140 · ui/src/components/sqlOnFhir/ExportJobCard.tsx:157 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (8 lines × 3 locations) ui/src/components/SearchParamsInput.tsx:95— ui/src/components/SearchParamsInput.tsx:95 · ui/src/components/import/ImportForm.tsx:86 · ui/src/components/resources/ResourceSearchForm.tsx:110 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 3 locations) ui/src/hooks/useBulkExport.ts:111— ui/src/hooks/useBulkExport.ts:111 · ui/src/hooks/useImport.ts:65 · ui/src/hooks/useImportPnp.ts:77 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Swallowed exception (caught, then discarded) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlValidator.java:848— `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) fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/FhirResourceResolver.java:144— `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.
AC3 · Page structure· Heading level jumps from h2 to h5 · ×1
Heading level jumps from h2 to h5 licenses/apache-2.0 - license-2.0.html:460— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Multiple navigation landmarks without distinguishing labels licenses/epl 2.0 - epl-2.0.html:1— With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus licenses/mit - mit.html:1314— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Low contrast colour pair in CSS (1.8:1) site/static/assets/css/home/main.css:2215— `input[type=checkbox]:checked + label:before, input[type=radio]:checked + label:before` sets color: #ffffff on background-color: #17d0f4 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Stateful singleton: CacheableDatabase server/src/main/java/au/csiro/pathling/cache/CacheableDatabase.java:56— `CacheableDatabase` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (cacheKey; e.g. `cacheKey` in `invalidate` at line 230).
ViewDefinitionResource.copy (cyclomatic 48) encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java:601— ViewDefinitionResource.copy has cyclomatic complexity 48 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java holds 2 of the 25 methods over the threshold — including the worst — and 52 of the 208 points over it (25%), 3.1× the next-largest file (.github/scripts/dap_upload.py at 17). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ViewDefinitionResource.isEmpty (cyclomatic 34) encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java:728— ViewDefinitionResource.isEmpty has cyclomatic complexity 34 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java holds 2 of the 25 methods over the threshold — including the worst — and 52 of the 208 points over it (25%), 3.1× the next-largest file (.github/scripts/dap_upload.py at 17). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
dap_upload.main (cyclomatic 32) .github/scripts/dap_upload.py:87— dap_upload.main has cyclomatic complexity 32 (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.
auth.checkServerCapabilities (cyclomatic 29) REDACTED:126— auth.checkServerCapabilities has cyclomatic complexity 29 (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.
SqlQueryForm.SqlQueryForm (cyclomatic 28) ui/src/components/sqlOnFhir/SqlQueryForm.tsx:93— SqlQueryForm.SqlQueryForm has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 5 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.
ViewDefinitionForm.ViewDefinitionForm (cyclomatic 28) ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:88— ViewDefinitionForm.ViewDefinitionForm has cyclomatic complexity 28 (threshold 15). Of this number, 20 points are the body's own statements and 8 belong to 4 function items inside it that branch. 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.
VersionResolver.guessLatestOfVersions (cyclomatic 25) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:336— VersionResolver.guessLatestOfVersions 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.
SqlDependencyResolver.resolveReference (cyclomatic 24) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java:264— SqlDependencyResolver.resolveReference 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.
ResourceCard.getResourceSummary (cyclomatic 24) ui/src/components/resources/ResourceCard.tsx:54— ResourceCard.getResourceSummary has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BulkExportClient._configure_builder (cyclomatic 23) lib/python/pathling/bulk.py:111— BulkExportClient._configure_builder 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.
FhirServer.initialize (cyclomatic 22) server/src/main/java/au/csiro/pathling/FhirServer.java:264— FhirServer.initialize has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useServerCapabilities.parseCapabilities (cyclomatic 22) REDACTED:88— useServerCapabilities.parseCapabilities 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.
ExportCard.ExportCard (cyclomatic 22) ui/src/components/export/ExportCard.tsx:84— ExportCard.ExportCard has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
config._resolve_tx_store (cyclomatic 21) lib/python/pathling/cli/config.py:470— config._resolve_tx_store has cyclomatic complexity 21 (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.
config.resolve_config (cyclomatic 21) lib/python/pathling/cli/config.py:609— config.resolve_config has cyclomatic complexity 21 (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.
SqlQueryInlineTab.SqlQueryInlineTab (cyclomatic 21) ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:143— SqlQueryInlineTab.SqlQueryInlineTab has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 262, 400, 337, …). 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.
ConformanceProvider.buildResources (cyclomatic 19) server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:356— ConformanceProvider.buildResources 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.
SnomedRf2Importer.locateFiles (cyclomatic 19) terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:609— SnomedRf2Importer.locateFiles 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.
VersionResolver.versionsAreEquivalent (cyclomatic 18) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:419— VersionResolver.versionsAreEquivalent 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.
CodeSystemStreamFlattener.flattenProperties (cyclomatic 18) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:232— CodeSystemStreamFlattener.flattenProperties 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.
ExportJobCard.ExportJobCard (cyclomatic 18) ui/src/components/sqlOnFhir/ExportJobCard.tsx:115— ExportJobCard.ExportJobCard has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
FhirPathDateTime.parse (cyclomatic 17) fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:62— FhirPathDateTime.parse 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.
ErrorHandlingInterceptor.convertError (cyclomatic 17) server/src/main/java/au/csiro/pathling/errors/ErrorHandlingInterceptor.java:120— ErrorHandlingInterceptor.convertError 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.
ImportPnpExecutor.buildBulkExportClient (cyclomatic 17) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java:230— ImportPnpExecutor.buildBulkExportClient 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.
DenseIdPreOrder.compute (cyclomatic 16) terminology/src/main/java/au/csiro/pathling/terminology/store/DenseIdPreOrder.java:69— DenseIdPreOrder.compute 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.
TodoComment server/src/main/java/au/csiro/pathling/async/RequestTagFactory.java:87— // TODO - implement auth correctly in E-Tag — 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.
ViewDefinitionResource.copy (cognitive 62) encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java:601— ViewDefinitionResource.copy has cognitive complexity 62 (threshold 15). Drivers by points: loops 15 (30 pts), ternaries 17, if/else 15 (nesting depth added 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
auth.checkServerCapabilities (cognitive 59) REDACTED:126— auth.checkServerCapabilities has cognitive complexity 59 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 8 (21 pts), boolean chains 11, error handling 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useServerCapabilities.parseCapabilities (cognitive 57) REDACTED:88— useServerCapabilities.parseCapabilities has cognitive complexity 57 (threshold 15). Drivers by points: if/else 8 (29 pts), loops 9 (24 pts), boolean chains 4 (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.
VersionResolver.guessLatestOfVersions (cognitive 46) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:336— VersionResolver.guessLatestOfVersions has cognitive complexity 46 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 4 (14 pts), boolean chains 8, error handling 1 (4 pts), loops 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dap_upload.main (cognitive 45) .github/scripts/dap_upload.py:87— dap_upload.main has cognitive complexity 45 (threshold 15). Drivers by points: if/else 27 (33 pts), error handling 5 (8 pts), boolean chains 2, loops 2 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BulkExportClient._configure_builder (cognitive 38) lib/python/pathling/bulk.py:111— BulkExportClient._configure_builder has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (30 pts), loops 4 (8 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeSystemStreamFlattener.flattenProperties (cognitive 37) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStreamFlattener.java:232— CodeSystemStreamFlattener.flattenProperties has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlDependencyResolver.resolveReference (cognitive 34) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java:264— SqlDependencyResolver.resolveReference has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (29 pts), error handling 2 (4 pts), ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewDefinitionResource.isEmpty (cognitive 33) encoders/src/main/java/au/csiro/pathling/encoders/ViewDefinitionResource.java:728— ViewDefinitionResource.isEmpty has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 33. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
VersionResolver.versionsAreEquivalent (cognitive 28) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:419— VersionResolver.versionsAreEquivalent has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 5 (8 pts), boolean chains 6, error handling 1 (3 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.
ConformanceProvider.buildResources (cognitive 27) server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java:356— ConformanceProvider.buildResources has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 3, loops 1, ternaries 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.
ResourceCard.getResourceSummary (cognitive 27) ui/src/components/resources/ResourceCard.tsx:54— ResourceCard.getResourceSummary has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 10 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
FhirServer.initialize (cognitive 26) server/src/main/java/au/csiro/pathling/FhirServer.java:264— FhirServer.initialize has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15, loops 5 (10 pts), error handling 1 (nesting depth added 5). 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.
config.resolve_config (cognitive 24) lib/python/pathling/cli/config.py:609— config.resolve_config has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 10, ternaries 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.
ViewDefinitionForm.ViewDefinitionForm (cognitive 24) ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:88— ViewDefinitionForm.ViewDefinitionForm has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, ternaries 4 (6 pts), if/else 4, error handling 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 9 belong to 4 function items inside it that branch. 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.
ErrorHandlingInterceptor.convertError (cognitive 23) server/src/main/java/au/csiro/pathling/errors/ErrorHandlingInterceptor.java:120— ErrorHandlingInterceptor.convertError has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 11 (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.
SnomedRf2Importer.locateFiles (cognitive 23) terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java:609— SnomedRf2Importer.locateFiles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config._resolve_tx_store (cognitive 23) lib/python/pathling/cli/config.py:470— config._resolve_tx_store has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 9, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SqlQueryForm.SqlQueryForm (cognitive 22) ui/src/components/sqlOnFhir/SqlQueryForm.tsx:93— SqlQueryForm.SqlQueryForm has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), ternaries 5 (6 pts), error handling 1 (nesting depth added 2). Of this number, 11 points are the body's own statements and 11 belong to 5 function items inside it that branch. 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.
ImportPnpExecutor.buildBulkExportClient (cognitive 21) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java:230— ImportPnpExecutor.buildBulkExportClient has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 3, ternaries 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.
DenseIdPreOrder.compute (cognitive 21) terminology/src/main/java/au/csiro/pathling/terminology/store/DenseIdPreOrder.java:69— DenseIdPreOrder.compute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 8 (9 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.
config.load_config_file (cognitive 21) lib/python/pathling/cli/config.py:289— config.load_config_file has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (7 pts), boolean chains 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.
VersionResolver.compareSemVer (cognitive 20) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:281— VersionResolver.compareSemVer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, loops 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.
ImportPnpExecutor.validateDownloadResult (cognitive 19) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpExecutor.java:366— ImportPnpExecutor.validateDownloadResult has cognitive complexity 19 (threshold 15). Drivers by points: error handling 3 (10 pts), if/else 3 (7 pts), loops 1, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rest.search (cognitive 19) ui/src/api/rest.ts:90— rest.search has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (8 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.
SqlQueryInlineTab.SqlQueryInlineTab (cognitive 19) ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:143— SqlQueryInlineTab.SqlQueryInlineTab has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, ternaries 6. Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 262, 400, 337, …). 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.
ExportOperationValidator.parseTypeFilters (cognitive 18) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:322— ExportOperationValidator.parseTypeFilters has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, 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.
ExpandExecutor.page (cognitive 18) terminology/src/main/java/au/csiro/pathling/terminology/expand/ExpandExecutor.java:158— ExpandExecutor.page has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 2, boolean chains 1, 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.
LocalTerminologyService.addDesignations (cognitive 18) terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java:927— LocalTerminologyService.addDesignations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 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.
VersionResolver.getLatestOfSnomedVersions (cognitive 18) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:118— VersionResolver.getLatestOfSnomedVersions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, 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.
FhirPathDateTime.parse (cognitive 17) fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:62— FhirPathDateTime.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, ternaries 7, boolean chains 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.
LocalTerminologyService.buildLookup (cognitive 17) terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java:803— LocalTerminologyService.buildLookup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 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.
PathlingContext.create (cognitive 17) REDACTED:133— PathlingContext.create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, 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.
SqlLibraryParser.extractViewReferences (cognitive 16) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlLibraryParser.java:175— SqlLibraryParser.extractViewReferences has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 1 (3 pts), boolean chains 2, 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.
ConceptMapReader.search (cognitive 16) terminology/src/main/java/au/csiro/pathling/terminology/conceptmap/ConceptMapReader.java:111— ConceptMapReader.search has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 3, loops 2 (3 pts), error handling 2, ternaries 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.
VersionResolver.getLatestOfDateVersions (cognitive 16) terminology/src/main/java/au/csiro/pathling/terminology/local/VersionResolver.java:189— VersionResolver.getLatestOfDateVersions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, 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.
UnresolvedTransformTree.mapChildren (cognitive 16) encoders/src/main/scala/au/csiro/pathling/encoders/Expressions.scala:665— UnresolvedTransformTree.mapChildren has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, error handling 1, match/switch 1 (nesting depth added 3). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
errors.friendly_message (cognitive 16) lib/python/pathling/cli/errors.py:157— errors.friendly_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: SqlDependencyResolver.resolveReference server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java:264— MethodTooLong — resolveReference runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Near-duplicate member pair (25 shared lines) library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:113— library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:113-166 | library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.java:107-157 — These two members are variants of one another: 25 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· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:104— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:104-153 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportProvider.java:109-150 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:659— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:659-695 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:820-858 — 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) library-api/src/main/java/au/csiro/pathling/library/io/sink/CatalogSink.java:100— library-api/src/main/java/au/csiro/pathling/library/io/sink/CatalogSink.java:100-137 | library-api/src/main/java/au/csiro/pathling/library/io/sink/DeltaSink.java:104-131 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) terminology/src/main/java/au/csiro/pathling/terminology/local/index/RefsetIndex.java:62— terminology/src/main/java/au/csiro/pathling/terminology/local/index/RefsetIndex.java:62-83 | terminology/src/main/java/au/csiro/pathling/terminology/local/index/RelationshipIndex.java:62-84 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:198— server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:198-225 | server/src/main/java/au/csiro/pathling/operations/update/BatchProvider.java:228-254 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) server/src/main/java/au/csiro/pathling/operations/OperationValidation.java:50— server/src/main/java/au/csiro/pathling/operations/OperationValidation.java:50-74 | server/src/main/java/au/csiro/pathling/operations/OperationValidation.java:86-114 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) server/src/main/java/au/csiro/pathling/operations/sql/SqlFilterResolver.java:107— server/src/main/java/au/csiro/pathling/operations/sql/SqlFilterResolver.java:107-140 | server/src/main/java/au/csiro/pathling/operations/sql/SqlFilterResolver.java:150-179 — 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 copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java:196— fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java:196-222 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ValidationLogic.java:99-122 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:377— server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:377-399 | server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java:626-652 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:71— terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:71-91 | terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:151-165 | terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:185-206 | terminology/src/main/java/au/csiro/pathling/fhir/DefaultTerminologyClient.java:214-230 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) fhirpath/src/main/java/au/csiro/pathling/sql/misc/HighBoundaryForDateTime.java:75— fhirpath/src/main/java/au/csiro/pathling/sql/misc/HighBoundaryForDateTime.java:75-92 | fhirpath/src/main/java/au/csiro/pathling/sql/misc/LowBoundaryForDateTime.java:75-92 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) server/src/main/java/au/csiro/pathling/async/SparkJobListener.java:64— server/src/main/java/au/csiro/pathling/async/SparkJobListener.java:64-82 | server/src/main/java/au/csiro/pathling/async/SparkJobListener.java:85-106 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) lib/python/pathling/cli/terminology.py:413— lib/python/pathling/cli/terminology.py:413-444 | lib/python/pathling/cli/terminology.py:826-856 | lib/python/pathling/cli/terminology.py:895-929 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.java:422— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.java:422-428 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.java:439-445 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.java:456-462 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/resolver/FunctionInvocation.java:60— fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/resolver/FunctionInvocation.java:60-69 | terminology/src/main/java/au/csiro/pathling/fhirpath/encoding/ImmutableCoding.java:111-122 | terminology/src/main/java/au/csiro/pathling/terminology/TerminologyService.java:67-78 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:202— terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:202-214 | terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:256-267 | terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:279-289 | terminology/src/main/java/au/csiro/pathling/terminology/store/CodeSystemStaging.java:317-327 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) fhirpath/src/main/java/au/csiro/pathling/fhirpath/definition/defaults/DefaultChoiceDefinition.java:78— fhirpath/src/main/java/au/csiro/pathling/fhirpath/definition/defaults/DefaultChoiceDefinition.java:78-80 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/definition/defaults/DefaultCompositeDefinition.java:48-50 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/definition/defaults/DefaultResourceDefinition.java:39-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (21–23 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:435— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:435-455 | server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:507-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:530` calls `filter` and `server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:456` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18–21 lines × 2) fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:73— fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:73-93 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathTime.java:66-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:456— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:456-474 | server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:531-550 — 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 `server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:456` 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, `server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:529` calls `filter` and `server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:454` 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 (17–18 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:159— server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:159-175 | server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:256-273 — 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 `server/src/main/java/au/csiro/pathling/operations/bulkexport/ExportOperationValidator.java:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:119— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:119-133 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportProvider.java:125-139 — 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 `server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:119` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9–13 lines × 3) server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:100— server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:100-108 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:150-158 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.java:193-205 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:100` 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 (12 lines × 3) server/src/main/java/au/csiro/pathling/async/JobProvider.java:105— server/src/main/java/au/csiro/pathling/async/JobProvider.java:105-116 | server/src/main/java/au/csiro/pathling/async/JobProvider.java:148-159 | server/src/main/java/au/csiro/pathling/async/JobResultProvider.java:98-109 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/async/JobProvider.java` and `server/src/main/java/au/csiro/pathling/async/JobResultProvider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7–8 lines × 2) server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryResultStreamer.java:123— server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryResultStreamer.java:123-129 | server/src/main/java/au/csiro/pathling/operations/view/ViewExecutionHelper.java:136-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6–7 lines × 2) server/src/main/java/au/csiro/pathling/operations/bulkexport/PatientExportProvider.java:162— server/src/main/java/au/csiro/pathling/operations/bulkexport/PatientExportProvider.java:162-167 | server/src/main/java/au/csiro/pathling/operations/bulkexport/PatientExportProvider.java:171-177 — 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 `server/src/main/java/au/csiro/pathling/operations/bulkexport/PatientExportProvider.java:171` 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 (4–6 lines × 3) server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:267— server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:267-272 | server/src/main/java/au/csiro/pathling/operations/sqlquery/LibraryReferenceResolver.java:102-105 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:145-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:267` 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 (44 lines × 2) fhirpath/src/main/java/au/csiro/pathling/fhirpath/variable/Hl7ExtensionResolver.java:1— fhirpath/src/main/java/au/csiro/pathling/fhirpath/variable/Hl7ExtensionResolver.java:1-44 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/variable/Hl7ValueSetResolver.java:1-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `fhirpath/src/main/java/au/csiro/pathling/fhirpath/variable/Hl7ExtensionResolver.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) server/src/main/java/au/csiro/pathling/operations/sql/FhirViewValidator.java:136— server/src/main/java/au/csiro/pathling/operations/sql/FhirViewValidator.java:136-141 | server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.java:205-210 | server/src/main/java/au/csiro/pathling/operations/view/ViewExecutionHelper.java:204-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 6) fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/BooleanCollection.java:67— fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/BooleanCollection.java:67-74 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/CodingCollection.java:103-110 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DateTimeCollection.java:78-85 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/DecimalCollection.java:84-91 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/IntegerCollection.java:91-98 | fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/QuantityCollection.java:108-115 — 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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/BooleanCollection.java:67` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `definition` to `Optional<NodeDefinition>` in one and `Optional<? extends NodeDefinition>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 3) library-api/src/main/java/au/csiro/pathling/library/io/SaveMode.java:79— library-api/src/main/java/au/csiro/pathling/library/io/SaveMode.java:79-86 | server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportMode.java:56-63 | terminology/src/main/java/au/csiro/pathling/config/TerminologyMode.java:55-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) server/src/main/java/au/csiro/pathling/operations/sql/SqlRunFormat.java:174— server/src/main/java/au/csiro/pathling/operations/sql/SqlRunFormat.java:174-178 | server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryOutputFormat.java:95-99 | server/src/main/java/au/csiro/pathling/operations/view/ViewOutputFormat.java:84-88 — before extracting anything, compare `server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryOutputFormat.java` and `server/src/main/java/au/csiro/pathling/operations/view/ViewOutputFormat.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Edited copy of a member (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:175— test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:175-239 | test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:436-508 — 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.
Duplicated block (11–13 lines × 4) test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:187— test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:187-199 | test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:442-452 | test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:468-478 | test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:487-498 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:480` calls `addItem` and `test-data/src/main/java/au/csiro/pathling/testdata/QuestionnaireResponseGenerator.java:454` 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.
Outbound HTTP without resilience server/src/main/java/au/csiro/pathling/security/PathlingJwtDecoderBuilder.java:106— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplication concentrated across 4 sibling directories (13 clone groups) ui/src/components/export/ExportCard.tsx:150— 13 duplicated blocks under ui/src/components/ have copies in at least two of the sibling directories export, import, resources, sqlOnFhir — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (7 clone groups) ui/src/components/jobs/JobsTable.tsx:110— 7 duplicated blocks under ui/src/ have copies in at least two of the sibling directories api, components, hooks, pages, services, types — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (75 matched lines × 2 locations) · ×1
Duplicated block with local edits (75 matched lines × 2 locations) ui/src/components/sqlOnFhir/SqlQueryCard.tsx:69— ui/src/components/sqlOnFhir/SqlQueryCard.tsx:69 · ui/src/components/sqlOnFhir/ViewCard.tsx:104 — the two spans are one implementation copied and then locally edited — 546 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (73 matched lines × 2 locations) · ×1
Duplicated block with local edits (73 matched lines × 2 locations) ui/src/api/bulkExport.ts:69— ui/src/api/bulkExport.ts:69 · ui/src/api/bulkSubmit.ts:80 — the two spans are one implementation copied and then locally edited — 366 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) ui/src/components/sqlOnFhir/SqlQueryForm.tsx:180— ui/src/components/sqlOnFhir/SqlQueryForm.tsx:180 · ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:117 — the two spans are one implementation copied and then locally edited — 347 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) ui/src/components/export/ExportCard.tsx:150— ui/src/components/export/ExportCard.tsx:150 · ui/src/components/sqlOnFhir/ExportJobCard.tsx:158 — the two spans are one implementation copied and then locally edited — 272 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) ui/src/hooks/useImport.ts:57— ui/src/hooks/useImport.ts:57 · ui/src/hooks/useImportPnp.ts:69 — the two spans are one implementation copied and then locally edited — 203 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (23 lines × 2 locations) ui/src/components/import/ImportForm.tsx:99— ui/src/components/import/ImportForm.tsx:99 · ui/src/components/import/ImportPnpForm.tsx:96 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (22 lines × 2 locations) ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:261— ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:261 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:336 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:309— ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:309 · ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:370 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2 locations) ui/src/api/rest.ts:196— ui/src/api/rest.ts:196 · ui/src/api/rest.ts:236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 3 locations) ui/src/components/SearchParamsInput.tsx:146— ui/src/components/SearchParamsInput.tsx:146 · ui/src/components/import/ImportForm.tsx:163 · ui/src/components/resources/ResourceSearchForm.tsx:173 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (15 lines × 4 locations) ui/src/api/bulkExport.ts:154— ui/src/api/bulkExport.ts:154 · ui/src/api/import.ts:114 · ui/src/api/import.ts:240 · ui/src/api/sqlOnFhirOperations.ts:312 — the 4 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 3 locations) ui/src/api/import.ts:109— ui/src/api/import.ts:109 · ui/src/api/import.ts:235 · ui/src/api/sqlOnFhirOperations.ts:307 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (13 lines × 2 locations) ui/src/components/SearchParamsInput.tsx:109— ui/src/components/SearchParamsInput.tsx:109 · ui/src/components/resources/ResourceSearchForm.tsx:157 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 3 locations) ui/src/components/export/ExportForm.tsx:86— ui/src/components/export/ExportForm.tsx:86 · ui/src/components/import/ImportForm.tsx:107 · ui/src/components/import/ImportPnpForm.tsx:104 — the 3 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (11 lines × 2 locations) ui/src/components/export/ExportOptions.tsx:159— ui/src/components/export/ExportOptions.tsx:159 · ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:178 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (11 lines × 3 locations) ui/src/components/sqlOnFhir/ExportSetPanel.tsx:151— ui/src/components/sqlOnFhir/ExportSetPanel.tsx:151 · ui/src/components/sqlOnFhir/ExportSetPanel.tsx:163 · ui/src/components/sqlOnFhir/ExportSetPanel.tsx:175 — 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 (9 lines × 6 locations) ui/src/components/export/ExportForm.tsx:88— ui/src/components/export/ExportForm.tsx:88 · ui/src/components/export/ExportOptions.tsx:161 · ui/src/components/import/ImportForm.tsx:112 · ui/src/components/import/ImportPnpForm.tsx:109 · +2 more site(s) not listed — the 6 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (8 lines × 4 locations) ui/src/components/sqlOnFhir/SqlOnFhirForm.tsx:104— ui/src/components/sqlOnFhir/SqlOnFhirForm.tsx:104 · ui/src/components/sqlOnFhir/SqlQueryForm.tsx:249 · ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:157 · ui/src/pages/Import.tsx:92 — the 4 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) ui/src/components/resources/ResourceSearchForm.tsx:91— ui/src/components/resources/ResourceSearchForm.tsx:91 · ui/src/types/exportOptions.ts:80 — the two spans are one implementation copied and then locally edited — 67 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (7 lines × 2 locations) REDACTED:91— REDACTED:91 · REDACTED:139 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function getResourceSummary (cyclomatic 41, cognitive 38) ui/src/components/resources/ResourceCard.tsx:54— getResourceSummary has cyclomatic complexity 41 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseCapabilities (cyclomatic 31, cognitive 66) REDACTED:88— parseCapabilities has cyclomatic complexity 31 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkServerCapabilities (cyclomatic 29, cognitive 59) REDACTED:126— checkServerCapabilities has cyclomatic complexity 29 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SqlQueryForm (cyclomatic 24, cognitive 18) ui/src/components/sqlOnFhir/SqlQueryForm.tsx:93— SqlQueryForm has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ViewDefinitionForm (cyclomatic 21, cognitive 17) ui/src/components/sqlOnFhir/ViewDefinitionForm.tsx:88— ViewDefinitionForm has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ExportCard (cyclomatic 20, cognitive 12) ui/src/components/export/ExportCard.tsx:84— ExportCard has cyclomatic complexity 20 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ExportJobCard (cyclomatic 16, cognitive 9) ui/src/components/sqlOnFhir/ExportJobCard.tsx:115— ExportJobCard has cyclomatic complexity 16 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function libraryToSummary (cyclomatic 15, cognitive 16) ui/src/hooks/sqlQueryHelpers.ts:96— libraryToSummary has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Dashboard (cyclomatic 14, cognitive 11) ui/src/pages/Dashboard.tsx:46— Dashboard has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildPnpParameters (cyclomatic 13, cognitive 15) ui/src/api/import.ts:140— buildPnpParameters has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SqlQueryStoredTab (cyclomatic 13, cognitive 12) ui/src/components/sqlOnFhir/SqlQueryStoredTab.tsx:73— SqlQueryStoredTab has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ImportCard (cyclomatic 13, cognitive 9) ui/src/components/import/ImportCard.tsx:82— ImportCard has cyclomatic complexity 13 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function search (cyclomatic 11, cognitive 20) ui/src/api/rest.ts:90— search has cyclomatic complexity 11 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 11, cognitive 9) ui/src/pages/BulkSubmit.tsx:57— (anonymous) has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx · ×1
ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx: 475 lines of code ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx:1— ui/src/components/sqlOnFhir/SqlQueryInlineTab.tsx has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~31 LoC) ui/src/types/polling.ts— no import path from any entry point (13 application, 5 tooling, 99 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Third-party script without Subresource Integrity licenses/apache-2.0 - license-2.0.html:34— `https://www.apachecon.com/event-images/snippet.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 41 such include(s) across the repository's markup.
redundant comment ui/e2e/export.spec.ts:507— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/export.spec.ts:710— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/export.spec.ts:985— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/import.spec.ts:272— "Click add input button." repeats the code it sits on: 4 of its 4 words (click, add, input, button) are already in `await page.getByRole("button", { name: "Add input" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/import.spec.ts:456— "Click cancel button." repeats the code it sits on: 3 of its 3 words (click, cancel, button) are already in `await page.getByRole("button", { name: "Cancel" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/import.spec.ts:907— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/import.spec.ts:968— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/resources.spec.ts:125— "Click search button." repeats the code it sits on: 3 of its 3 words (click, search, button) are already in `await page.getByRole("button", { name: "Search" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/resources.spec.ts:222— "Click add filter button." repeats the code it sits on: 4 of its 4 words (click, add, filter, button) are already in `await page.getByRole("button", { name: "Add filter" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/resources.spec.ts:344— "Grant clipboard permissions." repeats the code it sits on: 3 of its 3 words (grant, clipboard, permissions) are already in `await context.grantPermissions(["clipboard-read", "clipboard-write"]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/resources.spec.ts:535— "Click cancel button." repeats the code it sits on: 3 of its 3 words (click, cancel, button) are already in `await page.getByRole("button", { name: "Cancel" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/sqlOnFhir.spec.ts:239— "Grant clipboard permissions." repeats the code it sits on: 3 of its 3 words (grant, clipboard, permissions) are already in `await context.grantPermissions(["clipboard-read", "clipboard-write"]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/sqlOnFhir.spec.ts:249— "Click the copy button." repeats the code it sits on: 3 of its 3 words (click, copy, button) are already in `await page.getByRole("button", { name: "Copy to clipboard" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/sqlOnFhir.spec.ts:1100— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/e2e/sqlOnFhir.spec.ts:1158— "Click close button." repeats the code it sits on: 3 of its 3 words (click, close, button) are already in `await page.getByRole("button", { name: "Close" }).click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/auth/__tests__/SessionExpiredDialog.test.tsx:39— "Mock the auth context." repeats the code it sits on: 3 of its 3 words (mock, auth, context) are already in `vi.mock("../../../contexts/AuthContext", () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/export/__tests__/ExportCard.test.tsx:192— "Verify deleteJob was called before onClose." repeats the code it sits on: 4 of its 5 words (delete, job, called, close) are already in `expect(mockDeleteJob.mock.invocationCallOrder[0]).toBeLessThan(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/import/__tests__/ImportCard.test.tsx:66— "Mock useImport hook." repeats the code it sits on: 4 of its 4 words (mock, use, import, hook) are already in `vi.mock("../../../hooks", () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/import/__tests__/ImportCard.test.tsx:90— "Mock formatDateTime utility." repeats the code it sits on: 4 of its 5 words (mock, format, date, time) are already in `vi.mock("../../../utils", () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/jobs/__tests__/JobsContent.test.tsx:180— "Dismissing the confirmation leaves the job alone." repeats the code it sits on: 5 of its 5 words (dismissing, confirmation, leaves, job, alone) are already in `it("leaves the job alone when the confirmation is dismissed", async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/layout/__tests__/Layout.test.tsx:41— "Mock the auth context." repeats the code it sits on: 3 of its 3 words (mock, auth, context) are already in `vi.mock("../../../contexts/AuthContext", () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/layout/__tests__/Layout.test.tsx:56— "Mock useDocumentTitle hook." repeats the code it sits on: 5 of its 5 words (mock, use, document, title, hook) are already in `vi.mock("../../../hooks/useDocumentTitle", () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/resources/__tests__/ResourceCard.test.tsx:51— "Mock window.open." repeats the code it sits on: 3 of its 3 words (mock, window, open) are already in `vi.spyOn(window, "open").mockImplementation(mockWindowOpen);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/sqlOnFhir/__tests__/ParameterValueInput.test.tsx:153— "A valid value carries no message." repeats the code it sits on: 4 of its 5 words (valid, value, no, message) are already in `it("shows no message for a valid value", () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment ui/src/components/sqlOnFhir/__tests__/SqlQueryInlineTab.test.tsx:140— "The per-row source selector groups ViewDefinitions and SQLViews." repeats the code it sits on: 7 of its 8 words (source, selector, groups, view, definitions, sql, views) are already in `it("groups ViewDefinitions and SQLViews in the source selector", async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate server/src/main/java/au/csiro/pathling/async/JobProvider.java:370— `cause != null && cause.getCause() != null` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/async/JobProvider.java, server/src/main/java/au/csiro/pathling/async/JobResultProvider.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 server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java:137— `currentUserId.isPresent() && !ownJob.getOwnerId().equals(currentUserId)` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpProvider.java, server/src/main/java/au/csiro/pathling/operations/sql/SqlExportSupport.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 server/src/main/java/au/csiro/pathling/operations/sql/SqlFilterResolver.java:192— `e.getMessage() != null && e.getMessage().contains("No data found for resource type")` appears character-identically in 4 files — server/src/main/java/au/csiro/pathling/operations/sql/SqlFilterResolver.java, server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java, server/src/main/java/au/csiro/pathling/operations/sqlquery/LibraryReferenceResolver.java, server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.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 server/src/main/java/au/csiro/pathling/operations/sql/SqlExportFormat.java:94— `f.code.equals(base) || f.contentType.equals(base)` appears character-identically in 4 files — server/src/main/java/au/csiro/pathling/operations/sql/SqlExportFormat.java, server/src/main/java/au/csiro/pathling/operations/sql/SqlRunFormat.java, server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryOutputFormat.java, server/src/main/java/au/csiro/pathling/operations/view/ViewOutputFormat.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 server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java:210— `formatString == null || formatString.isBlank()` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.java, server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportPnpOperationValidator.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 fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java:80— `hoursGroup != null && (Integer.parseInt(hoursGroup) > 23)` appears character-identically in 2 files — fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java, fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathTime.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 server/src/main/java/au/csiro/pathling/async/JobProvider.java:165— `id == null || !ID_PATTERN.matcher(id).matches()` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/async/JobProvider.java, server/src/main/java/au/csiro/pathling/async/JobResultProvider.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 terminology/src/main/java/au/csiro/pathling/terminology/lookup/LookupExecutor.java:75— `isNull(coding.getSystem()) || isNull(coding.getCode())` appears character-identically in 2 files — terminology/src/main/java/au/csiro/pathling/terminology/lookup/LookupExecutor.java, terminology/src/main/java/au/csiro/pathling/terminology/translate/TranslateExecutor.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 server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryRequestParser.java:123— `limit != null && limit.getValue() != null` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlQueryRequestParser.java, server/src/main/java/au/csiro/pathling/operations/view/ViewExecutionHelper.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 server/src/main/java/au/csiro/pathling/interceptors/ImportManifestInterceptor.java:220— `manifest.saveMode() != null && !manifest.saveMode().isBlank()` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/interceptors/ImportManifestInterceptor.java, server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportOperationValidator.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 server/src/main/java/au/csiro/pathling/operations/sql/SqlExportRequestParser.java:401— `name.equals(part.getName()) && part.getResource() != null` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/operations/sql/SqlExportRequestParser.java, server/src/main/java/au/csiro/pathling/operations/sql/SqlRunProvider.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 server/src/main/java/au/csiro/pathling/io/DerivedSource.java:157— `resourceCode != null && driftedTypes.contains(resourceCode)` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/io/DerivedSource.java, server/src/main/java/au/csiro/pathling/io/DriftGuardedSource.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 library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java:133— `saveMode == SaveMode.IGNORE && !replaced.isEmpty()` appears character-identically in 2 files — library-api/src/main/java/au/csiro/pathling/library/io/sink/NdjsonSink.java, library-api/src/main/java/au/csiro/pathling/library/io/sink/ParquetSink.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 fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java:212— `sourceType == targetType && sourceType != FhirPathType.QUANTITY` appears character-identically in 2 files — fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ConversionLogic.java, fhirpath/src/main/java/au/csiro/pathling/fhirpath/function/provider/ValidationLogic.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 server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitProvider.java:328— `submission.state() == SubmissionState.COMPLETED || submission.state() == SubmissionState.COMPLETED_WITH_ERRORS || submission.state() == Subm…` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitProvider.java, server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitStatusProvider.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 server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java:346— `view.getStatusElement() != null && ACTIVE_STATUS.equals(view.getStatusElement().getValueAsString())` appears character-identically in 2 files — server/src/main/java/au/csiro/pathling/operations/sql/SubjectResolver.java, server/src/main/java/au/csiro/pathling/operations/sqlquery/ViewResolver.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 REDACTED:91— `capability.implementation?.description || capability.name` appears character-identically in 2 files — REDACTED, REDACTED. 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 REDACTED:108— `coding.system === SMART_SERVICE_SYSTEM && coding.code === SMART_SERVICE_CODE` appears character-identically in 2 files — REDACTED, REDACTED. 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 REDACTED:119— `ext.url?.includes("oauth-uris") || ext.url?.includes("smart-configuration")` appears character-identically in 2 files — REDACTED, REDACTED. 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 ui/src/hooks/useSqlQueryLibraries.ts:72— `options?.enabled !== false && !!fhirBaseUrl` appears character-identically in 3 files — ui/src/hooks/useSqlQueryLibraries.ts, ui/src/hooks/useSqlViews.ts, ui/src/hooks/useViewDefinitions.ts. 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 ui/src/components/export/ExportCard.tsx:102— `status === "complete" || status === "cancelled" || status === "error"` appears character-identically in 2 files — ui/src/components/export/ExportCard.tsx, ui/src/components/import/ImportCard.tsx. 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 ui/src/components/export/ExportCard.tsx:98— `status === "pending" || status === "in-progress"` appears character-identically in 2 files — ui/src/components/export/ExportCard.tsx, ui/src/components/import/ImportCard.tsx. 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.
Orphaned file server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportResultRegistry.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file server/src/main/java/au/csiro/pathling/errors/DiagnosticContext.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file server/src/main/java/au/csiro/pathling/security/PathlingAuthority.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file server/src/main/java/au/csiro/pathling/security/OidcConfiguration.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file server/src/main/java/au/csiro/pathling/errors/ErrorReportingInterceptor.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file server/src/main/java/au/csiro/pathling/security/PathlingJwtDecoderFactory.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×5
Projects may be oversized for their cohesion REDACTED:1— `server` (30377 LoC, 208 module-visible types across 25 directories) overshoots its size bounds. 5 of 10 build unit(s) (Maven, Python, npm) overshoot their size bounds, lowering Project Cohesion to 0.7/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 REDACTED:1— `fhirpath` (28976 LoC, 259 module-visible types across 31 directories) overshoots its size bounds. 5 of 10 build unit(s) (Maven, Python, npm) overshoot their size bounds, lowering Project Cohesion to 0.7/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 REDACTED:1— `terminology` (22217 LoC, 167 module-visible types across 21 directories) overshoots its size bounds. 5 of 10 build unit(s) (Maven, Python, npm) overshoot their size bounds, lowering Project Cohesion to 0.7/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 REDACTED:1— `ui` (14947 LoC, 290 module-visible types across 18 directories) overshoots its size bounds. 5 of 10 build unit(s) (Maven, Python, npm) overshoot their size bounds, lowering Project Cohesion to 0.7/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 REDACTED:1— `encoders` (7131 LoC, 86 module-visible types across 12 directories) overshoots its size bounds. 5 of 10 build unit(s) (Maven, Python, npm) overshoot their size bounds, lowering Project Cohesion to 0.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 229 significant file(s) lose their only recent owner: terminology/src/main/java/au/csiro/pathling/terminology/store/SnomedRf2Importer.java, terminology/src/main/java/au/csiro/pathling/terminology/local/LocalTerminologyService.java, server/src/main/java/au/csiro/pathling/operations/bulksubmit/BulkSubmitExecutor.java, terminology/src/main/java/au/csiro/pathling/terminology/store/FhirTerminologyImporter.java, lib/python/pathling/cli/terminology.py, server/src/main/java/au/csiro/pathling/fhir/ConformanceProvider.java, lib/python/pathling/cli/config.py, server/src/main/java/au/csiro/pathling/operations/sqlquery/SqlDependencyResolver.java (+221 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 21 significant file(s) lose their only recent owner: fhirpath/src/main/java/au/csiro/pathling/views/ansi/AnsiSqlDataTypeFactory.java, fhirpath/src/main/java/au/csiro/pathling/search/filter/TokenMatcher.java, fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/DatasetEvaluatorBuilder.java, fhirpath/src/main/java/au/csiro/pathling/fhirpath/FhirPathDateTime.java, fhirpath/src/main/java/au/csiro/pathling/search/FhirSearch.java, fhirpath/src/main/java/au/csiro/pathling/fhirpath/evaluation/SingleResourceEvaluatorBuilder.java, fhirpath/src/main/java/au/csiro/pathling/fhirpath/collection/ResolvedReferenceCollection.java, fhirpath/src/main/java/au/csiro/pathling/search/filter/DateMatcher.java (+13 more). Pair on, review, or document these before any departure.
No ADRs found REDACTED:991— 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 `REDACTED` makes this repository a deployable product (line 991).
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 6 of 556 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; 556 of the 838 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: server/src/main/java/au/csiro/pathling/operations/bulkimport/ImportResultRegistry.java, server/src/main/java/au/csiro/pathling/errors/DiagnosticContext.java, server/src/main/java/au/csiro/pathling/security/PathlingAuthority.java, server/src/main/java/au/csiro/pathling/security/OidcConfiguration.java, server/src/main/java/au/csiro/pathling/errors/ErrorReportingInterceptor.java, server/src/main/java/au/csiro/pathling/security/PathlingJwtDecoderFactory.java. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
Disabled test fhirpath/src/test/java/au/csiro/pathling/views/FhirViewExperimentalComplianceTest.java:25— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· Architecture diagram out of date · ×1
Architecture diagram out of date CONTRIBUTING.md:49— `CONTRIBUTING.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `fhirpath-lab-api`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Logging is not universal — Only 7/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `lib/python`.
No dependency-update automation site/package.json:16— `site/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.)
Benchmarks don't track allocations benchmark/src/main/java/au/csiro/pathling/benchmark/PathlingBenchmark.java— A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
R7 · Dead Code· Unused export 'AsyncJobExecutorFn' · ×1
Unused export 'AsyncJobExecutorFn' ui/src/api/asyncJob.ts:52— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SystemExportKickOffFn' · ×1
Unused export 'SystemExportKickOffFn' ui/src/api/bulkExport.ts:72— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'AllPatientsExportKickOffFn' · ×1
Unused export 'AllPatientsExportKickOffFn' ui/src/api/bulkExport.ts:75— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'PatientExportKickOffFn' · ×1
Unused export 'PatientExportKickOffFn' ui/src/api/bulkExport.ts:78— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'GroupExportKickOffFn' · ×1
Unused export 'GroupExportKickOffFn' ui/src/api/bulkExport.ts:81— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'BulkExportStatusFn' · ×1
Unused export 'BulkExportStatusFn' ui/src/api/bulkExport.ts:84— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'BulkExportDownloadFn' · ×1
Unused export 'BulkExportDownloadFn' ui/src/api/bulkExport.ts:87— Nothing imports this binding — it is safe to review for removal.
Unused export 'streamToText' ui/src/utils/ndjson.ts:24— Nothing ultimately consumes this binding: its only referrer is the re-export in ui/src/utils/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ui/src/utils/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'extractColumns' · ×1
Unused export 'extractColumns' ui/src/utils/ndjson.ts:60— Nothing ultimately consumes this binding: its only referrer is the re-export in ui/src/utils/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ui/src/utils/index.ts in the same commit, or the barrel will import a name that no longer exists.
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/24 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.
Null assertions (`!`) override strict null checking — ~3.0 `!` null assertions per 1k TypeScript source lines — 49 assertion(s) across the 16513 source line(s) of the 116 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: ui/src/api/import.ts (9), ui/src/hooks/useBulkExport.ts (8), ui/src/hooks/useBulkSubmit.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Hand-rolled JSON/XML parsing via regex lib/python/pathling/cli/io.py:48— 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 Python code already uses a real parser in the same package; use it here too.
X7 · Silent fallback defaults· Pending state with no failure state · ×1
Pending state with no failure state ui/src/components/auth/CapabilityGuard.tsx:65— The view draws `Checking server capabilities...` under `isLoadingCapabilities`, but `isLoadingCapabilities` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Silent fallback default on parse failure server/src/main/java/au/csiro/pathling/operations/sql/SqlRunFormat.java:206— `quality` returns `1.0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Skipped (documented): test fhirpath/src/test/java/au/csiro/pathling/views/FhirViewTest.java:499— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): ndjsonSourceFilterByResourceType library-api/src/test/java/au/csiro/pathling/library/io/DataSourcesTest.java:1083— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): parquetFilterByResourceType library-api/src/test/java/au/csiro/pathling/library/io/DataSourcesTest.java:1131— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): test_files_are_renamed_following_pathling_pattern library-api/src/test/java/au/csiro/pathling/library/io/FileSystemPersistenceTest.java:58— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
doc comments repeat the names ui/src/api/jobs.ts:50— 0 of 540 documented parameters and 11 of 824 summaries in `ui` only repeat the member or parameter name (e.g. "Options for ." for `ListJobsOptions`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a1e7ed-f08e-72d9-8448-87cb9198ffc7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 214 · Warnings: 622 · Recommendations: 153 · Info: 268 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 05:14 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.