Public report of onc-healthit/lantern-back-end, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 23:14 UTC · Survey ID cd_5cc1d2803a1d4a7ba4a75d9356c3a6f0
onc-healthit/lantern-back-end
Measured 16 November 2026, 23:13 UTC, at code version 34237cb
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
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 medium codebase: 20,956 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 42.4
Findings by how serious they are
54 critical578 serious99 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 23:13 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
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 ▸
53of 53 dimensions measured by tools.
694of 731 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
53dimensions across 6 lenses, read from 20,956 lines of product code in 6 projects.
onc-healthit/lantern-back-end is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 54.1 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 42.4, is the weakest lens and counts most in the score. The best first step for the work it takes is pinning the dependencies to tagged releases, worth about 6.2 points. Planning backups and recovery would lift Production Readiness itself, worth about 7.2 points. Raising Production Readiness to 70 would lift the score to about 63.7.
Twenty-six known security holes in the packages the code depends on can be used by attackers. Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and seven settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Fixing the weaknesses the scanner points to would fix the four security weaknesses in the code, and the two passwords or keys in the code's history need replacing, with the old ones switched off. The three pages or frames without a title need a descriptive title.
The product code is 20,956 lines, about €35,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 42.4 to 70, the lowest score rated Strong, the score would rise from 54.1 to about 63.7.
Code composition: what the lines of code are
Product code 59%Tests 41%
Rebuild cost: about €35,000 · Estimate
Cost to rebuild
€12,000 to €59,000, for 195 to 619 hours of work, about 0.2 person-years for one engineer
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 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 20,956 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 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Resolve the 180 Low coverage finding(s) in Code Coverage — start with REDACTED (25), messagequeue.go (2), REDACTED.
Raises the score by about 9.7 points · High effort · Code Coverage
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.
Files that change often carry extra risk · Combined risk
One file is changed often and is hard to read, which makes it the likeliest place for a mistake. It also has under half its code tested, or was written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to this file therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (1 file) · Code Coverage (155 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: REDACTED
What to do: Add tests to these files and have a second person review every change to them, starting with REDACTED.
Where the investment is most exposed · Value at risk
This code would cost about €35,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 42.4 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 3.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 11% to 25% on every change. The history of the code shows how much it changes: about 6,588 lines over the last 90 days, which is about 26,718 lines a year. At that pace, the extra work comes to an estimated 7.4 to 44.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
If you do one thing first · First action
Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 6.2 points for low effort, because it clears the 3 Dependency Hygiene 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: 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.
59 modules, with 44 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 19 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.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/versionsoperatorparser.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/versionsoperatorparser, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/versionsoperatorparser can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/versionsoperatorparser.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager uses a module listed above it, which is the healthy direction.
com/onc-healthit/lantern-back-end/lanternmq/mock uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/lanternmq/mock, while a change to com/onc-healthit/lantern-back-end/lanternmq/mock can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/lanternmq/mock uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/lanternmq/pkg/accessqueue uses a type in com/onc-healthit/lantern-back-end/lanternmq.
com/onc-healthit/lantern-back-end/lanternmq/pkg/accessqueue uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/lanternmq/pkg/accessqueue, while a change to com/onc-healthit/lantern-back-end/lanternmq/pkg/accessqueue can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/lanternmq/pkg/accessqueue uses a module listed above it, which is the healthy direction.
com/onc-healthit/lantern-back-end/lanternmq/rabbitmq uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/lanternmq/rabbitmq, while a change to com/onc-healthit/lantern-back-end/lanternmq/rabbitmq can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/lanternmq/rabbitmq uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/smartparser.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler/validation uses a module listed above it, which is the healthy direction.
12 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers can break com/onc-healthit/lantern-back-end/capabilityquerier/cmd, while a change to com/onc-healthit/lantern-back-end/capabilityquerier/cmd can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses a module listed above it, which is the healthy direction.
com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/capabilityquerier/cmd, while a change to com/onc-healthit/lantern-back-end/capabilityquerier/cmd can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityquerier/cmd, while a change to com/onc-healthit/lantern-back-end/capabilityquerier/cmd can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityquerier/cmd uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier uses a type in com/onc-healthit/lantern-back-end/lanternmq.
com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier, while a change to com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier, while a change to com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityquerier/pkg/capabilityquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/cmd uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityreceiver/cmd uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityreceiver/cmd, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/cmd can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/cmd uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers can break com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migrateresources uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers can break com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/cmd/migratevalidations uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/cmd/chplsharedlistsources uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/cmd/chplsharedlistsources uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/cmd/chplsharedlistsources, while a change to com/onc-healthit/lantern-back-end/endpointmanager/cmd/chplsharedlistsources can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/cmd/chplsharedlistsources uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/workers.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/archivefile uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/chplquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/datacleanup uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/datacleanup uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/datacleanup, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/datacleanup can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/datacleanup uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointlinker uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/fetcher.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/fetcher, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/fetcher can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/fetcher.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/fhirendpointquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/historycleanup uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/historycleanup uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/historycleanup, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/historycleanup can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/historycleanup uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/historypruning uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/historypruning uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/historypruning, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/historypruning can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/historypruning uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/nppesquerier uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints uses a type in com/onc-healthit/lantern-back-end/lanternmq.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints, while a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/endpointmanager/pkg/sendendpoints uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/capabilityparser.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a type in com/onc-healthit/lantern-back-end/lanternmq.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses com/onc-healthit/lantern-back-end/lanternmq, so a change to com/onc-healthit/lantern-back-end/lanternmq can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler can't break com/onc-healthit/lantern-back-end/lanternmq.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a type in com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql, so a change to com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler can't break com/onc-healthit/lantern-back-end/endpointmanager/pkg/endpointmanager/postgresql.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a type in com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper.
com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper, so a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper can break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler, while a change to com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler can't break com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/chplmapper.
Position
Below the diagonal: com/onc-healthit/lantern-back-end/capabilityreceiver/pkg/capabilityhandler uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 61.0 · Adequate · gated by D1, D2, D4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
59
High / Critical
A03:2025 — Software Supply Chain Failures
47
High / Critical
A02:2025 — Security Misconfiguration
28
High / Critical
A07:2025 — Authentication Failures
7
High / Critical
Roadmap
Top priorities: Resolve the 180 Low coverage finding(s) in Code Coverage — start with REDACTED (25), messagequeue.go (2), REDACTED; Resolve the 1 finding(s) in DR & Backup; Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
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.
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 — 54
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 — 578
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 — 99
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 53 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 — 53 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, 694 of 731 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.
D4 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 97 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .R (9,913 lines, 32% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's REDACTED declares a Go language version older than 1.17 (or none), and before 1.17 a REDACTED lists only the modules version selection needs, not every module the build compiles. The licences are resolved per module version, so grading the modules that file happens to list would be a verdict over part of the dependency graph. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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.
D26 Project Cohesion — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .R source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 952 sampled here came from .go files. This repository's .R source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
AX6 Interface segregation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docker-compose.override.yml). compose up failed (exit 15 — the compose project is invalid) — time="2026-11-16T23:13:37Z" level=warning msg="The \"LANTERN_TEST_QUSER\" variable is not set. Defaulting to a blank string." time="2026-11-16T23:13:37Z" level=warning msg="The \"LANTERN_TEST_QPASSWORD\" variable is not set. Defaulting to a blank string." service "plumber" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Go, Python, r is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Go, Python, r is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
X16 Unfloored truncation loop — 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.
X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X28 Index access outside its own emptiness guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X29 Per-element action decided by a fixed element — 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.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Python, R is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 6 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
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.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
+ 23 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with chplendpointquerier.QueryCHPLEndpointList (cyclomatic 153). — Refactoring it lifts Cyclomatic Complexity from 3.5 to about 5.3/10.
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.
+ 55 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 26 bodies over 30 down to 30 or less in Cognitive Complexity — start with chplendpointquerier.QueryCHPLEndpointList (cognitive 153), chplendpointquerier.extractOrganizationFields (cognitive 122), chplendpointquerier.BundleToLanternFormat (cognitive 115). — 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 26 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.0 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 6 FunctionTooLong finding(s) in God Classes — start with capabilityreceiver.go (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 FileTooLong finding(s) in God Classes — start with fhirendpointstore.go, fhirendpointinfostore.go, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 TooManyFields finding(s) in God Classes — start with populatenpiorgs.go. — One of this dimension's main actionable groups (1 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.
97 duplicated block group(s) detected. 28.7 % of the production lines (6,024 of 20,956) are in a reported copy. A further 69 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .R (32% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
Duplicated block (13 lines × 2) · ×4REDACTED:56
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3endpointmanager/cmd/endpointpopulator/main.go:23
Edited copy of a member (20 corresponding lines) · ×3REDACTED:148
Edited copy of a member (19 corresponding lines) · ×3REDACTED:57
+ 117 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), medhostquerier.go, betterdayhealthwebscraper.go. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with REDACTED, REDACTED, mdlogicehrwebscraper.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with REDACTED, vendorstore.go, base.go. — One of this dimension's main actionable groups (3 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.
6 production modules (Go), 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.
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.
Low cohesion: Store (LCOM4 46)endpointmanager/pkg/endpointmanager/postgresql/store.go:17
What to do
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with store.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage4.3 / 10Weak✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 17.6% — 180 file(s) below 50%. Measured from the Go suite (github.com/onc-healthit/lantern-back-end/capabilityquerier: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made; github.com/onc-healthit/lantern-back-end/capabilityreceiver: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made; github.com/onc-healthit/lantern-back-end/e2e: no cover profile; github.com/onc-healthit/lantern-back-end/endpointmanager: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made; github.com/onc-healthit/lantern-back-end/lanternmq: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
Resolve the 180 Low coverage finding(s) in Code Coverage — start with REDACTED (25), messagequeue.go (2), REDACTED. — One of this dimension's main actionable groups (180 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
20 outdated, 3 author-deprecated direct Go module(s), 3 pinning or checksum defect(s). 33 of 33 direct requirement(s) were graded against proxy.golang.org (0 not served there, 6 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and REDACTED there.
Deprecated module: github.com/streadway/amqp · ×3
Dependency pinned to a stale untagged commit: github.com/streadway/amqp · ×3
Outdated: github.com/PuerkitoBio/goquery · ×20
What to do
Resolve the 3 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
REDACTED scan ran and found no leaked secrets. 2 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material. 3 password hash(es) are listed to check and are not counted as leaked credentials.
REDACTED
✓ On the Gold path — maintain.
Detailed fixes: d13_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.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 62 of the 215 production source files in this repository: 146 are under the ~2,400-byte size floor this dimension measures over, and the remaining 7 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 20956 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.
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. 8 document(s) read across 1 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 refresh.go. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 265 declarations measured against a convention their peers follow.
`ServiceBaseUrlList` spells `Url` where 263 names in the project spell it `URL`endpointmanager/cmd/CHPLpopulator/main.go:62
`LogoUrl` spells `Url` where 263 names in the project spell it `URL`endpointmanager/pkg/chplendpointquerier/anthemparser.go:16
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency9.8 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
1 API inconsistencies among 558 exposed members measured against a convention their peers follow.
`capabilityhandler.RunSupportedResourcesChecks` returns a map (`map[K]V`) where its 4 siblings return a slice (`[]T`)REDACTED:8
What to do
Resolve the 1 `capabilityhandler.RunSupportedResourcesChecks` returns a map… finding(s) in Internal API Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_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.
1 of 6 build units (Go) flagged as possibly oversized/incoherent. This repository's .R source was read by no build unit, so this covers part of the tree, not all of it.
Projects may be oversized for their cohesionREDACTED:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 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.
28 % of calls cross a namespace and 1 % go through an interface, but 54 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .go source only — this repository's .R was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
3 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
59 finding(s): 0 critical, 16 high, 42 medium, 1 low. 7 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 6 file(s) — `resources/dev_resources/LanternEndpointSources.json`, `resources/dev_resources/linkerMatchesAllowlist.json`, `resources/dev_resources/linkerMatchesBlocklist.json`, `resources/prod_resources/LanternEndpointSources.json`, `resources/prod_resources/linkerMatchesAllowlist.json`, … (+1 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 23 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (8). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED (6). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 13 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 8 Low IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 recommendation-level).
Detailed fixes: d31_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.
44 of 69 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is endpointmanager/pkg/nppesquerier/populatenpiorgs.go. Counted over 69 of the 215 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned fileendpointmanager/pkg/nppesquerier/populatenpiorgs.go:1
What to do
Resolve the 43 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (7), messagequeue.go (2), base.go (2). — One of this dimension's main actionable groups (43 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with populatenpiorgs.go. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with fhirendpointstore.go, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with fhirendpoint.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 7 platform declaration(s) and 0 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.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC3 · Page structure4.0 / 10Weak✓ Tool-verified
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.
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×3) — shinydashboard/lantern/about-lantern.html:2, shinydashboard/lantern/aboutInfo.html:2, shinydashboard/lantern/disclaimer.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — shinydashboard/lantern/about-lantern.html:2, shinydashboard/lantern/aboutInfo.html:2, shinydashboard/lantern/disclaimer.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 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
`CapabilityStatement` declares 17 methods: `GetPublisher`, `GetFHIRVersion`, `GetSoftware`, `GetSoftwareName`, `GetSoftwareVersion`, `GetCopyright`, `GetRest`, `GetResourceList`, `GetKind`, `GetImplementation`, `GetMessaging`, `GetMessagingEndpoint`, `GetDocument`, `GetDescription`, `Equal`, `EqualIgnore`, `GetJSON`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — endpointmanager/pkg/capabilityparser/factory.go:20
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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.
`REDACTED` 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`. — REDACTED:5
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.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
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 database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. 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.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `shiny-server.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — shinydashboard/shiny-server.conf:8
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context (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 4/11 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`QueryEndpointList` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. (×2) — refresh.go:46, REDACTED:148
`NewTestClientNoTLS` calls `net.Dial(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:30
`testingHTTPClient` calls `net.Dial(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:103
`QueryEndpointListWithTLSOption` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:170
`downloadFile` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:240
`EmdsCloudWebscraper` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — endpointmanager/pkg/chplendpointquerier/emdscloudwebscraper.go:11
What to do
Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
Do you agree with this assessment?
X27 · Collection changed while being enumerated7.5 / 10Strong✓ Tool-verified
Other · Code Health — 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 … range` leaves the slice or map it is walking alone — Go raises nothing, but the walk and the collection part: a range evaluates its slice once, so an element appended in the body is never visited and a removal by reslicing (`s = append(s[:i], s[i+1:]...)`, `slices.Delete`) shifts the next element under the index, which is then skipped while the last is read twice; a reslice, a reassignment or a sort leaves every later `s[i]` naming another element; and a map's order is unspecified, so deleting another key (or clearing the map) changes from run to run which entries the loop still sees.
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.
`e.OrganizationList` is walked by the `for … range` at line 489, and line 498 appends to `e.OrganizationList`. A range evaluates its slice once and walks the length it had when the loop began, so the elements appended here are never visited by this loop — work queued for it is silently dropped. — endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:489
What to do
Each finding names the two lines that cannot both stand — the `for` over the collection (or its `keys()`/`values()`/`items()` view), and the call inside the body that changes its size. Confirm from those two, then pick one: walk a snapshot (`for k in list(d):`, `for x in s.copy():`); build the result instead of editing in place (`d = {k: v for k, v in d.items() if keep(v)}`); collect what needs removing and remove it after the loop; or — where only the first match was ever meant — `break` straight after the change, which is the one shape that is already safe. In Go: Each finding names the two lines that cannot both stand — the `for … range` over the collection, and the change to it in the body. Confirm from those two, then pick one: build the result instead of editing the walked collection (`var kept []T` … `kept = append(kept, v)`, or `kept := s[:0]` and assign `s = kept` after the loop; `slices.DeleteFunc(s, drop)` in one call); for a worklist that must visit what it adds, loop `for len(queue) > 0` or by index (`for i := 0; i < len(s); i++`); walk a copy (`range slices.Clone(s)`, `range slices.Collect(maps.Keys(m))`) and change the original; delete only the CURRENT key (`delete(m, k)`), which the specification allows; or — where only the first match was ever meant — `break` straight after the change.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard4.6 / 10Weak✓ Tool-verified
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.
`index` is the result of a search that answers -1 when nothing is found, and `urlString[index:]` uses it as a bound with no test of `index` in between. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Test `index < 0` (or use `strings.Cut`) before using it. — endpointmanager/cmd/CHPLupdatecheck/main.go:145
`index` is the result of a search that answers -1 when nothing is found, and `fileName[:index]` uses it as a bound with no test of `index` in between. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Test `index < 0` (or use `strings.Cut`) before using it. — endpointmanager/cmd/CHPLupdatecheck/main.go:163
What to do
Each finding names the index access that escapes the guard and the line of the correctly bracketed access beside it. Compare the two: they differ only in where one parenthesis sits. Move it so the emptiness test brackets every access to that symbol — and if the value provably cannot be empty at this point, delete the test rather than leave a condition that guards one access and not its neighbour.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — shinydashboard/lantern/www/js/lcp-optimizer.js:51
`if err != nil` 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. (×14) — REDACTED:19, REDACTED:23, endpointmanager/pkg/smartparser/smartresponse.go:70, …
`byteValue, _ := io.ReadAll(jsonFile)` writes the call's error to `_` and then uses `byteValue` as if the call succeeded. When `io.ReadAll` fails, `byteValue` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `byteValue` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — endpointmanager/pkg/fetcher/fetcher.go:57
`endpointName, _ := NormalizeOrgName(org.OrganizationName)` writes the call's error to `_` and then uses `endpointName` as if the call succeeded. When `NormalizeOrgName` fails, `endpointName` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `endpointName` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — endpointmanager/pkg/endpointlinker/endpointlinker.go:219
`if _, err := os.Stat(csvFilePath); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here. (×2) — endpointmanager/pkg/chplendpointquerier/csvparser.go:92, endpointmanager/pkg/chplendpointquerier/customcsvparser.go:95
`if err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here. — capabilityreceiver/pkg/chplmapper/capabilityinfo.go:99
`fhirVersion, _ = capStat.GetFHIRVersion()` writes the call's error to `_` and then uses `fhirVersion` as if the call succeeded. When `capStat.GetFHIRVersion` fails, `fhirVersion` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `fhirVersion` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:168
`if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`. (×6) — REDACTED:270, REDACTED:281, REDACTED:299, …
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`Warn` at line 44 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Warn("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Warn("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Warn("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — endpointmanager/cmd/datavalidation/main.go:44
`Info` at line 108 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — endpointmanager/cmd/CHPLupdatecheck/main.go:108
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 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.
D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
Not included — 59 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
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 — compose up failed (exit 15 — the compose project is invalid) — time="2026-11-16T23:13:37Z" level=warning msg="The \"LANTERN_TEST_QUSER\" variable is not set. Defaulting to a blank string." time="2026-11-16T23:13:37Z" level=warning msg="The \"LANTERN_TEST_QPASSWORD\" variable is not set. Defaulting to a blank string." service "plumber" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~14834 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D14 License Compliance — Go module licences not graded — a REDACTED predates Go 1.17 and does not list its whole module graph
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.
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
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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
DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
P9 Domain vs controller coverage — coverage data present for 209 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 2% of this repository's production lines — go (20,930 lines), r (9,913 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — go (20,930 lines), r (9,913 lines), python (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X18 Disposal-pattern correctness — 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 — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — 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
X29 Per-element action decided by a fixed element — X29 reached only 1% of this repository's production lines — go (20,930 lines), r (9,913 lines), python (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC3 · Page structure· Document without a <title> · ×3
Document without a <title> shinydashboard/lantern/about-lantern.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> shinydashboard/lantern/aboutInfo.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> shinydashboard/lantern/disclaimer.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Swallowed exception (caught, then discarded) REDACTED:19— `if err != nil` 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) REDACTED:23— `if err != nil` 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) endpointmanager/pkg/smartparser/smartresponse.go:70— `if err != nil` 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) endpointmanager/pkg/smartparser/smartresponse.go:74— `if err != nil` 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) endpointmanager/pkg/smartparser/smartresponse.go:100— `if err != nil` 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) endpointmanager/pkg/smartparser/smartresponse.go:104— `if err != nil` 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) REDACTED:75— `if err != nil` 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) endpointmanager/pkg/capabilityparser/base.go:272— `if err != nil` 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) endpointmanager/pkg/capabilityparser/base.go:276— `if err != nil` 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) endpointmanager/pkg/capabilityparser/base.go:282— `if err != nil` 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) endpointmanager/pkg/capabilityparser/base.go:286— `if err != nil` 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) endpointmanager/pkg/capabilityparser/base.go:303— `if err != nil` 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) endpointmanager/pkg/capabilityparser/base.go:307— `if err != nil` 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) endpointmanager/cmd/CHPLpopulator/main.go:114— `if err != nil` 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×13
X3 · Exception handling· Lost error (reports an error that is nil on this path) · ×9
Lost error (reports an error that is nil on this path) endpointmanager/pkg/chplendpointquerier/csvparser.go:92— `if _, err := os.Stat(csvFilePath); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here.
Lost error (reports an error that is nil on this path) endpointmanager/pkg/chplendpointquerier/customcsvparser.go:95— `if _, err := os.Stat(csvFilePath); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here.
Lost error (reports an error that is nil on this path) capabilityreceiver/pkg/chplmapper/capabilityinfo.go:99— `if err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here.
Lost error (reports an error that is nil on this path) REDACTED:270— `if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`.
Lost error (reports an error that is nil on this path) REDACTED:281— `if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`.
Lost error (reports an error that is nil on this path) REDACTED:299— `if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`.
Lost error (reports an error that is nil on this path) REDACTED:307— `if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`.
Lost error (reports an error that is nil on this path) REDACTED:315— `if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`.
Lost error (reports an error that is nil on this path) REDACTED:323— `if httpErr != nil && httpResponseCode != 0` handles a failure of `httpErr` but reports `err`, which the earlier `if err != nil { return … }` already proved nil here: the real failure is lost and a nil error is reported (or returned as success) in its place. Report `httpErr`.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×8
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
X2 · Cancellation propagation· Function without context.Context · ×7
Function without context.Context: QueryEndpointList refresh.go:46— `QueryEndpointList` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: NewTestClientNoTLS REDACTED:30— `NewTestClientNoTLS` calls `net.Dial(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: testingHTTPClient REDACTED:103— `testingHTTPClient` calls `net.Dial(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: QueryEndpointList REDACTED:148— `QueryEndpointList` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: QueryEndpointListWithTLSOption REDACTED:170— `QueryEndpointListWithTLSOption` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: downloadFile REDACTED:240— `downloadFile` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: EmdsCloudWebscraper endpointmanager/pkg/chplendpointquerier/emdscloudwebscraper.go:11— `EmdsCloudWebscraper` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
FunctionTooLong: chplendpointquerier.QueryCHPLEndpointList REDACTED:227— FunctionTooLong — QueryCHPLEndpointList runs 311 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 211 over it, 3.11× 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: chplendpointquerier.BundleToLanternFormat REDACTED:205— FunctionTooLong — BundleToLanternFormat 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: archivefile.CreateArchive REDACTED:105— FunctionTooLong — CreateArchive 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: capabilityhandler.updateOrInsertEndpointRows capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:479— FunctionTooLong — updateOrInsertEndpointRows runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: main.main endpointmanager/cmd/CHPLpopulator/main.go:82— FunctionTooLong — main runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: capabilityhandler.formatMessage capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:46— FunctionTooLong — formatMessage 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.
FileTooLong: postgresql/fhirendpointstore.go endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go— FileTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: Store (25 blocks, 35-841). The bar is 500 significant lines; this is 50 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: postgresql/fhirendpointinfostore.go endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: Store (10 blocks, 51-786). 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.
FileTooLong: REDACTED REDACTED— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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: capabilityhandler/capabilityreceiver.go capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go— FileTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 11 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (13 lines × 2) REDACTED:56— REDACTED:56-68 | capabilityreceiver/cmd/migratevalidations/main.go:106-118 — `REDACTED` and `capabilityreceiver/cmd/migratevalidations/main.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 109 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:56` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) endpointmanager/cmd/archivefile/main.go:18— endpointmanager/cmd/archivefile/main.go:18-30 | endpointmanager/cmd/endpointwebscraper/main.go:14-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) endpointmanager/pkg/chplendpointquerier/medhostquerier.go:16— endpointmanager/pkg/chplendpointquerier/medhostquerier.go:16-28 | endpointmanager/pkg/endpointwebscraper/1upparser.go:29-41 — 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 `endpointmanager/pkg/chplendpointquerier/medhostquerier.go:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `endpointmanager/pkg/endpointwebscraper/1upparser.go:25` calls `TrimSpace` and `endpointmanager/pkg/chplendpointquerier/medhostquerier.go:14` 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 (13 lines × 2) endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:13— endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:13-25 | endpointmanager/pkg/chplendpointquerier/hmsfirstwebscraper.go:13-25 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/hmsfirstwebscraper.go` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:13` 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, `endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:26` calls `Contains`, `TrimSpace`, `Eq` and `endpointmanager/pkg/chplendpointquerier/hmsfirstwebscraper.go:26` 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.
AC3 · Page structure· Page without a main landmark · ×3
Page without a main landmark shinydashboard/lantern/about-lantern.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 shinydashboard/lantern/aboutInfo.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 shinydashboard/lantern/disclaimer.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Deprecated module: github.com/streadway/amqp — `github.com/streadway/amqp` is required at v0.0.0-20200108173154-1c71cc93ed71 in REDACTED, and its author has DEPRECATED the module: "Consider using the github.com/rabbitmq/amqp091-go package instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
Deprecated module: github.com/streadway/amqp — `github.com/streadway/amqp` is required at v0.0.0-20200108173154-1c71cc93ed71 in REDACTED, and its author has DEPRECATED the module: "Consider using the github.com/rabbitmq/amqp091-go package instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
Deprecated module: github.com/streadway/amqp — `github.com/streadway/amqp` is required at v0.0.0-20200108173154-1c71cc93ed71 in REDACTED, and its author has DEPRECATED the module: "Consider using the github.com/rabbitmq/amqp091-go package instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×3
Dependency pinned to a stale untagged commit: github.com/streadway/amqp — Direct dependency `github.com/streadway/amqp` is required at `v0.0.0-20200108173154-1c71cc93ed71` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2020-01-08, 6.9 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/streadway/amqp` and has not moved this requirement in 6.9 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/streadway/amqp` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/streadway/amqp — Direct dependency `github.com/streadway/amqp` is required at `v0.0.0-20200108173154-1c71cc93ed71` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2020-01-08, 6.9 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/streadway/amqp` and has not moved this requirement in 6.9 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/streadway/amqp` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/streadway/amqp — Direct dependency `github.com/streadway/amqp` is required at `v0.0.0-20200108173154-1c71cc93ed71` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2020-01-08, 6.9 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/streadway/amqp` and has not moved this requirement in 6.9 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/streadway/amqp` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) endpointmanager/cmd/endpointpopulator/main.go:23— endpointmanager/cmd/endpointpopulator/main.go:23-153 | endpointmanager/cmd/historypruning/main.go:18-35 | endpointmanager/cmd/nppescontactpopulator/main.go:18-36 | endpointmanager/cmd/nppesorgpopulator/main.go:18-33 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:549— REDACTED:549-575 | endpointmanager/pkg/endpointwebscraper/endpointwebscraper.go:34-60 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:90-116 | endpointmanager/pkg/medicareendpointquerier/medicareendpointquerier.go:93-119 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:11-43 | endpointmanager/pkg/chplendpointquerier/medicscloudwebscraper.go:11-43 | endpointmanager/pkg/chplendpointquerier/medicsdaextapiwebscraper.go:10-41 | endpointmanager/pkg/chplendpointquerier/praxisemrwebscraper.go:11-43 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) REDACTED:148— REDACTED:148-167 | REDACTED:170-193 — 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) endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:172— endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:172-192 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:195-214 — 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) capabilityreceiver/pkg/capabilityhandler/validation/base.go:53— capabilityreceiver/pkg/capabilityhandler/validation/base.go:53-72 | capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:229-248 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) REDACTED:57— REDACTED:57-75 | REDACTED:78-96 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:269— endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:269-288 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:151-169 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) endpointmanager/cmd/chplendpointquerier/main.go:10— endpointmanager/cmd/chplendpointquerier/main.go:10-28 | endpointmanager/cmd/endpointwebscraper/main.go:12-33 — 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.
Duplicated block (23 lines × 2) endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:29— endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:29-51 | endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go:29-51 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:29` 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 (23 lines × 2) endpointmanager/pkg/chplendpointquerier/intelichartwebscraper.go:26— endpointmanager/pkg/chplendpointquerier/intelichartwebscraper.go:26-48 | endpointmanager/pkg/chplendpointquerier/kodjinwebscraper.go:25-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/intelichartwebscraper.go:26` 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 (23 lines × 2) endpointmanager/pkg/config/config.go:63— endpointmanager/pkg/config/config.go:63-85 | endpointmanager/pkg/config/config.go:187-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 3) endpointmanager/pkg/chplendpointquerier/allegiancemdwebscraper.go:21— endpointmanager/pkg/chplendpointquerier/allegiancemdwebscraper.go:21-40 | endpointmanager/pkg/chplendpointquerier/carecloudwebscraper.go:22-41 | endpointmanager/pkg/chplendpointquerier/tebrawebscraper.go:23-42 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/allegiancemdwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/tebrawebscraper.go` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/allegiancemdwebscraper.go:21` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 3) endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:85— endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:85-104 | REDACTED:126-145 | refresh.go:84-103 — 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 `endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:85` 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 (20 lines × 3) REDACTED:219— REDACTED:219-238 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:68-87 | endpointmanager/pkg/medicareendpointquerier/medicareendpointquerier.go:71-90 — `endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go` and `endpointmanager/pkg/medicareendpointquerier/medicareendpointquerier.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) endpointmanager/cmd/CHPLpopulator/main.go:212— endpointmanager/cmd/CHPLpopulator/main.go:212-231 | endpointmanager/cmd/CHPLpopulator/main.go:233-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) endpointmanager/pkg/endpointlinker/endpointlinker.go:440— endpointmanager/pkg/endpointlinker/endpointlinker.go:440-459 | endpointmanager/pkg/endpointlinker/endpointlinker.go:498-517 — 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 (20 lines × 2) REDACTED:345— REDACTED:345-364 | REDACTED:445-464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (18 lines × 2) endpointmanager/pkg/capabilityparser/base.go:298— endpointmanager/pkg/capabilityparser/base.go:298-315 | endpointmanager/pkg/smartparser/smartresponse.go:65-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:121— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:121-138 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:155-172 — 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 `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) REDACTED:150— REDACTED:150-167 | REDACTED:176-193 — 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 `REDACTED:150` 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (17 lines × 2) endpointmanager/pkg/chplendpointquerier/csvparser.go:82— endpointmanager/pkg/chplendpointquerier/csvparser.go:82-98 | endpointmanager/pkg/chplendpointquerier/customcsvparser.go:85-101 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/csvparser.go` and `endpointmanager/pkg/chplendpointquerier/customcsvparser.go` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/csvparser.go:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) endpointmanager/pkg/chplendpointquerier/nextgenapiIwebscraper.go:27— endpointmanager/pkg/chplendpointquerier/nextgenapiIwebscraper.go:27-43 | endpointmanager/pkg/chplendpointquerier/pointclickwebscraper.go:26-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/nextgenapiIwebscraper.go:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) endpointmanager/pkg/chplendpointquerier/pcisgoldwebscraper.go:12— endpointmanager/pkg/chplendpointquerier/pcisgoldwebscraper.go:12-28 | endpointmanager/pkg/chplendpointquerier/qualifactswebscraper.go:13-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/pcisgoldwebscraper.go:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) endpointmanager/pkg/capabilityparser/base.go:323— endpointmanager/pkg/capabilityparser/base.go:323-336 | endpointmanager/pkg/smartparser/smartresponse.go:118-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:59— endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:59-72 | REDACTED:112-125 — 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 `endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (14 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:38— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:38-54 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:176-189 — 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 `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10 lines × 2) endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:12— endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:12-21 | endpointmanager/pkg/chplendpointquerier/varianmedicalwebscraper.go:13-22 — 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 `endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:12` 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, `endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:22` calls `Find`, `Each`, `Contains` and `endpointmanager/pkg/chplendpointquerier/varianmedicalwebscraper.go:23` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) REDACTED:446— REDACTED:446-455 | REDACTED:25-34 — 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) endpointmanager/pkg/capabilityparser/base.go:59— endpointmanager/pkg/capabilityparser/base.go:59-68 | endpointmanager/pkg/capabilityparser/base.go:76-85 — 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 `endpointmanager/pkg/capabilityparser/base.go:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) REDACTED:142— REDACTED:142-150 | REDACTED:223-231 — 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 `REDACTED:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) endpointmanager/pkg/capabilityparser/base.go:116— endpointmanager/pkg/capabilityparser/base.go:116-124 | endpointmanager/pkg/capabilityparser/base.go:187-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/capabilityparser/base.go:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) REDACTED:136— REDACTED:136-144 | REDACTED:146-154 — 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.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×3
Discarded error (assigned to `_`, then its result used) endpointmanager/pkg/fetcher/fetcher.go:57— `byteValue, _ := io.ReadAll(jsonFile)` writes the call's error to `_` and then uses `byteValue` as if the call succeeded. When `io.ReadAll` fails, `byteValue` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `byteValue` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) endpointmanager/pkg/endpointlinker/endpointlinker.go:219— `endpointName, _ := NormalizeOrgName(org.OrganizationName)` writes the call's error to `_` and then uses `endpointName` as if the call succeeded. When `NormalizeOrgName` fails, `endpointName` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `endpointName` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:168— `fhirVersion, _ = capStat.GetFHIRVersion()` writes the call's error to `_` and then uses `fhirVersion` as if the call succeeded. When `capStat.GetFHIRVersion` fails, `fhirVersion` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `fhirVersion` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Change coupling: fhirendpointstore.go ↔ lanternlist.go endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:1— `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go` and `endpointmanager/pkg/fetcher/lanternlist.go` change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `03e97135` Modified the BundleQuerierParser and population script to parse and s…; `85677a3d` Changed the datatype of HTI-1 orgActive from boolean to string. Modif…; `5e41990d` Rectified errors in the bundle parser which resulted in duplicate HTI… — run `git show` on any of them.
Change coupling: REDACTED ↔ lanternlist.go REDACTED:1— `REDACTED` and `endpointmanager/pkg/fetcher/lanternlist.go` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `03e97135` Modified the BundleQuerierParser and population script to parse and s…; `85677a3d` Changed the datatype of HTI-1 orgActive from boolean to string. Modif…; `7c7732c0` Modified the scraping and population code to fetch organization data … — run `git show` on any of them.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×2
Edited copies of one member (3 members, 29+ corresponding lines) endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:11-44 | endpointmanager/pkg/chplendpointquerier/hmsfirstwebscraper.go:11-41 | endpointmanager/pkg/chplendpointquerier/officepracticumwebscraper.go:10-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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, 29+ corresponding lines) endpointmanager/pkg/chplendpointquerier/advancedmdwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/advancedmdwebscraper.go:11-40 | endpointmanager/pkg/chplendpointquerier/humanaurlwebscraper.go:11-39 | endpointmanager/pkg/chplendpointquerier/naphcareparser.go:11-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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 (28 corresponding lines) · ×2
Edited copy of a member (28 corresponding lines) REDACTED:41— REDACTED:41-68 | capabilityreceiver/cmd/migratevalidations/main.go:88-118 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) endpointmanager/pkg/chplendpointquerier/ezemrxwebscraper.go:9— endpointmanager/pkg/chplendpointquerier/ezemrxwebscraper.go:9-38 | endpointmanager/pkg/chplendpointquerier/ontadawebscraper.go:9-36 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) endpointmanager/pkg/fetcher/cernerlist.go:7— endpointmanager/pkg/fetcher/cernerlist.go:7-33 | endpointmanager/pkg/fetcher/defaultlist.go:4-27 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:760— capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:760-783 | capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:793-816 — 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 (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) REDACTED:63— REDACTED:63-84 | REDACTED:153-175 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) capabilityreceiver/pkg/capabilityhandler/vendor_policy.go:201— capabilityreceiver/pkg/capabilityhandler/vendor_policy.go:201-222 | capabilityreceiver/pkg/capabilityhandler/vendor_policy.go:224-248 — 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 (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) endpointmanager/pkg/capabilityparser/base.go:58— endpointmanager/pkg/capabilityparser/base.go:58-72 | endpointmanager/pkg/capabilityparser/base.go: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.
Edited copy of a member (15 corresponding lines) endpointmanager/pkg/capabilityparser/factory.go:43— endpointmanager/pkg/capabilityparser/factory.go:43-57 | endpointmanager/pkg/smartparser/smartresponse.go:47-61 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) endpointmanager/pkg/capabilityparser/base.go:43— endpointmanager/pkg/capabilityparser/base.go:43-55 | endpointmanager/pkg/capabilityparser/base.go:162-173 — 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) capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:287— capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:287-299 | capabilityreceiver/pkg/capabilityhandler/validation/stu3validation.go:129-140 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (29 lines × 2) capabilityreceiver/pkg/capabilityhandler/validation/base.go:22— capabilityreceiver/pkg/capabilityhandler/validation/base.go:22-50 | capabilityreceiver/pkg/capabilityhandler/validation/stu3validation.go:26-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (29 lines × 2) endpointmanager/pkg/chplendpointquerier/aidboxquerier.go:12— endpointmanager/pkg/chplendpointquerier/aidboxquerier.go:12-40 | endpointmanager/pkg/chplendpointquerier/willowquerierparser.go:11-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (25–26 lines × 2) endpointmanager/pkg/chplendpointquerier/medicscloudwebscraper.go:13— endpointmanager/pkg/chplendpointquerier/medicscloudwebscraper.go:13-38 | endpointmanager/pkg/chplendpointquerier/medicsdaextapiwebscraper.go:12-36 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/medicscloudwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/medicsdaextapiwebscraper.go` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (25–26 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:217— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:217-242 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:309-333 — 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 `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:217` 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 (19–20 lines × 2) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:536— capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:536-554 | capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:605-624 — 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 `capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:536` 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) endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:27— endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:27-45 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:27-46 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:27` 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 (19 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:33— endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:33-51 | endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:72-90 — 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 `endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:33` 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 (19 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:52— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:52-70 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:350-368 — 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 (16 lines × 2) REDACTED:73— REDACTED:73-88 | REDACTED:158-173 — 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 `REDACTED: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 (16 lines × 2) endpointmanager/pkg/chplendpointquerier/medifusionwebscraper.go:29— endpointmanager/pkg/chplendpointquerier/medifusionwebscraper.go:29-45 | endpointmanager/pkg/chplendpointquerier/webchartnowwebscraper.go:30-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/medifusionwebscraper.go:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:459— capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:459-473 | capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:621-633 — 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 `capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:459` 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–15 lines × 2) endpointmanager/pkg/chplendpointquerier/moyaewebscraper.go:34— endpointmanager/pkg/chplendpointquerier/moyaewebscraper.go:34-46 | endpointmanager/pkg/chplendpointquerier/techcarewebscraper.go:26-40 — 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 (15 lines × 2) endpointmanager/pkg/chplendpointquerier/hcscwebscraper.go:48— endpointmanager/pkg/chplendpointquerier/hcscwebscraper.go:48-62 | endpointmanager/pkg/chplendpointquerier/hcscwebscraper.go:69-83 — 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 (15 lines × 2) endpointmanager/pkg/capabilityparser/base.go:338— endpointmanager/pkg/capabilityparser/base.go:338-352 | endpointmanager/pkg/smartparser/smartresponse.go:133-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 4) REDACTED:551— REDACTED:551-562 | endpointmanager/pkg/endpointwebscraper/endpointwebscraper.go:36-47 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:92-103 | endpointmanager/pkg/medicareendpointquerier/medicareendpointquerier.go:95-106 — `REDACTED` and `endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 48 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 4) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:177— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:177-188 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:328-339 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:478-489 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:768-779 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 2) REDACTED:88— REDACTED:88-99 | REDACTED:179-190 — 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 `REDACTED:88` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) endpointmanager/cmd/medicaidendpointquerier/main.go:11— endpointmanager/cmd/medicaidendpointquerier/main.go:11-22 | endpointmanager/cmd/medicareendpointquerier/main.go:11-22 — `endpointmanager/cmd/medicaidendpointquerier/main.go` and `endpointmanager/cmd/medicareendpointquerier/main.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 12 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:257— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:257-267 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:398-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (11 lines × 2) endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:34— endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:34-44 | endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:137-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 3) REDACTED:578— REDACTED:578-587 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:119-128 | endpointmanager/pkg/medicareendpointquerier/medicareendpointquerier.go:122-131 — `REDACTED` and `endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 48 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:36— endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:36-45 | endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:70-79 | endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:139-148 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:36` 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) endpointmanager/cmd/CHPLreport/main.go:14— endpointmanager/cmd/CHPLreport/main.go:14-18 | endpointmanager/cmd/endpointexporter/main.go:14-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) REDACTED:33— REDACTED:33-37 | REDACTED:106-110 — 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 `REDACTED:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:17— endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:17-23 | endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go:17-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:17— endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:17-23 | endpointmanager/pkg/chplendpointquerier/praxisemrwebscraper.go:17-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:17` 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.
X28 · Index access outside its own emptiness guard· Index access outside its own emptiness guard · ×2
Index access outside its own emptiness guard endpointmanager/cmd/CHPLupdatecheck/main.go:145— `index` is the result of a search that answers -1 when nothing is found, and `urlString[index:]` uses it as a bound with no test of `index` in between. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Test `index < 0` (or use `strings.Cut`) before using it.
Index access outside its own emptiness guard endpointmanager/cmd/CHPLupdatecheck/main.go:163— `index` is the result of a search that answers -1 when nothing is found, and `fileName[:index]` uses it as a bound with no test of `index` in between. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Test `index < 0` (or use `strings.Cut`) before using it.
chplendpointquerier.QueryCHPLEndpointList (cyclomatic 153) REDACTED:227— chplendpointquerier.QueryCHPLEndpointList has cyclomatic complexity 153 (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.
capabilityquerier.requestCapabilityStatementAndSmartOnFhir (cyclomatic 46) REDACTED:239— capabilityquerier.requestCapabilityStatementAndSmartOnFhir has cyclomatic complexity 46 (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.
chplendpointquerier.BundleToLanternFormat (cyclomatic 45) REDACTED:205— chplendpointquerier.BundleToLanternFormat has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
chplendpointquerier.extractOrganizationFields (cyclomatic 39) REDACTED:66— chplendpointquerier.extractOrganizationFields has cyclomatic complexity 39 (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.
(anonymous) (cyclomatic 35) shinydashboard/lantern/www/js/accessibility.js:203— (anonymous) has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
capabilityhandler.updateOrInsertEndpointRows (cyclomatic 32) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:479— capabilityhandler.updateOrInsertEndpointRows has cyclomatic complexity 32 (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.
capabilityhandler.formatMessage (cyclomatic 26) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:46— capabilityhandler.formatMessage has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
archivefile.CreateArchive (cyclomatic 25) REDACTED:105— archivefile.CreateArchive 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.
FHIREndpointInfo.EqualExcludeMetadata (cyclomatic 25) endpointmanager/pkg/endpointmanager/fhirendpointinfo.go:39— FHIREndpointInfo.EqualExcludeMetadata has cyclomatic complexity 25 (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.
historycleanup.GetInfoHistoryDuplicateData (cyclomatic 24) endpointmanager/pkg/historycleanup/historycleanup.go:20— historycleanup.GetInfoHistoryDuplicateData 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.
validation.checkResourceList (cyclomatic 22) capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:148— validation.checkResourceList 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.
main.main (cyclomatic 22) endpointmanager/cmd/CHPLpopulator/main.go:82— main.main 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.
config.SetupConfig (cyclomatic 22) endpointmanager/pkg/config/config.go:7— config.SetupConfig 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.
FHIRList.GetEndpoints (cyclomatic 21) REDACTED:25— FHIRList.GetEndpoints has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
postgresql.prepareFHIREndpointStatements (cyclomatic 20) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:843— postgresql.prepareFHIREndpointStatements has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HealthITProduct.Equal (cyclomatic 19) endpointmanager/pkg/endpointmanager/healthitproduct.go:37— HealthITProduct.Equal has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
populatefhirendpoints.AddEndpointData (cyclomatic 19) endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:21— populatefhirendpoints.AddEndpointData 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.
historypruning.PruneInfoHistory (cyclomatic 19) endpointmanager/pkg/historypruning/historypruning.go:17— historypruning.PruneInfoHistory 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.
capabilityhandler.saveMsgInDB (cyclomatic 18) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:208— capabilityhandler.saveMsgInDB 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.
chplendpointquerier.CustomCSVParser (cyclomatic 18) endpointmanager/pkg/chplendpointquerier/customcsvparser.go:23— chplendpointquerier.CustomCSVParser 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.
endpointlinker.LinkAllOrgsAndEndpoints (cyclomatic 18) endpointmanager/pkg/endpointlinker/endpointlinker.go:327— endpointlinker.LinkAllOrgsAndEndpoints 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.
LanternList.GetEndpoints (cyclomatic 18) endpointmanager/pkg/fetcher/lanternlist.go:9— LanternList.GetEndpoints 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.
chplmapper.MatchEndpointToProduct (cyclomatic 17) capabilityreceiver/pkg/chplmapper/capabilityinfo.go:39— chplmapper.MatchEndpointToProduct 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.
main.main (cyclomatic 17) endpointmanager/cmd/endpointpopulator/main.go:23— main.main 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.
chplendpointquerier.CSVParser (cyclomatic 17) endpointmanager/pkg/chplendpointquerier/csvparser.go:25— chplendpointquerier.CSVParser 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.
chplquerier.prodNeedsUpdate (cyclomatic 17) REDACTED:356— chplquerier.prodNeedsUpdate 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.
endpointlinker.linkerFix (cyclomatic 17) endpointmanager/pkg/endpointlinker/endpointlinker.go:433— endpointlinker.linkerFix 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.
postgresql.prepareHistoryPruningStatements (cyclomatic 16) endpointmanager/pkg/endpointmanager/postgresql/historypruningstore.go:167— postgresql.prepareHistoryPruningStatements has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Hotspot: REDACTED REDACTED:205— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in chplendpointquerier.BundleToLanternFormat at line 205. 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-08-03..2026-11-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-03 15:35:11 -06:00' --until='2026-11-01 15:35:11 -06:00' --full-history --no-merges -- REDACTED`: 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.
chplendpointquerier.QueryCHPLEndpointList (cognitive 153) REDACTED:227— chplendpointquerier.QueryCHPLEndpointList has cognitive complexity 153 (threshold 15). Drivers by points: if/else 152, 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.
chplendpointquerier.extractOrganizationFields (cognitive 122) REDACTED:66— chplendpointquerier.extractOrganizationFields has cognitive complexity 122 (threshold 15). Drivers by points: if/else 30 (102 pts), loops 4 (15 pts), boolean chains 5 (nesting depth added 83). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
chplendpointquerier.BundleToLanternFormat (cognitive 115) REDACTED:205— chplendpointquerier.BundleToLanternFormat has cognitive complexity 115 (threshold 15). Drivers by points: if/else 32 (97 pts), loops 6 (12 pts), boolean chains 6 (nesting depth added 71). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
(anonymous) (cognitive 114) shinydashboard/lantern/www/js/accessibility.js:203— (anonymous) has cognitive complexity 114 (threshold 15). Drivers by points: loops 12 (56 pts), if/else 16 (54 pts), boolean chains 4 (nesting depth added 82). Of this number, 110 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
FHIRList.GetEndpoints (cognitive 103) REDACTED:25— FHIRList.GetEndpoints has cognitive complexity 103 (threshold 15). Drivers by points: if/else 19 (88 pts), loops 3 (13 pts), boolean chains 2 (nesting depth added 79). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
capabilityhandler.updateOrInsertEndpointRows (cognitive 92) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:479— capabilityhandler.updateOrInsertEndpointRows has cognitive complexity 92 (threshold 15). Drivers by points: if/else 28 (85 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 58). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
capabilityquerier.requestCapabilityStatementAndSmartOnFhir (cognitive 80) REDACTED:239— capabilityquerier.requestCapabilityStatementAndSmartOnFhir has cognitive complexity 80 (threshold 15). Drivers by points: if/else 28 (65 pts), boolean chains 14, match/switch 1 (nesting depth added 37). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
historycleanup.GetInfoHistoryDuplicateData (cognitive 71) endpointmanager/pkg/historycleanup/historycleanup.go:20— historycleanup.GetInfoHistoryDuplicateData has cognitive complexity 71 (threshold 15). Drivers by points: if/else 22 (65 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
historypruning.PruneInfoHistory (cognitive 63) endpointmanager/pkg/historypruning/historypruning.go:17— historypruning.PruneInfoHistory has cognitive complexity 63 (threshold 15). Drivers by points: if/else 18 (59 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 42). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
main.main (cognitive 46) endpointmanager/cmd/CHPLpopulator/main.go:82— main.main has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (38 pts), loops 3 (8 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.
archivefile.CreateArchive (cognitive 46) REDACTED:105— archivefile.CreateArchive has cognitive complexity 46 (threshold 15). Drivers by points: if/else 19 (36 pts), loops 8 (10 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validation.checkResourceList (cognitive 44) capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:148— validation.checkResourceList has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (37 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 23). 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.
endpointlinker.linkerFix (cognitive 43) endpointmanager/pkg/endpointlinker/endpointlinker.go:433— endpointlinker.linkerFix has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (39 pts), loops 2 (4 pts) (nesting depth added 23). 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.
populatefhirendpoints.AddEndpointData (cognitive 39) endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:21— populatefhirendpoints.AddEndpointData has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (35 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanternList.GetEndpoints (cognitive 38) endpointmanager/pkg/fetcher/lanternlist.go:9— LanternList.GetEndpoints has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (34 pts), boolean chains 3, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capabilityhandler.formatMessage (cognitive 36) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:46— capabilityhandler.formatMessage has cognitive complexity 36 (threshold 15). Drivers by points: if/else 24 (34 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
endpointlinker.LinkAllOrgsAndEndpoints (cognitive 34) endpointmanager/pkg/endpointlinker/endpointlinker.go:327— endpointlinker.LinkAllOrgsAndEndpoints has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 4 (10 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Store.UpdateFHIREndpointsNPIOrg (cognitive 34) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:432— Store.UpdateFHIREndpointsNPIOrg has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 3 (11 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
capabilityhandler.RunSupportedResourcesChecks (cognitive 33) REDACTED:8— capabilityhandler.RunSupportedResourcesChecks has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chplmapper.MatchEndpointToProduct (cognitive 33) capabilityreceiver/pkg/chplmapper/capabilityinfo.go:39— chplmapper.MatchEndpointToProduct has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chplendpointquerier.CustomCSVParser (cognitive 32) endpointmanager/pkg/chplendpointquerier/customcsvparser.go:23— chplendpointquerier.CustomCSVParser has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capabilityhandler.saveMsgInDB (cognitive 31) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:208— capabilityhandler.saveMsgInDB has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (31 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 31) endpointmanager/cmd/endpointpopulator/main.go:23— main.main has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (26 pts), loops 2 (4 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.
chplquerier.persistProduct (cognitive 31) REDACTED:284— chplquerier.persistProduct has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (27 pts), loops 2 (4 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.
Store.GetFHIREndpointInfosUsingURL (cognitive 31) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:194— Store.GetFHIREndpointInfosUsingURL has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (30 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Store.GetFHIREndpointInfosByURLWithDifferentRequestedVersion) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Store.GetFHIREndpointInfosByURLWithDifferentRequestedVersion (cognitive 31) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:662— Store.GetFHIREndpointInfosByURLWithDifferentRequestedVersion has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (30 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Store.GetFHIREndpointInfosUsingURL) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
archivefile.getMetadata (cognitive 29) REDACTED:440— archivefile.getMetadata has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 5 (9 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chplendpointquerier.CSVParser (cognitive 29) endpointmanager/pkg/chplendpointquerier/csvparser.go:25— chplendpointquerier.CSVParser has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capabilityhandler.insertEndpointRows (cognitive 28) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:383— capabilityhandler.insertEndpointRows has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
endpointwebscraper.OneUpQuerier (cognitive 26) endpointmanager/pkg/endpointwebscraper/1upparser.go:14— endpointwebscraper.OneUpQuerier has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
nppesquerier.ParseAndStoreNPIContactsFile (cognitive 25) REDACTED:210— nppesquerier.ParseAndStoreNPIContactsFile has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (22 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FHIREndpointInfo.EqualExcludeMetadata (cognitive 24) endpointmanager/pkg/endpointmanager/fhirendpointinfo.go:39— FHIREndpointInfo.EqualExcludeMetadata has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18, boolean chains 6. 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.
sendendpoints.GetEnptsAndSend (cognitive 24) REDACTED:19— sendendpoints.GetEnptsAndSend has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capabilityquerier.GetAndSendVersionsResponse (cognitive 23) REDACTED:93— capabilityquerier.GetAndSendVersionsResponse has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.CHPLEndpointListUpdateCheck (cognitive 23) endpointmanager/cmd/CHPLupdatecheck/main.go:113— main.CHPLEndpointListUpdateCheck has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 3 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chplendpointquerier.MagilenEnterprisesWebscraper (cognitive 23) endpointmanager/pkg/chplendpointquerier/magilenenterpriseswebscraper.go:11— chplendpointquerier.MagilenEnterprisesWebscraper has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (23 pts) (nesting depth added 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 25). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Store.UpdateFHIREndpointOrganizations (cognitive 23) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:487— Store.UpdateFHIREndpointOrganizations has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
archivefile.getHistory (cognitive 22) REDACTED:334— archivefile.getHistory has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
populatefhirendpoints.RemoveOldEndpoints (cognitive 22) endpointmanager/pkg/fhirendpointquerier/populatefhirendpoints.go:177— populatefhirendpoints.RemoveOldEndpoints has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (5 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 22) shinydashboard/lantern/www/js/accessibility.js:64— (anonymous) has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (9 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.
chplmapper.OpenCHPLEndpointListInfoFile (cognitive 21) capabilityreceiver/pkg/chplmapper/capabilityinfo.go:145— chplmapper.OpenCHPLEndpointListInfoFile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (9 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.SetupConfig (cognitive 21) endpointmanager/pkg/config/config.go:7— config.SetupConfig has cognitive complexity 21 (threshold 15). Drivers by points: if/else 21. 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.
main.main (cognitive 20) endpointmanager/cmd/CHPLupdatecheck/main.go:25— main.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (20 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
chplquerier.prodNeedsUpdate (cognitive 20) REDACTED:356— chplquerier.prodNeedsUpdate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
endpointlinker.getIdsOfMatchingNPIOrgs (cognitive 20) endpointmanager/pkg/endpointlinker/endpointlinker.go:77— endpointlinker.getIdsOfMatchingNPIOrgs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 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.
postgresql.prepareFHIREndpointStatements (cognitive 19) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:843— postgresql.prepareFHIREndpointStatements has cognitive complexity 19 (threshold 15). Drivers by points: if/else 19. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
main.addToValidationTableHistory (cognitive 18) capabilityreceiver/cmd/migratevalidations/main.go:122— main.addToValidationTableHistory has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 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.
capabilityhandler.getCapabilityStatementProfiles (cognitive 18) REDACTED:54— capabilityhandler.getCapabilityStatementProfiles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chplendpointquerier.eMedPracticeWebscraper (cognitive 18) endpointmanager/pkg/chplendpointquerier/emedpracticewebscraper.go:12— chplendpointquerier.eMedPracticeWebscraper has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 24). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
HealthITProduct.Equal (cognitive 18) endpointmanager/pkg/endpointmanager/healthitproduct.go:37— HealthITProduct.Equal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, 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.
main.addToValidationField (cognitive 17) capabilityreceiver/cmd/migratevalidations/main.go:235— main.addToValidationField has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), 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.
capabilityhandler.checkArrFieldExtension (cognitive 17) REDACTED:178— capabilityhandler.checkArrFieldExtension has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 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.
Store.GetFHIREndpointInfo (cognitive 17) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:51— Store.GetFHIREndpointInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (17 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Store.GetFHIREndpointInfoUsingURLAndRequestedVersion) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Store.GetFHIREndpointInfoUsingURLAndRequestedVersion (cognitive 17) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:349— Store.GetFHIREndpointInfoUsingURLAndRequestedVersion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (17 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Store.GetFHIREndpointInfo) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
endpointwebscraper.HTMLtablewebscraper (cognitive 17) endpointmanager/pkg/endpointwebscraper/htmltablewebscraper.go:14— endpointwebscraper.HTMLtablewebscraper has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (17 pts) (nesting depth added 10). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 24). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
main.updateOperationResource (cognitive 16) REDACTED:72— main.updateOperationResource has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
capabilityhandler.saveVersionResponseMsgInDB (cognitive 16) capabilityreceiver/pkg/capabilityhandler/capabilityreceiver.go:675— capabilityhandler.saveVersionResponseMsgInDB has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 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.
baseVal.DocumentSetValid (cognitive 16) capabilityreceiver/pkg/capabilityhandler/validation/base.go:252— baseVal.DocumentSetValid has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 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.
nppesquerier.removeNestedDoubleQuotesFromCSV (cognitive 16) REDACTED:119— nppesquerier.removeNestedDoubleQuotesFromCSV has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
accessibility.applyNavTabAria (cognitive 16) shinydashboard/lantern/www/js/accessibility.js:101— accessibility.applyNavTabAria has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 2 (4 pts), boolean chains 1, ternaries 1 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D22 · Internal API Consistency· `capabilityhandler.RunSupportedResourcesChecks` returns a map (`map[K]V`) where its 4 siblings return a slice (`[]T`) · ×1
`capabilityhandler.RunSupportedResourcesChecks` returns a map (`map[K]V`) where its 4 siblings return a slice (`[]T`) REDACTED:8— 4 of 5 collection-returning members of `package capabilityhandler` return a slice (`[]T`) (4 of 5). Siblings: capabilityhandler.RunIncludedFieldsAndExtensionsChecks (REDACTED:18); capabilityhandler.RunIncludedFieldsChecks (REDACTED:30); capabilityhandler.RunIncludedExtensionsChecks (REDACTED:123); capabilityhandler.RunSupportedProfilesCheck (REDACTED:10). Return a slice (`[]T`). [rule A4]
TooManyFields: NPICsvLine endpointmanager/pkg/nppesquerier/populatenpiorgs.go:19— TooManyFields — 329 stored fields. The bar is 30 stored fields; this is 299 over it, 10.97× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyMethods: Store endpointmanager/pkg/endpointmanager/postgresql/store.go:17— TooManyMethods — 95 methods, declared across 13 files: postgresql/fhirendpointstore.go (25), postgresql/healthitproductstore.go (12), postgresql/npiorganizationstore.go (12), postgresql/fhirendpointinfostore.go (10), +9 more file(s). The bar is 30 methods; this is 65 over it, 3.17× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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.
Change-coupling hub: fhirendpoint.go → REDACTED, REDACTED, fetcher.go, lanternlist.go endpointmanager/pkg/endpointmanager/fhirendpoint.go— `endpointmanager/pkg/endpointmanager/fhirendpoint.go` changes together with 4 other files — `REDACTED`, `REDACTED`, `endpointmanager/pkg/fetcher/fetcher.go`, `endpointmanager/pkg/fetcher/lanternlist.go` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication· Near-duplicate member family (4 members, 71 shared lines) · ×1
Near-duplicate member family (4 members, 71 shared lines) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:51— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:51-191 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:194-346 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:349-492 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:662-786 — These 4 members are variants of one another: a block of 71 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) endpointmanager/pkg/chplendpointquerier/broadstreetwebscraper.go:10— endpointmanager/pkg/chplendpointquerier/broadstreetwebscraper.go:10-44 | endpointmanager/pkg/chplendpointquerier/elationwebscraper.go:11-47 | endpointmanager/pkg/chplendpointquerier/geniussolutionswebscraper.go:11-53 | endpointmanager/pkg/chplendpointquerier/intelichartwebscraper.go:11-48 | endpointmanager/pkg/chplendpointquerier/interopxparser.go:11-45 | endpointmanager/pkg/chplendpointquerier/kodjinwebscraper.go:10-47 | endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:11-48 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:11-46 | endpointmanager/pkg/chplendpointquerier/triarqparser.go:11-44 | endpointmanager/pkg/chplendpointquerier/zhhealthcarewebscraper.go:11-44 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) endpointmanager/pkg/chplendpointquerier/athenaparser.go:14— endpointmanager/pkg/chplendpointquerier/athenaparser.go:14-57 | endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:14-56 | endpointmanager/pkg/chplendpointquerier/netsmartparser.go:14-57 | endpointmanager/pkg/chplendpointquerier/nextechparser.go:12-53 | endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go:12-58 | endpointmanager/pkg/chplendpointquerier/patientpatternparser.go:12-58 | endpointmanager/pkg/chplendpointquerier/streamlinemdparser.go:14-57 | endpointmanager/pkg/chplendpointquerier/zoommdParser.go:14-59 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:24-63 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) capabilityquerier/cmd/main.go:180— capabilityquerier/cmd/main.go:180-209 | capabilityreceiver/cmd/main.go:48-61 | REDACTED:268-376 | capabilityreceiver/cmd/migratevalidations/main.go:326-439 | endpointmanager/cmd/chplquerier/main.go:37-74 | endpointmanager/cmd/datavalidation/main.go:17-46 | endpointmanager/cmd/historycleanup/main.go:14-25 | endpointmanager/cmd/sendendpoints/main.go:16-47 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:35— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:35-77 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:201-242 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:245-288 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:292-333 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:387-429 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (78 corresponding lines) · ×1
Edited copy of a member (78 corresponding lines) capabilityreceiver/cmd/migratevalidations/main.go:122— capabilityreceiver/cmd/migratevalidations/main.go:122-199 | capabilityreceiver/cmd/migratevalidations/main.go:235-321 — These two members are one piece of code written twice and then edited apart: 78 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (77 corresponding lines) · ×1
Edited copy of a member (77 corresponding lines) REDACTED:72— REDACTED:72-153 | REDACTED:157-233 — These two members are one piece of code written twice and then edited apart: 77 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) endpointmanager/pkg/chplendpointquerier/csvparser.go:25— endpointmanager/pkg/chplendpointquerier/csvparser.go:25-98 | endpointmanager/pkg/chplendpointquerier/customcsvparser.go:23-101 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 41+ corresponding lines) · ×1
Edited copies of one member (3 members, 41+ corresponding lines) endpointmanager/pkg/chplendpointquerier/indianhealthwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/indianhealthwebscraper.go:11-59 | endpointmanager/pkg/chplendpointquerier/nextgenapiIwebscraper.go:11-53 | endpointmanager/pkg/chplendpointquerier/pointclickwebscraper.go:11-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 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, 57+ corresponding lines) · ×1
Edited copies of one member (3 members, 57+ corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:25— endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:25-102 | endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:106-162 | endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:165-255 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 57 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) endpointmanager/pkg/chplendpointquerier/altheawebscraper.go:11— endpointmanager/pkg/chplendpointquerier/altheawebscraper.go:11-55 | endpointmanager/pkg/chplendpointquerier/onemedicalwebscraper.go:11-57 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:507— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:507-562 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:565-629 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:11-45 | endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:11-48 | endpointmanager/pkg/chplendpointquerier/canvaswebscraper.go:11-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) capabilityreceiver/pkg/capabilityhandler/validation/base.go:163— capabilityreceiver/pkg/capabilityhandler/validation/base.go:163-204 | capabilityreceiver/pkg/capabilityhandler/validation/base.go:208-249 — 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) endpointmanager/pkg/chplendpointquerier/moyaewebscraper.go:10— endpointmanager/pkg/chplendpointquerier/moyaewebscraper.go:10-58 | endpointmanager/pkg/chplendpointquerier/techcarewebscraper.go:11-51 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:57— endpointmanager/pkg/chplendpointquerier/kaiserwebscraper.go:57-104 | refresh.go:68-103 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 32+ corresponding lines) · ×1
Edited copies of one member (6 members, 32+ corresponding lines) endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:11-51 | endpointmanager/pkg/chplendpointquerier/meridianwebscraper.go:11-45 | endpointmanager/pkg/chplendpointquerier/microfourwebscraper.go:11-43 | endpointmanager/pkg/chplendpointquerier/nextgenpracticewebscraper.go:11-42 | endpointmanager/pkg/chplendpointquerier/pcesystemswebscraper.go:11-47 | endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go:11-51 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) endpointmanager/pkg/chplendpointquerier/carefluencewebscraper.go:11— endpointmanager/pkg/chplendpointquerier/carefluencewebscraper.go:11-42 | endpointmanager/pkg/chplendpointquerier/inpracsyswebscraper.go:11-44 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 46+ corresponding lines) · ×1
Edited copies of one member (3 members, 46+ corresponding lines) endpointmanager/pkg/chplendpointquerier/medhostquerier.go:11— endpointmanager/pkg/chplendpointquerier/medhostquerier.go:11-56 | endpointmanager/pkg/chplendpointquerier/pcisgoldwebscraper.go:10-55 | endpointmanager/pkg/chplendpointquerier/qualifactswebscraper.go:11-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 46 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) REDACTED:87— REDACTED:87-120 | REDACTED:178-215 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) endpointmanager/pkg/chplendpointquerier/chntechsolutionswebscraper.go:12— endpointmanager/pkg/chplendpointquerier/chntechsolutionswebscraper.go:12-44 | endpointmanager/pkg/chplendpointquerier/criterionswebscraper.go:11-41 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 31+ corresponding lines) · ×1
Edited copies of one member (5 members, 31+ corresponding lines) endpointmanager/pkg/chplendpointquerier/centenewebscraper.go:11— endpointmanager/pkg/chplendpointquerier/centenewebscraper.go:11-41 | endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:11-49 | endpointmanager/pkg/chplendpointquerier/medicalminewebscraper.go:11-48 | endpointmanager/pkg/chplendpointquerier/medifusionwebscraper.go:11-45 | endpointmanager/pkg/chplendpointquerier/webchartnowwebscraper.go:11-45 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) endpointmanager/pkg/chplendpointquerier/firstinsightparser.go:10— endpointmanager/pkg/chplendpointquerier/firstinsightparser.go:10-52 | endpointmanager/pkg/chplendpointquerier/modernizingmedicineparser.go:8-54 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 34+ corresponding lines) · ×1
Edited copies of one member (7 members, 34+ corresponding lines) endpointmanager/pkg/chplendpointquerier/cignawebscraper.go:11— endpointmanager/pkg/chplendpointquerier/cignawebscraper.go:11-44 | endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:10-47 | endpointmanager/pkg/chplendpointquerier/escribehostwebscraper.go:11-49 | endpointmanager/pkg/chplendpointquerier/ethizowebscraper.go:11-48 | endpointmanager/pkg/chplendpointquerier/smartemrwebscraper.go:11-45 | endpointmanager/pkg/chplendpointquerier/smilecdrwebscraper.go:11-45 | endpointmanager/pkg/chplendpointquerier/varianmedicalwebscraper.go:11-48 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) endpointmanager/pkg/chplendpointquerier/cernerBundleParser.go:8— endpointmanager/pkg/chplendpointquerier/cernerBundleParser.go:8-36 | endpointmanager/pkg/chplendpointquerier/epicquerier.go:10-38 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:306— endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:306-339 | endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:342-374 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 41+ corresponding lines) · ×1
Edited copies of one member (5 members, 41+ corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:24— endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:24-66 | endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:77-119 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:18-58 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:62-103 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:107-148 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 26+ corresponding lines) · ×1
Edited copies of one member (6 members, 26+ corresponding lines) endpointmanager/pkg/chplendpointquerier/allegiancemdwebscraper.go:10— endpointmanager/pkg/chplendpointquerier/allegiancemdwebscraper.go:10-40 | endpointmanager/pkg/chplendpointquerier/betaAfoundriaWebScraper.go:9-34 | endpointmanager/pkg/chplendpointquerier/carecloudwebscraper.go:11-41 | endpointmanager/pkg/chplendpointquerier/myhelowebscraper.go:10-37 | endpointmanager/pkg/chplendpointquerier/swaggeruiparser.go:12-50 | endpointmanager/pkg/chplendpointquerier/tebrawebscraper.go:11-42 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) endpointmanager/pkg/chplendpointquerier/anthemparser.go:20— endpointmanager/pkg/chplendpointquerier/anthemparser.go:20-51 | endpointmanager/pkg/chplendpointquerier/azurewebsitesurlwebscraper.go:10-45 | endpointmanager/pkg/chplendpointquerier/footholdparser.go:11-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) endpointmanager/cmd/CHPLreport/main.go:13— endpointmanager/cmd/CHPLreport/main.go:13-80 | endpointmanager/cmd/endpointexporter/main.go:13-27 | endpointmanager/cmd/endpointlinker/main.go:15-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:80— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:80-111 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:114-138 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:141-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 20+ corresponding lines) · ×1
Edited copies of one member (6 members, 20+ corresponding lines) endpointmanager/pkg/capabilityparser/base.go:105— endpointmanager/pkg/capabilityparser/base.go:105-124 | endpointmanager/pkg/capabilityparser/base.go:127-146 | endpointmanager/pkg/capabilityparser/base.go:176-195 | endpointmanager/pkg/capabilityparser/base.go:198-217 | endpointmanager/pkg/capabilityparser/base.go:220-239 | endpointmanager/pkg/fetcher/fetcher.go:138-159 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:17— endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:17-51 | endpointmanager/pkg/endpointmanager/postgresql/criteriastore.go:56-90 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) endpointmanager/pkg/endpointmanager/npiorganization.go:23— endpointmanager/pkg/endpointmanager/npiorganization.go:23-48 | endpointmanager/pkg/endpointmanager/vendor.go:23-55 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 28+ corresponding lines) · ×1
Edited copies of one member (4 members, 28+ corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:601— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:601-629 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:631-658 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:660-688 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:690-718 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/npicontactstore.go:88— endpointmanager/pkg/endpointmanager/postgresql/npicontactstore.go:88-113 | endpointmanager/pkg/endpointmanager/postgresql/npicontactstore.go:116-140 — 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:175— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:175-197 | endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:190-210 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) REDACTED:211— REDACTED:211-238 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:65-87 | endpointmanager/pkg/medicareendpointquerier/medicareendpointquerier.go:68-90 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) REDACTED:30— REDACTED:30-47 | REDACTED:103-120 — 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 copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) endpointmanager/pkg/chplquerier/criteriaquerier.go:142— endpointmanager/pkg/chplquerier/criteriaquerier.go:142-163 | REDACTED:262-279 | endpointmanager/pkg/chplquerier/vendorquerier.go:143-164 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) endpointmanager/pkg/chplquerier/criteriaquerier.go:58— endpointmanager/pkg/chplquerier/criteriaquerier.go:58-71 | REDACTED:145-157 | endpointmanager/pkg/chplquerier/vendorquerier.go:76-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) endpointmanager/pkg/chplquerier/criteriaquerier.go:86— endpointmanager/pkg/chplquerier/criteriaquerier.go:86-103 | endpointmanager/pkg/chplquerier/criteriaquerier.go:106-123 | REDACTED:171-188 | endpointmanager/pkg/chplquerier/vendorquerier.go:100-117 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:122— endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:122-141 | endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:144-161 | endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:164-180 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) endpointmanager/pkg/chplendpointquerier/axeiumwebscraper.go:8— endpointmanager/pkg/chplendpointquerier/axeiumwebscraper.go:8-25 | endpointmanager/pkg/chplendpointquerier/interopwebscraper.go:9-22 — 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 (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:90— capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go:90-104 | capabilityreceiver/pkg/capabilityhandler/validation/stu3validation.go:58-70 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) endpointmanager/pkg/chplquerier/criteriaquerier.go:74— endpointmanager/pkg/chplquerier/criteriaquerier.go:74-83 | REDACTED:159-168 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:385— endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:385-401 | endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:223-239 — 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 (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) endpointmanager/pkg/endpointwebscraper/endpointwebscraper.go:10— endpointmanager/pkg/endpointwebscraper/endpointwebscraper.go:10-22 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:12-22 — 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 (86 lines × 2) REDACTED:291— REDACTED:291-376 | capabilityreceiver/cmd/migratevalidations/main.go:354-439 — `REDACTED` and `capabilityreceiver/cmd/migratevalidations/main.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 109 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:291` 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (59–61 lines × 4) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:116— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:116-174 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:265-325 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:415-475 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:705-765 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:116` 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 (47 lines × 2) endpointmanager/pkg/chplendpointquerier/csvparser.go:26— endpointmanager/pkg/chplendpointquerier/csvparser.go:26-72 | endpointmanager/pkg/chplendpointquerier/customcsvparser.go:24-70 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/csvparser.go` and `endpointmanager/pkg/chplendpointquerier/customcsvparser.go` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/csvparser.go:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (44 lines × 2) REDACTED:93— REDACTED:93-136 | REDACTED:178-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (41 lines × 2) capabilityreceiver/cmd/migratevalidations/main.go:138— capabilityreceiver/cmd/migratevalidations/main.go:138-178 | capabilityreceiver/cmd/migratevalidations/main.go:262-302 — 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 `capabilityreceiver/cmd/migratevalidations/main.go:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (38 lines × 3) endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:62— endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:62-99 | endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:122-159 | endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:209-246 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go:62` 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 (37 lines × 2) endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go:21— endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go:21-57 | endpointmanager/pkg/chplendpointquerier/patientpatternparser.go:21-57 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/patientpatternparser.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 85 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (33 lines × 2) endpointmanager/pkg/historycleanup/historycleanup.go:197— endpointmanager/pkg/historycleanup/historycleanup.go:197-229 | endpointmanager/pkg/historypruning/historypruning.go:208-240 — 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 (32 lines × 2) endpointmanager/pkg/historycleanup/historycleanup.go:107— endpointmanager/pkg/historycleanup/historycleanup.go:107-138 | endpointmanager/pkg/historypruning/historypruning.go:91-122 — 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 (27–29 lines × 3) endpointmanager/pkg/chplendpointquerier/athenaparser.go:26— endpointmanager/pkg/chplendpointquerier/athenaparser.go:26-54 | endpointmanager/pkg/chplendpointquerier/nextechparser.go:24-50 | endpointmanager/pkg/chplendpointquerier/streamlinemdparser.go:26-54 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenaparser.go` and `endpointmanager/pkg/chplendpointquerier/nextechparser.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenaparser.go:26` 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 (26 lines × 3) REDACTED:550— REDACTED:550-575 | endpointmanager/pkg/endpointwebscraper/endpointwebscraper.go:35-60 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:91-116 — `REDACTED` and `endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 48 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (36 lines × 2) endpointmanager/pkg/chplendpointquerier/trimedtechwebscraper.go:13— endpointmanager/pkg/chplendpointquerier/trimedtechwebscraper.go:13-48 | endpointmanager/pkg/chplendpointquerier/trimedtechwebscraperV8.go:13-48 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/trimedtechwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/trimedtechwebscraperV8.go` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (26 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:41— endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:41-66 | endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:94-119 — 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 `endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go:41` 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 (24–40 lines × 3) endpointmanager/pkg/chplendpointquerier/cernerBundleParser.go:13— endpointmanager/pkg/chplendpointquerier/cernerBundleParser.go:13-36 | endpointmanager/pkg/chplendpointquerier/epicquerier.go:15-38 | endpointmanager/pkg/chplendpointquerier/modernizingmedicineparser.go:15-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/cernerBundleParser.go:13` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 3) endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:35— endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:35-58 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:80-103 | endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:125-148 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go:35` 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 (24 lines × 2) endpointmanager/cmd/chplsharedlistsources/main.go:165— endpointmanager/cmd/chplsharedlistsources/main.go:165-188 | endpointmanager/cmd/chplsharedlistsources/main.go:216-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/cmd/chplsharedlistsources/main.go:165` 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 (22 lines × 2) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:515— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:515-536 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:577-598 — 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 `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointinfostore.go:515` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 3) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:57— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:57-77 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:269-288 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:409-429 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:57` 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 (21 lines × 2) endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:28— endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:28-48 | endpointmanager/pkg/chplendpointquerier/canvaswebscraper.go:28-48 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/canvaswebscraper.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:28` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 4) endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:24— endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:24-43 | endpointmanager/pkg/chplendpointquerier/medicscloudwebscraper.go:24-43 | endpointmanager/pkg/chplendpointquerier/medicsdaextapiwebscraper.go:22-41 | endpointmanager/pkg/chplendpointquerier/praxisemrwebscraper.go:24-43 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/medicscloudwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/medicsdaextapiwebscraper.go` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/mdlogicehrwebscraper.go:24` 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 (19 lines × 3) endpointmanager/pkg/chplendpointquerier/cignawebscraper.go:26— endpointmanager/pkg/chplendpointquerier/cignawebscraper.go:26-44 | endpointmanager/pkg/chplendpointquerier/escribehostwebscraper.go:30-49 | endpointmanager/pkg/chplendpointquerier/smartemrwebscraper.go:26-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/cignawebscraper.go:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:40— endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:40-56 | endpointmanager/pkg/chplendpointquerier/zoommdParser.go:42-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `endpointmanager/pkg/chplendpointquerier/zoommdParser.go:39` calls `TrimSpace` and `endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:38` 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–17 lines × 8) endpointmanager/pkg/chplendpointquerier/athenaparser.go:21— endpointmanager/pkg/chplendpointquerier/athenaparser.go:21-37 | endpointmanager/pkg/chplendpointquerier/netsmartparser.go:21-36 | endpointmanager/pkg/chplendpointquerier/nextechparser.go:19-34 | endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go:18-33 | endpointmanager/pkg/chplendpointquerier/patientpatternparser.go:18-33 | endpointmanager/pkg/chplendpointquerier/streamlinemdparser.go:21-37 | endpointmanager/pkg/chplendpointquerier/zoommdParser.go:21-37 | endpointmanager/pkg/medicaidendpointquerier/medicaidendpointquerier.go:30-44 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenaparser.go` and `endpointmanager/pkg/chplendpointquerier/netsmartparser.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenaparser.go:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `endpointmanager/pkg/chplendpointquerier/netsmartparser.go:38` calls `TrimSpace` and `endpointmanager/pkg/chplendpointquerier/athenaparser.go:40` 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 (16 lines × 6) endpointmanager/pkg/chplendpointquerier/athenaparser.go:41— endpointmanager/pkg/chplendpointquerier/athenaparser.go:41-57 | endpointmanager/pkg/chplendpointquerier/netsmartparser.go:42-57 | endpointmanager/pkg/chplendpointquerier/nextechparser.go:38-53 | endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go:43-58 | endpointmanager/pkg/chplendpointquerier/patientpatternparser.go:43-58 | endpointmanager/pkg/chplendpointquerier/streamlinemdparser.go:41-57 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenaparser.go` and `endpointmanager/pkg/chplendpointquerier/netsmartparser.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenaparser.go:41` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–16 lines × 5) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:58— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:58-72 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:224-239 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:270-283 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:316-330 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:410-424 — all 5 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 (14–15 lines × 4) endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:23— endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:23-36 | endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:24-38 | endpointmanager/pkg/chplendpointquerier/canvaswebscraper.go:24-38 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:23-36 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:23` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 8) endpointmanager/pkg/chplendpointquerier/athenaparser.go:20— endpointmanager/pkg/chplendpointquerier/athenaparser.go:20-33 | endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:20-33 | endpointmanager/pkg/chplendpointquerier/netsmartparser.go:20-33 | endpointmanager/pkg/chplendpointquerier/nextechparser.go:18-31 | endpointmanager/pkg/chplendpointquerier/novomedicwebscraper.go:17-30 | endpointmanager/pkg/chplendpointquerier/patientpatternparser.go:17-30 | endpointmanager/pkg/chplendpointquerier/streamlinemdparser.go:20-33 | endpointmanager/pkg/chplendpointquerier/zoommdParser.go:20-33 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenaparser.go` and `endpointmanager/pkg/chplendpointquerier/netsmartparser.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenaparser.go:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `endpointmanager/pkg/chplendpointquerier/landmarkhealthparser.go:35` calls `TrimSpace`, `Contains` and `endpointmanager/pkg/chplendpointquerier/athenaparser.go:35` 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 (14 lines × 3) endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:28— endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:28-41 | endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:25-38 | endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go:28-41 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:28` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 7) endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:27— endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:27-38 | endpointmanager/pkg/chplendpointquerier/cignawebscraper.go:23-34 | endpointmanager/pkg/chplendpointquerier/dssincwebscraper.go:24-35 | endpointmanager/pkg/chplendpointquerier/ethizowebscraper.go:26-38 | endpointmanager/pkg/chplendpointquerier/smartemrwebscraper.go:23-35 | endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go:27-38 | endpointmanager/pkg/chplendpointquerier/varianmedicalwebscraper.go:26-37 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/tenzingwebscraper.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/bridgepatientportalwebscraper.go:27` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 3) endpointmanager/pkg/chplendpointquerier/imedemrwebscraper.go:11— endpointmanager/pkg/chplendpointquerier/imedemrwebscraper.go:11-23 | endpointmanager/pkg/chplendpointquerier/magilenenterpriseswebscraper.go:13-25 | endpointmanager/pkg/chplendpointquerier/pcesystemswebscraper.go:13-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/imedemrwebscraper.go:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:94— endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:94-106 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:123-135 | endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:157-169 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:94` 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 (12–13 lines × 2) REDACTED:56— REDACTED:56-68 | REDACTED:15-26 — 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 `REDACTED:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:54` calls `getCapabilityStatementProfiles` and `REDACTED:12` 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 (11–12 lines × 5) endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:24— endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:24-34 | endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:25-35 | endpointmanager/pkg/chplendpointquerier/canvaswebscraper.go:25-35 | endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:25-36 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:24-34 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:13— endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:13-22 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:13-22 | endpointmanager/pkg/chplendpointquerier/zhhealthcarewebscraper.go:13-21 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:13` 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 (2–10 lines × 8) capabilityquerier/cmd/main.go:181— capabilityquerier/cmd/main.go:181-182 | capabilityreceiver/cmd/main.go:49-50 | REDACTED:269-278 | capabilityreceiver/cmd/migratevalidations/main.go:327-336 | endpointmanager/cmd/chplquerier/main.go:43-45 | endpointmanager/cmd/datavalidation/main.go:18-19 | endpointmanager/cmd/historycleanup/main.go:15-16 | endpointmanager/cmd/sendendpoints/main.go:17-18 — `REDACTED` and `capabilityreceiver/cmd/migratevalidations/main.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 109 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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, `capabilityquerier/cmd/main.go:182` calls `FailOnError` and `endpointmanager/cmd/chplquerier/main.go:45` 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) endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:17— endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:17-23 | endpointmanager/pkg/chplendpointquerier/hmsfirstwebscraper.go:17-23 | endpointmanager/pkg/chplendpointquerier/webchartnowwebscraper.go:17-23 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/hmsfirstwebscraper.go` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/betterdayhealthwebscraper.go:17` 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 (2–5 lines × 10) endpointmanager/pkg/chplendpointquerier/broadstreetwebscraper.go:21— endpointmanager/pkg/chplendpointquerier/broadstreetwebscraper.go:21-22 | endpointmanager/pkg/chplendpointquerier/elationwebscraper.go:17-22 | endpointmanager/pkg/chplendpointquerier/geniussolutionswebscraper.go:17-22 | endpointmanager/pkg/chplendpointquerier/intelichartwebscraper.go:22-23 | endpointmanager/pkg/chplendpointquerier/interopxparser.go:17-22 | endpointmanager/pkg/chplendpointquerier/kodjinwebscraper.go:16-21 | endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go:17-22 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:17-22 | endpointmanager/pkg/chplendpointquerier/triarqparser.go:17-22 | endpointmanager/pkg/chplendpointquerier/zhhealthcarewebscraper.go:17-21 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/medinfoengineeringwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/broadstreetwebscraper.go:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `endpointmanager/pkg/chplendpointquerier/broadstreetwebscraper.go:19` calls `Find`, `Each` and `endpointmanager/pkg/chplendpointquerier/intelichartwebscraper.go:19` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 5) endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:23— endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:23-27 | endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go:24-28 | endpointmanager/pkg/chplendpointquerier/canvaswebscraper.go:24-28 | endpointmanager/pkg/chplendpointquerier/meditechwebscraper.go:23-27 | endpointmanager/pkg/chplendpointquerier/triarqparser.go:23-27 — before extracting anything, compare `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go` and `endpointmanager/pkg/chplendpointquerier/canvasmedicalwebscraper.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:23` 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, `endpointmanager/pkg/chplendpointquerier/athenahealthwebscraper.go:28` calls `TrimSpace`, `Eq`, `Text` and `endpointmanager/pkg/chplendpointquerier/triarqparser.go:29` 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 (6 lines × 2) endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:23— endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:23-28 | endpointmanager/pkg/chplendpointquerier/medifusionwebscraper.go:21-26 — 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 `endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `endpointmanager/pkg/chplendpointquerier/maximuswebscraper.go:21` calls `Find`, `Length` and `endpointmanager/pkg/chplendpointquerier/medifusionwebscraper.go:19` 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 (11 lines × 3) endpointmanager/pkg/chplquerier/criteriaquerier.go:61— endpointmanager/pkg/chplquerier/criteriaquerier.go:61-71 | REDACTED:147-157 | endpointmanager/pkg/chplquerier/vendorquerier.go:78-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/chplquerier/criteriaquerier.go:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 5) endpointmanager/pkg/capabilityparser/base.go:116— endpointmanager/pkg/capabilityparser/base.go:116-124 | endpointmanager/pkg/capabilityparser/base.go:138-146 | endpointmanager/pkg/capabilityparser/base.go:187-195 | endpointmanager/pkg/capabilityparser/base.go:209-217 | endpointmanager/pkg/capabilityparser/base.go:231-239 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `endpointmanager/pkg/capabilityparser/base.go:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The 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 (2–5 lines × 4) endpointmanager/cmd/endpointpopulator/main.go:84— endpointmanager/cmd/endpointpopulator/main.go:84-85 | endpointmanager/cmd/historypruning/main.go:31-32 | endpointmanager/cmd/nppescontactpopulator/main.go:24-28 | endpointmanager/cmd/nppesorgpopulator/main.go:24-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `endpointmanager/cmd/nppesorgpopulator/main.go:24` calls `FailOnError` and `endpointmanager/cmd/endpointpopulator/main.go:84` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) endpointmanager/cmd/CHPLreport/main.go:14— endpointmanager/cmd/CHPLreport/main.go:14-18 | endpointmanager/cmd/endpointexporter/main.go:14-18 | endpointmanager/cmd/endpointlinker/main.go:20-24 — 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.
Low cohesion: Store (LCOM4 46) endpointmanager/pkg/endpointmanager/postgresql/store.go:17— Store's methods fall into 46 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 46 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.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
X27 · Collection changed while being enumerated· Collection is structurally changed while it is being enumerated · ×1
Collection is structurally changed while it is being enumerated endpointmanager/pkg/endpointmanager/postgresql/fhirendpointstore.go:489— `e.OrganizationList` is walked by the `for … range` at line 489, and line 498 appends to `e.OrganizationList`. A range evaluates its slice once and walks the length it had when the loop began, so the elements appended here are never visited by this loop — work queued for it is silently dropped.
Swallowed exception (empty catch) shinydashboard/lantern/www/js/lcp-optimizer.js:51— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Orphaned file endpointmanager/pkg/endpointlinker/endpointlinker.go: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 REDACTED: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 REDACTED: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 capabilityreceiver/pkg/capabilityhandler/validation/r4validation.go: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 endpointmanager/pkg/endpointmanager/postgresql/healthitproductstore.go: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 capabilityreceiver/cmd/migratevalidations/main.go: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 REDACTED: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 lanternmq/rabbitmq/messagequeue.go: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 capabilityreceiver/pkg/capabilityhandler/validation/base.go: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 endpointmanager/pkg/capabilityparser/base.go: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 endpointmanager/pkg/endpointmanager/postgresql/npiorganizationstore.go: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 endpointmanager/cmd/CHPLpopulator/main.go: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 REDACTED: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 capabilityquerier/cmd/main.go: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 endpointmanager/pkg/chplquerier/vendorquerier.go: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 endpointmanager/pkg/chplquerier/criteriaquerier.go: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 capabilityreceiver/pkg/capabilityhandler/validation/stu3validation.go: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 endpointmanager/pkg/endpointmanager/fhirendpointinfo.go: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 endpointmanager/pkg/endpointmanager/postgresql/vendorstore.go: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 endpointmanager/pkg/config/config.go: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 endpointmanager/pkg/endpointmanager/postgresql/npicontactstore.go: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 endpointmanager/pkg/endpointmanager/fhirendpoint.go: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 lanternmq/mock/messagequeue.go: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 lanternmq/lanternmq.go: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 endpointmanager/cmd/CHPLupdatecheck/main.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate endpointmanager/pkg/chplendpointquerier/bundleQuerierParser.go:124— `!strings.HasPrefix(trimmed, "{") && !strings.HasPrefix(trimmed, "[")` appears character-identically in 2 files — endpointmanager/pkg/chplendpointquerier/bundleQuerierParser.go, 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 endpointmanager/pkg/chplendpointquerier/trimedtechwebscraper.go:26— `exists && !strings.Contains(hrefText, "#")` appears character-identically in 2 files — endpointmanager/pkg/chplendpointquerier/trimedtechwebscraper.go, endpointmanager/pkg/chplendpointquerier/trimedtechwebscraperV8.go. 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 endpointmanager/pkg/chplendpointquerier/csvparser.go:63— `numrecords >= 0 && records >= numrecords+startrecord` appears character-identically in 2 files — endpointmanager/pkg/chplendpointquerier/csvparser.go, endpointmanager/pkg/chplendpointquerier/customcsvparser.go. 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 endpointmanager/pkg/chplendpointquerier/csvparser.go:32— `strings.HasPrefix(inputSource, "http://") || strings.HasPrefix(inputSource, "https://")` appears character-identically in 2 files — endpointmanager/pkg/chplendpointquerier/csvparser.go, endpointmanager/pkg/chplendpointquerier/customcsvparser.go. 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.
Interpolated log message defeats structured logging endpointmanager/cmd/datavalidation/main.go:44— `Warn` at line 44 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Warn("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Warn("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Warn("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
Interpolated log message defeats structured logging endpointmanager/cmd/CHPLupdatecheck/main.go:108— `Info` at line 108 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
Fat interface: CapabilityStatement (17 methods) endpointmanager/pkg/capabilityparser/factory.go:20— `CapabilityStatement` declares 17 methods: `GetPublisher`, `GetFHIRVersion`, `GetSoftware`, `GetSoftwareName`, `GetSoftwareVersion`, `GetCopyright`, `GetRest`, `GetResourceList`, `GetKind`, `GetImplementation`, `GetMessaging`, `GetMessagingEndpoint`, `GetDocument`, `GetDescription`, `Equal`, `EqualIgnore`, `GetJSON`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: REDACTED, capabilityreceiver/pkg/capabilityhandler/vendor_policy.go, capabilityreceiver/pkg/chplmapper/capabilityinfo.go. Pair on, review, or document these before any departure.
No ADRs found refresh.go:1— 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 `refresh.go` makes this repository a deployable product (line 1).
D21 · Naming Consistency· `ServiceBaseUrlList` spells `Url` where 263 names in the project spell it `URL` · ×1
`ServiceBaseUrlList` spells `Url` where 263 names in the project spell it `URL` endpointmanager/cmd/CHPLpopulator/main.go:62— 263 of 265 names in project github.com/onc-healthit/lantern-back-end/endpointmanager spell the token `URL` (263 of 265; unit: names in project github.com/onc-healthit/lantern-back-end/endpointmanager containing `URL`). Peers: softwareInfo.ListSourceURL (endpointmanager/cmd/CHPLpopulator/main.go:18); github.com/onc-healthit/lantern-back-end/endpointmanager/cmd/CHPLpopulator.serviceBaseURL (endpointmanager/cmd/CHPLpopulator/main.go:40); main.getEndpointListJSON(chplURL) (endpointmanager/cmd/CHPLpopulator/main.go:256); historyArgs.fhirURL (REDACTED:66); chplendpointquerier.AdvancedMdWebscraper(chplURL) (endpointmanager/pkg/chplendpointquerier/advancedmdwebscraper.go:11). Rename to `ServiceBaseURLList`. [rule N6]
D21 · Naming Consistency· `LogoUrl` spells `Url` where 263 names in the project spell it `URL` · ×1
`LogoUrl` spells `Url` where 263 names in the project spell it `URL` endpointmanager/pkg/chplendpointquerier/anthemparser.go:16— 263 of 265 names in project github.com/onc-healthit/lantern-back-end/endpointmanager spell the token `URL` (263 of 265; unit: names in project github.com/onc-healthit/lantern-back-end/endpointmanager containing `URL`). Peers: softwareInfo.ListSourceURL (endpointmanager/cmd/CHPLpopulator/main.go:18); github.com/onc-healthit/lantern-back-end/endpointmanager/cmd/CHPLpopulator.serviceBaseURL (endpointmanager/cmd/CHPLpopulator/main.go:40); main.getEndpointListJSON(chplURL) (endpointmanager/cmd/CHPLpopulator/main.go:256); historyArgs.fhirURL (REDACTED:66); chplendpointquerier.AdvancedMdWebscraper(chplURL) (endpointmanager/pkg/chplendpointquerier/advancedmdwebscraper.go:11). Rename to `LogoURL`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion REDACTED:1— `endpointmanager` (16252 LoC, 100 module-visible types across 44 directories) overshoots its size bounds. 1 of 6 build unit(s) (Go) overshoot their size bounds, lowering Project Cohesion to 6.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.
Concentrated knowledge decay — 44 of 69 significant files have no living knowledge, while the repository is still being changed at a low rate (28 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 44 separate risks. Counted over 69 of the 215 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
D34 · Knowledge Freshness· Most significant orphaned file · ×1
Most significant orphaned file endpointmanager/pkg/nppesquerier/populatenpiorgs.go:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No dependency-update automation REDACTED:5— `REDACTED` 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`.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
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.)
No security response headers detected shinydashboard/shiny-server.conf:8— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `shiny-server.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all functions that make a request accept a context.Context · ×1
Not all functions that make a request accept a context.Context — Only 4/11 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Outdated: github.com/PuerkitoBio/goquery — `github.com/PuerkitoBio/goquery` is required at v1.8.0 in REDACTED, but v1.14.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/PuerkitoBio/goquery@v1.14.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/PuerkitoBio/goquery — `github.com/PuerkitoBio/goquery` is required at v1.8.0 in REDACTED, but v1.14.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/PuerkitoBio/goquery@v1.14.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/chromedp/chromedp — `github.com/chromedp/chromedp` is required at v0.8.6 in REDACTED, but v0.23.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/chromedp/chromedp@v0.23.1 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/chromedp/chromedp — `github.com/chromedp/chromedp` is required at v0.7.8 in REDACTED, but v0.23.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/chromedp/chromedp@v0.23.1 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/golang-migrate/migrate/v4 — `github.com/golang-migrate/migrate/v4` is required at v4.15.1 in REDACTED, but v4.20.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/golang-migrate/migrate/v4@v4.20.1 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/google/go-cmp — `github.com/google/go-cmp` is required at v0.5.7 in REDACTED, but v0.7.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/google/go-cmp@v0.7.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/lib/pq — `github.com/lib/pq` is required at v1.10.4 in REDACTED, but v1.12.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/lib/pq@v1.12.3 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/lib/pq — `github.com/lib/pq` is required at v1.3.0 in REDACTED, but v1.12.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/lib/pq@v1.12.3 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/lib/pq — `github.com/lib/pq` is required at v1.3.0 in REDACTED, but v1.12.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/lib/pq@v1.12.3 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/sirupsen/logrus — `github.com/sirupsen/logrus` is required at v1.8.1 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/sirupsen/logrus@v1.10.2 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/sirupsen/logrus — `github.com/sirupsen/logrus` is required at v1.8.1 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/sirupsen/logrus@v1.10.2 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/sirupsen/logrus — `github.com/sirupsen/logrus` is required at v1.8.1 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/sirupsen/logrus@v1.10.2 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/sirupsen/logrus — `github.com/sirupsen/logrus` is required at v1.8.1 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/sirupsen/logrus@v1.10.2 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.10.1 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.10.1 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.10.1 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.10.1 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/spf13/viper — `github.com/spf13/viper` is required at v1.10.1 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/viper@v1.21.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: github.com/xuri/excelize/v2 — `github.com/xuri/excelize/v2` is required at v2.4.1 in REDACTED, but v2.11.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/xuri/excelize/v2@v2.11.1 && go mod tidy` and commit the updated REDACTED and REDACTED.
Outdated: gonum.org/v1/gonum — `gonum.org/v1/gonum` is required at v0.12.0 in REDACTED, but v0.17.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get gonum.org/v1/gonum@v0.17.0 && go mod tidy` and commit the updated REDACTED and REDACTED.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e6a3-1e05-7100-abb1-d91a33d7e447 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 54 · Warnings: 578 · Recommendations: 79 · Info: 20 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 23:13 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.