Public report of michaeldcanady/servicenow-sdk-go, 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, 20:39 UTC · Survey ID cd_c29b2d8cda0d4e97ba08cb474ccc1c2d
michaeldcanady/servicenow-sdk-go
Measured 16 November 2026, 20:38 UTC, at code version d59c450
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 32,223 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Accessibility, 29.1
Findings by how serious they are
3 critical338 serious23 minor
15 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, 20:38 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
52of 52 dimensions measured by tools.
357of 364 findings point to an exact file and line, so you can open each one in the code. The other 7 concern the repository as a whole, such as missing documentation.
52dimensions across 6 lenses, read from 32,223 lines of product code in 2 projects.
michaeldcanady/servicenow-sdk-go falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 58.6 out of 100 and is rated Adequate, and one of its three critical findings is a leaked password or key.
Accessibility, at 29.1, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 9.4 points. Fixing focus, motion and contrast comes next, worth about 7.0 points. Raising Accessibility to 70 would lift the score to about 77.5.
One password or key is open to anyone who can read the repository. One control can't be used without a mouse, and one form field can't be read by a screen reader. Making the controls work with a keyboard, replacing the exposed password or key and labelling the form fields would close these risks.
The product code is 32,223 lines, about €83,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 29.1 to 70, the lowest score rated Strong, the score would rise from 58.6 to about 77.5.
Code composition: what the lines of code are
Product code 41%Tests 59%
Rebuild cost: about €83,000 · Estimate
Cost to rebuild
€28,000 to €140,000, for 460 to 1,459 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 32,223 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
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 9.4 points · Medium effort · Keyboard semantics
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 2.0 points · Low effort · Secret Scanning
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €83,000 to build again, about 0.6 person-years of work. Its weakest lens is Accessibility, at 29.1 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 9.4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 113,677 lines over the last 90 days, which is about 461,023 lines a year. At that pace, the extra work comes to an estimated 23.1 to 153.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
42 modules, with 49 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 2 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 github.com/michaeldcanady/servicenow-sdk-go/v2/core uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal.
github.com/michaeldcanady/servicenow-sdk-go/v2/core uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal can break github.com/michaeldcanady/servicenow-sdk-go/v2/core, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/core uses a module listed above it, which is the healthy direction.
19→31 github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/credentialspart of a loop✕
Connections
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/credentials.
github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/credentials, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/credentials can break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/credentials.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/conversion.
github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/conversion, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/conversion can break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/conversion.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization uses a module listed above it, which is the healthy direction.
8 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/query uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/ast.
github.com/michaeldcanady/servicenow-sdk-go/v2/query uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/ast, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/ast can break github.com/michaeldcanady/servicenow-sdk-go/v2/query, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/query can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/ast.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/query uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization.
github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization can break github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/serialization.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi uses a module listed above it, which is the healthy direction.
13 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi uses a module listed above it, which is the healthy direction.
26→35 github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/batchapipart of a loop✕
Connections
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi uses a module listed above it, which is the healthy direction.
25 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi uses a module listed above it, which is the healthy direction.
14 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/credentials uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2/pkce.
github.com/michaeldcanady/servicenow-sdk-go/v2/credentials uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2/pkce, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2/pkce can break github.com/michaeldcanady/servicenow-sdk-go/v2/credentials, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/credentials can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2/pkce.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/credentials uses a module listed above it, which is the healthy direction.
11 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/credentials uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2.
github.com/michaeldcanady/servicenow-sdk-go/v2/credentials uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2 can break github.com/michaeldcanady/servicenow-sdk-go/v2/credentials, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/credentials can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/oauth2.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/credentials uses a module listed above it, which is the healthy direction.
24 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http.
github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http can break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi uses a module listed above it, which is the healthy direction.
14 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi can't break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/core.
github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking can't break github.com/michaeldcanady/servicenow-sdk-go/v2/appserviceapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking can't break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/internal/mocking uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2/website/snippets uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
github.com/michaeldcanady/servicenow-sdk-go/v2/website/snippets uses github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can break github.com/michaeldcanady/servicenow-sdk-go/v2/website/snippets, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2/website/snippets can't break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2/website/snippets uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/internal/http.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/core, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/core can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/core.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/accountapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/activitysubscriptionsapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/aggregationapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/appointmentbookingapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/attachmentapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/cdmapplicationsapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/cdmchangesetapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/cdmeditorapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/documentsapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/policyapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/tableapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/batchapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/michaeldcanady/servicenow-sdk-go/v2 uses a type in github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/cmdbinstanceapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
github.com/michaeldcanady/servicenow-sdk-go/v2 uses github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi, so a change to github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi can break github.com/michaeldcanady/servicenow-sdk-go/v2, while a change to github.com/michaeldcanady/servicenow-sdk-go/v2 can't break github.com/michaeldcanady/servicenow-sdk-go/v2/caseapi.
Position
Below the diagonal: github.com/michaeldcanady/servicenow-sdk-go/v2 uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 81.3 · Adequate · gated by 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
3
Medium
A03:2025 — Software Supply Chain Failures
3
Medium
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
God Classes: TooManyMethods: MockSerializationWriter
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 3
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 — 338
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 — 23
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 52 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, 357 of 364 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.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Go module dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (7 contributor(s) across 1415 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 6 hold 0.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — 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. 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.
D25 ADR Conformance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The code index reads C#, Razor, TypeScript, JavaScript and Vue. A rule whose scope holds production code in another language is not called honoured, because its uses could sit in that code.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `appserviceapi/convert_to_dynamic_service_request_builder.go`, `appserviceapi/convert_to_manual_service_request_builder.go`, `appserviceapi/create_dynamic_service_request_builder.go`, `appserviceapi/create_request_builder.go`, `appserviceapi/create_service_response.go`, … (+15 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 330 commits in the last 90 days, yet 169 of 192 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
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 DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
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 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 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 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
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.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with quick_validate.validate_agent (cyclomatic 30), run_loop.run_loop (cyclomatic 28), improve_description.improve_description (cyclomatic 23). — 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 11 together lifts Cyclomatic Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 14 bodies over 15 down to 15 or less in Cognitive Complexity — start with aggregate_benchmark.load_run_results (cognitive 58), run_loop.run_loop (cognitive 55), generate_review.build_run (cognitive 44). — 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 14 together lifts Cognitive Complexity from 7.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.1 / 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 11 TooManyMethods finding(s) in God Classes — start with account.go, case_result.go, attachment.go. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 FunctionTooLong finding(s) in God Classes — start with attachments.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with reference_actions.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.
Do you agree with this assessment?
D4 · Code Duplication3.0 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
91 duplicated block group(s) detected. 17.4 % of the production lines (5,611 of 32,223) are in a reported copy. A further 82 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (13 corresponding lines) · ×7documentsapi/delete_request_builder.go:53
+ 109 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with reference_actions.go (2), delete_request_builder.go, external_oidc_client.go. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with attachment_item_request_builder.go, attachment_request_builder.go, deployables_request_builder.go. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with attachment_item_file_request_builder.go, attachment_upload_request_builder.go, attachments_delete_aging.go. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
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 86.9% — 26 file(s) below 50%. Measured from the Go suite (github.com/michaeldcanady/servicenow-sdk-go/v2: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made; github.com/michaeldcanady/servicenow-sdk-go/v2/tests/integration/v2: `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 26 Low coverage finding(s) in Code Coverage — start with user_window_request.go, user_window_response.go, activities_result_entry.go. — One of this dimension's main actionable groups (26 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.
5 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). 10 of 10 direct requirement(s) were graded against proxy.golang.org (0 not served there, 1 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 go.sum there.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 22 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. ★ COVERAGE OF THIS VERDICT: it grades this repository's Go module dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
85 deducted task-comment markers across 32223 LoC (0.2/KLoC) → score 9.5. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment · ×72servicenow_service_client.go:83
TodoComment repeated across 11 filescaseapi/case_activities_request_builder.go:76
What to do
Resolve the 72 TodoComment finding(s) in Explicit Debt — start with service_config.go (9), availability_request.go (7), appointment_request.go (6). — One of this dimension's main actionable groups (72 warning-level).
Resolve the 1 TodoComment repeated across 11 files finding(s) in Explicit Debt — start with case_activities_request_builder.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
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.
0 of 21 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
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.
7 naming inconsistencies among 420 declarations measured against a convention their peers follow.
`rawUrl` spells `Url` where 208 names in the project spell it `URL` · ×2accountapi/account_item_request_builder.go:34
`getContentUrlKey` spells `Url` where 208 names in the project spell it `URL`appserviceapi/create_service_result.go:90
`userSysIdKey` spells `Id` where 272 names in the project spell it `ID`caseapi/activities_result_entry.go:24
`SubscribeWithId` spells `Id` where 272 names in the project spell it `ID`REDACTED:55
`SetBaseUrl` spells `Url` where 208 names in the project spell it `URL`internal/mocking/mock_request_adapter.go:97
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 `rawUrl` spells `Url` where 208 names in the project spell it `URL` finding(s) in Naming Consistency — start with account_item_request_builder.go, account_request_builder.go. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `getContentUrlKey` spells `Url` where 208 names in the project spell it… finding(s) in Naming Consistency — start with create_service_result.go. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `userSysIdKey` spells `Id` where 272 names in the project spell it `ID` finding(s) in Naming Consistency — start with activities_result_entry.go. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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 603 exposed members measured against a convention their peers follow.
`ServiceRelationship.GetFieldDeserializers` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`)appserviceapi/service_relationships.go:42
What to do
Resolve the 1 `ServiceRelationship.GetFieldDeserializers` returns a map (`map[K]V`)… finding(s) in Internal API Consistency — start with service_relationships.go. — 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.
1 of 2 build units (Go, npm) flagged as possibly oversized/incoherent.
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.
87 % of calls cross a namespace and 11 % go through an interface, but 91 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
3 finding(s): 0 critical, 0 high, 3 medium, 0 low. semgrep hit a parse error in 20 file(s) — `appserviceapi/convert_to_dynamic_service_request_builder.go` (lines 19–20, line 21, line 24), `appserviceapi/convert_to_manual_service_request_builder.go` (lines 19–20, line 21, line 24), `appserviceapi/create_dynamic_service_request_builder.go` (lines 19–20, line 21, line 24), `appserviceapi/create_request_builder.go` (lines 19–20, line 21, line 24), `appserviceapi/create_service_response.go` (lines 12–13, line 14, line 17), … (+15 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Build pipeline generates provenance, signs artifacts and produces an SBOM.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 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 & labels5.3 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — .agents/skills/subagent-creator/eval-viewer/viewer.html:604
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — .agents/skills/subagent-creator/assets/eval_review.html:2, .agents/skills/subagent-creator/eval-viewer/viewer.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
The repo's own CSS styles .summary with `cursor: pointer`, so this <p> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — .agents/skills/subagent-creator/assets/eval_review.html:60
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
`.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/assets/eval_review.html:17
`.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/assets/eval_review.html:19
`.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .agents/skills/subagent-creator/eval-viewer/viewer.html:275
`.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:83
`.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:136
`.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:197
`.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:221
`.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:302
`.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:303
`.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/subagent-creator/eval-viewer/viewer.html:467
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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.
`AppointmentRequest` declares 26 methods: `GetActualEndDate`, `SetActualEndDate`, `GetActualStartDate`, `SetActualStartDate`, `GetCatalogID`, `SetCatalogID`, `GetEndDateUTC`, `SetEndDateUTC`, `GetLocation`, `SetLocation`, `GetOpenedFor`, `SetOpenedFor`, `GetReschedule`, `SetReschedule`, `GetServiceConfigRule`, `SetServiceConfigRule`, `GetStartDateUTC`, `SetStartDateUTC`, `GetTaskID`, `SetTaskID`, `GetTaskTable`, `SetTaskTable`, `GetTimezone`, `SetTimezone`, `GetValidateRequest`, `SetValidateRequest`. 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. — appointmentbookingapi/appointment_request.go:17
`AvailabilityRequest` declares 30 methods: `GetCatalogID`, `SetCatalogID`, `GetEndDate`, `SetEndDate`, `GetFetchDaysSlot`, `SetFetchDaysSlot`, `GetFullDay`, `SetFullDay`, `GetGetNextAvailableSlot`, `SetGetNextAvailableSlot`, `GetLimit`, `SetLimit`, `GetLocation`, `SetLocation`, `GetOpenedFor`, `SetOpenedFor`, `GetOtherInputs`, `SetOtherInputs`, `GetServiceConfigRule`, `SetServiceConfigRule`, `GetStartDate`, `SetStartDate`, `GetTaskID`, `SetTaskID`, `GetTaskTable`, `SetTaskTable`, `GetUseReadReplica`, `SetUseReadReplica`, `GetView`, `SetView`. 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. — appointmentbookingapi/availability_request.go:17
`ServiceConfig` declares 30 methods: `GetActive`, `SetActive`, `GetActiveString`, `SetActiveString`, `GetAppointmentBookingConfig`, `SetAppointmentBookingConfig`, `GetAppointmentDuration`, `SetAppointmentDuration`, `GetAppointmentsPerBookableSlot`, `SetAppointmentsPerBookableSlot`, `GetBookableDays`, `SetBookableDays`, `GetCancelByTime`, `SetCancelByTime`, `GetDefaultTimezone`, `SetDefaultTimezone`, `GetEnableAdvancedConfig`, `SetEnableAdvancedConfig`, `GetFieldMapping`, `SetFieldMapping`, `GetFutureBookableMaxDays`, `SetFutureBookableMaxDays`, `GetLeadTime`, `SetLeadTime`, `GetMandatory`, `SetMandatory`, `GetUseSlotEndTimeAs`, `SetUseSlotEndTimeAs`, `GetWorkDuration`, `SetWorkDuration`. 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. — appointmentbookingapi/service_config.go:16
`ActivitiesResultEntry` declares 24 methods: `GetAttachment`, `SetAttachment`, `GetContainsCode`, `SetContainsCode`, `GetElement`, `SetElement`, `GetFieldLabel`, `SetFieldLabel`, `GetInitials`, `SetInitials`, `GetLoginName`, `SetLoginName`, `GetName`, `SetName`, `GetSysCreatedOn`, `SetSysCreatedOn`, `GetSysCreatedOnAdjusted`, `SetSysCreatedOnAdjusted`, `GetSysID`, `SetSysID`, `GetUserSysID`, `SetUserSysID`, `GetValue`, `SetValue`. 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. — caseapi/activities_result_entry.go:30
`ActivitiesResultEntryAttachment` declares 24 methods: `GetAverageImageColor`, `SetAverageImageColor`, `GetContentType`, `SetContentType`, `GetFileName`, `SetFileName`, `GetImageHeight`, `SetImageHeight`, `GetImagePath`, `SetImagePath`, `GetImageWidth`, `SetImageWidth`, `GetPath`, `SetPath`, `GetSize`, `SetSize`, `GetSizeBytes`, `SetSizeBytes`, `GetState`, `SetState`, `GetSysID`, `SetSysID`, `GetThumbnailPath`, `SetThumbnailPath`. 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. — caseapi/activities_result_entry_attachment.go:30
`CaseResult` declares 64 methods: `GetAccount`, `SetAccount`, `GetActive`, `SetActive`, `GetActiveAccountEscalation`, `SetActiveAccountEscalation`, `GetActiveEscalation`, `SetActiveEscalation`, `GetActivityDue`, `SetActivityDue`, `GetAdditionalAssigneeList`, `SetAdditionalAssigneeList`, `GetApproval`, `SetApproval`, `GetApprovalHistory`, `SetApprovalHistory`, `GetApprovalSet`, `SetApprovalSet`, `GetAsset`, `SetAsset`, `GetAssignedTo`, `SetAssignedTo`, `GetAssignmentGroup`, `SetAssignmentGroup`, `GetBusinessDuration`, `SetBusinessDuration`, `GetBusinessImpact`, `SetBusinessImpact`, `GetBusinessService`, `SetBusinessService`, `GetCase`, `SetCase`, `GetCaseReport`, `SetCaseReport`, `GetCategory`, `SetCategory`, `GetCause`, `SetCause`, `GetCausedBy`, `SetCausedBy`, and 24 more. 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. — caseapi/case_result.go:41
`PoliciesMappingable` declares 36 methods: `GetDescription`, `SetDescription`, `GetDocument`, `SetDocument`, `GetDocumentRef`, `SetDocumentRef`, `GetError`, `SetError`, `GetException`, `SetException`, `GetExceptionAllowed`, `SetExceptionAllowed`, `GetInputStatus`, `SetInputStatus`, `GetLastUpdatedBy`, `SetLastUpdatedBy`, `GetNumber`, `SetNumber`, `GetPolicy`, `SetPolicy`, `GetReason`, `SetReason`, `GetState`, `SetState`, `GetSysClassName`, `SetSysClassName`, `GetSysCreatedBy`, `SetSysCreatedBy`, `GetSysCreatedOn`, `SetSysCreatedOn`, `GetSysID`, `SetSysID`, `GetSysUpdatedBy`, `SetSysUpdatedBy`, `GetSysUpdatedOn`, `SetSysUpdatedOn`. 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. — policyapi/policies_mappings.go:17
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether 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 behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
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.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — 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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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.
`body, _ := io.ReadAll(res.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `io.ReadAll` fails, `body` 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 `body` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×4) — internal/oauth2/client.go:140, internal/oauth2/client.go:256, internal/oauth2/client.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. (×3) — credentials/base_access_token_provider.go:170, batchapi/batch_response.go:125, batchapi/shared.go:73
`response, ok := rawResponse.(ServiceNowCollectionResponse[T])` failed on this branch, so `response` is the zero value of `ServiceNowCollectionResponse[T]` here, and that is what is reported: the value that did not fit is lost. Report `rawResponse` itself (and `%T` of it) instead. — core/page_iterator.go:334
`mainErr, _ := exc.GetError()` writes the call's error to `_` and then uses `mainErr` as if the call succeeded. When `exc.GetError` fails, `mainErr` 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 `mainErr` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — core/service_now_error.go:146
What to do
Discarded error (assigned to `_`, then its result used)
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~1.4 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 727 source line(s) of the 10 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: website/src/components/GoSnippet/region.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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.
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.
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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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 — ~46727 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.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go source were not judged.
D25 ADR Conformance — 1 binding ADR(s) rule out an element in code we do not index (.go); their rules were neither confirmed nor broken.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 20 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
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.
D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
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
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P2 Observability — This repository's Go, JavaScript/TypeScript source (2 module(s), 533 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 364 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.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 (31,542 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not 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
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 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
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 3 finding(s)
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label .agents/skills/subagent-creator/eval-viewer/viewer.html:604— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×1
Clickable element isn't keyboard-operable .agents/skills/subagent-creator/assets/eval_review.html:60— The repo's own CSS styles .summary with `cursor: pointer`, so this <p> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
TodoComment servicenow_service_client.go:83— // TODO: sentinel-ize this error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tableapi/record_element_test.go:46— // TODO: improve test table design — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tableapi/record_element_test.go:164— // TODO: improve test table design — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/service_now_error_test.go:280— // TODO: improve test table design — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tableapi/table_request_builder_test.go:211— // TODO: fix test table design — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment credentials/auth_options_test.go:152— // TODO: should be a Mock token store — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment credentials/authority_test.go:37— // TODO: only tests happy path, should also test invalid authority strings (e.g., empty, missing https, etc.) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment credentials/authorization_code_credential_test.go:18— // TODO: should be a Mock.mock — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cdmapplicationsapi/deployables_request_builder_delete_query_parameters.go:8— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cdmapplicationsapi/deployables_request_builder_put_query_parameters.go:8— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appserviceapi/basic_details.go:60— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/appointment_request.go:49— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/appointment_request.go:52— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/availability_request.go:34— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/availability_request.go:37— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/availability_request.go:45— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/availability_request.go:50— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/availability_request.go:55— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/calendar_request_builder_get_query_parameters.go:8— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/calendar_request_builder_get_query_parameters.go:11— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/calendar_request_builder_get_query_parameters.go:14— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/configuration_request_builder_get_query_parameters.go:8— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment appointmentbookingapi/execute_rule_conditions.go:21— // TODO: required — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caseapi/activities_result_entry_attachment.go:49— // TODO: is a url http.url — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caseapi/activities_result_entry_attachment.go:58— // TODO: is a url http.url — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TooManyMethods: Account accountapi/account.go:73— TooManyMethods — 106 methods. The bar is 30 methods; this is 76 over it, 3.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CaseResultModel caseapi/case_result.go:210— TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.63× the bar. Most of these members implement caseapi.CaseResult (64 of 79 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: Attachment attachmentapi/attachment.go:43— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: File attachmentapi/file.go:71— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. Most of these members implement attachmentapi.file (42 of 44 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: MockFile internal/mocking/mock_file.go:15— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MockSerializationWriter internal/mocking/mock_serialization_writer.go:14— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PoliciesMapping policyapi/policies_mappings.go:59— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. Most of these members implement policyapi.PoliciesMappingable (36 of 38 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: ImpactedDeployableBySysIDResult cdmchangesetapi/impacted_deployable_by_sys_id_result.go:15— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AvailabilityRequestModel appointmentbookingapi/availability_request.go:61— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. Most of these members implement appointmentbookingapi.AvailabilityRequest (30 of 32 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: ServiceConfigModel appointmentbookingapi/service_config.go:53— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. Most of these members implement appointmentbookingapi.ServiceConfig (30 of 32 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: ImpactedDeployableResult cdmchangesetapi/impacted_deployable_result.go:15— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×7
Edited copy of a member (13 corresponding lines) documentsapi/delete_request_builder.go:53— documentsapi/delete_request_builder.go:53-65 | documentsapi/explore_request_builder.go:68-80 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) website/snippets/reference_actions.go:634— website/snippets/reference_actions.go:634-646 | website/snippets/reference_actions.go:648-660 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) credentials/external_oidc_client.go:81— credentials/external_oidc_client.go:81-93 | credentials/external_oidc_client.go:97-109 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) internal/serialization/deserializer_func.go:97— internal/serialization/deserializer_func.go:97-109 | internal/serialization/deserializer_func.go:112-124 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) website/snippets/reference_actions.go:592— website/snippets/reference_actions.go:592-604 | website/snippets/reference_actions.go:606-618 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) query/query.go:54— query/query.go:54-66 | query/query.go:72-84 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) credentials/client_credentials_credential.go:14— credentials/client_credentials_credential.go:14-26 | credentials/ropc_credential.go:14-27 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) attachmentapi/attachment_item_request_builder.go:126— attachmentapi/attachment_item_request_builder.go:126-136 | tableapi/table_item_request_builder.go:212-222 — before extracting anything, compare `attachmentapi/attachment_item_request_builder.go` and `tableapi/table_item_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) attachmentapi/attachment_request_builder.go:99— attachmentapi/attachment_request_builder.go:99-109 | tableapi/table_request_builder.go:90-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) cdmapplicationsapi/deployables_request_builder.go:60— cdmapplicationsapi/deployables_request_builder.go:60-70 | cdmapplicationsapi/shared_components_request_builder.go:59-69 — before extracting anything, compare `cdmapplicationsapi/deployables_request_builder.go` and `cdmapplicationsapi/shared_components_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) documentsapi/delete_request_builder.go:55— documentsapi/delete_request_builder.go:55-65 | documentsapi/explore_request_builder.go:70-80 — 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 `documentsapi/delete_request_builder.go:55` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) website/snippets/account_guide.go:41— website/snippets/account_guide.go:41-51 | website/snippets/cmdb_guide.go:41-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `website/snippets/account_guide.go:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) internal/http/servicenow_client_config.go:19— internal/http/servicenow_client_config.go:19-31 | internal/http/servicenow_request_adapter_config.go:26-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×5
Discarded error (assigned to `_`, then its result used) internal/oauth2/client.go:140— `body, _ := io.ReadAll(res.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `io.ReadAll` fails, `body` 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 `body` (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) internal/oauth2/client.go:256— `body, _ := io.ReadAll(res.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `io.ReadAll` fails, `body` 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 `body` (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) internal/oauth2/client.go:307— `body, _ := io.ReadAll(res.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `io.ReadAll` fails, `body` 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 `body` (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) internal/oauth2/client.go:344— `body, _ := io.ReadAll(res.Body)` writes the call's error to `_` and then uses `body` as if the call succeeded. When `io.ReadAll` fails, `body` 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 `body` (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) core/service_now_error.go:146— `mainErr, _ := exc.GetError()` writes the call's error to `_` and then uses `mainErr` as if the call succeeded. When `exc.GetError` fails, `mainErr` 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 `mainErr` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) attachmentapi/attachment_item_file_request_builder.go:124— attachmentapi/attachment_item_file_request_builder.go:124-136 | documentsapi/content_request_builder.go:69-78 | documentsapi/document_get_request_builder.go:75-88 | documentsapi/versions_request_builder.go:68-77 — 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) attachmentapi/attachment_upload_request_builder.go:49— attachmentapi/attachment_upload_request_builder.go:49-112 | tableapi/table_item_request_builder.go:123-157 | tableapi/table_item_request_builder.go:160-194 | tableapi/table_request_builder.go:121-155 — 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) website/snippets/attachments_delete_aging.go:23— website/snippets/attachments_delete_aging.go:23-100 | website/snippets/attachments_download.go:24-111 | website/snippets/attachments_recent.go:21-82 | website/snippets/attachments_upload.go:22-84 — 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) website/snippets/cdm_applications_guide.go:20— website/snippets/cdm_applications_guide.go:20-50 | website/snippets/cdm_changesets_guide.go:20-55 | website/snippets/cdm_editor_guide.go:20-50 | website/snippets/policy_guide.go:20-53 — 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 (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) policyapi/policies_mappings_request_builder.go:129— policyapi/policies_mappings_request_builder.go:129-140 | policyapi/policies_mappings_request_builder.go:143-154 — 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) appointmentbookingapi/execute_rule_conditions_result.go:30— appointmentbookingapi/execute_rule_conditions_result.go:30-41 | caseapi/activities_result_field.go:70-81 — 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) internal/store/backed_model_accessor.go:21— internal/store/backed_model_accessor.go:21-34 | internal/store/backed_model_mutator.go:18-29 — 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) internal/option.go:12— internal/option.go:12-25 | internal/serialization/serializer_func.go:18-29 — 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 (10 lines × 2) appserviceapi/app_service_action_result.go:33— appserviceapi/app_service_action_result.go:33-42 | appserviceapi/app_service_action_result.go:127-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) batchapi/rest_request.go:141— batchapi/rest_request.go:141-150 | batchapi/serviced_request_model.go:73-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `batchapi/rest_request.go:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) cdmapplicationsapi/export_item_status_request_builder.go:72— cdmapplicationsapi/export_item_status_request_builder.go:72-81 | cdmapplicationsapi/upload_status_item_request_builder.go:70-79 — before extracting anything, compare `cdmapplicationsapi/export_item_status_request_builder.go` and `cdmapplicationsapi/upload_status_item_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 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 `cdmapplicationsapi/export_item_status_request_builder.go:72` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) website/snippets/query_guide.go:44— website/snippets/query_guide.go:44-53 | website/snippets/tables_query.go:41-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `website/snippets/query_guide.go:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low contrast colour pair in CSS (2.1:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:83— `.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.1:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:136— `.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.1:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:221— `.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) attachmentapi/attachment_request_builder.go:86— attachmentapi/attachment_request_builder.go:86-127 | attachmentapi/attachment_request_builder.go:130-158 | batchapi/batch_request_builder.go:51-80 | tableapi/table_request_builder.go:77-118 | tableapi/table_request_builder.go:165-193 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) website/snippets/account_guide.go:20— website/snippets/account_guide.go:20-56 | website/snippets/appointment_guide.go:20-54 | website/snippets/appservice_guide.go:20-42 | website/snippets/cmdb_guide.go:20-56 | website/snippets/pagination_guide.go:22-61 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) website/snippets/auth.go:79— website/snippets/auth.go:79-103 | website/snippets/auth.go:105-127 | website/snippets/auth.go:129-151 | website/snippets/auth.go:153-174 | website/snippets/auth.go:225-252 — 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 (31 corresponding lines) · ×3
Edited copy of a member (31 corresponding lines) cmdbinstanceapi/cmdb_class_request_builder.go:71— cmdbinstanceapi/cmdb_class_request_builder.go:71-101 | cmdbinstanceapi/cmdb_relation_request_builder.go:39-69 — 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.
Edited copy of a member (31 corresponding lines) documentsapi/explore_request_builder.go:35— documentsapi/explore_request_builder.go:35-65 | documentsapi/versions_request_builder.go:35-65 — 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.
Edited copy of a member (31 corresponding lines) aggregationapi/stats_request_builder.go:54— aggregationapi/stats_request_builder.go:54-88 | attachmentapi/attachment_item_request_builder.go:59-89 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) appointmentbookingapi/appointment_request.go:75— appointmentbookingapi/appointment_request.go:75-94 | appointmentbookingapi/availability_request.go:76-97 — 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) cdmchangesetapi/changeset_request_builders.go:118— cdmchangesetapi/changeset_request_builders.go:118-138 | cdmeditorapi/editor_request_builders.go:197-216 — 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) website/snippets/concepts.go:26— website/snippets/concepts.go:26-56 | website/snippets/modules.go:389-408 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×3
Edited copies of one member (3 members, 13+ corresponding lines) website/snippets/reference_actions.go:303— website/snippets/reference_actions.go:303-315 | website/snippets/reference_actions.go:343-355 | website/snippets/reference_actions.go:357-369 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) internal/ast/stringer.go:27— internal/ast/stringer.go:27-39 | internal/ast/stringer.go:41-56 | internal/ast/stringer.go:58-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) appserviceapi/cmdb_group_based_population_method.go:62— appserviceapi/cmdb_group_based_population_method.go:62-74 | appserviceapi/discovery_population_method.go:51-64 | appserviceapi/tag_list_population_method.go:52-64 — 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.
Duplicated block (14 lines × 2) cdmapplicationsapi/deployables_request_builder.go:43— cdmapplicationsapi/deployables_request_builder.go:43-56 | cdmapplicationsapi/shared_components_request_builder.go:42-55 — before extracting anything, compare `cdmapplicationsapi/deployables_request_builder.go` and `cdmapplicationsapi/shared_components_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) cdmapplicationsapi/deployables_request_builder.go:104— cdmapplicationsapi/deployables_request_builder.go:104-117 | cdmapplicationsapi/shared_components_request_builder.go:87-100 — before extracting anything, compare `cdmapplicationsapi/deployables_request_builder.go` and `cdmapplicationsapi/shared_components_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) website/snippets/tables.go:134— website/snippets/tables.go:134-147 | website/snippets/tables.go:158-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) attachmentapi/attachment_item_file_request_builder.go:126— attachmentapi/attachment_item_file_request_builder.go:126-133 | documentsapi/document_get_request_builder.go:77-84 — 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 `attachmentapi/attachment_item_file_request_builder.go:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) documentsapi/document_get_request_builder.go:81— documentsapi/document_get_request_builder.go:81-88 | documentsapi/versions_request_builder.go:70-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `documentsapi/document_get_request_builder.go:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) appserviceapi/find_service_result.go:30— appserviceapi/find_service_result.go:30-37 | appserviceapi/service_details_request.go:30-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) website/snippets/tables.go:302— website/snippets/tables.go:302-308 | website/snippets/tables_create.go:35-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) cmdbinstanceapi/cmdb_instance.go:59— cmdbinstanceapi/cmdb_instance.go:59-65 | documentsapi/document.go:51-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) tableapi/table_item_request_builder.go:35— tableapi/table_item_request_builder.go:35-41 | tableapi/table_request_builder.go:41-47 — before extracting anything, compare `tableapi/table_item_request_builder.go` and `tableapi/table_request_builder.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 68 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 `tableapi/table_item_request_builder.go:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Swallowed exception (caught, then discarded) credentials/base_access_token_provider.go:170— `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) batchapi/batch_response.go:125— `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) batchapi/shared.go:73— `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.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark .agents/skills/subagent-creator/assets/eval_review.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 .agents/skills/subagent-creator/eval-viewer/viewer.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (3.1:1) .agents/skills/subagent-creator/assets/eval_review.html:19— `.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.1:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:467— `.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) cdmeditorapi/editor_request_builders.go:112— cdmeditorapi/editor_request_builders.go:112-145 | cdmeditorapi/editor_request_builders.go:160-193 — 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.
Edited copy of a member (34 corresponding lines) website/snippets/tables_create.go:21— website/snippets/tables_create.go:21-62 | website/snippets/tables_update.go:21-54 — 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 (41 corresponding lines) · ×2
Edited copy of a member (41 corresponding lines) internal/oauth2/client.go:232— internal/oauth2/client.go:232-273 | internal/oauth2/client.go:322-362 — 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.
Edited copy of a member (41 corresponding lines) tableapi/table_item_request_builder_patch_query_parameters.go:7— tableapi/table_item_request_builder_patch_query_parameters.go:7-47 | tableapi/table_item_request_builder_put_query_parameters.go:7-47 — 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 (48 corresponding lines) · ×2
Edited copy of a member (48 corresponding lines) website/snippets/tables.go:128— website/snippets/tables.go:128-181 | website/snippets/tables.go:183-230 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (48 corresponding lines) website/snippets/stats_guide.go:21— website/snippets/stats_guide.go:21-68 | website/snippets/tables_query.go:21-72 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×2
Edited copies of one member (3 members, 31+ corresponding lines) cmdbinstanceapi/cmdb_item_request_builder.go:105— cmdbinstanceapi/cmdb_item_request_builder.go:105-135 | documentsapi/document_get_request_builder.go:42-72 | documentsapi/document_post_request_builder.go:42-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 31+ corresponding lines) credentials/client_credentials_credential.go:57— credentials/client_credentials_credential.go:57-87 | credentials/jwt_credential.go:106-136 | credentials/ropc_credential.go:59-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) activitysubscriptionsapi/facets_instance_request_builder.go:32— activitysubscriptionsapi/facets_instance_request_builder.go:32-61 | cmdbinstanceapi/cmdb_class_request_builder.go:38-68 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) website/snippets/case_guide.go:20— website/snippets/case_guide.go:20-62 | website/snippets/quickstart.go:20-49 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×2
Edited copies of one member (3 members, 34+ corresponding lines) website/snippets/modules.go:196— website/snippets/modules.go:196-230 | website/snippets/modules.go:232-265 | website/snippets/modules.go:296-330 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 34+ corresponding lines) website/snippets/tables.go:54— website/snippets/tables.go:54-89 | website/snippets/tables.go:91-126 | website/snippets/tables.go:232-265 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) appointmentbookingapi/appointment_request.go:97— appointmentbookingapi/appointment_request.go:97-113 | appointmentbookingapi/availability_request.go:100-118 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) cdmapplicationsapi/uploads_collections_file_request_builder.go:70— cdmapplicationsapi/uploads_collections_file_request_builder.go:70-86 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:70-86 — 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 copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) appserviceapi/populate_service_request_builder.go:71— appserviceapi/populate_service_request_builder.go:71-86 | appserviceapi/service_details_request_builder.go:72-87 | caseapi/case_item_request_builder.go:126-142 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) appointmentbookingapi/appointment_request_builder.go:75— appointmentbookingapi/appointment_request_builder.go:75-90 | appserviceapi/register_service_request_builder.go:74-89 | tableapi/table_item_request_builder.go:245-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) cdmapplicationsapi/deployables_request_builder.go:86— cdmapplicationsapi/deployables_request_builder.go:86-101 | cdmapplicationsapi/shared_components_request_builder.go:103-118 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) internal/concurrent_dictionary.go:26— internal/concurrent_dictionary.go:26-41 | internal/concurrent_dictionary.go:105-121 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) website/snippets/auth.go:176— website/snippets/auth.go:176-198 | website/snippets/auth.go:200-223 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) cmdbinstanceapi/cmdb_instance.go:15— cmdbinstanceapi/cmdb_instance.go:15-44 | documentsapi/document.go:14-36 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) tableapi/element_visitor.go:51— tableapi/element_visitor.go:51-60 | tableapi/element_visitor.go:63-73 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) cmdbinstanceapi/cmdb_class_request_builder.go:19— cmdbinstanceapi/cmdb_class_request_builder.go:19-28 | cmdbinstanceapi/cmdb_relation_request_builder.go:19-29 — 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 (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) query/condition.go:35— query/condition.go:35-43 | query/condition.go:45-53 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) website/snippets/reference_actions.go:371— website/snippets/reference_actions.go:371-379 | website/snippets/reference_actions.go:487-495 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) internal/concurrent_dictionary.go:44— internal/concurrent_dictionary.go:44-57 | internal/concurrent_dictionary.go:60-73 | internal/concurrent_dictionary.go:89-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) caseapi/reference.go:16— caseapi/reference.go:16-29 | cdmapplicationsapi/reference.go:15-34 | cdmeditorapi/node_update_request_model.go:16-29 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (16–17 lines × 2) attachmentapi/attachment_request_builder.go:143— attachmentapi/attachment_request_builder.go:143-158 | batchapi/batch_request_builder.go:64-80 — 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 `attachmentapi/attachment_request_builder.go:143` 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 (16–17 lines × 2) website/snippets/attachments.go:118— website/snippets/attachments.go:118-133 | website/snippets/attachments.go:146-162 — 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–16 lines × 2) attachmentapi/attachment_request_builder.go:87— attachmentapi/attachment_request_builder.go:87-102 | attachmentapi/attachment_request_builder.go:131-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) tableapi/table_request_builder.go:78— tableapi/table_request_builder.go:78-93 | tableapi/table_request_builder.go:166-180 — 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 × 3) attachmentapi/attachment_item_request_builder.go:94— attachmentapi/attachment_item_request_builder.go:94-108 | documentsapi/delete_request_builder.go:36-50 | tableapi/table_item_request_builder.go:106-120 — before extracting anything, compare `attachmentapi/attachment_item_request_builder.go` and `documentsapi/delete_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `attachmentapi/attachment_item_request_builder.go:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) credentials/client_credentials_credential.go:58— credentials/client_credentials_credential.go:58-72 | credentials/jwt_credential.go:107-121 | credentials/ropc_credential.go:60-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (12 lines × 2) cdmchangesetapi/changeset_request_builders.go:119— cdmchangesetapi/changeset_request_builders.go:119-130 | cdmeditorapi/editor_request_builders.go:198-209 — before extracting anything, compare `cdmchangesetapi/changeset_request_builders.go` and `cdmeditorapi/editor_request_builders.go` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cdmchangesetapi/changeset_request_builders.go:119` 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 (12 lines × 2) website/snippets/tables_create.go:24— website/snippets/tables_create.go:24-35 | website/snippets/tables_update.go:24-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 3) attachmentapi/attachment_request_builder.go:162— attachmentapi/attachment_request_builder.go:162-172 | batchapi/batch_request_builder.go:84-94 | tableapi/table_request_builder.go:232-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) credentials/client.go:90— credentials/client.go:90-100 | credentials/client.go:103-113 | credentials/confidential_client.go:58-68 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 6) cdmapplicationsapi/uploads_collections_file_request_builder.go:71— cdmapplicationsapi/uploads_collections_file_request_builder.go:71-78 | cdmapplicationsapi/uploads_collections_request_builder.go:72-79 | cdmapplicationsapi/uploads_components_request_builder.go:72-79 | cdmapplicationsapi/uploads_components_vars_request_builder.go:70-77 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:71-78 | cdmeditorapi/editor_request_builders.go:119-126 — before extracting anything, compare `cdmapplicationsapi/uploads_collections_file_request_builder.go` and `cdmapplicationsapi/uploads_collections_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `cdmapplicationsapi/uploads_collections_file_request_builder.go:71` 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, `cdmapplicationsapi/uploads_collections_file_request_builder.go:80` calls `AddQueryParameters` and `cdmapplicationsapi/uploads_collections_request_builder.go:80` 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 (8 lines × 6) cmdbinstanceapi/cmdb_class_request_builder.go:125— cmdbinstanceapi/cmdb_class_request_builder.go:125-132 | cmdbinstanceapi/cmdb_item_request_builder.go:140-147 | cmdbinstanceapi/cmdb_item_request_builder.go:156-163 | cmdbinstanceapi/cmdb_item_request_builder.go:179-186 | cmdbinstanceapi/cmdb_relation_item_request_builder.go:59-66 | cmdbinstanceapi/cmdb_relation_request_builder.go:74-81 — before extracting anything, compare `cmdbinstanceapi/cmdb_class_request_builder.go` and `cmdbinstanceapi/cmdb_item_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cmdbinstanceapi/cmdb_item_request_builder.go:148` calls `TryAdd`, `String` and `cmdbinstanceapi/cmdb_relation_item_request_builder.go:68` 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 (8 lines × 4) cdmapplicationsapi/deployables_request_builder.go:104— cdmapplicationsapi/deployables_request_builder.go:104-111 | cdmapplicationsapi/shared_components_request_builder.go:87-94 | cdmchangesetapi/changeset_request_builders.go:125-132 | cdmeditorapi/editor_request_builders.go:204-211 — before extracting anything, compare `cdmapplicationsapi/deployables_request_builder.go` and `cdmapplicationsapi/shared_components_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 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 `cdmapplicationsapi/deployables_request_builder.go:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) appserviceapi/get_content_result.go:31— appserviceapi/get_content_result.go:31-38 | appserviceapi/population_method.go:70-77 | cdmchangesetapi/commit_status_result.go:25-32 | core/service_now_error.go:113-121 — 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.
Duplicated block (7 lines × 7) cmdbinstanceapi/cmdb_class_request_builder.go:106— cmdbinstanceapi/cmdb_class_request_builder.go:106-112 | cmdbinstanceapi/cmdb_class_request_builder.go:125-131 | cmdbinstanceapi/cmdb_item_request_builder.go:140-146 | cmdbinstanceapi/cmdb_item_request_builder.go:156-162 | cmdbinstanceapi/cmdb_item_request_builder.go:179-185 | cmdbinstanceapi/cmdb_relation_item_request_builder.go:59-65 | cmdbinstanceapi/cmdb_relation_request_builder.go:74-80 — before extracting anything, compare `cmdbinstanceapi/cmdb_class_request_builder.go` and `cmdbinstanceapi/cmdb_item_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 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 `cmdbinstanceapi/cmdb_class_request_builder.go:106` 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, `cmdbinstanceapi/cmdb_class_request_builder.go:113` calls `IsNil`, `AddQueryParameters` and `cmdbinstanceapi/cmdb_class_request_builder.go:132` 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 × 7) attachmentapi/attachment_request_builder.go:64— attachmentapi/attachment_request_builder.go:64-72 | attachmentapi/attachment_request_builder.go:75-83 | cmdbinstanceapi/cmdb_item_request_builder.go:200-207 | documentsapi/documents_request_builder.go:40-46 | documentsapi/documents_request_builder.go:49-55 | documentsapi/documents_request_builder.go:58-64 | documentsapi/documents_request_builder.go:87-93 — there are 7 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) appserviceapi/discovery_population_method_attribute.go:51— appserviceapi/discovery_population_method_attribute.go:51-59 | batchapi/rest_request_header.go:54-63 | cdmeditorapi/node_update_request_model.go:37-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) caseapi/reference.go:37— caseapi/reference.go:37-45 | cdmapplicationsapi/reference.go:42-50 | cdmchangesetapi/reference.go:25-33 — `caseapi/reference.go` and `cdmapplicationsapi/reference.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 2 separate duplicated blocks between them, totalling at least 15 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 (9 lines × 2) appserviceapi/populate_service_result.go:30— appserviceapi/populate_service_result.go:30-38 | appserviceapi/service_details_result.go:25-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) appserviceapi/register_service_result.go:30— appserviceapi/register_service_result.go:30-38 | cdmapplicationsapi/upload_status_output.go:25-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) appserviceapi/populate_service_result.go:41— appserviceapi/populate_service_result.go:41-46 | appserviceapi/service_details_result.go:36-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) .agents/skills/subagent-creator/scripts/run_eval.py:254— .agents/skills/subagent-creator/scripts/run_eval.py:254-259 | .agents/skills/subagent-creator/scripts/run_loop.py:246-251 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `.agents/skills/subagent-creator/scripts/run_loop.py:253` calls `add_argument` and `.agents/skills/subagent-creator/scripts/run_eval.py:261` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) documentsapi/attach_request_builder.go:32— documentsapi/attach_request_builder.go:32-37 | documentsapi/create_document_request_builder.go:32-37 | documentsapi/create_request_builder.go:32-37 | documentsapi/sync_down_request_builder.go:32-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (6 lines × 4) documentsapi/attach_request_builder.go:40— documentsapi/attach_request_builder.go:40-45 | documentsapi/create_document_request_builder.go:40-45 | documentsapi/create_request_builder.go:40-45 | documentsapi/sync_down_request_builder.go:40-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 4 call sites, so a change lands once.
Low contrast colour pair in CSS (2.9:1) .agents/skills/subagent-creator/assets/eval_review.html:17— `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard .agents/skills/subagent-creator/eval-viewer/viewer.html:275— `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Low contrast colour pair in CSS (3.0:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:197— `.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.2:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:302— `.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) .agents/skills/subagent-creator/eval-viewer/viewer.html:303— `.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
quick_validate.validate_agent (cyclomatic 30) .agents/skills/subagent-creator/scripts/quick_validate.py:48— quick_validate.validate_agent has cyclomatic complexity 30 (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.
run_loop.run_loop (cyclomatic 28) .agents/skills/subagent-creator/scripts/run_loop.py:47— run_loop.run_loop has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
improve_description.improve_description (cyclomatic 23) .agents/skills/subagent-creator/scripts/improve_description.py:43— improve_description.improve_description has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generate_report.generate_html (cyclomatic 22) .agents/skills/subagent-creator/scripts/generate_report.py:16— generate_report.generate_html 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.
run_eval.run_single_query (cyclomatic 22) .agents/skills/subagent-creator/scripts/run_eval.py:46— run_eval.run_single_query 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.
snippets._ (cyclomatic 21) website/snippets/attachments.go:23— snippets._ has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
aggregate_benchmark.load_run_results (cyclomatic 21) .agents/skills/subagent-creator/scripts/aggregate_benchmark.py:67— aggregate_benchmark.load_run_results 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.
generate_review.build_run (cyclomatic 20) .agents/skills/subagent-creator/eval-viewer/generate_review.py:85— generate_review.build_run has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttachmentFileRequestBuilder.Post (cyclomatic 19) attachmentapi/attachment_file_request_builder.go:49— AttachmentFileRequestBuilder.Post 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.
AttachmentUploadRequestBuilder.Post (cyclomatic 17) attachmentapi/attachment_upload_request_builder.go:49— AttachmentUploadRequestBuilder.Post 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.
PoliciesMappingsRequestBuilder.Post (cyclomatic 16) policyapi/policies_mappings_request_builder.go:76— PoliciesMappingsRequestBuilder.Post 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.
TodoComment repeated across 11 files caseapi/case_activities_request_builder.go:76— The identical TodoComment appears in 11 files (13 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 13 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO: check for nil/empty template and path parameters". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
aggregate_benchmark.load_run_results (cognitive 58) .agents/skills/subagent-creator/scripts/aggregate_benchmark.py:67— aggregate_benchmark.load_run_results has cognitive complexity 58 (threshold 15). Drivers by points: if/else 11 (31 pts), error handling 4 (15 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 37). 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.
run_loop.run_loop (cognitive 55) .agents/skills/subagent-creator/scripts/run_loop.py:47— run_loop.run_loop has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (44 pts), ternaries 5 (9 pts), boolean chains 1, loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate_review.build_run (cognitive 44) .agents/skills/subagent-creator/eval-viewer/generate_review.py:85— generate_review.build_run has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (27 pts), error handling 3 (10 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
improve_description.improve_description (cognitive 42) .agents/skills/subagent-creator/scripts/improve_description.py:43— improve_description.improve_description has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 5 (14 pts), loops 4 (10 pts), boolean chains 3 (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.
generate_report.generate_html (cognitive 40) .agents/skills/subagent-creator/scripts/generate_report.py:16— generate_report.generate_html has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 11 (23 pts), loops 7 (12 pts), if/else 4 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quick_validate.validate_agent (cognitive 37) .agents/skills/subagent-creator/scripts/quick_validate.py:48— quick_validate.validate_agent has cognitive complexity 37 (threshold 15). Drivers by points: if/else 25 (33 pts), boolean chains 3, error handling 1 (nesting depth added 8). 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.
run_eval.run_single_query (cognitive 35) .agents/skills/subagent-creator/scripts/run_eval.py:46— run_eval.run_single_query has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 5, error handling 1 (3 pts), loops 2 (3 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.
utils.parse_agent_md (cognitive 23) .agents/skills/subagent-creator/scripts/utils.py:6— utils.parse_agent_md has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
snippets._ (cognitive 21) website/snippets/attachments.go:23— snippets._ has cognitive complexity 21 (threshold 15). Drivers by points: if/else 19 (20 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AttachmentFileRequestBuilder.Post (cognitive 18) attachmentapi/attachment_file_request_builder.go:49— AttachmentFileRequestBuilder.Post has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, boolean chains 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
quick_validate._parse_frontmatter (cognitive 17) .agents/skills/subagent-creator/scripts/quick_validate.py:13— quick_validate._parse_frontmatter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CreateServiceResult.GetSysID (cognitive 16) appserviceapi/create_service_result.go:122— CreateServiceResult.GetSysID has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3 (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.
AttachmentUploadRequestBuilder.Post (cognitive 16) attachmentapi/attachment_upload_request_builder.go:49— AttachmentUploadRequestBuilder.Post has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, 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.
snippets.tableGuideSnippets (cognitive 16) website/snippets/tables.go:267— snippets.tableGuideSnippets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D22 · Internal API Consistency· `ServiceRelationship.GetFieldDeserializers` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) · ×1
`ServiceRelationship.GetFieldDeserializers` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) appserviceapi/service_relationships.go:42— 3 of 4 collection-returning members of `ServiceRelationship` return a slice (`[]T`) (3 of 4). Siblings: ServiceRelationship.GetBusinessApp (appserviceapi/service_relationships.go:51); ServiceRelationship.GetBusinessServiceOffering (appserviceapi/service_relationships.go:61); ServiceRelationship.GetTechnicalServiceOffering (appserviceapi/service_relationships.go:71). Return a slice (`[]T`). [rule A4]
FunctionTooLong: snippets._ website/snippets/attachments.go:23— FunctionTooLong — _ 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.
FileTooLong: snippets/reference_actions.go website/snippets/reference_actions.go— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Members sharing a duplicated core (17 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (17 members, 50+ identical tokens) accountapi/account_item_request_builder.go:73— accountapi/account_item_request_builder.go:73-84 | accountapi/account_request_builder.go:84-95 | activitysubscriptionsapi/activities_request_builder.go:89-100 | activitysubscriptionsapi/facets_instance_request_builder.go:64-75 | aggregationapi/stats_request_builder.go:91-102 | appointmentbookingapi/calendar_request_builder.go:74-86 | appointmentbookingapi/configuration_request_builder.go:74-86 | appserviceapi/find_service_request_builder.go:74-85 | appserviceapi/get_content_request_builder.go:74-84 | attachmentapi/attachment_item_request_builder.go:111-122 | attachmentapi/attachment_request_builder.go:175-186 | caseapi/case_activities_request_builder.go:71-82 | caseapi/case_field_values_request_builder.go:73-84 | caseapi/case_item_request_builder.go:82-93 | caseapi/case_request_builder.go:93-104 | tableapi/table_item_request_builder.go:197-208 | tableapi/table_request_builder.go:196-208 — These 17 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 17 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 17 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) cmdbinstanceapi/cmdb_class_request_builder.go:104— cmdbinstanceapi/cmdb_class_request_builder.go:104-120 | cmdbinstanceapi/cmdb_class_request_builder.go:123-143 | cmdbinstanceapi/cmdb_item_request_builder.go:138-151 | cmdbinstanceapi/cmdb_item_request_builder.go:154-174 | cmdbinstanceapi/cmdb_item_request_builder.go:177-197 | cmdbinstanceapi/cmdb_relation_item_request_builder.go:57-69 | cmdbinstanceapi/cmdb_relation_request_builder.go:72-92 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) attachmentapi/attachment_item_request_builder.go:92— attachmentapi/attachment_item_request_builder.go:92-108 | cdmapplicationsapi/deployables_request_builder.go:42-56 | cdmapplicationsapi/shared_components_request_builder.go:41-55 | cmdbinstanceapi/cmdb_relation_item_request_builder.go:33-54 | documentsapi/delete_request_builder.go:34-50 | tableapi/table_item_request_builder.go:104-120 — These 6 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 6 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 6 times.
D4 · Code Duplication· Edited copies of one member (8 members, 30+ corresponding lines) · ×1
Edited copies of one member (8 members, 30+ corresponding lines) cdmchangesetapi/changeset_request_builders.go:83— cdmchangesetapi/changeset_request_builders.go:83-115 | cdmchangesetapi/changeset_request_builders.go:153-185 | cdmchangesetapi/changeset_request_builders.go:222-251 | cdmchangesetapi/changeset_request_builders.go:266-298 | cdmchangesetapi/changeset_request_builders.go:313-345 | cdmchangesetapi/changeset_request_builders.go:380-409 | cdmeditorapi/editor_request_builders.go:77-109 | cdmeditorapi/editor_request_builders.go:231-263 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) appointmentbookingapi/appointment_request.go:17— appointmentbookingapi/appointment_request.go:17-62 | appointmentbookingapi/availability_request.go:17-63 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 26+ corresponding lines) · ×1
Edited copies of one member (5 members, 26+ corresponding lines) cdmapplicationsapi/uploads_collections_file_request_builder.go:42— cdmapplicationsapi/uploads_collections_file_request_builder.go:42-67 | cdmapplicationsapi/uploads_collections_request_builder.go:43-68 | cdmapplicationsapi/uploads_components_request_builder.go:43-68 | cdmapplicationsapi/uploads_components_vars_request_builder.go:41-66 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:42-67 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 26+ corresponding lines) · ×1
Edited copies of one member (4 members, 26+ corresponding lines) appserviceapi/populate_service_request_builder.go:40— appserviceapi/populate_service_request_builder.go:40-68 | appserviceapi/service_details_request_builder.go:41-69 | cdmapplicationsapi/deployables_request_builder.go:59-84 | cdmapplicationsapi/shared_components_request_builder.go:58-83 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) cdmapplicationsapi/export_item_content_request_builder.go:41— cdmapplicationsapi/export_item_content_request_builder.go:41-66 | documentsapi/content_request_builder.go:36-66 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) appointmentbookingapi/configuration_response.go:44— appointmentbookingapi/configuration_response.go:44-64 | appointmentbookingapi/service_config.go:70-100 — 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, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) cdmapplicationsapi/uploads_collections_request_builder.go:71— cdmapplicationsapi/uploads_collections_request_builder.go:71-87 | cdmapplicationsapi/uploads_components_request_builder.go:71-87 | cdmapplicationsapi/uploads_components_vars_request_builder.go:69-85 — 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) documentsapi/action_request_builder.go:92— documentsapi/action_request_builder.go:92-106 | documentsapi/document_post_request_builder.go:75-93 — 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 (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) caseapi/activities_result_entry_attachment.go:104— caseapi/activities_result_entry_attachment.go:104-122 | cdmchangesetapi/change_set_result.go:25-42 — 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 (4 members, 27+ corresponding lines) · ×1
Edited copies of one member (4 members, 27+ corresponding lines) website/snippets/modules.go:168— website/snippets/modules.go:168-194 | website/snippets/modules.go:267-294 | website/snippets/modules.go:332-358 | website/snippets/modules.go:360-387 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 19+ corresponding lines) · ×1
Edited copies of one member (4 members, 19+ corresponding lines) core/page_iterator.go:192— core/page_iterator.go:192-210 | core/page_iterator.go:213-231 | core/page_iterator.go:234-252 | core/page_iterator.go:255-273 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) website/snippets/modules.go:42— website/snippets/modules.go:42-60 | website/snippets/modules.go:129-150 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) credentials/confidential_client.go:16— credentials/confidential_client.go:16-42 | credentials/public_client.go:20-43 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 12+ corresponding lines) · ×1
Edited copies of one member (5 members, 12+ corresponding lines) appserviceapi/create_service_result.go:95— appserviceapi/create_service_result.go:95-107 | appserviceapi/service.go:30-42 | cdmapplicationsapi/export_result.go:25-36 | cdmapplicationsapi/shared_library_component_application.go:25-36 | cdmeditorapi/node_result.go:45-57 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 9+ corresponding lines) · ×1
Edited copies of one member (5 members, 9+ corresponding lines) appserviceapi/create_service_result.go:110— appserviceapi/create_service_result.go:110-119 | caseapi/activities_result.go:67-76 | cdmapplicationsapi/export_result.go:39-47 | cdmapplicationsapi/shared_library_component_application.go:39-47 | cdmeditorapi/node_result.go:60-69 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) appserviceapi/app_service_action_result.go:45— appserviceapi/app_service_action_result.go:45-52 | appserviceapi/app_service_action_result.go:139-146 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) website/snippets/reference_actions.go:69— website/snippets/reference_actions.go:69-79 | website/snippets/reference_actions.go:161-171 | website/snippets/reference_actions.go:317-327 | website/snippets/reference_actions.go:533-543 | website/snippets/reference_actions.go:545-555 | website/snippets/reference_actions.go:580-590 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) website/snippets/reference_actions.go:187— website/snippets/reference_actions.go:187-199 | website/snippets/reference_actions.go:201-213 | website/snippets/reference_actions.go:253-265 | website/snippets/reference_actions.go:329-341 | website/snippets/reference_actions.go:782-794 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) credentials/client.go:77— credentials/client.go:77-87 | credentials/confidential_client.go:45-55 | credentials/public_client.go:46-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) cdmapplicationsapi/collection_upload_request.go:25— cdmapplicationsapi/collection_upload_request.go:25-35 | cdmapplicationsapi/component_upload_request.go:25-35 | cdmapplicationsapi/component_vars_upload_request.go:25-34 | cdmapplicationsapi/shared_component_update_request.go:25-34 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) credentials/authorization_code_credential.go:41— credentials/authorization_code_credential.go:41-55 | credentials/client_credentials_credential.go:29-43 | credentials/external_oidc_credential.go:37-51 | credentials/ropc_credential.go:30-45 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) cdmapplicationsapi/collection_upload_request.go:38— cdmapplicationsapi/collection_upload_request.go:38-45 | cdmapplicationsapi/component_upload_request.go:38-45 | cdmapplicationsapi/shared_component_update_request.go:37-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) cmdbinstanceapi/cmdb_instance.go:68— cmdbinstanceapi/cmdb_instance.go:68-75 | documentsapi/document.go:60-66 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) core/base_model.go:49— core/base_model.go:49-59 | core/service_now_item_response.go:60-73 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) appserviceapi/create_service_result.go:38— appserviceapi/create_service_result.go:38-43 | batchapi/rest_request_header.go:66-75 | cdmeditorapi/node_update_request_model.go:48-53 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) aggregationapi/stats_result.go:58— aggregationapi/stats_result.go:58-66 | appserviceapi/populate_service_request.go:30-37 | core/service_now_item_response.go:42-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (25–26 lines × 2) website/snippets/attachments_delete_aging.go:48— website/snippets/attachments_delete_aging.go:48-72 | website/snippets/attachments_download.go:44-69 — 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 `website/snippets/attachments_delete_aging.go:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `website/snippets/attachments_delete_aging.go:47` calls `Date`, `Before`, `NewDateTimeValue` and `website/snippets/attachments_download.go:43` 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 (25 lines × 2) documentsapi/explore_request_builder.go:41— documentsapi/explore_request_builder.go:41-65 | documentsapi/versions_request_builder.go:41-65 — before extracting anything, compare `documentsapi/explore_request_builder.go` and `documentsapi/versions_request_builder.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 `documentsapi/explore_request_builder.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 (21 lines × 5) cmdbinstanceapi/cmdb_class_request_builder.go:81— cmdbinstanceapi/cmdb_class_request_builder.go:81-101 | cmdbinstanceapi/cmdb_item_request_builder.go:49-69 | cmdbinstanceapi/cmdb_item_request_builder.go:82-102 | cmdbinstanceapi/cmdb_item_request_builder.go:115-135 | cmdbinstanceapi/cmdb_relation_request_builder.go:49-69 — before extracting anything, compare `cmdbinstanceapi/cmdb_class_request_builder.go` and `cmdbinstanceapi/cmdb_item_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 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 `cmdbinstanceapi/cmdb_class_request_builder.go:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 4) tableapi/table_item_request_builder.go:81— tableapi/table_item_request_builder.go:81-101 | tableapi/table_item_request_builder.go:137-157 | tableapi/table_item_request_builder.go:174-194 | tableapi/table_request_builder.go:135-155 — before extracting anything, compare `tableapi/table_item_request_builder.go` and `tableapi/table_request_builder.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 68 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 `tableapi/table_item_request_builder.go:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) documentsapi/document_get_request_builder.go:52— documentsapi/document_get_request_builder.go:52-72 | documentsapi/document_post_request_builder.go:52-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `documentsapi/document_get_request_builder.go:52` 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) caseapi/case_item_request_builder.go:60— caseapi/case_item_request_builder.go:60-79 | caseapi/case_item_request_builder.go:104-123 | caseapi/case_request_builder.go:115-134 — before extracting anything, compare `caseapi/case_item_request_builder.go` and `caseapi/case_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 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 `caseapi/case_item_request_builder.go:60` 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 × 5) website/snippets/auth.go:86— website/snippets/auth.go:86-103 | website/snippets/auth.go:110-127 | website/snippets/auth.go:134-151 | website/snippets/auth.go:157-174 | website/snippets/auth.go:235-252 — 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 `website/snippets/auth.go:86` 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 (18 lines × 2) cdmeditorapi/editor_request_builders.go:128— cdmeditorapi/editor_request_builders.go:128-145 | cdmeditorapi/editor_request_builders.go: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 `cdmeditorapi/editor_request_builders.go:128` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 6) cdmapplicationsapi/upload_status_item_request_builder.go:48— cdmapplicationsapi/upload_status_item_request_builder.go:48-64 | cdmapplicationsapi/uploads_collections_file_request_builder.go:51-67 | cdmapplicationsapi/uploads_collections_request_builder.go:52-68 | cdmapplicationsapi/uploads_components_request_builder.go:52-68 | cdmapplicationsapi/uploads_components_vars_request_builder.go:50-66 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:51-67 — before extracting anything, compare `cdmapplicationsapi/upload_status_item_request_builder.go` and `cdmapplicationsapi/uploads_collections_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cdmapplicationsapi/upload_status_item_request_builder.go:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 4) cmdbinstanceapi/cmdb_class_request_builder.go:127— cmdbinstanceapi/cmdb_class_request_builder.go:127-143 | cmdbinstanceapi/cmdb_item_request_builder.go:158-174 | cmdbinstanceapi/cmdb_item_request_builder.go:181-197 | cmdbinstanceapi/cmdb_relation_request_builder.go:76-92 — before extracting anything, compare `cmdbinstanceapi/cmdb_class_request_builder.go` and `cmdbinstanceapi/cmdb_item_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 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 `cmdbinstanceapi/cmdb_class_request_builder.go:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–17 lines × 3) website/snippets/concepts.go:118— website/snippets/concepts.go:118-134 | website/snippets/tables.go:284-296 | website/snippets/tables_query.go:57-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (15 lines × 2) cdmapplicationsapi/uploads_collections_file_request_builder.go:72— cdmapplicationsapi/uploads_collections_file_request_builder.go:72-86 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:72-86 — before extracting anything, compare `cdmapplicationsapi/uploads_collections_file_request_builder.go` and `cdmapplicationsapi/uploads_deployables_file_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 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 `cdmapplicationsapi/uploads_collections_file_request_builder.go:72` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (14 lines × 4) attachmentapi/attachment_item_request_builder.go:93— attachmentapi/attachment_item_request_builder.go:93-106 | cmdbinstanceapi/cmdb_relation_item_request_builder.go:34-47 | documentsapi/delete_request_builder.go:35-48 | tableapi/table_item_request_builder.go:105-118 — before extracting anything, compare `attachmentapi/attachment_item_request_builder.go` and `documentsapi/delete_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–14 lines × 2) website/snippets/concepts.go:83— website/snippets/concepts.go:83-96 | website/snippets/quickstart.go:31-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 (13 lines × 9) accountapi/account_item_request_builder.go:42— accountapi/account_item_request_builder.go:42-54 | accountapi/account_request_builder.go:53-65 | attachmentapi/attachment_item_request_builder.go:61-73 | cmdbinstanceapi/cmdb_class_request_builder.go:40-52 | cmdbinstanceapi/cmdb_item_request_builder.go:41-53 | documentsapi/content_request_builder.go:38-50 | documentsapi/explore_request_builder.go:37-49 | documentsapi/versions_request_builder.go:37-49 | tableapi/table_item_request_builder.go:73-85 — before extracting anything, compare `accountapi/account_item_request_builder.go` and `accountapi/account_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `accountapi/account_item_request_builder.go:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) internal/oauth2/client.go:138— internal/oauth2/client.go:138-150 | internal/oauth2/client.go:254-266 | internal/oauth2/client.go:342-354 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 (12–13 lines × 2) website/snippets/modules.go:414— website/snippets/modules.go:414-425 | website/snippets/stats_guide.go:35-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 `website/snippets/modules.go:414` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–12 lines × 23) accountapi/account_item_request_builder.go:41— accountapi/account_item_request_builder.go:41-52 | accountapi/account_request_builder.go:52-63 | activitysubscriptionsapi/facets_instance_request_builder.go:33-44 | appointmentbookingapi/calendar_request_builder.go:43-54 | appointmentbookingapi/configuration_request_builder.go:43-54 | appserviceapi/find_service_request_builder.go:43-54 | appserviceapi/get_content_request_builder.go:43-54 | attachmentapi/attachment_item_request_builder.go:60-71 | caseapi/case_activities_request_builder.go:42-51 | caseapi/case_field_values_request_builder.go:44-53 | caseapi/case_item_request_builder.go:53-62 | caseapi/case_request_builder.go:64-73 | cdmapplicationsapi/export_item_content_request_builder.go:42-52 | cdmapplicationsapi/export_item_status_request_builder.go:42-52 | cdmapplicationsapi/exports_request_builder.go:43-53 | cdmapplicationsapi/shared_libraries_components_applications_request_builder.go:42-52 | cdmapplicationsapi/upload_status_item_request_builder.go:40-50 | cmdbinstanceapi/cmdb_class_request_builder.go:39-50 | cmdbinstanceapi/cmdb_item_request_builder.go:40-51 | documentsapi/content_request_builder.go:37-48 | documentsapi/explore_request_builder.go:36-47 | documentsapi/versions_request_builder.go:36-47 | tableapi/table_item_request_builder.go:72-83 — before extracting anything, compare `accountapi/account_item_request_builder.go` and `accountapi/account_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–12 lines × 17) accountapi/account_item_request_builder.go:74— accountapi/account_item_request_builder.go:74-84 | accountapi/account_request_builder.go:85-95 | activitysubscriptionsapi/activities_request_builder.go:90-100 | activitysubscriptionsapi/facets_instance_request_builder.go:65-75 | aggregationapi/stats_request_builder.go:92-102 | appointmentbookingapi/calendar_request_builder.go:75-86 | appointmentbookingapi/configuration_request_builder.go:75-86 | appserviceapi/find_service_request_builder.go:75-85 | appserviceapi/get_content_request_builder.go:75-84 | attachmentapi/attachment_item_request_builder.go:112-122 | attachmentapi/attachment_request_builder.go:176-186 | caseapi/case_activities_request_builder.go:72-82 | caseapi/case_field_values_request_builder.go:74-84 | caseapi/case_item_request_builder.go:83-93 | caseapi/case_request_builder.go:94-104 | tableapi/table_item_request_builder.go:198-208 | tableapi/table_request_builder.go:197-208 — before extracting anything, compare `accountapi/account_item_request_builder.go` and `accountapi/account_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10–12 lines × 13) appointmentbookingapi/appointment_request_builder.go:44— appointmentbookingapi/appointment_request_builder.go:44-55 | appointmentbookingapi/availability_request_builder.go:43-54 | appointmentbookingapi/execute_rule_conditions_request_builder.go:43-54 | appointmentbookingapi/user_window_request_builder.go:43-54 | appserviceapi/register_service_request_builder.go:43-54 | caseapi/case_request_builder.go:108-117 | cdmapplicationsapi/uploads_collections_file_request_builder.go:43-53 | cdmapplicationsapi/uploads_collections_request_builder.go:44-54 | cdmapplicationsapi/uploads_components_request_builder.go:44-54 | cdmapplicationsapi/uploads_components_vars_request_builder.go:42-52 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:43-53 | cmdbinstanceapi/cmdb_class_request_builder.go:72-83 | cmdbinstanceapi/cmdb_relation_request_builder.go:40-51 — before extracting anything, compare `appointmentbookingapi/availability_request_builder.go` and `appointmentbookingapi/execute_rule_conditions_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 8) cdmchangesetapi/changeset_request_builders.go:84— cdmchangesetapi/changeset_request_builders.go:84-95 | cdmchangesetapi/changeset_request_builders.go:154-165 | cdmchangesetapi/changeset_request_builders.go:223-234 | cdmchangesetapi/changeset_request_builders.go:267-278 | cdmchangesetapi/changeset_request_builders.go:314-325 | cdmchangesetapi/changeset_request_builders.go:381-392 | cdmeditorapi/editor_request_builders.go:78-89 | cdmeditorapi/editor_request_builders.go:232-243 — before extracting anything, compare `cdmchangesetapi/changeset_request_builders.go` and `cdmeditorapi/editor_request_builders.go` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cdmchangesetapi/changeset_request_builders.go:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 5) cdmapplicationsapi/uploads_collections_request_builder.go:74— cdmapplicationsapi/uploads_collections_request_builder.go:74-85 | cdmapplicationsapi/uploads_components_request_builder.go:74-85 | cdmapplicationsapi/uploads_components_vars_request_builder.go:72-83 | cdmeditorapi/editor_request_builders.go:121-132 | cdmeditorapi/editor_request_builders.go:169-180 — before extracting anything, compare `cdmapplicationsapi/uploads_collections_request_builder.go` and `cdmapplicationsapi/uploads_components_request_builder.go` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 82 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 `cdmapplicationsapi/uploads_collections_request_builder.go:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10–12 lines × 4) appserviceapi/populate_service_request_builder.go:41— appserviceapi/populate_service_request_builder.go:41-52 | appserviceapi/service_details_request_builder.go:42-53 | caseapi/case_item_request_builder.go:97-106 | cmdbinstanceapi/cmdb_item_request_builder.go:73-84 — before extracting anything, compare `appserviceapi/populate_service_request_builder.go` and `appserviceapi/service_details_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 4) website/snippets/attachments_delete_aging.go:26— website/snippets/attachments_delete_aging.go:26-37 | website/snippets/attachments_download.go:27-38 | website/snippets/attachments_recent.go:24-35 | website/snippets/attachments_upload.go:25-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `website/snippets/attachments_delete_aging.go:41` calls `Now`, `AddDate` and `website/snippets/attachments_download.go:41` 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 (12 lines × 3) tableapi/table_item_request_builder.go:231— tableapi/table_item_request_builder.go:231-242 | tableapi/table_item_request_builder.go:251-262 | tableapi/table_request_builder.go:217-228 — before extracting anything, compare `tableapi/table_item_request_builder.go` and `tableapi/table_request_builder.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 68 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 `tableapi/table_item_request_builder.go:231` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–12 lines × 2) website/snippets/concepts.go:64— website/snippets/concepts.go:64-74 | website/snippets/tables_query.go:35-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `website/snippets/concepts.go:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 15) cdmapplicationsapi/deployables_request_builder.go:88— cdmapplicationsapi/deployables_request_builder.go:88-98 | cdmapplicationsapi/deployables_request_builder.go:105-115 | cdmapplicationsapi/exports_request_builder.go:72-82 | cdmapplicationsapi/shared_components_request_builder.go:88-98 | cdmapplicationsapi/shared_components_request_builder.go:105-115 | cdmapplicationsapi/shared_libraries_components_applications_request_builder.go:71-81 | cdmapplicationsapi/uploads_collections_file_request_builder.go:72-82 | cdmapplicationsapi/uploads_deployables_file_request_builder.go:72-82 | cdmchangesetapi/changeset_request_builders.go:91-101 | cdmchangesetapi/changeset_request_builders.go:126-136 | cdmchangesetapi/changeset_request_builders.go:161-171 | cdmchangesetapi/changeset_request_builders.go:274-284 | cdmchangesetapi/changeset_request_builders.go:321-331 | cdmeditorapi/editor_request_builders.go:85-95 | cdmeditorapi/editor_request_builders.go:239-249 — before extracting anything, compare `cdmapplicationsapi/deployables_request_builder.go` and `cdmapplicationsapi/shared_components_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cdmapplicationsapi/deployables_request_builder.go:99` calls `TryAdd`, `String` and `cdmapplicationsapi/deployables_request_builder.go:116` 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 lines × 6) attachmentapi/attachment_item_request_builder.go:93— attachmentapi/attachment_item_request_builder.go:93-104 | cdmapplicationsapi/deployables_request_builder.go:43-53 | cdmapplicationsapi/shared_components_request_builder.go:42-52 | cmdbinstanceapi/cmdb_relation_item_request_builder.go:34-45 | documentsapi/delete_request_builder.go:35-46 | tableapi/table_item_request_builder.go:105-116 — before extracting anything, compare `attachmentapi/attachment_item_request_builder.go` and `documentsapi/delete_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 4) attachmentapi/attachment_upload_request_builder.go:50— attachmentapi/attachment_upload_request_builder.go:50-60 | tableapi/table_item_request_builder.go:124-134 | tableapi/table_item_request_builder.go:161-171 | tableapi/table_request_builder.go:122-132 — before extracting anything, compare `tableapi/table_item_request_builder.go` and `tableapi/table_request_builder.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) documentsapi/action_request_builder.go:94— documentsapi/action_request_builder.go:94-106 | documentsapi/document_post_request_builder.go:81-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `documentsapi/action_request_builder.go:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 5) website/snippets/account_guide.go:23— website/snippets/account_guide.go:23-32 | website/snippets/appointment_guide.go:23-32 | website/snippets/appservice_guide.go:23-32 | website/snippets/cmdb_guide.go:23-32 | website/snippets/pagination_guide.go:25-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (10 lines × 4) website/snippets/cdm_applications_guide.go:23— website/snippets/cdm_applications_guide.go:23-32 | website/snippets/cdm_changesets_guide.go:23-32 | website/snippets/cdm_editor_guide.go:23-32 | website/snippets/policy_guide.go:23-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (7–9 lines × 13) appointmentbookingapi/availability_request_builder.go:82— appointmentbookingapi/availability_request_builder.go:82-90 | appointmentbookingapi/execute_rule_conditions_request_builder.go:83-91 | appointmentbookingapi/user_window_request_builder.go:82-90 | appserviceapi/populate_service_request_builder.go:80-86 | appserviceapi/service_details_request_builder.go:81-87 | appserviceapi/service_post_request_builder.go:71-77 | attachmentapi/attachment_upload_request_builder.go:123-130 | batchapi/batch_request_builder.go:143-151 | caseapi/case_item_request_builder.go:134-142 | caseapi/case_request_builder.go:145-153 | cdmapplicationsapi/uploads_collections_request_builder.go:81-87 | cdmapplicationsapi/uploads_components_request_builder.go:81-87 | cdmapplicationsapi/uploads_components_vars_request_builder.go:79-85 — before extracting anything, compare `appointmentbookingapi/availability_request_builder.go` and `appointmentbookingapi/execute_rule_conditions_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 `appointmentbookingapi/availability_request_builder.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–9 lines × 10) appointmentbookingapi/appointment_request_builder.go:76— appointmentbookingapi/appointment_request_builder.go:76-83 | appointmentbookingapi/availability_request_builder.go:75-82 | appointmentbookingapi/execute_rule_conditions_request_builder.go:75-83 | appointmentbookingapi/user_window_request_builder.go:75-82 | appserviceapi/service_post_request_builder.go:64-71 | attachmentapi/attachment_file_request_builder.go:117-124 | attachmentapi/attachment_upload_request_builder.go:116-123 | batchapi/batch_request_builder.go:136-143 | caseapi/case_request_builder.go:138-145 | tableapi/table_request_builder.go:212-219 — before extracting anything, compare `appointmentbookingapi/availability_request_builder.go` and `appointmentbookingapi/execute_rule_conditions_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `tableapi/table_request_builder.go:221` calls `IsNil` and `appointmentbookingapi/appointment_request_builder.go:85` 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 (9 lines × 10) cdmapplicationsapi/export_item_status_request_builder.go:71— cdmapplicationsapi/export_item_status_request_builder.go:71-79 | cdmapplicationsapi/upload_status_item_request_builder.go:69-77 | cdmapplicationsapi/uploads_collections_request_builder.go:73-81 | cdmapplicationsapi/uploads_components_request_builder.go:73-81 | cdmapplicationsapi/uploads_components_vars_request_builder.go:71-79 | cdmchangesetapi/changeset_request_builders.go:230-238 | cdmchangesetapi/changeset_request_builders.go:388-396 | cdmeditorapi/editor_request_builders.go:120-128 | cdmeditorapi/editor_request_builders.go:168-176 | cdmeditorapi/editor_request_builders.go:205-213 — before extracting anything, compare `cdmapplicationsapi/export_item_status_request_builder.go` and `cdmapplicationsapi/upload_status_item_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) cmdbinstanceapi/cmdb_class_request_builder.go:125— cmdbinstanceapi/cmdb_class_request_builder.go:125-133 | cmdbinstanceapi/cmdb_item_request_builder.go:140-148 | cmdbinstanceapi/cmdb_item_request_builder.go:156-164 | cmdbinstanceapi/cmdb_item_request_builder.go:179-187 | cmdbinstanceapi/cmdb_relation_request_builder.go:74-82 — before extracting anything, compare `cmdbinstanceapi/cmdb_class_request_builder.go` and `cmdbinstanceapi/cmdb_item_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 4) appserviceapi/populate_service_request_builder.go:72— appserviceapi/populate_service_request_builder.go:72-80 | appserviceapi/service_details_request_builder.go:73-81 | caseapi/case_item_request_builder.go:127-134 | tableapi/table_item_request_builder.go:226-233 — before extracting anything, compare `appserviceapi/populate_service_request_builder.go` and `appserviceapi/service_details_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 13) cdmapplicationsapi/export_item_content_request_builder.go:70— cdmapplicationsapi/export_item_content_request_builder.go:70-77 | cdmapplicationsapi/export_item_status_request_builder.go:70-77 | cdmapplicationsapi/exports_request_builder.go:71-78 | cdmapplicationsapi/shared_libraries_components_applications_request_builder.go:70-77 | cdmapplicationsapi/upload_status_item_request_builder.go:68-75 | cdmchangesetapi/changeset_request_builders.go:90-97 | cdmchangesetapi/changeset_request_builders.go:160-167 | cdmchangesetapi/changeset_request_builders.go:229-236 | cdmchangesetapi/changeset_request_builders.go:273-280 | cdmchangesetapi/changeset_request_builders.go:320-327 | cdmchangesetapi/changeset_request_builders.go:387-394 | cdmeditorapi/editor_request_builders.go:84-91 | cdmeditorapi/editor_request_builders.go:238-245 — before extracting anything, compare `cdmapplicationsapi/export_item_status_request_builder.go` and `cdmapplicationsapi/upload_status_item_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 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 `cdmapplicationsapi/export_item_content_request_builder.go:70` 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, `cdmapplicationsapi/exports_request_builder.go:80` calls `AddQueryParameters` and `cdmapplicationsapi/export_item_status_request_builder.go:78` 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 (8 lines × 11) cdmapplicationsapi/export_item_content_request_builder.go:71— cdmapplicationsapi/export_item_content_request_builder.go:71-78 | cdmapplicationsapi/export_item_status_request_builder.go:71-78 | cdmapplicationsapi/upload_status_item_request_builder.go:69-76 | cdmapplicationsapi/uploads_collections_request_builder.go:73-80 | cdmapplicationsapi/uploads_components_request_builder.go:73-80 | cdmapplicationsapi/uploads_components_vars_request_builder.go:71-78 | cdmchangesetapi/changeset_request_builders.go:230-237 | cdmchangesetapi/changeset_request_builders.go:388-395 | cdmeditorapi/editor_request_builders.go:120-127 | cdmeditorapi/editor_request_builders.go:168-175 | cdmeditorapi/editor_request_builders.go:205-212 — before extracting anything, compare `cdmapplicationsapi/export_item_status_request_builder.go` and `cdmapplicationsapi/upload_status_item_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) cdmapplicationsapi/deployables_request_builder.go:87— cdmapplicationsapi/deployables_request_builder.go:87-94 | cdmapplicationsapi/shared_components_request_builder.go:104-111 | cdmeditorapi/editor_request_builders.go:167-174 — before extracting anything, compare `cdmapplicationsapi/deployables_request_builder.go` and `cdmapplicationsapi/shared_components_request_builder.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 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 `cdmapplicationsapi/deployables_request_builder.go:87` 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, `cdmapplicationsapi/deployables_request_builder.go:96` calls `AddQueryParameters` and `cdmeditorapi/editor_request_builders.go:175` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 4) attachmentapi/attachment_item_file_request_builder.go:129— attachmentapi/attachment_item_file_request_builder.go:129-133 | documentsapi/content_request_builder.go:70-74 | documentsapi/document_get_request_builder.go:80-84 | documentsapi/versions_request_builder.go:69-73 — before extracting anything, compare `documentsapi/content_request_builder.go` and `documentsapi/versions_request_builder.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `attachmentapi/attachment_item_file_request_builder.go:125` calls `IsNil` and `documentsapi/content_request_builder.go:69` 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 (19 lines × 2) appointmentbookingapi/enum.go:16— appointmentbookingapi/enum.go:16-34 | caseapi/enum.go:16-34 — `appointmentbookingapi/enum.go` and `caseapi/enum.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 19 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 (32 lines × 2) caseapi/display_value.go:8— caseapi/display_value.go:8-39 | tableapi/display_value.go:8-39 — `caseapi/display_value.go` and `tableapi/display_value.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 32 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 (6 lines × 3) caseapi/reference.go:48— caseapi/reference.go:48-53 | cdmapplicationsapi/reference.go:53-58 | cdmchangesetapi/reference.go:36-41 — `caseapi/reference.go` and `cdmapplicationsapi/reference.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 2 separate duplicated blocks between them, totalling at least 15 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 (6 lines × 5) appointmentbookingapi/calendar_response.go:52— appointmentbookingapi/calendar_response.go:52-57 | appserviceapi/discovery_population_method_attribute.go:43-48 | appserviceapi/register_service_result.go:41-46 | appserviceapi/tag_list_population_method_tag.go:47-52 | policyapi/ref.go:47-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (8 lines × 8) appserviceapi/app_service_request_builder.go:47— appserviceapi/app_service_request_builder.go:47-55 | appserviceapi/csdm_request_builder.go:47-55 | attachmentapi/attachment_request_builder.go:52-61 | caseapi/case_item_request_builder.go:42-49 | caseapi/case_request_builder.go:53-60 | cmdbinstanceapi/cmdb_class_request_builder.go:146-154 | cmdbinstanceapi/cmdb_instance_request_builder.go:39-47 | cmdbinstanceapi/cmdb_relation_request_builder.go:95-103 — before extracting anything, compare `caseapi/case_item_request_builder.go` and `caseapi/case_request_builder.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) tableapi/table_item_request_builder.go:64— tableapi/table_item_request_builder.go:64-68 | tableapi/table_request_builder.go:70-74 — before extracting anything, compare `tableapi/table_item_request_builder.go` and `tableapi/table_request_builder.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 68 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 `tableapi/table_item_request_builder.go:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
X3 · Exception handling· Lost error (reports the zero value of a failed type assertion) · ×1
Lost error (reports the zero value of a failed type assertion) core/page_iterator.go:334— `response, ok := rawResponse.(ServiceNowCollectionResponse[T])` failed on this branch, so `response` is the zero value of `ServiceNowCollectionResponse[T]` here, and that is what is reported: the value that did not fit is lost. Report `rawResponse` itself (and `%T` of it) instead.
Fat interface: AppointmentRequest (26 methods) appointmentbookingapi/appointment_request.go:17— `AppointmentRequest` declares 26 methods: `GetActualEndDate`, `SetActualEndDate`, `GetActualStartDate`, `SetActualStartDate`, `GetCatalogID`, `SetCatalogID`, `GetEndDateUTC`, `SetEndDateUTC`, `GetLocation`, `SetLocation`, `GetOpenedFor`, `SetOpenedFor`, `GetReschedule`, `SetReschedule`, `GetServiceConfigRule`, `SetServiceConfigRule`, `GetStartDateUTC`, `SetStartDateUTC`, `GetTaskID`, `SetTaskID`, `GetTaskTable`, `SetTaskTable`, `GetTimezone`, `SetTimezone`, `GetValidateRequest`, `SetValidateRequest`. 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.
Fat interface: AvailabilityRequest (30 methods) appointmentbookingapi/availability_request.go:17— `AvailabilityRequest` declares 30 methods: `GetCatalogID`, `SetCatalogID`, `GetEndDate`, `SetEndDate`, `GetFetchDaysSlot`, `SetFetchDaysSlot`, `GetFullDay`, `SetFullDay`, `GetGetNextAvailableSlot`, `SetGetNextAvailableSlot`, `GetLimit`, `SetLimit`, `GetLocation`, `SetLocation`, `GetOpenedFor`, `SetOpenedFor`, `GetOtherInputs`, `SetOtherInputs`, `GetServiceConfigRule`, `SetServiceConfigRule`, `GetStartDate`, `SetStartDate`, `GetTaskID`, `SetTaskID`, `GetTaskTable`, `SetTaskTable`, `GetUseReadReplica`, `SetUseReadReplica`, `GetView`, `SetView`. 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.
Fat interface: ServiceConfig (30 methods) appointmentbookingapi/service_config.go:16— `ServiceConfig` declares 30 methods: `GetActive`, `SetActive`, `GetActiveString`, `SetActiveString`, `GetAppointmentBookingConfig`, `SetAppointmentBookingConfig`, `GetAppointmentDuration`, `SetAppointmentDuration`, `GetAppointmentsPerBookableSlot`, `SetAppointmentsPerBookableSlot`, `GetBookableDays`, `SetBookableDays`, `GetCancelByTime`, `SetCancelByTime`, `GetDefaultTimezone`, `SetDefaultTimezone`, `GetEnableAdvancedConfig`, `SetEnableAdvancedConfig`, `GetFieldMapping`, `SetFieldMapping`, `GetFutureBookableMaxDays`, `SetFutureBookableMaxDays`, `GetLeadTime`, `SetLeadTime`, `GetMandatory`, `SetMandatory`, `GetUseSlotEndTimeAs`, `SetUseSlotEndTimeAs`, `GetWorkDuration`, `SetWorkDuration`. 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.
Fat interface: ActivitiesResultEntry (24 methods) caseapi/activities_result_entry.go:30— `ActivitiesResultEntry` declares 24 methods: `GetAttachment`, `SetAttachment`, `GetContainsCode`, `SetContainsCode`, `GetElement`, `SetElement`, `GetFieldLabel`, `SetFieldLabel`, `GetInitials`, `SetInitials`, `GetLoginName`, `SetLoginName`, `GetName`, `SetName`, `GetSysCreatedOn`, `SetSysCreatedOn`, `GetSysCreatedOnAdjusted`, `SetSysCreatedOnAdjusted`, `GetSysID`, `SetSysID`, `GetUserSysID`, `SetUserSysID`, `GetValue`, `SetValue`. 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.
Fat interface: ActivitiesResultEntryAttachment (24 methods) caseapi/activities_result_entry_attachment.go:30— `ActivitiesResultEntryAttachment` declares 24 methods: `GetAverageImageColor`, `SetAverageImageColor`, `GetContentType`, `SetContentType`, `GetFileName`, `SetFileName`, `GetImageHeight`, `SetImageHeight`, `GetImagePath`, `SetImagePath`, `GetImageWidth`, `SetImageWidth`, `GetPath`, `SetPath`, `GetSize`, `SetSize`, `GetSizeBytes`, `SetSizeBytes`, `GetState`, `SetState`, `GetSysID`, `SetSysID`, `GetThumbnailPath`, `SetThumbnailPath`. 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.
Fat interface: CaseResult (64 methods) caseapi/case_result.go:41— `CaseResult` declares 64 methods: `GetAccount`, `SetAccount`, `GetActive`, `SetActive`, `GetActiveAccountEscalation`, `SetActiveAccountEscalation`, `GetActiveEscalation`, `SetActiveEscalation`, `GetActivityDue`, `SetActivityDue`, `GetAdditionalAssigneeList`, `SetAdditionalAssigneeList`, `GetApproval`, `SetApproval`, `GetApprovalHistory`, `SetApprovalHistory`, `GetApprovalSet`, `SetApprovalSet`, `GetAsset`, `SetAsset`, `GetAssignedTo`, `SetAssignedTo`, `GetAssignmentGroup`, `SetAssignmentGroup`, `GetBusinessDuration`, `SetBusinessDuration`, `GetBusinessImpact`, `SetBusinessImpact`, `GetBusinessService`, `SetBusinessService`, `GetCase`, `SetCase`, `GetCaseReport`, `SetCaseReport`, `GetCategory`, `SetCategory`, `GetCause`, `SetCause`, `GetCausedBy`, `SetCausedBy`, and 24 more. 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.
Fat interface: PoliciesMappingable (36 methods) policyapi/policies_mappings.go:17— `PoliciesMappingable` declares 36 methods: `GetDescription`, `SetDescription`, `GetDocument`, `SetDocument`, `GetDocumentRef`, `SetDocumentRef`, `GetError`, `SetError`, `GetException`, `SetException`, `GetExceptionAllowed`, `SetExceptionAllowed`, `GetInputStatus`, `SetInputStatus`, `GetLastUpdatedBy`, `SetLastUpdatedBy`, `GetNumber`, `SetNumber`, `GetPolicy`, `SetPolicy`, `GetReason`, `SetReason`, `GetState`, `SetState`, `GetSysClassName`, `SetSysClassName`, `GetSysCreatedBy`, `SetSysCreatedBy`, `GetSysCreatedOn`, `SetSysCreatedOn`, `GetSysID`, `SetSysID`, `GetSysUpdatedBy`, `SetSysUpdatedBy`, `GetSysUpdatedOn`, `SetSysUpdatedOn`. 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.
D21 · Naming Consistency· `rawUrl` spells `Url` where 208 names in the project spell it `URL` · ×2
`rawUrl` spells `Url` where 208 names in the project spell it `URL` accountapi/account_item_request_builder.go:34— 208 of 213 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `URL` (208 of 213; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `URL`). Peers: accountapi.accountItemURLTemplate (accountapi/account_item_request_builder.go:19); accountapi.accountURLTemplate (accountapi/account_request_builder.go:21); activitysubscriptionsapi.actSubURLTemplate (activitysubscriptionsapi/act_sub_request_builder.go:15); activitysubscriptionsapi.NewActSubRequestBuilder(rawURL) (activitysubscriptionsapi/act_sub_request_builder.go:31); activitysubscriptionsapi.activitiesURLTemplate (activitysubscriptionsapi/activities_request_builder.go:20). Rename to `rawURL`. [rule N6]
`rawUrl` spells `Url` where 208 names in the project spell it `URL` accountapi/account_request_builder.go:38— 208 of 213 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `URL` (208 of 213; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `URL`). Peers: accountapi.accountItemURLTemplate (accountapi/account_item_request_builder.go:19); accountapi.accountURLTemplate (accountapi/account_request_builder.go:21); activitysubscriptionsapi.actSubURLTemplate (activitysubscriptionsapi/act_sub_request_builder.go:15); activitysubscriptionsapi.NewActSubRequestBuilder(rawURL) (activitysubscriptionsapi/act_sub_request_builder.go:31); activitysubscriptionsapi.activitiesURLTemplate (activitysubscriptionsapi/activities_request_builder.go:20). Rename to `rawURL`. [rule N6]
D21 · Naming Consistency· `getContentUrlKey` spells `Url` where 208 names in the project spell it `URL` · ×1
`getContentUrlKey` spells `Url` where 208 names in the project spell it `URL` appserviceapi/create_service_result.go:90— 208 of 213 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `URL` (208 of 213; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `URL`). Peers: accountapi.accountItemURLTemplate (accountapi/account_item_request_builder.go:19); accountapi.accountURLTemplate (accountapi/account_request_builder.go:21); activitysubscriptionsapi.actSubURLTemplate (activitysubscriptionsapi/act_sub_request_builder.go:15); activitysubscriptionsapi.NewActSubRequestBuilder(rawURL) (activitysubscriptionsapi/act_sub_request_builder.go:31); activitysubscriptionsapi.activitiesURLTemplate (activitysubscriptionsapi/activities_request_builder.go:20). Rename to `getContentURLKey`. [rule N6]
D21 · Naming Consistency· `userSysIdKey` spells `Id` where 272 names in the project spell it `ID` · ×1
`userSysIdKey` spells `Id` where 272 names in the project spell it `ID` caseapi/activities_result_entry.go:24— 272 of 274 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `ID` (272 of 274; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `ID`). Peers: accountapi.sysIDKey (accountapi/account.go:50); Account.GetSysID (accountapi/account.go:530); Account.SetSysID (accountapi/account.go:535); accountapi.accountIDKey (accountapi/account_request_builder.go:22); AccountRequestBuilder.ByID (accountapi/account_request_builder.go:44). Rename to `userSysIDKey`. [rule N6]
D21 · Naming Consistency· `SubscribeWithId` spells `Id` where 272 names in the project spell it `ID` · ×1
`SubscribeWithId` spells `Id` where 272 names in the project spell it `ID` REDACTED:55— 272 of 274 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `ID` (272 of 274; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `ID`). Peers: accountapi.sysIDKey (accountapi/account.go:50); Account.GetSysID (accountapi/account.go:530); Account.SetSysID (accountapi/account.go:535); accountapi.accountIDKey (accountapi/account_request_builder.go:22); AccountRequestBuilder.ByID (accountapi/account_request_builder.go:44). Rename to `SubscribeWithID`. [rule N6]
D21 · Naming Consistency· `SetBaseUrl` spells `Url` where 208 names in the project spell it `URL` · ×1
`SetBaseUrl` spells `Url` where 208 names in the project spell it `URL` internal/mocking/mock_request_adapter.go:97— 208 of 213 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `URL` (208 of 213; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `URL`). Peers: accountapi.accountItemURLTemplate (accountapi/account_item_request_builder.go:19); accountapi.accountURLTemplate (accountapi/account_request_builder.go:21); activitysubscriptionsapi.actSubURLTemplate (activitysubscriptionsapi/act_sub_request_builder.go:15); activitysubscriptionsapi.NewActSubRequestBuilder(rawURL) (activitysubscriptionsapi/act_sub_request_builder.go:31); activitysubscriptionsapi.activitiesURLTemplate (activitysubscriptionsapi/activities_request_builder.go:20). Rename to `SetBaseURL`. [rule N6]
D21 · Naming Consistency· `GetBaseUrl` spells `Url` where 208 names in the project spell it `URL` · ×1
`GetBaseUrl` spells `Url` where 208 names in the project spell it `URL` internal/mocking/mock_request_adapter.go:102— 208 of 213 names in project github.com/michaeldcanady/servicenow-sdk-go/v2 spell the token `URL` (208 of 213; unit: names in project github.com/michaeldcanady/servicenow-sdk-go/v2 containing `URL`). Peers: accountapi.accountItemURLTemplate (accountapi/account_item_request_builder.go:19); accountapi.accountURLTemplate (accountapi/account_request_builder.go:21); activitysubscriptionsapi.actSubURLTemplate (activitysubscriptionsapi/act_sub_request_builder.go:15); activitysubscriptionsapi.NewActSubRequestBuilder(rawURL) (activitysubscriptionsapi/act_sub_request_builder.go:31); activitysubscriptionsapi.activitiesURLTemplate (activitysubscriptionsapi/activities_request_builder.go:20). Rename to `GetBaseURL`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion REDACTED:1— `(repository root)` (27869 LoC, 516 module-visible types across 34 directories) overshoots its size bounds. 1 of 2 build unit(s) (Go, npm) overshoot their size bounds, lowering Project Cohesion to 0.0/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.
Duplicated predicate accountapi/account_item_request_builder.go:41— `conversion.IsNil(rB) || conversion.IsNil(rB.RequestBuilder)` appears character-identically in 71 files — accountapi/account_item_request_builder.go, accountapi/account_request_builder.go, activitysubscriptionsapi/activities_request_builder.go, activitysubscriptionsapi/facets_context_request_builder.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.
Null assertions (`!`) override strict null checking — ~1.4 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 727 source line(s) of the 10 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: website/src/components/GoSnippet/region.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default in catch website/src/components/GoSnippet/placeholders.ts:30— `readStoredValues` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated: github.com/microsoft/kiota-abstractions-go — `github.com/microsoft/kiota-abstractions-go` is required at v1.12.0 in REDACTED, but v1.12.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/microsoft/kiota-abstractions-go@v1.12.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/microsoft/kiota-http-go — `github.com/microsoft/kiota-http-go` is required at v1.6.0 in REDACTED, but v1.6.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/microsoft/kiota-http-go@v1.6.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/microsoft/kiota-serialization-form-go — `github.com/microsoft/kiota-serialization-form-go` is required at v1.1.6 in REDACTED, but v1.1.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/microsoft/kiota-serialization-form-go@v1.1.7 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/microsoft/kiota-serialization-multipart-go — `github.com/microsoft/kiota-serialization-multipart-go` is required at v1.1.4 in REDACTED, but v1.1.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/microsoft/kiota-serialization-multipart-go@v1.1.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/microsoft/kiota-serialization-text-go — `github.com/microsoft/kiota-serialization-text-go` is required at v1.1.6 in REDACTED, but v1.1.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/microsoft/kiota-serialization-text-go@v1.1.7 && go mod tidy` and commit the updated REDACTED and go.sum.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 20 file(s) — `appserviceapi/convert_to_dynamic_service_request_builder.go`, `appserviceapi/convert_to_manual_service_request_builder.go`, `appserviceapi/create_dynamic_service_request_builder.go`, `appserviceapi/create_request_builder.go`, `appserviceapi/create_service_response.go`, … (+15 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e615-68ec-7b5d-bc0a-18551e924283 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 3 · Warnings: 338 · Recommendations: 18 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 20:38 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.