Public report of ory/hydra, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 19:44 UTC · Survey ID cd_875cf32324c44ce7af14eaf43379afd6
ory/hydra
Measured 17 November 2026, 19:41 UTC, at code version 4174065
First survey, so nothing to compare with yet
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 54,243 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Security and Compliance, 49.8
Findings by how serious they are
2189 critical452 serious139 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 19:41 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
58of 58 dimensions measured by tools.
2675of 2780 findings point to an exact file and line, so you can open each one in the code. The other 105 concern the repository as a whole, such as missing documentation.
58dimensions across 6 lenses, read from 54,243 lines of product code in 5 projects.
ory/hydra is rated At risk because critical security findings are open, most of them leaked passwords or keys. Its score is held back because 24 of the dependencies have a known vulnerability and it has passwords or keys in the code's history. It scores 60.3 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 49.8, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the product with no limit on what it can connect to, worth about 1.9 points. Updating the 24 dependencies with a known vulnerability would lift Security and Compliance itself, worth about 2.5 points. Raising Security and Compliance to 70 would lift the score to about 68.4.
1,326 passwords or keys in the code, and 767 in the code's history are open to anyone who can read the repository. Forty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and nineteen secrets can leak from the build pipeline. Replacing each exposed password or key, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the 18 packages with a known security hole, and the nine pipeline steps that run downloads without checking them need each download checked against a known checksum first.
The product code is 54,243 lines, about €120,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 Security and Compliance rose from 49.8 to 70, the lowest score rated Strong, the score would rise from 60.3 to about 68.4.
Code composition: what the lines of code are
Product code 56%Tests 44%
Rebuild cost: about €120,000 · Estimate
Cost to rebuild
€41,000 to €210,000, for 690 to 2,189 hours of work, about 0.9 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 60. 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: 54,243 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No network policy finding(s) in Network Egress Confinement.
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 €120,000 to build again, about 0.9 person-years of work. Its weakest lens is Security and Compliance, at 49.8 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No network policy finding(s) in Network Egress Confinement. Of all the actions in this report, it raises the score most for the work it takes: about 1.9 points for low effort, because it clears the 1 Network Egress Confinement findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 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 11,760 lines over the last 90 days, which is about 47,693 lines a year. At that pace, the extra work comes to an estimated 2.5 to 15.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
124 modules, with 252 dependencies between them. One loop runs through 8 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 84 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.
com/ory/hydra/v2/fosite/handler/rfc7523 uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fosite/handler/rfc7523, while a change to com/ory/hydra/v2/fosite/handler/rfc7523 can't break com/ory/hydra/v2/fosite/handler/oauth2.
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.
6→19 com/ory/hydra/v2/fosite/handler/rfc7523 uses com/ory/hydra/v2/fositepart of a loop✕
Connections
4 pairs of types, where a type in com/ory/hydra/v2/fosite/handler/rfc7523 uses a type in com/ory/hydra/v2/fosite.
com/ory/hydra/v2/fosite/handler/rfc7523 uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/handler/rfc7523, while a change to com/ory/hydra/v2/fosite/handler/rfc7523 can't break com/ory/hydra/v2/fosite.
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.
7→19 com/ory/hydra/v2/fosite/token/hmac uses com/ory/hydra/v2/fositepart of a loop✕
Connections
4 pairs of types, where a type in com/ory/hydra/v2/fosite/token/hmac uses a type in com/ory/hydra/v2/fosite.
com/ory/hydra/v2/fosite/token/hmac uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/token/hmac, while a change to com/ory/hydra/v2/fosite/token/hmac can't break com/ory/hydra/v2/fosite.
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.
com/ory/x/configx uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/x/configx, while a change to com/ory/x/configx can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/x/configx uses a module listed above it, which is the healthy direction.
com/ory/x/configx uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/x/configx, while a change to com/ory/x/configx can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/x/configx uses a module listed above it, which is the healthy direction.
com/ory/x/httpx uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/x/httpx, while a change to com/ory/x/httpx can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/x/httpx uses a module listed above it, which is the healthy direction.
com/ory/x/popx uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/x/popx, while a change to com/ory/x/popx can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/x/popx uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/oauth2 uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/fosite/handler/oauth2, while a change to com/ory/hydra/v2/fosite/handler/oauth2 can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/oauth2 uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/fosite/handler/oauth2, while a change to com/ory/hydra/v2/fosite/handler/oauth2 can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/oauth2 uses com/ory/hydra/v2/fosite/token/hmac, so a change to com/ory/hydra/v2/fosite/token/hmac can break com/ory/hydra/v2/fosite/handler/oauth2, while a change to com/ory/hydra/v2/fosite/handler/oauth2 can't break com/ory/hydra/v2/fosite/token/hmac.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/oauth2 uses a module listed above it, which is the healthy direction.
11→19 com/ory/hydra/v2/fosite/handler/oauth2 uses com/ory/hydra/v2/fositepart of a loop✕
Connections
54 pairs of types, where a type in com/ory/hydra/v2/fosite/handler/oauth2 uses a type in com/ory/hydra/v2/fosite. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com/ory/hydra/v2/fosite/handler/oauth2 uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/handler/oauth2, while a change to com/ory/hydra/v2/fosite/handler/oauth2 can't break com/ory/hydra/v2/fosite.
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.
com/ory/hydra/v2/fosite/handler/rfc8628 uses com/ory/hydra/v2/fosite/token/hmac, so a change to com/ory/hydra/v2/fosite/token/hmac can break com/ory/hydra/v2/fosite/handler/rfc8628, while a change to com/ory/hydra/v2/fosite/handler/rfc8628 can't break com/ory/hydra/v2/fosite/token/hmac.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/rfc8628 uses a module listed above it, which is the healthy direction.
12→19 com/ory/hydra/v2/fosite/handler/rfc8628 uses com/ory/hydra/v2/fositepart of a loop✕
Connections
15 pairs of types, where a type in com/ory/hydra/v2/fosite/handler/rfc8628 uses a type in com/ory/hydra/v2/fosite.
com/ory/hydra/v2/fosite/handler/rfc8628 uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/handler/rfc8628, while a change to com/ory/hydra/v2/fosite/handler/rfc8628 can't break com/ory/hydra/v2/fosite.
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.
com/ory/x/contextx uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/x/contextx, while a change to com/ory/x/contextx can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/x/contextx uses a module listed above it, which is the healthy direction.
com/ory/x/metricsx uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/x/metricsx, while a change to com/ory/x/metricsx can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/x/metricsx uses a module listed above it, which is the healthy direction.
com/ory/x/metricsx uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/x/metricsx, while a change to com/ory/x/metricsx can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/x/metricsx uses a module listed above it, which is the healthy direction.
com/ory/x/networkx uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/x/networkx, while a change to com/ory/x/networkx can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/x/networkx uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/openid uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/fosite/handler/openid, while a change to com/ory/hydra/v2/fosite/handler/openid can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/openid uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/openid uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/fosite/handler/openid, while a change to com/ory/hydra/v2/fosite/handler/openid can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/openid uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/openid uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fosite/handler/openid, while a change to com/ory/hydra/v2/fosite/handler/openid can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/openid uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/openid uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/fosite/handler/openid, while a change to com/ory/hydra/v2/fosite/handler/openid can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/openid uses a module listed above it, which is the healthy direction.
16→19 com/ory/hydra/v2/fosite/handler/openid uses com/ory/hydra/v2/fositepart of a loop✕
Connections
32 pairs of types, where a type in com/ory/hydra/v2/fosite/handler/openid uses a type in com/ory/hydra/v2/fosite. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com/ory/hydra/v2/fosite/handler/openid uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/handler/openid, while a change to com/ory/hydra/v2/fosite/handler/openid can't break com/ory/hydra/v2/fosite.
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.
com/ory/x/servicelocatorx uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/x/servicelocatorx, while a change to com/ory/x/servicelocatorx can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/x/servicelocatorx uses a module listed above it, which is the healthy direction.
com/ory/x/servicelocatorx uses com/ory/x/contextx, so a change to com/ory/x/contextx can break com/ory/x/servicelocatorx, while a change to com/ory/x/servicelocatorx can't break com/ory/x/contextx.
Position
Below the diagonal: com/ory/x/servicelocatorx uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/compose uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/fosite/compose, while a change to com/ory/hydra/v2/fosite/compose can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/fosite/compose uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/compose uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fosite/compose, while a change to com/ory/hydra/v2/fosite/compose can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/fosite/compose uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/compose uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/fosite/compose, while a change to com/ory/hydra/v2/fosite/compose can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/fosite/compose uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/compose uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/fosite/compose, while a change to com/ory/hydra/v2/fosite/compose can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/fosite/compose uses a module listed above it, which is the healthy direction.
18→19 com/ory/hydra/v2/fosite/compose uses com/ory/hydra/v2/fositepart of a loop✕
Connections
12 pairs of types, where a type in com/ory/hydra/v2/fosite/compose uses a type in com/ory/hydra/v2/fosite.
com/ory/hydra/v2/fosite/compose uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/compose, while a change to com/ory/hydra/v2/fosite/compose can't break com/ory/hydra/v2/fosite.
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.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/fosite uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/fosite uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/fosite/token/hmac, so a change to com/ory/hydra/v2/fosite/token/hmac can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/fosite/token/hmac.
Position
Below the diagonal: com/ory/hydra/v2/fosite uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/fosite uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/fosite uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/fosite/compose, so a change to com/ory/hydra/v2/fosite/compose can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/fosite/compose.
Position
Below the diagonal: com/ory/hydra/v2/fosite uses a module listed above it, which is the healthy direction.
19→20 com/ory/hydra/v2/fosite uses com/ory/hydra/v2/aeadpart of a loop✕
Connections
1 pair of types, where a type in com/ory/hydra/v2/fosite uses a type in com/ory/hydra/v2/aead.
com/ory/hydra/v2/fosite uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/fosite, while a change to com/ory/hydra/v2/fosite can't break com/ory/hydra/v2/aead.
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.
com/ory/hydra/v2/aead uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/aead, while a change to com/ory/hydra/v2/aead can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/aead uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/pkce uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fosite/handler/pkce, while a change to com/ory/hydra/v2/fosite/handler/pkce can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/pkce uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/pkce uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/handler/pkce, while a change to com/ory/hydra/v2/fosite/handler/pkce can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/pkce uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/handler/verifiable uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/handler/verifiable, while a change to com/ory/hydra/v2/fosite/handler/verifiable can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/fosite/handler/verifiable uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/storage uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/fosite/storage, while a change to com/ory/hydra/v2/fosite/storage can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/fosite/storage uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/storage uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fosite/storage, while a change to com/ory/hydra/v2/fosite/storage can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/fosite/storage uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/storage uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/fosite/storage, while a change to com/ory/hydra/v2/fosite/storage can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/fosite/storage uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/storage uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/fosite/storage, while a change to com/ory/hydra/v2/fosite/storage can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/fosite/storage uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/storage uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fosite/storage, while a change to com/ory/hydra/v2/fosite/storage can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/fosite/storage uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fosite/storage uses com/ory/hydra/v2/fosite/handler/pkce, so a change to com/ory/hydra/v2/fosite/handler/pkce can break com/ory/hydra/v2/fosite/storage, while a change to com/ory/hydra/v2/fosite/storage can't break com/ory/hydra/v2/fosite/handler/pkce.
Position
Below the diagonal: com/ory/hydra/v2/fosite/storage uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/handler/pkce, so a change to com/ory/hydra/v2/fosite/handler/pkce can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/handler/pkce.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/handler/verifiable, so a change to com/ory/hydra/v2/fosite/handler/verifiable can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/handler/verifiable.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/x uses com/ory/hydra/v2/fosite/storage, so a change to com/ory/hydra/v2/fosite/storage can break com/ory/hydra/v2/x, while a change to com/ory/hydra/v2/x can't break com/ory/hydra/v2/fosite/storage.
Position
Below the diagonal: com/ory/hydra/v2/x uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/x/contextx, so a change to com/ory/x/contextx can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/x/contextx.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver/config uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/driver/config, while a change to com/ory/hydra/v2/driver/config can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/driver/config uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/jwk uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/jwk, while a change to com/ory/hydra/v2/jwk can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/jwk uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/x/pagination/keysetpagination_v2, so a change to com/ory/x/pagination/keysetpagination_v2 can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/x/pagination/keysetpagination_v2.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/fosite/token/hmac, so a change to com/ory/hydra/v2/fosite/token/hmac can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/fosite/token/hmac.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/client uses com/ory/hydra/v2/jwk, so a change to com/ory/hydra/v2/jwk can break com/ory/hydra/v2/client, while a change to com/ory/hydra/v2/client can't break com/ory/hydra/v2/jwk.
Position
Below the diagonal: com/ory/hydra/v2/client uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/hsm uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/hsm, while a change to com/ory/hydra/v2/hsm can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/hsm uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/hsm uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/hsm, while a change to com/ory/hydra/v2/hsm can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/hsm uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/hsm uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/hsm, while a change to com/ory/hydra/v2/hsm can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/hsm uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/hsm uses com/ory/hydra/v2/jwk, so a change to com/ory/hydra/v2/jwk can break com/ory/hydra/v2/hsm, while a change to com/ory/hydra/v2/hsm can't break com/ory/hydra/v2/jwk.
Position
Below the diagonal: com/ory/hydra/v2/hsm uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/x/pagination/keysetpagination_v2, so a change to com/ory/x/pagination/keysetpagination_v2 can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/x/pagination/keysetpagination_v2.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2/trust uses com/ory/hydra/v2/jwk, so a change to com/ory/hydra/v2/jwk can break com/ory/hydra/v2/oauth2/trust, while a change to com/ory/hydra/v2/oauth2/trust can't break com/ory/hydra/v2/jwk.
Position
Below the diagonal: com/ory/hydra/v2/oauth2/trust uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/flow uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/flow, while a change to com/ory/hydra/v2/flow can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/flow uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/flow uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/flow, while a change to com/ory/hydra/v2/flow can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/flow uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/flow uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/flow, while a change to com/ory/hydra/v2/flow can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/flow uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/flow uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/flow, while a change to com/ory/hydra/v2/flow can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/flow uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/flow uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/flow, while a change to com/ory/hydra/v2/flow can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/flow uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/flow uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/flow, while a change to com/ory/hydra/v2/flow can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/flow uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/kratos uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/internal/kratos, while a change to com/ory/hydra/v2/internal/kratos can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/internal/kratos uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/kratos uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/internal/kratos, while a change to com/ory/hydra/v2/internal/kratos can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/internal/kratos uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/kratos uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/internal/kratos, while a change to com/ory/hydra/v2/internal/kratos can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/internal/kratos uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/kratos uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/internal/kratos, while a change to com/ory/hydra/v2/internal/kratos can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/internal/kratos uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/kratos uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/internal/kratos, while a change to com/ory/hydra/v2/internal/kratos can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/internal/kratos uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/x/pagination/keysetpagination_v2, so a change to com/ory/x/pagination/keysetpagination_v2 can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/x/pagination/keysetpagination_v2.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/flow, so a change to com/ory/hydra/v2/flow can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/flow.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/consent uses com/ory/hydra/v2/internal/kratos, so a change to com/ory/hydra/v2/internal/kratos can break com/ory/hydra/v2/consent, while a change to com/ory/hydra/v2/consent can't break com/ory/hydra/v2/internal/kratos.
Position
Below the diagonal: com/ory/hydra/v2/consent uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/jwk, so a change to com/ory/hydra/v2/jwk can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/jwk.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/oauth2/trust, so a change to com/ory/hydra/v2/oauth2/trust can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/oauth2/trust.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/flow, so a change to com/ory/hydra/v2/flow can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/flow.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/oauth2 uses com/ory/hydra/v2/consent, so a change to com/ory/hydra/v2/consent can break com/ory/hydra/v2/oauth2, while a change to com/ory/hydra/v2/oauth2 can't break com/ory/hydra/v2/consent.
Position
Below the diagonal: com/ory/hydra/v2/oauth2 uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence uses com/ory/x/networkx, so a change to com/ory/x/networkx can break com/ory/hydra/v2/persistence, while a change to com/ory/hydra/v2/persistence can't break com/ory/x/networkx.
Position
Below the diagonal: com/ory/hydra/v2/persistence uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/persistence, while a change to com/ory/hydra/v2/persistence can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/persistence uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/persistence, while a change to com/ory/hydra/v2/persistence can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/persistence uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence uses com/ory/hydra/v2/oauth2/trust, so a change to com/ory/hydra/v2/oauth2/trust can break com/ory/hydra/v2/persistence, while a change to com/ory/hydra/v2/persistence can't break com/ory/hydra/v2/oauth2/trust.
Position
Below the diagonal: com/ory/hydra/v2/persistence uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence uses com/ory/hydra/v2/consent, so a change to com/ory/hydra/v2/consent can break com/ory/hydra/v2/persistence, while a change to com/ory/hydra/v2/persistence can't break com/ory/hydra/v2/consent.
Position
Below the diagonal: com/ory/hydra/v2/persistence uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/fosite/token/hmac, so a change to com/ory/hydra/v2/fosite/token/hmac can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/fosite/token/hmac.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/fosite/compose, so a change to com/ory/hydra/v2/fosite/compose can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/fosite/compose.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/fositex uses com/ory/hydra/v2/persistence, so a change to com/ory/hydra/v2/persistence can break com/ory/hydra/v2/fositex, while a change to com/ory/hydra/v2/fositex can't break com/ory/hydra/v2/persistence.
Position
Below the diagonal: com/ory/hydra/v2/fositex uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/x/pagination/keysetpagination_v2, so a change to com/ory/x/pagination/keysetpagination_v2 can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/x/pagination/keysetpagination_v2.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/x/popx, so a change to com/ory/x/popx can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/x/popx.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/x/contextx, so a change to com/ory/x/contextx can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/x/contextx.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/x/networkx, so a change to com/ory/x/networkx can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/x/networkx.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite/handler/pkce, so a change to com/ory/hydra/v2/fosite/handler/pkce can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite/handler/pkce.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/fosite/handler/verifiable, so a change to com/ory/hydra/v2/fosite/handler/verifiable can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/fosite/handler/verifiable.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/jwk, so a change to com/ory/hydra/v2/jwk can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/jwk.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/oauth2/trust, so a change to com/ory/hydra/v2/oauth2/trust can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/oauth2/trust.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/flow, so a change to com/ory/hydra/v2/flow can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/flow.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/internal/kratos, so a change to com/ory/hydra/v2/internal/kratos can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/internal/kratos.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/consent, so a change to com/ory/hydra/v2/consent can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/consent.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/oauth2, so a change to com/ory/hydra/v2/oauth2 can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/persistence/sql uses com/ory/hydra/v2/persistence, so a change to com/ory/hydra/v2/persistence can break com/ory/hydra/v2/persistence/sql, while a change to com/ory/hydra/v2/persistence/sql can't break com/ory/hydra/v2/persistence.
Position
Below the diagonal: com/ory/hydra/v2/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/handler/rfc7523, so a change to com/ory/hydra/v2/fosite/handler/rfc7523 can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/handler/rfc7523.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/token/hmac, so a change to com/ory/hydra/v2/fosite/token/hmac can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/token/hmac.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/popx, so a change to com/ory/x/popx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/popx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/handler/oauth2, so a change to com/ory/hydra/v2/fosite/handler/oauth2 can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/handler/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/handler/rfc8628, so a change to com/ory/hydra/v2/fosite/handler/rfc8628 can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/handler/rfc8628.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/contextx, so a change to com/ory/x/contextx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/contextx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/handler/openid, so a change to com/ory/hydra/v2/fosite/handler/openid can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/handler/openid.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/x/servicelocatorx, so a change to com/ory/x/servicelocatorx can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/x/servicelocatorx.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/aead, so a change to com/ory/hydra/v2/aead can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/aead.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/handler/pkce, so a change to com/ory/hydra/v2/fosite/handler/pkce can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/handler/pkce.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fosite/handler/verifiable, so a change to com/ory/hydra/v2/fosite/handler/verifiable can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fosite/handler/verifiable.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/jwk, so a change to com/ory/hydra/v2/jwk can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/jwk.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/hsm, so a change to com/ory/hydra/v2/hsm can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/hsm.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/oauth2/trust, so a change to com/ory/hydra/v2/oauth2/trust can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/oauth2/trust.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/flow, so a change to com/ory/hydra/v2/flow can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/flow.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/internal/kratos, so a change to com/ory/hydra/v2/internal/kratos can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/internal/kratos.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/consent, so a change to com/ory/hydra/v2/consent can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/consent.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/oauth2, so a change to com/ory/hydra/v2/oauth2 can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/oauth2.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/persistence, so a change to com/ory/hydra/v2/persistence can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/persistence.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/fositex, so a change to com/ory/hydra/v2/fositex can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/fositex.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/driver uses com/ory/hydra/v2/persistence/sql, so a change to com/ory/hydra/v2/persistence/sql can break com/ory/hydra/v2/driver, while a change to com/ory/hydra/v2/driver can't break com/ory/hydra/v2/persistence/sql.
Position
Below the diagonal: com/ory/hydra/v2/driver uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/cmd/cli uses com/ory/hydra/v2/persistence, so a change to com/ory/hydra/v2/persistence can break com/ory/hydra/v2/cmd/cli, while a change to com/ory/hydra/v2/cmd/cli can't break com/ory/hydra/v2/persistence.
Position
Below the diagonal: com/ory/hydra/v2/cmd/cli uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/cmd/cli uses com/ory/hydra/v2/persistence/sql, so a change to com/ory/hydra/v2/persistence/sql can break com/ory/hydra/v2/cmd/cli, while a change to com/ory/hydra/v2/cmd/cli can't break com/ory/hydra/v2/persistence/sql.
Position
Below the diagonal: com/ory/hydra/v2/cmd/cli uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/cmd/cli uses com/ory/hydra/v2/driver, so a change to com/ory/hydra/v2/driver can break com/ory/hydra/v2/cmd/cli, while a change to com/ory/hydra/v2/cmd/cli can't break com/ory/hydra/v2/driver.
Position
Below the diagonal: com/ory/hydra/v2/cmd/cli uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/cmd/server uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/hydra/v2/cmd/server, while a change to com/ory/hydra/v2/cmd/server can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/hydra/v2/cmd/server uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/cmd/server uses com/ory/x/metricsx, so a change to com/ory/x/metricsx can break com/ory/hydra/v2/cmd/server, while a change to com/ory/hydra/v2/cmd/server can't break com/ory/x/metricsx.
Position
Below the diagonal: com/ory/hydra/v2/cmd/server uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/cmd/server uses com/ory/hydra/v2/driver, so a change to com/ory/hydra/v2/driver can break com/ory/hydra/v2/cmd/server, while a change to com/ory/hydra/v2/cmd/server can't break com/ory/hydra/v2/driver.
Position
Below the diagonal: com/ory/hydra/v2/cmd/server uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/fosite/token/jwt, so a change to com/ory/hydra/v2/fosite/token/jwt can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/fosite/token/jwt.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/fosite, so a change to com/ory/hydra/v2/fosite can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/fosite.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/x, so a change to com/ory/hydra/v2/x can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/x.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/driver/config, so a change to com/ory/hydra/v2/driver/config can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/driver/config.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/client, so a change to com/ory/hydra/v2/client can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/client.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/oauth2/trust, so a change to com/ory/hydra/v2/oauth2/trust can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/oauth2/trust.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/hydra/v2/internal/testhelpers uses com/ory/hydra/v2/driver, so a change to com/ory/hydra/v2/driver can break com/ory/hydra/v2/internal/testhelpers, while a change to com/ory/hydra/v2/internal/testhelpers can't break com/ory/hydra/v2/driver.
Position
Below the diagonal: com/ory/hydra/v2/internal/testhelpers uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64.0 · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
2102
High / Critical
A05:2025 — Injection
82
High / Critical
A03:2025 — Software Supply Chain Failures
57
High / Critical
A02:2025 — Security Misconfiguration
48
High / Critical
Roadmap
Top priorities: Resolve the 765 REDACTED finding(s) in Secrets (history) — start with REDACTED (39), REDACTED (38), REDACTED (36); Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive; Resolve the 24 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (19), REDACTED (4), REDACTED.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No network policy finding(s) in Network Egress Confinement.
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Per-file score 0–10 — a quality signature. Of 423 files carrying findings, judged against the Production bar: 53% slop · 34% mixed · 13% near-clean.
File
Score
Band
Worst signal
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
REDACTED Scanning: Leaked secret: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 2189
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 — 452
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 — 139
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 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 — 58 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, 2675 of 2780 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — the repository root (cypress) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`go test -coverprofile`) shows coverage is measured in your own CI.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — 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 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.
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. `oryx/jsonx/patch.go`, `oryx/otelx/attribute.go`, `oryx/otelx/semconv/context.go`, `oryx/otelx/semconv/events.go`, `oryx/pagination/keysetpagination/paginator.go`, … (+2 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.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run start` in test/e2e/oauth2-client/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "info: HTTP GET / {"meta":{"req":{"headers":{"accept":"*/*","host":"127.0.0.1:5003","user-agent":"curl/8.5.0"},"httpVersion":"1.1","method":"GET","originalUrl":"/","query":{},"url":"/"},"res":{"statusCode":404},"responseTime":1}} / info: HTTP GET / {"meta":{"req":{"headers":{"accept":"*/*","host":"127.0.0.1:5003","user-agent":"curl/8.5.0"},"httpVersion":"1.1","method":"GET","originalUrl":"/","query":{},"url":"/"},"res":{"statusCode":404},"responseTime":0}}" 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` in test/e2e/oauth2-client/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "info: HTTP GET / {"meta":{"req":{"headers":{"accept":"*/*","host":"127.0.0.1:5003","user-agent":"curl/8.5.0"},"httpVersion":"1.1","method":"GET","originalUrl":"/","query":{},"url":"/"},"res":{"statusCode":404},"responseTime":1}} / info: HTTP GET / {"meta":{"req":{"headers":{"accept":"*/*","host":"127.0.0.1:5003","user-agent":"curl/8.5.0"},"httpVersion":"1.1","method":"GET","originalUrl":"/","query":{},"url":"/"},"res":{"statusCode":404},"responseTime":0}}" 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 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
Repo exclusion declarations: 37 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with jsonschemax.listPaths (cyclomatic 62), Validator.Validate (cyclomatic 52), Fosite.DefaultClientAuthenticationStrategy (cyclomatic 52). — 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 8 together lifts Cyclomatic Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 58 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with decoderx.decodeURLValues (cognitive 117), jsonschemax.listPaths (cognitive 95), Validator.Validate (cognitive 79). — 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 6 together lifts Cognitive Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 TooManyMethods finding(s) in God Classes — start with provider.go, persister.go, registry_sql.go. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 TooManyFields finding(s) in God Classes — start with config_default.go, client.go, registry_sql.go. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with strategy_default.go (2), client_authentication.go, migrator.go. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
87 duplicated block group(s) detected. 7.1 % of the production lines (3,872 of 54,243) are in a reported copy. A further 79 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 6 of the 166 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (23 corresponding lines) · ×4client/handler.go:908
+ 71 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with persister_device.go (2), cmd_create_client.go, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with types.go (3), manager_test_helpers.go (2), migrator.go. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
5 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 3 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: github.com/ory/x
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with config_default.go, REDACTED, client.go. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d6_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.
81 outdated, 3 author-deprecated direct Go module(s), 7 pinning or checksum defect(s). 149 of 149 direct requirement(s) were graded against proxy.golang.org (0 not served there, 7 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.
Dependency pinned to a stale untagged commit: github.com/asaskevich/govalidator · ×7
Resolve the 7 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 3 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
548 secret(s) detected. 8 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material. 5 password hash(es) are listed to check and are not counted as leaked credentials.
REDACTED
REDACTED
What to do
Resolve the 1326 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (86), REDACTED (62), REDACTED (62). — One of this dimension's main actionable groups (1326 issue-level).
Resolve the 5 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 367 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 367 package(s) this repository's committed lockfile installs for a consumer — its 13 production, optional and peer dependency(ies), across 3 product REDACTED manifest(s), and everything those install in turn. Its 16 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 2 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. Third-party code that ships WITHOUT a manifest entry was read too: 1 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), 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.
Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with migrator.go, validator.go, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is oryx/proxy/proxy.go. Counted over 214 of the 526 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
16 deducted task-comment markers across 54243 LoC (0.0/KLoC) → score 9.9. 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 · ×14x/sqlx.go:78
HackCommenttest/mock-client/main.go:77
FixmeCommentoryx/mailhog/memory.go:51
What to do
Resolve the 14 TodoComment finding(s) in Explicit Debt — start with flow.go (3), validator.go (2), sqlx.go. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with main.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with REDACTED. — 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.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 25 declarations measured against a convention their peers follow.
`instanceId` spells `Id` where 23 names in the project spell it `ID`oryx/metricsx/middleware.go:52
`DeploymentId` spells `Id` where 23 names in the project spell it `ID`oryx/metricsx/middleware.go:74
What to do
Resolve the 1 `instanceId` spells `Id` where 23 names in the project spell it `ID` finding(s) in Naming Consistency — start with middleware.go. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `DeploymentId` spells `Id` where 23 names in the project spell it `ID` finding(s) in Naming Consistency — start with middleware.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 538 exposed members measured against a convention their peers follow.
`MigrationBox.SelectedMigrations` takes no context.Context; its 6 sibling operations take oneoryx/popx/migration_box.go:240
What to do
Resolve the 1 `MigrationBox.SelectedMigrations` takes no context.Context; its 6… finding(s) in Internal API Consistency — start with migration_box.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.
3 of 4 build units (Go, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3REDACTED:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability7.0 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
70 % of calls cross a namespace and 27 % go through an interface, but 54 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
Scattered collaborators
What to do
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
777 finding(s): 0 critical, 774 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 765 REDACTED finding(s) in Secrets (history) — start with REDACTED (39), REDACTED (38), REDACTED (36). — One of this dimension's main actionable groups (765 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
82 finding(s): 0 critical, 74 high, 5 medium, 3 low. 45 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 8 file(s) — `internal/testhelpers/uuid/uuid.go` (line 14), `oryx/jsonx/patch.go` (line 78), `oryx/otelx/attribute.go` (line 23, line 28, line 45), `oryx/otelx/semconv/context.go` (line 49), `oryx/otelx/semconv/events.go` (line 42, line 88, line 92, …), … (+3 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (11), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (18 issue-level).
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
No action in Static Analysis (SAST) — all 45 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (45 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 24 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (19), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 17 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (17 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 34 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (26), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (34 warning-level).
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 11 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (11 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
5 of 214 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is persistence/sql/persister_device.go. Counted over 214 of the 526 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
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 issue-level).
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
0/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.
No seccomp profileREDACTED:1
What to do
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 1 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.
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.
`RFC6749Error` is shared by every request (`WithHintf` is called per request from the net/http handler `Handler.oauth2TokenExchange`, on the one `RFC6749Error` value that handler's shared receiver holds) but writes its fields outside any lock (hintIDField, hintArgs, HintField; e.g. `hintIDField` in `WithHintf` at line 395). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process. — fosite/errors.go:272
`Logger` is shared by every request (`WithField` is called per request from the net/http handler `Handler.oauth2TokenExchange`, on the one `Logger` value that handler's shared receiver holds) but writes its fields outside any lock (Entry; e.g. `Entry` in `WithField` at line 218). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process. — oryx/logrusx/helper.go:37
What to do
Go: guard the state handlers share with a sync.Mutex held for the whole update (`mu.Lock(); defer mu.Unlock()`), make counters sync/atomic types (atomic.Int64) and caches a sync.Map, or keep per-request data in locals and the request context. `go test -race` over a handler test confirms the race and then its fix.
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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
`OAuth2Provider` declares 21 methods: `NewAuthorizeRequest`, `NewAuthorizeResponse`, `WriteAuthorizeError`, `WriteAuthorizeResponse`, `NewAccessRequest`, `NewAccessResponse`, `WriteAccessError`, `WriteAccessResponse`, `NewDeviceRequest`, `NewDeviceResponse`, `WriteDeviceResponse`, `NewRevocationRequest`, `WriteRevocationResponse`, `IntrospectToken`, `NewIntrospectionRequest`, `WriteIntrospectionError`, `WriteIntrospectionResponse`, `NewPushedAuthorizeRequest`, `NewPushedAuthorizeResponse`, `WritePushedAuthorizeResponse`, `WritePushedAuthorizeError`. 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. — fosite/oauth2.go:44
`Requester` declares 18 methods: `SetID`, `GetID`, `GetRequestedAt`, `GetClient`, `GetRequestedScopes`, `GetRequestedAudience`, `SetRequestedScopes`, `SetRequestedAudience`, `AppendRequestedScope`, `GetGrantedScopes`, `GetGrantedAudience`, `GrantScope`, `GrantAudience`, `GetSession`, `SetSession`, `GetRequestForm`, `Merge`, `Sanitize`. 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. — fosite/oauth2.go:223
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.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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 key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
fosite/README.md names Go 1.11 or later, but REDACTED:3 requires `go 1.25.0` (the lowest of 4 declarations): the code does not build on Go 1.11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — fosite/README.md:173
What to do
Reconcile the README with reality: fosite/README.md names Go 1.11 or later, but REDACTED:3 requires `go 1.25.0` (the lowest of 4 declarations): the code does not build on Go 1.11.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `oryx/randx/strength`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — x/hasher_test.go
What to do
Call b.ReportAllocs() in the benchmarks, or run them with `go test -bench . -benchmem`, so allocation regressions are visible, not just time.
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.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen. Whether a `for … range` leaves the slice or map it is walking alone — Go raises nothing, but the walk and the collection part: a range evaluates its slice once, so an element appended in the body is never visited and a removal by reslicing (`s = append(s[:i], s[i+1:]...)`, `slices.Delete`) shifts the next element under the index, which is then skipped while the last is read twice; a reslice, a reassignment or a sort leaves every later `s[i]` naming another element; and a map's order is unspecified, so deleting another key (or clearing the map) changes from run to run which entries the loop still sees.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard6.6 / 10Adequate✓ Tool-verified
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
`parts` holds what `Split` returns, and `parts[0]` takes element 0 of it without checking its length — while this file tests that same result elsewhere before indexing it, because it can be nil or shorter. Here a short result panics with `index out of range`. Test `len(parts)` (or nil) first, as the other call site does. — oryx/urlx/parse.go:104
What to do
Each finding names the index access that escapes the guard and the line of the correctly bracketed access beside it. Compare the two: they differ only in where one parenthesis sits. Move it so the emptiness test brackets every access to that symbol — and if the value provably cannot be empty at this point, delete the test rather than leave a condition that guards one access and not its neighbour.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`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. (×20) — x/oauth2cors/cors.go:113, x/oauth2cors/cors.go:121, x/oauth2cors/cors.go:141, …
`if _, err := os.Lstat(watchedFile); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here. — oryx/watcherx/file.go:57
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — oryx/prometheusx/exemplar.go:41, oryx/prometheusx/exemplar.go:58
`if offset64, err := strconv.ParseInt(offsetParam, 10, 64); 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. — oryx/pagination/parse.go:18
`if limit64, err := strconv.ParseInt(limitParam, 10, 64); 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. — oryx/pagination/parse.go:28
`offset, _ = decode(offsetParam)` writes the call's error to `_` and then uses `offset` as if the call succeeded. When `decode` fails, `offset` 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 `offset` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/pagination/tokenpagination/pagination.go:55
`if offset, err := strconv.ParseInt(offsetParam, 10, 0); 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. — oryx/pagination/pagepagination/pagination.go:37
`if limit, err := strconv.ParseInt(limitParam, 10, 0); 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. — oryx/pagination/pagepagination/pagination.go:47
`optOut, _ = strconv.ParseBool(os.Getenv("SQA_OPT_OUT"))` writes the call's error to `_` and then uses `optOut` as if the call succeeded. When `strconv.ParseBool` fails, `optOut` 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 `optOut` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/metricsx/middleware.go:178
`optOut, _ = strconv.ParseBool(os.Getenv("SQA-OPT-OUT"))` writes the call's error to `_` and then uses `optOut` as if the call succeeded. When `strconv.ParseBool` fails, `optOut` 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 `optOut` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/metricsx/middleware.go:182
`def, _ = v.Float64()` writes the call's error to `_` and then uses `def` as if the call succeeded. When `v.Float64` fails, `def` 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 `def` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/jsonschemax/keys.go:302
`jsonnetBinaryPath, _ := os.Executable()` writes the call's error to `_` and then uses `jsonnetBinaryPath` as if the call succeeded. When `os.Executable` fails, `jsonnetBinaryPath` 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 `jsonnetBinaryPath` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/jsonnetsecure/jsonnet.go:55
`host, _, _ := net.SplitHostPort(address)` writes the call's error to `_` and then uses `host` as if the call succeeded. When `net.SplitHostPort` fails, `host` 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 `host` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/ipx/ssrf.go:75
`ip, _ := GetClientIPAddressesWithoutInternalIPs(strings.Split(forwardedIP, ","))` writes the call's error to `_` and then uses `ip` as if the call succeeded. When `GetClientIPAddressesWithoutInternalIPs` fails, `ip` 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 `ip` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/httpx/client_info.go:44
`f, _ := ToFloatSliceE(i)` writes the call's error to `_` and then uses `f` as if the call succeeded. When `ToFloatSliceE` fails, `f` 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 `f` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/castx/castx.go:17
`s, _ := ToStringSliceE(i)` writes the call's error to `_` and then uses `s` as if the call succeeded. When `ToStringSliceE` fails, `s` 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 `s` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — oryx/castx/castx.go:52
`res, ok := pk.Key.(*rsa.PublicKey)` failed on this branch, so `res` is the zero value of `*rsa.PublicKey` here, and that is what is reported: the value that did not fit is lost. Report `pk.Key` itself (and `%T` of it) instead. — jwk/cast.go:28
`res, ok := key.Key.(*rsa.PrivateKey)` failed on this branch, so `res` is the zero value of `*rsa.PrivateKey` here, and that is what is reported: the value that did not fit is lost. Report `key.Key` itself (and `%T` of it) instead. — jwk/cast.go:46
`e, ok := err.(*ValidationError)` failed on this branch, so `e` is the zero value of `*ValidationError` here, and that is what is reported: the value that did not fit is lost. Report `err` itself (and `%T` of it) instead. — fosite/token/jwt/token.go:225
`if err := v.Init(); 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. — fosite/i18n/default_catalog.go:41
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
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 — 7 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 — 54 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 — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Ruby 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.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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` in test/e2e/oauth2-client/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "info: HTTP GET / {"meta":{"req":{"headers":{"accept":"*/*","host":"127.0.0.1:5003","user-agent":"curl/8.5.0"},"httpVersion":"1.1","method":"GET","originalUrl":"/","query":{},"url":"/"},"res":{"statusCode":404},"responseTime":1}} / info: HTTP GET / {"meta":{"req":{"headers":{"accept":"*/*","host":"127.0.0.1:5003","user-agent":"curl/8.5.0"},"httpVersion":"1.1","method":"GET","originalUrl":"/","query":{},"url":"/"},"res":{"statusCode":404},"responseTime":0}}" 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 — ~42286 lines of test source are present (.go, .js) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 withholds "Go doc-comment coverage": 112 candidate(s) (56 of them library packages documenting under half of their exported API; package comments and Example functions count) were measured and not published.
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, .rb source were not judged.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 7 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one; 12 persistence-mapped domain entity/entities (gorm/bun/db/xorm-tagged)
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 CQRS handler(s); 3 domain event(s)
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.
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Swallowed exception (caught, then discarded) x/oauth2cors/cors.go:113— `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) x/oauth2cors/cors.go:121— `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) x/oauth2cors/cors.go:141— `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) persistence/sql/persister_grant_jwk.go:292— `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) oryx/urlx/extract.go:62— `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) oryx/urlx/extract.go:115— `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) oryx/pagination/parse.go:18— `if offset64, err := strconv.ParseInt(offsetParam, 10, 64); 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) oryx/pagination/parse.go:28— `if limit64, err := strconv.ParseInt(limitParam, 10, 64); 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) oryx/pagination/pagepagination/pagination.go:37— `if offset, err := strconv.ParseInt(offsetParam, 10, 0); 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) oryx/pagination/pagepagination/pagination.go:47— `if limit, err := strconv.ParseInt(limitParam, 10, 0); 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) oryx/pagination/keysetpagination_v2/parse_header.go:25— `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) oryx/pagination/keysetclient/parse_header.go:39— `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) oryx/mapx/type_assert.go:143— `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) oryx/logrusx/logrus.go:90— `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) oryx/landlockx/landlockx.go:31— `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) oryx/jsonschemax/print.go:67— `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) oryx/httpx/client_info.go:57— `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) oryx/httpx/content_type.go:24— `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) oryx/cookiex/cookiex.go:246— `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) fosite/authorize_helper.go:101— `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) fosite/authorize_helper.go:119— `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) fosite/authorize_request.go:53— `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) fosite/token/jwt/map_claims.go:97— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:535— `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) fosite/i18n/default_catalog.go:41— `if err := v.Init(); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D30 · Dependency Vulnerabilities· Medium CVE · ×24
TodoComment x/sqlx.go:78— // TODO delete this type and replace it with ory/x/sqlxx/NullDuration when applying the custom client token TTL patch to Hydra 2.x — 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 persistence/sql/persister_grant_jwk.go:191— // TODO: Consider merging this query with the one above using a `JOIN`. — 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 persistence/sql/persister_test.go:37— // TODO enable parallel tests for mysql once we support automatic transaction retries — 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 oryx/jsonnetsecure/limit_windows.go:14— // TODO No OS limit for now. Apparently there is a Windows-specific equivalent (Job control)? — 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 oryx/corsx/check_origin.go:20— // TODO: legacyAllowInsecureOrigins grandfathers a fixed set of projects through — 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 oauth2/handler.go:172— // TODO How are we supposed to test this? Maybe with cypress? #1368
TodoComment fosite/integration/refresh_token_grant_test.go:211— // t.Parallel() TODO remove side-effects on the fosite store clients to make this parallel — 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 fosite/handler/oauth2/introspector_jwt.go:77— // TODO: From here we assume it is an access token, but how do we know it is really and that is not an ID token? — 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 flow/encoding_test.go:61— // TODO? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment flow/flow.go:78— // TODO: Refactor error handling to persist error codes instead of JSON — 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 flow/flow.go:108— // TODO: Deprecate the structs that are made obsolete by the Flow concept. — 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 flow/flow.go:485— // TODO Populate the client field in FindInDB and FindByConsentChallengeID in — 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 client/validator.go:101— // TODO: For clients that support dynamic registration, validate that each of these URIs are part of the redirect_uris, as per the spec. — 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 client/validator.go:105— // TODO: In addition, the logo_uri should be a valid image. — 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.
Duplicated block (6 lines × 2) client/handler.go:466— client/handler.go:466-471 | client/handler.go:759-764 — 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 `client/handler.go:466` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:482— REDACTED:482-487 | REDACTED:519-524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:482` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (6 lines × 2) oryx/cmdx/printing.go:104— oryx/cmdx/printing.go:104-109 | oryx/cmdx/printing.go:167-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `oryx/cmdx/printing.go:104` 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, `oryx/cmdx/printing.go:103` calls `printYAML`, `Interface` and `oryx/cmdx/printing.go:166` 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 × 2) oryx/decoderx/http.go:455— oryx/decoderx/http.go:455-460 | oryx/decoderx/http.go:480-485 — 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 `oryx/decoderx/http.go:455` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) oryx/popx/migrator.go:239— oryx/popx/migrator.go:239-244 | oryx/popx/migrator.go:249-254 — 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 `oryx/popx/migrator.go:239` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) oryx/decoderx/http.go:406— oryx/decoderx/http.go:406-411 | oryx/decoderx/http.go:426-431 — 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 `oryx/decoderx/http.go:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) fosite/handler/oauth2/helper.go:39— fosite/handler/oauth2/helper.go:39-44 | fosite/handler/rfc8628/token_handler.go:291-296 — 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) fosite/handler/oauth2/strategy_jwt_session.go:48— fosite/handler/oauth2/strategy_jwt_session.go:48-53 | fosite/handler/openid/strategy_jwt.go:60-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) persistence/sql/persister_client.go:23— persistence/sql/persister_client.go:23-28 | persistence/sql/persister_client.go:122-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (6 lines × 2) persistence/sql/persister_oauth2.go:128— persistence/sql/persister_oauth2.go:128-133 | persistence/sql/persister_oauth2.go:163-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_oauth2.go:128` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also 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 (6 lines × 2) hsm/manager_hsm.go:92— hsm/manager_hsm.go:92-97 | jwk/manager_strategy.go:35-40 — 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 `hsm/manager_hsm.go:92` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also 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 (9 lines × 2) cmd/cmd_create_client.go:76— cmd/cmd_create_client.go:76-84 | cmd/cmd_import_client.go:62-70 — 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 `cmd/cmd_create_client.go:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) REDACTED:53— REDACTED:53-61 | REDACTED:73-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fosite/handler/openid/flow_refresh_token.go:28— fosite/handler/openid/flow_refresh_token.go:28-36 | fosite/handler/openid/flow_refresh_token.go:66-74 — 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 `fosite/handler/openid/flow_refresh_token.go:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) oryx/decoderx/http.go:413— oryx/decoderx/http.go:413-421 | oryx/decoderx/http.go:433-441 — 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 `oryx/decoderx/http.go:413` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) oryx/josex/generate.go:34— oryx/josex/generate.go:34-42 | oryx/jwksx/generator.go:56-64 — 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 `oryx/josex/generate.go:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) persistence/sql/persister_device.go:125— persistence/sql/persister_device.go:125-133 | persistence/sql/persister_oauth2.go:256-264 — before extracting anything, compare `persistence/sql/persister_device.go` and `persistence/sql/persister_oauth2.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) oryx/popx/cmd.go:97— oryx/popx/cmd.go:97-105 | oryx/popx/cmd.go:207-215 — 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 `oryx/popx/cmd.go:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) persistence/sql/persister_device.go:141— persistence/sql/persister_device.go:141-149 | persistence/sql/persister_oauth2.go:284-292 — before extracting anything, compare `persistence/sql/persister_device.go` and `persistence/sql/persister_oauth2.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) oryx/pagination/parse.go:15— oryx/pagination/parse.go:15-23 | oryx/pagination/parse.go:25-33 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) oryx/popx/migrator.go:394— oryx/popx/migrator.go:394-400 | oryx/popx/migrator.go:405-411 — 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 `oryx/popx/migrator.go:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) oryx/sqlxx/types.go:331— oryx/sqlxx/types.go:331-337 | x/sqlx.go:24-30 — before extracting anything, compare `oryx/sqlxx/types.go` and `x/sqlx.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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 (7 lines × 2) oryx/sqlxx/types.go:340— oryx/sqlxx/types.go:340-346 | x/sqlx.go:32-38 — before extracting anything, compare `oryx/sqlxx/types.go` and `x/sqlx.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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 (7 lines × 2) oryx/sqlxx/types.go:587— oryx/sqlxx/types.go:587-593 | x/sqlx.go:107-113 — before extracting anything, compare `oryx/sqlxx/types.go` and `x/sqlx.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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 (7 lines × 2) consent/handler.go:363— consent/handler.go:363-370 | consent/handler.go:452-458 — 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 `consent/handler.go:363` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) persistence/sql/persister_device.go:58— persistence/sql/persister_device.go:58-64 | persistence/sql/persister_oauth2.go:81-87 — before extracting anything, compare `persistence/sql/persister_device.go` and `persistence/sql/persister_oauth2.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_device.go:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (7 lines × 2) oryx/decoderx/http.go:462— oryx/decoderx/http.go:462-468 | oryx/decoderx/http.go:487-493 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `oryx/decoderx/http.go:462` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) oauth2/trust/manager_test_helpers.go:31— oauth2/trust/manager_test_helpers.go:31-37 | oauth2/trust/manager_test_helpers.go:147-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) oauth2/trust/manager_test_helpers.go:105— oauth2/trust/manager_test_helpers.go:105-111 | oauth2/trust/manager_test_helpers.go:116-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: Config (LCOM4 22) fosite/config_default.go:71— Config's methods fall into 22 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 22 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MemoryStore (LCOM4 10) REDACTED:49— MemoryStore's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Client (LCOM4 8) client/client.go:35— Client's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RegistrySQL (LCOM4 7) driver/registry_sql.go:60— RegistrySQL's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Fosite (LCOM4 6) fosite/fosite.go:160— Fosite's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DefaultSession (LCOM4 6) fosite/handler/openid/strategy_jwt.go:35— DefaultSession's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: JWTSession (LCOM4 5) fosite/handler/oauth2/strategy_jwt_session.go:26— JWTSession's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DefaultSession (LCOM4 5) fosite/session.go:36— DefaultSession's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Logger (LCOM4 4) oryx/logrusx/helper.go:37— Logger's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×9
Discarded error (assigned to `_`, then its result used) oryx/pagination/tokenpagination/pagination.go:55— `offset, _ = decode(offsetParam)` writes the call's error to `_` and then uses `offset` as if the call succeeded. When `decode` fails, `offset` 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 `offset` (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) oryx/metricsx/middleware.go:178— `optOut, _ = strconv.ParseBool(os.Getenv("SQA_OPT_OUT"))` writes the call's error to `_` and then uses `optOut` as if the call succeeded. When `strconv.ParseBool` fails, `optOut` 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 `optOut` (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) oryx/metricsx/middleware.go:182— `optOut, _ = strconv.ParseBool(os.Getenv("SQA-OPT-OUT"))` writes the call's error to `_` and then uses `optOut` as if the call succeeded. When `strconv.ParseBool` fails, `optOut` 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 `optOut` (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) oryx/jsonschemax/keys.go:302— `def, _ = v.Float64()` writes the call's error to `_` and then uses `def` as if the call succeeded. When `v.Float64` fails, `def` 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 `def` (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) oryx/jsonnetsecure/jsonnet.go:55— `jsonnetBinaryPath, _ := os.Executable()` writes the call's error to `_` and then uses `jsonnetBinaryPath` as if the call succeeded. When `os.Executable` fails, `jsonnetBinaryPath` 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 `jsonnetBinaryPath` (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) oryx/ipx/ssrf.go:75— `host, _, _ := net.SplitHostPort(address)` writes the call's error to `_` and then uses `host` as if the call succeeded. When `net.SplitHostPort` fails, `host` 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 `host` (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) oryx/httpx/client_info.go:44— `ip, _ := GetClientIPAddressesWithoutInternalIPs(strings.Split(forwardedIP, ","))` writes the call's error to `_` and then uses `ip` as if the call succeeded. When `GetClientIPAddressesWithoutInternalIPs` fails, `ip` 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 `ip` (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) oryx/castx/castx.go:17— `f, _ := ToFloatSliceE(i)` writes the call's error to `_` and then uses `f` as if the call succeeded. When `ToFloatSliceE` fails, `f` 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 `f` (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) oryx/castx/castx.go:52— `s, _ := ToStringSliceE(i)` writes the call's error to `_` and then uses `s` as if the call succeeded. When `ToStringSliceE` fails, `s` 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 `s` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×7
Dependency pinned to a stale untagged commit: github.com/asaskevich/govalidator — Direct dependency `github.com/asaskevich/govalidator` is required at `v0.0.0-20230301143203-a9d515a09cc2` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2023-03-01, 3.7 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/asaskevich/govalidator` and has not moved this requirement in 3.7 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/asaskevich/govalidator` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/mohae/deepcopy — Direct dependency `github.com/mohae/deepcopy` is required at `v0.0.0-20170929034955-c48cc78d4826` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2017-09-29, 9.1 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/mohae/deepcopy` and has not moved this requirement in 9.1 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/mohae/deepcopy` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/ory/go-acc — Direct dependency `github.com/ory/go-acc` is required at `v0.2.9-0.20230103102148-6b1c9a70dbbe` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2023-01-03, 3.9 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/ory/go-acc` and has not moved this requirement in 3.9 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/ory/go-acc` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/tomnomnom/linkheader — Direct dependency `github.com/tomnomnom/linkheader` is required at `v0.0.0-20180905144013-02ca5825eb80` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2018-09-05, 8.2 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/tomnomnom/linkheader` and has not moved this requirement in 8.2 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/tomnomnom/linkheader` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/inhies/go-bytesize — Direct dependency `github.com/inhies/go-bytesize` is required at `v0.0.0-20220417184213-4913239db9cf` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-04-17, 4.6 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/inhies/go-bytesize` and has not moved this requirement in 4.6 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/inhies/go-bytesize` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/mohae/deepcopy — Direct dependency `github.com/mohae/deepcopy` is required at `v0.0.0-20170929034955-c48cc78d4826` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2017-09-29, 9.1 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/mohae/deepcopy` and has not moved this requirement in 9.1 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/mohae/deepcopy` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/seatgeek/logrus-gelf-formatter — Direct dependency `github.com/seatgeek/logrus-gelf-formatter` is required at `v0.0.0-20210414080842-5b05eb8ff761` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2021-04-14, 5.6 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/seatgeek/logrus-gelf-formatter` and has not moved this requirement in 5.6 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/seatgeek/logrus-gelf-formatter` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
TooManyMethods: DefaultProvider driver/config/provider.go:135— TooManyMethods — 104 methods, declared across 3 files: config/provider.go (89), config/provider_fosite.go (11), config/serve.go (4). The bar is 30 methods; this is 74 over it, 3.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Persister persistence/sql/persister.go:36— TooManyMethods — 74 methods, declared across 7 files: sql/persister_oauth2.go (33), sql/persister_consent.go (14), sql/persister_grant_jwk.go (10), sql/persister_client.go (7), +3 more file(s). The bar is 30 methods; this is 44 over it, 2.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RegistrySQL driver/registry_sql.go:60— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Config fosite/config_default.go:71— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MemoryStore REDACTED:49— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Fosite fosite/fosite.go:160— TooManyMethods — 39 methods, declared across 20 files: fosite/authorize_request_handler.go (10), fosite/client_authentication.go (4), fosite/pushed_authorize_response_writer.go (3), fosite/access_error.go (2), +16 more file(s). The bar is 30 methods; this is 9 over it, 1.30× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Config fositex/config.go:38— 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.
Hotspot: oryx/popx/migrator.go oryx/popx/migrator.go:127— oryx/popx/migrator.go changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in MigrationBox.UpTo at line 127. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- oryx/popx/migrator.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: client/validator.go client/validator.go:54— client/validator.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in Validator.Validate at line 54. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- client/validator.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:46— REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in popx.TransactionWithOptions at line 46. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: consent/strategy_default.go consent/strategy_default.go:782— consent/strategy_default.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in defaultStrategy.issueLogoutVerifier at line 782. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- consent/strategy_default.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: cmd/cmd_import_jwk.go cmd/cmd_import_jwk.go:23— cmd/cmd_import_jwk.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in cmd.NewKeysImportCmd at line 23. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- cmd/cmd_import_jwk.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: fosite/handler/oauth2/flow_authorize_code_token.go fosite/handler/oauth2/flow_authorize_code_token.go:116— fosite/handler/oauth2/flow_authorize_code_token.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AuthorizeExplicitGrantHandler.PopulateTokenEndpointResponse at line 116. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- fosite/handler/oauth2/flow_authorize_code_token.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (10 lines × 2) client/handler.go:909— client/handler.go:909-918 | client/handler.go:974-983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) REDACTED:426— REDACTED:426-435 | REDACTED:545-554 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:426` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10 lines × 2) fosite/handler/oauth2/flow_authorize_code_token.go:131— fosite/handler/oauth2/flow_authorize_code_token.go:131-140 | fosite/handler/rfc8628/token_handler.go:78-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `fosite/handler/oauth2/flow_authorize_code_token.go:131` 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) oryx/hasherx/hasher_argon2.go:104— oryx/hasherx/hasher_argon2.go:104-113 | oryx/hasherx/hasher_pbkdf2.go:72-81 — 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 `oryx/hasherx/hasher_argon2.go:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) fosite/handler/oauth2/strategy_jwt_session.go:55— fosite/handler/oauth2/strategy_jwt_session.go:55-64 | fosite/handler/openid/strategy_jwt.go:67-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) persistence/sql/persister_grant_jwk.go:173— persistence/sql/persister_grant_jwk.go:173-182 | persistence/sql/persister_grant_jwk.go:265-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
TooManyFields: Config fosite/config_default.go:71— TooManyFields — 54 stored fields beside 54 methods. The bar is 30 stored fields; this is 24 over it, 1.80× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Client client/client.go:35— TooManyFields — 41 stored fields beside 22 methods. The bar is 30 stored fields; this is 11 over it, 1.37× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: RegistrySQL driver/registry_sql.go:60— TooManyFields — 40 stored fields beside 63 methods. The bar is 30 stored fields; this is 10 over it, 1.33× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Flow flow/flow.go:115— TooManyFields — 39 stored fields beside 22 methods. The bar is 30 stored fields; this is 9 over it, 1.30× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
MethodTooLong: Fosite.DefaultClientAuthenticationStrategy fosite/client_authentication.go:79— MethodTooLong — DefaultClientAuthenticationStrategy runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: defaultStrategy.issueLogoutVerifier consent/strategy_default.go:782— MethodTooLong — issueLogoutVerifier runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MigrationBox.UpTo oryx/popx/migrator.go:127— MethodTooLong — UpTo runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: defaultStrategy.verifyAuthentication consent/strategy_default.go:360— MethodTooLong — verifyAuthentication runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×4
Edited copy of a member (23 corresponding lines) client/handler.go:908— client/handler.go:908-941 | client/handler.go:973-995 — 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) client/handler.go:523— client/handler.go:523-552 | oauth2/trust/handler.go:291-313 — 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) fosite/access_error.go:18— fosite/access_error.go:18-43 | fosite/pushed_authorize_response_writer.go:73-95 — 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) oryx/sqlxx/types.go:596— oryx/sqlxx/types.go:596-618 | x/sqlx.go:116-138 — 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 (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) persistence/sql/persister_consent.go:199— persistence/sql/persister_consent.go:199-217 | persistence/sql/persister_consent.go:229-241 — 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) consent/handler.go:948— consent/handler.go:948-960 | consent/handler.go:988-1006 — 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) persistence/sql/persister_grant_jwk.go:43— persistence/sql/persister_grant_jwk.go:43-55 | persistence/sql/persister_grant_jwk.go:57-71 — 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) fosite/token/jwt/claims.go:52— fosite/token/jwt/claims.go:52-67 | fosite/token/jwt/header.go:16-28 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) persistence/sql/persister_client.go:22— persistence/sql/persister_client.go:22-38 | persistence/sql/persister_client.go:176-187 — 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) jwk/handler.go:164— jwk/handler.go:164-176 | jwk/handler.go:211-222 — 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/testhelpers/oauth2.go:129— internal/testhelpers/oauth2.go:129-141 | internal/testhelpers/oauth2.go:159-170 — 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) oryx/otelx/semconv/deprecated.go:18— oryx/otelx/semconv/deprecated.go:18-29 | oryx/otelx/semconv/warning.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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) oryx/decoderx/http.go:177— oryx/decoderx/http.go:177-190 | oryx/jsonschemax/keys.go:102-111 — 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) persistence/sql/persister_device.go:200— persistence/sql/persister_device.go:200-209 | persistence/sql/persister_oauth2.go:791-800 — 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) oryx/sqlxx/types.go:567— oryx/sqlxx/types.go:567-576 | x/sqlx.go:87-96 — 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) oryx/configx/koanf_env.go:26— oryx/configx/koanf_env.go:26-36 | oryx/configx/pflag.go:23-32 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) cmd/cmd_delete_client.go:42— cmd/cmd_delete_client.go:42-59 | cmd/cmd_delete_jwks.go:39-56 — 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 `cmd/cmd_delete_client.go:42` 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) fosite/integration/clients/introspect.go:50— fosite/integration/clients/introspect.go:50-67 | fosite/integration/clients/jwt_bearer.go:89-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `fosite/integration/clients/jwt_bearer.go:87` calls `Set` and `fosite/integration/clients/introspect.go:48` 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 (18 lines × 2) oauth2/refresh_hook.go:92— oauth2/refresh_hook.go:92-109 | oauth2/token_hook.go:198-215 — 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 `oauth2/refresh_hook.go:92` 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) oryx/sqlxx/types.go:601— oryx/sqlxx/types.go:601-618 | x/sqlx.go:121-138 — before extracting anything, compare `oryx/sqlxx/types.go` and `x/sqlx.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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 `oryx/sqlxx/types.go:601` 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 lines × 2) cmd/cmd_delete_client.go:25— cmd/cmd_delete_client.go:25-36 | cmd/cmd_delete_jwks.go:23-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/cmd_delete_client.go:25` 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) fosite/access_error.go:29— fosite/access_error.go:29-40 | fosite/authorize_error.go:26-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 (12 lines × 2) fosite/handler/oauth2/flow_authorize_code_token.go:103— fosite/handler/oauth2/flow_authorize_code_token.go:103-114 | fosite/handler/rfc8628/token_handler.go:191-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) REDACTED:189— REDACTED:189-200 | REDACTED:74-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:189` 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) oryx/pagination/keysetpagination/header.go:102— oryx/pagination/keysetpagination/header.go:102-112 | oryx/pagination/keysetpagination_v2/request_params.go:99-109 — 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 `oryx/pagination/keysetpagination/header.go:102` 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 lines × 2) oryx/pagination/keysetpagination/paginator.go:84— oryx/pagination/keysetpagination/paginator.go:84-94 | oryx/pagination/keysetpagination_v2/paginator.go:66-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `oryx/pagination/keysetpagination/paginator.go:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `oryx/pagination/keysetpagination/paginator.go:96` calls `WithColumn` and `oryx/pagination/keysetpagination_v2/paginator.go:77` 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 × 2) fosite/session.go:94— fosite/session.go:94-104 | oauth2/session.go:208-218 — 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) oauth2/trust/manager_test_helpers.go:53— oauth2/trust/manager_test_helpers.go:53-63 | oauth2/trust/manager_test_helpers.go:160-170 — 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 `oauth2/trust/manager_test_helpers.go:53` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) REDACTED:359— REDACTED:359-366 | REDACTED:452-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:359` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (8 lines × 2) oryx/assertx/assertx.go:26— oryx/assertx/assertx.go:26-33 | oryx/assertx/assertx.go:38-45 — 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) oryx/popx/cmd.go:86— oryx/popx/cmd.go:86-93 | oryx/popx/cmd.go:196-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) persistence/sql/persister_consent.go:655— persistence/sql/persister_consent.go:655-662 | persistence/sql/persister_consent.go:674-681 — 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 `persistence/sql/persister_consent.go:655` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Deprecated module: github.com/lestrrat-go/jwx — `github.com/lestrrat-go/jwx` is required at v1.2.31 in REDACTED, and its author has DEPRECATED the module: "This version of github.com/lestrrat-go/jwx is deprecated. Please use github.com/lestrrat-go/jwx/v3 or newer instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
Deprecated module: go.opentelemetry.io/otel/exporters/jaeger — `go.opentelemetry.io/otel/exporters/jaeger` is required at v1.17.0 in REDACTED, and its author has DEPRECATED the module: "This module is no longer supported. OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp] or [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc] instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
Deprecated module: go.opentelemetry.io/otel/exporters/zipkin — `go.opentelemetry.io/otel/exporters/zipkin` is required at v1.44.0 in REDACTED, and its author has DEPRECATED the module: "The zipkin exporter is deprecated and will be removed in early 2027. See the blog post "Deprecating Zipkin Exporter": https://opentelemetry.io/blog/2025/deprecating-zipkin-exporters/" A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
FunctionTooLong: jsonschemax.listPaths oryx/jsonschemax/keys.go:212— FunctionTooLong — listPaths runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: cmd.NewPerformAuthorizationCodeCmd REDACTED:140— FunctionTooLong — NewPerformAuthorizationCodeCmd runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: decoderx.decodeURLValues oryx/decoderx/http.go:393— FunctionTooLong — decodeURLValues runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) hsm/manager_hsm.go:149— hsm/manager_hsm.go:149-174 | hsm/manager_hsm.go:176-206 — 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.
Edited copy of a member (26 corresponding lines) hsm/manager_hsm.go:208— hsm/manager_hsm.go:208-234 | hsm/manager_hsm.go:236-261 — 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.
Edited copy of a member (26 corresponding lines) oryx/josex/utils.go:45— oryx/josex/utils.go:45-70 | oryx/josex/utils.go:73-103 — 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 (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) persistence/sql/persister_jwk.go:59— persistence/sql/persister_jwk.go:59-82 | persistence/sql/persister_jwk.go:85-112 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) cmd/cmd_delete_tokens.go:13— cmd/cmd_delete_tokens.go:13-36 | cmd/cmd_introspect_token.go:15-41 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) oryx/hasherx/hash_comparator.go:49— oryx/hasherx/hash_comparator.go:49-72 | oryx/hasherx/hash_comparator.go:74-97 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×3
Edited copy of a member (22 corresponding lines) oryx/pagination/keysetpagination/paginator.go:78— oryx/pagination/keysetpagination/paginator.go:78-102 | oryx/pagination/keysetpagination_v2/paginator.go:60-81 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) oryx/pagination/keysetpagination/header.go:91— oryx/pagination/keysetpagination/header.go:91-112 | oryx/pagination/keysetpagination_v2/request_params.go:88-109 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) persistence/sql/persister_grant_jwk.go:171— persistence/sql/persister_grant_jwk.go:171-198 | persistence/sql/persister_grant_jwk.go:263-284 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) persistence/sql/persister_jwk.go:115— persistence/sql/persister_jwk.go:115-131 | persistence/sql/persister_jwk.go:134-147 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) REDACTED:481— REDACTED:481-494 | REDACTED:518-531 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) oryx/pagination/keysetpagination_v2/parse_header.go:21— oryx/pagination/keysetpagination_v2/parse_header.go:21-35 | oryx/pagination/keysetclient/parse_header.go:35-48 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) persistence/sql/persister_jwk.go:197— persistence/sql/persister_jwk.go:197-206 | persistence/sql/persister_jwk.go:209-215 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) fosite/token/hmac/bytes.go:14— fosite/token/hmac/bytes.go:14-20 | jwk/manager_test_helpers.go:22-28 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) oryx/corsx/normalize.go:9— oryx/corsx/normalize.go:9-15 | oryx/popx/migrator.go:582-588 — 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 (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) internal/testhelpers/oauth2.go:249— internal/testhelpers/oauth2.go:249-253 | internal/testhelpers/oauth2.go:255-259 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) persistence/sql/persister_oauth2.go:777— persistence/sql/persister_oauth2.go:777-781 | persistence/sql/persister_oauth2.go:784-788 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) oryx/healthx/handler.go:208— oryx/healthx/handler.go:208-214 | oryx/reqlog/middleware.go:105-109 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 3) cmd/cmd_create_client.go:105— cmd/cmd_create_client.go:105-113 | cmd/cmd_import_client.go:112-120 | cmd/cmd_update_client.go:74-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 all 3 call sites, so a change lands once.
Duplicated block (9 lines × 3) consent/handler.go:484— consent/handler.go:484-492 | consent/handler.go:752-760 | consent/handler.go:849-857 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `consent/handler.go:484` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) fosite/handler/openid/flow_device_token.go:42— fosite/handler/openid/flow_device_token.go:42-50 | fosite/handler/openid/flow_explicit_token.go:42-50 | fosite/handler/openid/flow_refresh_token.go:83-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
X3 · Exception handling· Lost error (reports the zero value of a failed type assertion) · ×3
Lost error (reports the zero value of a failed type assertion) jwk/cast.go:28— `res, ok := pk.Key.(*rsa.PublicKey)` failed on this branch, so `res` is the zero value of `*rsa.PublicKey` here, and that is what is reported: the value that did not fit is lost. Report `pk.Key` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) jwk/cast.go:46— `res, ok := key.Key.(*rsa.PrivateKey)` failed on this branch, so `res` is the zero value of `*rsa.PrivateKey` here, and that is what is reported: the value that did not fit is lost. Report `key.Key` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) fosite/token/jwt/token.go:225— `e, ok := err.(*ValidationError)` failed on this branch, so `e` is the zero value of `*ValidationError` here, and that is what is reported: the value that did not fit is lost. Report `err` itself (and `%T` of it) instead.
Stateful handler dependency: RFC6749Error fosite/errors.go:272— `RFC6749Error` is shared by every request (`WithHintf` is called per request from the net/http handler `Handler.oauth2TokenExchange`, on the one `RFC6749Error` value that handler's shared receiver holds) but writes its fields outside any lock (hintIDField, hintArgs, HintField; e.g. `hintIDField` in `WithHintf` at line 395). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process.
Stateful handler dependency: Logger oryx/logrusx/helper.go:37— `Logger` is shared by every request (`WithField` is called per request from the net/http handler `Handler.oauth2TokenExchange`, on the one `Logger` value that handler's shared receiver holds) but writes its fields outside any lock (Entry; e.g. `Entry` in `WithField` at line 218). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process.
Handler.HandleTokenEndpointRequest (cognitive 20) fosite/handler/pkce/handler.go:119— Handler.HandleTokenEndpointRequest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Handler.HandleTokenEndpointRequest (cognitive 20) fosite/handler/rfc7523/handler.go:45— Handler.HandleTokenEndpointRequest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), loops 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
FileTooLong: consent/strategy_default.go consent/strategy_default.go— FileTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: defaultStrategy (26 blocks, 58-1345). The bar is 500 significant lines; this is 308 over it, 1.62× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: config/provider.go driver/config/provider.go— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: DefaultProvider (90 blocks, 135-825). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) consent/handler.go:351— consent/handler.go:351-384 | consent/handler.go:430-504 | consent/handler.go:549-600 | consent/handler.go:643-674 | consent/handler.go:725-772 | consent/handler.go:822-870 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) fosite/handler/oauth2/flow_authorize_code_auth.go:52— fosite/handler/oauth2/flow_authorize_code_auth.go:52-81 | fosite/handler/oauth2/flow_authorize_implicit.go:31-63 | fosite/handler/oauth2/flow_client_credentials.go:28-55 | fosite/handler/oauth2/flow_resource_owner.go:47-93 | fosite/handler/openid/flow_implicit.go:30-112 | fosite/handler/par/flow_pushed_authorize.go:33-79 — 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 copy of a member (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) oryx/cmdx/printing.go:87— oryx/cmdx/printing.go:87-120 | oryx/cmdx/printing.go:143-189 — 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) oryx/metricsx/middleware.go:309— oryx/metricsx/middleware.go:309-347 | oryx/metricsx/middleware.go:349-382 — 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 (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) persistence/sql/persister_consent.go:400— persistence/sql/persister_consent.go:400-428 | persistence/sql/persister_consent.go:430-459 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) oryx/hasherx/hasher_argon2.go:79— oryx/hasherx/hasher_argon2.go:79-113 | oryx/hasherx/hasher_pbkdf2.go:53-81 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) fosite/integration/clients/introspect.go:40— fosite/integration/clients/introspect.go:40-76 | fosite/integration/clients/jwt_bearer.go:67-115 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) oryx/pagination/pagepagination/pagination.go:31— oryx/pagination/pagepagination/pagination.go:31-67 | oryx/pagination/parse.go:12-48 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) fosite/compose/compose.go:37— fosite/compose/compose.go:37-62 | fositex/config.go:88-108 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) fosite/token/REDACTED:83— fosite/token/REDACTED:83-103 | fosite/token/REDACTED:106-126 — 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 copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) fosite/handler/oauth2/introspector.go:72— fosite/handler/oauth2/introspector.go:72-87 | fosite/handler/oauth2/introspector.go:89-105 — 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) oauth2/trust/handler.go:185— oauth2/trust/handler.go:185-201 | oauth2/trust/handler.go:239-254 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) client/handler.go:640— client/handler.go:640-662 | client/handler.go:805-822 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) flow/consent_types.go:139— flow/consent_types.go:139-156 | flow/consent_types.go:215-232 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×2
Edited copies of one member (3 members, 15+ corresponding lines) client/handler.go:257— client/handler.go:257-271 | jwk/handler.go:346-361 | jwk/handler.go:407-425 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) flow/flow_encoding.go:75— flow/flow_encoding.go:75-89 | flow/flow_encoding.go:91-105 | flow/flow_encoding.go:107-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) REDACTED:51— REDACTED:51-69 | REDACTED:71-89 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) oryx/fsx/merge.go:38— oryx/fsx/merge.go:38-56 | oryx/fsx/merge.go:88-107 — 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 (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) persistence/sql/persister_consent.go:174— persistence/sql/persister_consent.go:174-197 | persistence/sql/persister_grant_jwk.go:109-125 — 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) oryx/configx/provider.go:508— oryx/configx/provider.go:508-524 | oryx/configx/provider.go:526-542 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) fosite/access_write.go:12— fosite/access_write.go:12-26 | fosite/pushed_authorize_response_writer.go:48-70 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) oryx/randx/strength/main.go:28— oryx/randx/strength/main.go:28-42 | oryx/randx/strength/main.go:44-62 — 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 (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) oryx/pagination/keysetpagination/header.go:81— oryx/pagination/keysetpagination/header.go:81-88 | oryx/pagination/keysetpagination_v2/request_params.go:70-77 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) fosite/handler/oauth2/strategy_hmacsha_plain.go:49— fosite/handler/oauth2/strategy_hmacsha_plain.go:49-56 | fosite/handler/rfc8628/strategy_hmacsha.go:70-77 — 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 copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) oryx/urlx/copy.go:16— oryx/urlx/copy.go:16-24 | oryx/urlx/join.go:42-52 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) REDACTED:72— REDACTED:72-81 | REDACTED:102-110 — 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.
Duplicated block (17 lines × 2) REDACTED:145— REDACTED:145-161 | REDACTED:200-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:145` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:142` calls `HandlerFunc` and `REDACTED:197` 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 (17 lines × 2) persistence/sql/persister_device.go:69— persistence/sql/persister_device.go:69-85 | persistence/sql/persister_oauth2.go:92-108 — before extracting anything, compare `persistence/sql/persister_device.go` and `persistence/sql/persister_oauth2.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 lines × 2) REDACTED:466— REDACTED:466-481 | REDACTED:537-552 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:466` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also 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 (16 lines × 2) flow/consent_types.go:141— flow/consent_types.go:141-156 | flow/consent_types.go:217-232 — 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 `flow/consent_types.go:141` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) REDACTED:370— REDACTED:370-384 | REDACTED:475-489 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:370` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (15 lines × 2) fosite/handler/openid/flow_device_token.go:43— fosite/handler/openid/flow_device_token.go:43-57 | fosite/handler/openid/flow_explicit_token.go:43-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) consent/handler.go:753— consent/handler.go:753-766 | consent/handler.go:850-863 — 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 `consent/handler.go:753` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) persistence/sql/persister_consent.go:415— persistence/sql/persister_consent.go:415-428 | persistence/sql/persister_consent.go:446-459 — 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 `persistence/sql/persister_consent.go:415` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `persistence/sql/persister_consent.go:444` calls `Where` and `persistence/sql/persister_consent.go:413` 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 (13 lines × 2) fosite/handler/oauth2/flow_authorize_code_token.go:154— fosite/handler/oauth2/flow_authorize_code_token.go:154-166 | fosite/handler/rfc8628/token_handler.go:101-113 — 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 `fosite/handler/oauth2/flow_authorize_code_token.go:154` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `fosite/handler/oauth2/flow_authorize_code_token.go:172` calls `Is`, `WithStack` and `fosite/handler/rfc8628/token_handler.go:114` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) persistence/sql/persister_consent.go:402— persistence/sql/persister_consent.go:402-414 | persistence/sql/persister_consent.go:432-444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `persistence/sql/persister_consent.go:445` calls `Where` and `persistence/sql/persister_consent.go:415` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 3) consent/handler.go:354— consent/handler.go:354-364 | consent/handler.go:433-442 | consent/handler.go:552-562 — 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10–11 lines × 3) fosite/access_error.go:32— fosite/access_error.go:32-42 | fosite/authorize_error.go:29-38 | fosite/pushed_authorize_response_writer.go:85-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `fosite/access_error.go:32` 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 × 3) REDACTED:53— REDACTED:53-60 | REDACTED:73-80 | REDACTED:93-100 — 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) consent/handler.go:648— consent/handler.go:648-655 | consent/handler.go:730-737 | consent/handler.go:825-832 — 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) fosite/token/jwt/claims_id_token.go:117— fosite/token/jwt/claims_id_token.go:117-122 | fosite/token/jwt/claims_jwt.go:222-227 | fosite/token/jwt/header.go:31-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) jwk/handler.go:293— jwk/handler.go:293-298 | jwk/handler.go:348-353 | jwk/handler.go:412-417 — 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 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.
Swallowed exception (empty catch) oryx/prometheusx/exemplar.go:41— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) oryx/prometheusx/exemplar.go:58— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
jsonschemax.listPaths (cyclomatic 62) oryx/jsonschemax/keys.go:212— jsonschemax.listPaths has cyclomatic complexity 62 (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.
Validator.Validate (cyclomatic 52) client/validator.go:54— Validator.Validate has cyclomatic complexity 52 (threshold 15). Of this number, 50 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
Fosite.DefaultClientAuthenticationStrategy (cyclomatic 52) fosite/client_authentication.go:79— Fosite.DefaultClientAuthenticationStrategy has cyclomatic complexity 52 (threshold 15). Of this number, 37 points are the body's own statements and 15 belong to one function literal inside it that branches. 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.
decoderx.decodeURLValues (cyclomatic 43) oryx/decoderx/http.go:393— decoderx.decodeURLValues has cyclomatic complexity 43 (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.
Client.GetEffectiveLifespan (cyclomatic 39) client/client.go:536— Client.GetEffectiveLifespan has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MigrationBox.UpTo (cyclomatic 39) oryx/popx/migrator.go:127— MigrationBox.UpTo has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 13 of the 39 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 189, 163). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DefaultStrategy.GenerateIDToken (cyclomatic 35) fosite/handler/openid/strategy_jwt.go:124— DefaultStrategy.GenerateIDToken has cyclomatic complexity 35 (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.
Fosite.authorizeRequestParametersFromOpenIDConnectRequest (cyclomatic 33) fosite/authorize_request_handler.go:34— Fosite.authorizeRequestParametersFromOpenIDConnectRequest has cyclomatic complexity 33 (threshold 15). Of this number, 24 points are the body's own statements and 9 belong to one function literal inside it that branches. 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.
watcherx.streamFileEvents (cyclomatic 30) oryx/watcherx/file.go:49— watcherx.streamFileEvents has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
OpenIDConnectHybridHandler.HandleAuthorizeEndpointRequest (cyclomatic 29) fosite/handler/openid/flow_hybrid.go:33— OpenIDConnectHybridHandler.HandleAuthorizeEndpointRequest has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenIDConnectRequestValidator.ValidatePrompt (cyclomatic 28) fosite/handler/openid/validator.go:43— OpenIDConnectRequestValidator.ValidatePrompt has cyclomatic complexity 28 (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.
InMemory.Search (cyclomatic 28) oryx/mailhog/memory.go:48— InMemory.Search 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.
JWTClaims.FromMap (cyclomatic 27) fosite/token/jwt/claims_jwt.go:145— JWTClaims.FromMap has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
defaultStrategy.verifyAuthentication (cyclomatic 26) consent/strategy_default.go:360— defaultStrategy.verifyAuthentication has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
defaultStrategy.issueLogoutVerifier (cyclomatic 26) consent/strategy_default.go:782— defaultStrategy.issueLogoutVerifier has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
oauth2cors.Middleware (cyclomatic 26) x/oauth2cors/cors.go:20— oauth2cors.Middleware has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 26). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Env.extract (cyclomatic 24) oryx/configx/koanf_env.go:94— Env.extract has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
jwksx.generate (cyclomatic 24) oryx/jwksx/generator.go:55— jwksx.generate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
popx.TransactionWithOptions (cyclomatic 22) REDACTED:46— popx.TransactionWithOptions has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 86, 58). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DefaultClientWithCustomTokenLifespans.GetEffectiveLifespan (cyclomatic 21) fosite/client_with_custom_token_lifespans.go:57— DefaultClientWithCustomTokenLifespans.GetEffectiveLifespan 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.
Fosite.newAuthorizeRequest (cyclomatic 21) fosite/authorize_request_handler.go:347— Fosite.newAuthorizeRequest 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.
cmd.NewKeysImportCmd (cyclomatic 20) cmd/cmd_import_jwk.go:23— cmd.NewKeysImportCmd has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 34). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
MigrationBox.Down (cyclomatic 20) oryx/popx/migrator.go:331— MigrationBox.Down has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 341). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
cmd.NewPerformAuthorizationCodeCmd (cyclomatic 19) REDACTED:140— cmd.NewPerformAuthorizationCodeCmd has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 150). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Handler.HandleTokenEndpointRequest (cyclomatic 19) fosite/handler/pkce/handler.go:119— Handler.HandleTokenEndpointRequest 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.
jsonx.embed (cyclomatic 19) oryx/jsonx/embed.go:56— jsonx.embed 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.
Handler.revokeOAuth2ConsentSessions (cyclomatic 18) consent/handler.go:118— Handler.revokeOAuth2ConsentSessions has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Handler.HandleTokenEndpointRequest (cyclomatic 18) fosite/handler/rfc7523/handler.go:45— Handler.HandleTokenEndpointRequest has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
osx.readFile (cyclomatic 18) oryx/osx/file.go:148— osx.readFile has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
keysetpagination.BuildWhereAndOrder (cyclomatic 18) oryx/pagination/keysetpagination_v2/query_builder.go:60— keysetpagination.BuildWhereAndOrder has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cmd.NewImportClientCmd (cyclomatic 17) cmd/cmd_import_client.go:21— cmd.NewImportClientCmd has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 62). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Fosite.NewIntrospectionRequest (cyclomatic 17) REDACTED:98— Fosite.NewIntrospectionRequest has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RefreshTokenGrantHandler.HandleTokenEndpointRequest (cyclomatic 17) fosite/handler/oauth2/flow_refresh.go:42— RefreshTokenGrantHandler.HandleTokenEndpointRequest 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.
OpenIDConnectImplicitHandler.HandleAuthorizeEndpointRequest (cyclomatic 17) fosite/handler/openid/flow_implicit.go:30— OpenIDConnectImplicitHandler.HandleAuthorizeEndpointRequest 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.
Fosite.NewAccessRequest (cyclomatic 16) fosite/access_request_handler.go:45— Fosite.NewAccessRequest 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.
AuthorizeExplicitGrantHandler.PopulateTokenEndpointResponse (cyclomatic 16) fosite/handler/oauth2/flow_authorize_code_token.go:116— AuthorizeExplicitGrantHandler.PopulateTokenEndpointResponse has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Handler.validateTokenClaims (cyclomatic 16) fosite/handler/rfc7523/handler.go:258— Handler.validateTokenClaims 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.
DeviceCodeTokenEndpointHandler.PopulateTokenEndpointResponse (cyclomatic 16) fosite/handler/rfc8628/token_handler.go:59— DeviceCodeTokenEndpointHandler.PopulateTokenEndpointResponse has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
josex.NewSigningKey (cyclomatic 16) oryx/josex/generate.go:33— josex.NewSigningKey has cyclomatic complexity 16 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tlsx.GetCertificate (cyclomatic 16) oryx/tlsx/cert.go:139— tlsx.GetCertificate has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 161, 203). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Repeated repair: jwk/handler.go jwk/handler.go:94— jwk/handler.go changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is Handler.discoverJsonWebKeys at line 94), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: report the key set name in JWK CLI output”; “fix: eliminate JWK lock contention during token issuance”; “chore: upgrade herodot to fix information leaks and data races in error handling”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:09 +00:00' --until='2026-07-29 09:30:09 +00:00' --full-history --no-merges -- jwk/handler.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
HackComment test/mock-client/main.go:77— // Hack to fix cookie across domains — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
FixmeComment oryx/mailhog/memory.go:51— // FIXME needs optimising, or replacing with a proper db! — 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.
decoderx.decodeURLValues (cognitive 117) oryx/decoderx/http.go:393— decoderx.decodeURLValues has cognitive complexity 117 (threshold 15). Drivers by points: if/else 19 (72 pts), match/switch 5 (30 pts), loops 5 (14 pts), boolean chains 1 (nesting depth added 87). 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.
jsonschemax.listPaths (cognitive 95) oryx/jsonschemax/keys.go:212— jsonschemax.listPaths has cognitive complexity 95 (threshold 15). Drivers by points: if/else 31 (61 pts), loops 8 (16 pts), match/switch 5 (15 pts), boolean chains 3 (nesting depth added 48). 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.
Validator.Validate (cognitive 79) client/validator.go:54— Validator.Validate has cognitive complexity 79 (threshold 15). Drivers by points: if/else 37 (62 pts), boolean chains 9, loops 6 (8 pts) (nesting depth added 27). Of this number, 78 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
InMemory.Search (cognitive 78) oryx/mailhog/memory.go:48— InMemory.Search has cognitive complexity 78 (threshold 15). Drivers by points: if/else 16 (51 pts), loops 7 (24 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 53). 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.
MigrationBox.UpTo (cognitive 78) oryx/popx/migrator.go:127— MigrationBox.UpTo has cognitive complexity 78 (threshold 15). Drivers by points: if/else 34 (72 pts), boolean chains 5, loops 1 (nesting depth added 38). Of this number, 24 points are the body's own statements and 54 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
watcherx.streamFileEvents (cognitive 72) oryx/watcherx/file.go:49— watcherx.streamFileEvents has cognitive complexity 72 (threshold 15). Drivers by points: match/switch 9 (40 pts), if/else 10 (31 pts), loops 1 (nesting depth added 52). Of this number, 69 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Fosite.DefaultClientAuthenticationStrategy (cognitive 59) fosite/client_authentication.go:79— Fosite.DefaultClientAuthenticationStrategy has cognitive complexity 59 (threshold 15). Drivers by points: if/else 30 (48 pts), match/switch 3 (6 pts), boolean chains 5 (nesting depth added 21). Of this number, 41 points are the body's own statements and 18 belong to one function literal inside it that branches. 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.
DefaultStrategy.GenerateIDToken (cognitive 52) fosite/handler/openid/strategy_jwt.go:124— DefaultStrategy.GenerateIDToken has cognitive complexity 52 (threshold 15). Drivers by points: if/else 27 (45 pts), boolean chains 5, match/switch 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JWTClaims.FromMap (cognitive 46) fosite/token/jwt/claims_jwt.go:145— JWTClaims.FromMap has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (36 pts), loops 2 (5 pts), match/switch 2 (5 pts) (nesting depth added 29). 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.
Client.GetEffectiveLifespan (cognitive 45) client/client.go:536— Client.GetEffectiveLifespan has cognitive complexity 45 (threshold 15). Drivers by points: if/else 23 (30 pts), boolean chains 15 (nesting depth added 7). 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.
Env.extract (cognitive 44) oryx/configx/koanf_env.go:94— Env.extract has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (34 pts), loops 3 (7 pts), match/switch 1 (3 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fosite.authorizeRequestParametersFromOpenIDConnectRequest (cognitive 43) fosite/authorize_request_handler.go:34— Fosite.authorizeRequestParametersFromOpenIDConnectRequest has cognitive complexity 43 (threshold 15). Drivers by points: if/else 23 (36 pts), boolean chains 4, loops 2, match/switch 1 (nesting depth added 13). Of this number, 33 points are the body's own statements and 10 belong to one function literal inside it that branches. 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.
popx.TransactionWithOptions (cognitive 43) REDACTED:46— popx.TransactionWithOptions has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (35 pts), loops 2 (3 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 23). Most of this is not in the body itself: 11 of the 43 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 86, 58). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MigrationBox.Down (cognitive 39) oryx/popx/migrator.go:331— MigrationBox.Down has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (37 pts), boolean chains 1, loops 1 (nesting depth added 19). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to one function literal inside it that branches (line 341). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
defaultStrategy.issueLogoutVerifier (cognitive 38) consent/strategy_default.go:782— defaultStrategy.issueLogoutVerifier has cognitive complexity 38 (threshold 15). Drivers by points: if/else 23 (35 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenIDConnectHybridHandler.HandleAuthorizeEndpointRequest (cognitive 37) fosite/handler/openid/flow_hybrid.go:33— OpenIDConnectHybridHandler.HandleAuthorizeEndpointRequest has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 4, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cmd.NewKeysImportCmd (cognitive 36) cmd/cmd_import_jwk.go:23— cmd.NewKeysImportCmd has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (30 pts), loops 4 (6 pts) (nesting depth added 15). None of this is in the body itself: all 36 points belong to one function literal inside it that branches (line 34). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
oauth2cors.Middleware (cognitive 35) x/oauth2cors/cors.go:20— oauth2cors.Middleware has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 4, loops 3 (nesting depth added 10). None of this is in the body itself: all 35 points belong to one function literal inside it that branches (line 26). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
OpenIDConnectRequestValidator.ValidatePrompt (cognitive 34) fosite/handler/openid/validator.go:43— OpenIDConnectRequestValidator.ValidatePrompt has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (31 pts), boolean chains 3 (nesting depth added 7). 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.
defaultStrategy.verifyAuthentication (cognitive 32) consent/strategy_default.go:360— defaultStrategy.verifyAuthentication has cognitive complexity 32 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cmd.NewImportClientCmd (cognitive 31) cmd/cmd_import_client.go:21— cmd.NewImportClientCmd has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 14). None of this is in the body itself: all 31 points belong to one function literal inside it that branches (line 62). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
directoryWatcher.streamDirectoryEvents (cognitive 31) oryx/watcherx/directory.go:120— directoryWatcher.streamDirectoryEvents has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (28 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 21). Most of this is not in the body itself: 10 of the 31 points are its own statements and the rest belongs to one function literal inside it that branches (line 135). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
keysetpagination.BuildWhereAndOrder (cognitive 30) oryx/pagination/keysetpagination_v2/query_builder.go:60— keysetpagination.BuildWhereAndOrder has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 3, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
batch.buildInsertQueryValues (cognitive 29) oryx/sqlxx/batch/create.go:113— batch.buildInsertQueryValues has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
osx.readFile (cognitive 28) oryx/osx/file.go:148— osx.readFile has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultClientWithCustomTokenLifespans.GetEffectiveLifespan (cognitive 26) fosite/client_with_custom_token_lifespans.go:57— DefaultClientWithCustomTokenLifespans.GetEffectiveLifespan has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20 (26 pts) (nesting depth added 6). 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.
IDTokenClaims.ToMap (cognitive 26) fosite/token/jwt/claims_id_token.go:31— IDTokenClaims.ToMap has cognitive complexity 26 (threshold 15). Drivers by points: if/else 26. 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.
clidoc.GenMarkdownCustom (cognitive 26) oryx/clidoc/md_docs.go:57— clidoc.GenMarkdownCustom has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). Of this number, 23 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
jsonnetx.NewFormatCommand (cognitive 26) oryx/jsonnetx/format.go:17— jsonnetx.NewFormatCommand has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 2 (3 pts) (nesting depth added 15). None of this is in the body itself: all 26 points belong to one function literal inside it that branches (line 27). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
jwksx.generate (cognitive 25) oryx/jwksx/generator.go:55— jwksx.generate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 2, boolean chains 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RegistrySQL.Init (cognitive 24) driver/registry_sql.go:185— RegistrySQL.Init has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fosite.NewIntrospectionRequest (cognitive 24) REDACTED:98— Fosite.NewIntrospectionRequest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fosite.newAuthorizeRequest (cognitive 23) fosite/authorize_request_handler.go:347— Fosite.newAuthorizeRequest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
JWTClaims.ToMap (cognitive 22) fosite/token/jwt/claims_jwt.go:83— JWTClaims.ToMap has cognitive complexity 22 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
tlsx.GetCertificate (cognitive 22) oryx/tlsx/cert.go:139— tlsx.GetCertificate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (8 pts), boolean chains 1, loops 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 161, 203). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
cmd.NewPerformAuthorizationCodeCmd (cognitive 21) REDACTED:140— cmd.NewPerformAuthorizationCodeCmd has cognitive complexity 21 (threshold 15). Drivers by points: if/else 20 (21 pts) (nesting depth added 1). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 150). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
jsonx.embed (cognitive 21) oryx/jsonx/embed.go:56— jsonx.embed has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). 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.
MigrationBox.createMigrationStatusTableTransaction (cognitive 21) oryx/popx/migrator.go:494— MigrationBox.createMigrationStatusTableTransaction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (7 pts) (nesting depth added 13). Of this number, 14 points are the body's own statements and 7 belong to one function literal inside it that branches. 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.
urlx.ExtractPublicAddress (cognitive 21) oryx/urlx/extract.go:48— urlx.ExtractPublicAddress has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fosite.WildcardScopeStrategy (cognitive 20) fosite/scope_strategy.go:51— fosite.WildcardScopeStrategy has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenIDConnectImplicitHandler.HandleAuthorizeEndpointRequest (cognitive 20) fosite/handler/openid/flow_implicit.go:30— OpenIDConnectImplicitHandler.HandleAuthorizeEndpointRequest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
popx.MigrateSQLDown (cognitive 20) oryx/popx/cmd.go:141— popx.MigrateSQLDown has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RefreshTokenGrantHandler.HandleTokenEndpointRequest (cognitive 19) fosite/handler/oauth2/flow_refresh.go:42— RefreshTokenGrantHandler.HandleTokenEndpointRequest has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 2, boolean chains 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.
cmd.NewUpdateClientCmd (cognitive 18) cmd/cmd_update_client.go:17— cmd.NewUpdateClientCmd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2 (nesting depth added 5). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 32). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Fosite.NewAccessRequest (cognitive 18) fosite/access_request_handler.go:45— Fosite.NewAccessRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2, 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.
AuthorizeExplicitGrantHandler.PopulateTokenEndpointResponse (cognitive 18) fosite/handler/oauth2/flow_authorize_code_token.go:116— AuthorizeExplicitGrantHandler.PopulateTokenEndpointResponse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 2 (nesting depth added 3). Of this number, 13 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
Handler.validateTokenClaims (cognitive 18) fosite/handler/rfc7523/handler.go:258— Handler.validateTokenClaims has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
MigrationManager.migrateOldMigrationTables (cognitive 18) persistence/sql/persister_migration.go:126— MigrationManager.migrateOldMigrationTables has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
jsonnetx.NewLintCommand (cognitive 18) oryx/jsonnetx/lint.go:18— jsonnetx.NewLintCommand has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts) (nesting depth added 10). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 26). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
sqlcon.ParseConnectionOptions (cognitive 18) oryx/sqlcon/parse_opts.go:18— sqlcon.ParseConnectionOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (18 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
fosite.DefaultAudienceMatchingStrategy (cognitive 17) fosite/audience_strategy.go:16— fosite.DefaultAudienceMatchingStrategy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fosite.findPublicKey (cognitive 17) fosite/client_authentication.go:299— fosite.findPublicKey has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuthorizeExplicitGrantHandler.HandleTokenEndpointRequest (cognitive 17) fosite/handler/oauth2/flow_authorize_code_token.go:18— AuthorizeExplicitGrantHandler.HandleTokenEndpointRequest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DeviceCodeTokenEndpointHandler.PopulateTokenEndpointResponse (cognitive 17) fosite/handler/rfc8628/token_handler.go:59— DeviceCodeTokenEndpointHandler.PopulateTokenEndpointResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), loops 2 (nesting depth added 2). Of this number, 12 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
Persister.gracefulRefreshRotation (cognitive 17) persistence/sql/persister_oauth2.go:161— Persister.gracefulRefreshRotation has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (17 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Provider.createProviders (cognitive 17) oryx/configx/provider.go:122— Provider.createProviders has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 3, boolean chains 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body 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.
mergedFile.ReadDir (cognitive 17) oryx/fsx/merge.go:184— mergedFile.ReadDir has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
josex.NewSigningKey (cognitive 17) oryx/josex/generate.go:33— josex.NewSigningKey has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2, boolean chains 1 (nesting depth added 7). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
defaultStrategy.forwardAuthenticationRequest (cognitive 16) consent/strategy_default.go:196— defaultStrategy.forwardAuthenticationRequest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Fosite.WriteAuthorizeError (cognitive 16) fosite/authorize_error.go:13— Fosite.WriteAuthorizeError has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mergedFS.Stat (cognitive 16) oryx/fsx/merge.go:58— mergedFS.Stat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PageToken.MarshalJSON (cognitive 16) oryx/pagination/keysetpagination_v2/page_token.go:86— PageToken.MarshalJSON has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D22 · Internal API Consistency· `MigrationBox.SelectedMigrations` takes no context.Context; its 6 sibling operations take one · ×1
`MigrationBox.SelectedMigrations` takes no context.Context; its 6 sibling operations take one oryx/popx/migration_box.go:240— 6 of 7 fallible operations of `MigrationBox` take a `ctx context.Context` (6 of 7). Siblings: MigrationBox.Up (oryx/popx/migrator.go:48); MigrationBox.UpTo (oryx/popx/migrator.go:127); MigrationBox.Down (oryx/popx/migrator.go:331); MigrationBox.CreateSchemaMigrations (oryx/popx/migrator.go:524); MigrationBox.Status (oryx/popx/migrator.go:610). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
ClassTooLong: defaultStrategy consent/strategy_default.go:45— ClassTooLong — 766 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods, 26 blocks, lines 58-1345. The bar is 400 significant lines; this is 366 over it, 1.92× 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.
Near-duplicate member pair (34 shared lines) persistence/sql/persister_device.go:56— persistence/sql/persister_device.go:56-102 | persistence/sql/persister_oauth2.go:79-122 — These two members are variants of one another: 34 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:356— REDACTED:356-396 | REDACTED:398-447 | REDACTED:449-522 | REDACTED:524-568 — 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 (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) fosite/handler/oauth2/flow_authorize_code_token.go:116— fosite/handler/oauth2/flow_authorize_code_token.go:116-188 | fosite/handler/rfc8628/token_handler.go:59-127 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) REDACTED:126— REDACTED:126-179 | REDACTED:181-233 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) fosite/handler/openid/flow_device_token.go:19— fosite/handler/openid/flow_device_token.go:19-61 | fosite/handler/openid/flow_explicit_token.go:20-68 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (72 corresponding lines) · ×1
Edited copy of a member (72 corresponding lines) cmd/cmd_create_client.go:51— cmd/cmd_create_client.go:51-122 | cmd/cmd_update_client.go:17-92 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) oryx/jsonnetx/format.go:17— oryx/jsonnetx/format.go:17-76 | oryx/jsonnetx/lint.go:18-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 copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) oryx/hasherx/hash_comparator.go:142— oryx/hasherx/hash_comparator.go:142-184 | oryx/hasherx/hash_comparator.go:188-227 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) oauth2/refresh_hook.go:57— oauth2/refresh_hook.go:57-109 | oauth2/token_hook.go:169-215 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) cmd/cmd_delete_client.go:13— cmd/cmd_delete_client.go:13-59 | cmd/cmd_delete_jwks.go:15-56 | cmd/cmd_get_client.go:14-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) persistence/sql/persister_device.go:177— persistence/sql/persister_device.go:177-197 | persistence/sql/persister_device.go:212-237 | persistence/sql/persister_oauth2.go:556-585 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) persistence/sql/persister_consent.go:631— persistence/sql/persister_consent.go:631-646 | persistence/sql/persister_consent.go:648-665 | persistence/sql/persister_consent.go:667-684 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) fosite/handler/oauth2/strategy_hmacsha_plain.go:58— fosite/handler/oauth2/strategy_hmacsha_plain.go:58-69 | fosite/handler/oauth2/strategy_hmacsha_plain.go:103-114 | fosite/handler/rfc8628/strategy_hmacsha.go:58-67 | fosite/handler/rfc8628/strategy_hmacsha.go:85-96 — 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, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) jwk/manager_strategy.go:73— jwk/manager_strategy.go:73-88 | jwk/manager_strategy.go:90-102 | jwk/manager_strategy.go:104-119 | jwk/manager_strategy.go:121-133 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) persistence/sql/persister_consent.go:48— persistence/sql/persister_consent.go:48-53 | persistence/sql/persister_consent.go:55-61 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) client/handler.go:700— client/handler.go:700-708 | jwk/handler.go:459-468 | jwk/handler.go:511-520 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) jwk/manager_strategy.go:45— jwk/manager_strategy.go:45-50 | jwk/manager_strategy.go:52-57 | jwk/manager_strategy.go:59-64 | jwk/manager_strategy.go:66-71 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) oryx/pagination/header.go:15— oryx/pagination/header.go:15-21 | oryx/pagination/keysetpagination/header.go:71-77 | oryx/pagination/pagepagination/pagination.go:69-75 | oryx/pagination/tokenpagination/pagination.go:83-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (31 lines × 2) fosite/token/jwt/claims_id_token.go:32— fosite/token/jwt/claims_id_token.go:32-62 | fosite/token/jwt/claims_jwt.go:84-114 — 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 (27 lines × 2) oryx/jsonnetx/format.go:26— oryx/jsonnetx/format.go:26-52 | oryx/jsonnetx/lint.go:25-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 `oryx/jsonnetx/format.go:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) oryx/hasherx/hash_comparator.go:159— oryx/hasherx/hash_comparator.go:159-184 | oryx/hasherx/hash_comparator.go:202-227 — 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 `oryx/hasherx/hash_comparator.go:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The 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) oryx/watcherx/file.go:78— oryx/watcherx/file.go:78-98 | oryx/watcherx/file.go:150-170 — 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 `oryx/watcherx/file.go:78` 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 (19–20 lines × 2) cmd/cmd_create_client.go:101— cmd/cmd_create_client.go:101-119 | cmd/cmd_update_client.go:70-89 — 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 `cmd/cmd_create_client.go:101` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cmd/cmd_create_client.go:120` calls `Flags`, `String` and `cmd/cmd_update_client.go:91` 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 (17 lines × 3) oryx/sqlxx/types.go:597— oryx/sqlxx/types.go:597-613 | x/sqlx.go:49-65 | x/sqlx.go:117-133 — before extracting anything, compare `oryx/sqlxx/types.go` and `x/sqlx.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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 (12–13 lines × 2) oryx/otelx/otlp.go:40— oryx/otelx/otlp.go:40-52 | oryx/otelx/zipkin.go:17-28 — 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 `oryx/otelx/otlp.go:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) REDACTED:437— REDACTED:437-447 | REDACTED:557-568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:437` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10–11 lines × 2) persistence/sql/persister_device.go:90— persistence/sql/persister_device.go:90-100 | persistence/sql/persister_oauth2.go:111-120 — before extracting anything, compare `persistence/sql/persister_device.go` and `persistence/sql/persister_oauth2.go` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 5) fosite/handler/oauth2/flow_authorize_code_auth.go:69— fosite/handler/oauth2/flow_authorize_code_auth.go:69-78 | fosite/handler/oauth2/flow_authorize_implicit.go:48-57 | fosite/handler/oauth2/flow_client_credentials.go:33-42 | fosite/handler/oauth2/flow_resource_owner.go:56-65 | fosite/handler/par/flow_pushed_authorize.go:47-56 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–10 lines × 3) client/handler.go:347— client/handler.go:347-356 | client/handler.go:641-650 | client/handler.go:806-814 — 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 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 × 3) fosite/handler/oauth2/flow_client_credentials.go:73— fosite/handler/oauth2/flow_client_credentials.go:73-90 | fosite/handler/oauth2/flow_resource_owner.go:126-143 | fosite/handler/rfc7523/handler.go:144-161 — 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 (9–10 lines × 2) consent/handler.go:556— consent/handler.go:556-565 | consent/handler.go:827-835 — 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 `consent/handler.go:556` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 5) fosite/handler/oauth2/flow_authorize_code_auth.go:69— fosite/handler/oauth2/flow_authorize_code_auth.go:69-74 | fosite/handler/oauth2/flow_authorize_implicit.go:48-53 | fosite/handler/oauth2/flow_resource_owner.go:56-61 | fosite/handler/openid/flow_implicit.go:69-74 | fosite/handler/par/flow_pushed_authorize.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 (13 lines × 3) internal/testhelpers/driver.go:107— internal/testhelpers/driver.go:107-119 | internal/testhelpers/driver.go:122-134 | internal/testhelpers/driver.go:137-149 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `internal/testhelpers/driver.go:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) persistence/sql/persister_consent.go:597— persistence/sql/persister_consent.go:597-601 | persistence/sql/persister_consent.go:633-637 | persistence/sql/persister_consent.go:650-654 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_consent.go:597` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) REDACTED:83— REDACTED:83-100 | REDACTED:112-129 | REDACTED:139-160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (5 lines × 2) client/manager_test_helpers.go:321— client/manager_test_helpers.go:321-325 | client/manager_test_helpers.go:327-331 — 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.
Off the main sequence: github.com/ory/x — github.com/ory/x: abstractness 0.15, instability 0.00, distance 0.85 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
X28 · Index access outside its own emptiness guard· Index access outside its own emptiness guard · ×1
Index access outside its own emptiness guard oryx/urlx/parse.go:104— `parts` holds what `Split` returns, and `parts[0]` takes element 0 of it without checking its length — while this file tests that same result elsewhere before indexing it, because it can be nil or shorter. Here a short result panics with `index out of range`. Test `len(parts)` (or nil) first, as the other call site does.
X3 · Exception handling· Lost error (reports an error that is nil on this path) · ×1
Lost error (reports an error that is nil on this path) oryx/watcherx/file.go:57— `if _, err := os.Lstat(watchedFile); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here.
Duplicated predicate oryx/clidoc/generate.go:32— `!c.IsAvailableCommand() || c.IsAdditionalHelpTopicCommand()` appears character-identically in 3 files — oryx/clidoc/generate.go, oryx/clidoc/md_docs.go, oryx/clidoc/util.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate fosite/handler/openid/strategy_jwt.go:169— `!claims.AuthTime.Equal(claims.RequestedAt) && claims.AuthTime.After(claims.RequestedAt)` appears character-identically in 2 files — fosite/handler/openid/strategy_jwt.go, fosite/handler/openid/validator.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate fosite/handler/oauth2/strategy_hmacsha_plain.go:64— `!exp.IsZero() && exp.Before(time.Now().UTC())` appears character-identically in 2 files — fosite/handler/oauth2/strategy_hmacsha_plain.go, fosite/handler/rfc8628/strategy_hmacsha.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cmd/cmd_create_client.go:101— `client.ClientSecret == nil && len(secret) > 0` appears character-identically in 2 files — cmd/cmd_create_client.go, cmd/cmd_update_client.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cmd/cmd_create_client.go:105— `encryptSecret && client.ClientSecret != nil` appears character-identically in 2 files — cmd/cmd_create_client.go, cmd/cmd_update_client.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate fosite/handler/oauth2/flow_authorize_code_token.go:50— `err != nil && errors.Is(err, fosite.ErrNotFound)` appears character-identically in 2 files — fosite/handler/oauth2/flow_authorize_code_token.go, fosite/handler/rfc8628/token_handler.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate oryx/sqlxx/types.go:171— `len(data) == 0 || string(data) == "null"` appears character-identically in 2 files — oryx/sqlxx/types.go, x/sqlx.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.
Orphaned file persistence/sql/persister_device.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file oauth2/token_hook.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cmd/cli/handler_janitor.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file oauth2/refresh_hook.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file x/sqlx.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion REDACTED:1— `oryx` (19995 LoC, 288 module-visible types across 78 directories) overshoots its size bounds. 3 of 4 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.
Projects may be oversized for their cohesion REDACTED:1— `(repository root)` (20559 LoC, 167 module-visible types across 29 directories) overshoots its size bounds. 3 of 4 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.
Projects may be oversized for their cohesion fosite/REDACTED:1— `fosite` (11461 LoC, 251 module-visible types across 16 directories) overshoots its size bounds. 3 of 4 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.
Fat interface: OAuth2Provider (21 methods) fosite/oauth2.go:44— `OAuth2Provider` declares 21 methods: `NewAuthorizeRequest`, `NewAuthorizeResponse`, `WriteAuthorizeError`, `WriteAuthorizeResponse`, `NewAccessRequest`, `NewAccessResponse`, `WriteAccessError`, `WriteAccessResponse`, `NewDeviceRequest`, `NewDeviceResponse`, `WriteDeviceResponse`, `NewRevocationRequest`, `WriteRevocationResponse`, `IntrospectToken`, `NewIntrospectionRequest`, `WriteIntrospectionError`, `WriteIntrospectionResponse`, `NewPushedAuthorizeRequest`, `NewPushedAuthorizeResponse`, `WritePushedAuthorizeResponse`, `WritePushedAuthorizeError`. 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: Requester (18 methods) fosite/oauth2.go:223— `Requester` declares 18 methods: `SetID`, `GetID`, `GetRequestedAt`, `GetClient`, `GetRequestedScopes`, `GetRequestedAudience`, `SetRequestedScopes`, `SetRequestedAudience`, `AppendRequestedScope`, `GetGrantedScopes`, `GetGrantedAudience`, `GrantScope`, `GrantAudience`, `GetSession`, `SetSession`, `GetRequestForm`, `Merge`, `Sanitize`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: oryx/proxy/proxy.go, REDACTED, fosite/client_authentication_jwks_strategy.go, oryx/cmdx/usage.go, cmd/cmd_update_client.go. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (11 single-owned of 214 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 214 of the 526 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: oryx/cookiex/cookiex.go, oryx/cookiex/legacy_securecookie.go, oryx/sqlxx/sqlxx.go, oryx/mailhog/memory.go, oryx/pagination/paginationplanner/planner.go, oryx/httprouterx/router.go.
No ADRs found doc.go:5— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `doc.go` makes this repository a deployable product (line 5).
D21 · Naming Consistency· `instanceId` spells `Id` where 23 names in the project spell it `ID` · ×1
`instanceId` spells `Id` where 23 names in the project spell it `ID` oryx/metricsx/middleware.go:52— 23 of 25 names in project github.com/ory/x spell the token `ID` (23 of 25; unit: names in project github.com/ory/x containing `ID`). Peers: configx.CORSConfigSchemaID (oryx/configx/cors.go:15); configx.ServeConfigSchemaID (oryx/configx/serve.go:20); configx.TLSConfigSchemaID (oryx/configx/serve.go:21); github.com/ory/x/errorsx.RequestIDCarrier (oryx/errorsx/errors.go:57); RequestIDCarrier.RequestID (oryx/errorsx/errors.go:59). Rename to `instanceID`. [rule N6]
D21 · Naming Consistency· `DeploymentId` spells `Id` where 23 names in the project spell it `ID` · ×1
`DeploymentId` spells `Id` where 23 names in the project spell it `ID` oryx/metricsx/middleware.go:74— 23 of 25 names in project github.com/ory/x spell the token `ID` (23 of 25; unit: names in project github.com/ory/x containing `ID`). Peers: configx.CORSConfigSchemaID (oryx/configx/cors.go:15); configx.ServeConfigSchemaID (oryx/configx/serve.go:20); configx.TLSConfigSchemaID (oryx/configx/serve.go:21); github.com/ory/x/errorsx.RequestIDCarrier (oryx/errorsx/errors.go:57); RequestIDCarrier.RequestID (oryx/errorsx/errors.go:59). Rename to `DeploymentID`. [rule N6]
Scattered collaborators — 70 % of calls cross a namespace and only 54 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 5 of 214 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 214 of the 526 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: oauth2/token_hook.go, cmd/cli/handler_janitor.go, persistence/sql/persister_device.go, oauth2/refresh_hook.go, x/sqlx.go. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No seccomp profile REDACTED:1— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift fosite/README.md:173— fosite/README.md names Go 1.11 or later, but REDACTED:3 requires `go 1.25.0` (the lowest of 4 declarations): the code does not build on Go 1.11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `oryx/randx/strength`.
Benchmarks don't track allocations x/hasher_test.go— A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
X5 · Nullable reference types· Ruby's type checker does not check nil everywhere · ×1
Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Silent fallback default on error oryx/landlockx/landlockx.go:31— `runningExe` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. 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 `if` or in the doc comment, and the row stops firing.
Outdated: code.dny.dev/ssrf — `code.dny.dev/ssrf` is required at v0.2.0 in REDACTED, but v0.3.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get code.dny.dev/ssrf@v0.3.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: connectrpc.com/connect — `connectrpc.com/connect` is required at v1.20.0 in REDACTED, but v1.21.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get connectrpc.com/connect@v1.21.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/ThalesGroup/crypto11 — `github.com/ThalesGroup/crypto11` is required at v1.4.1 in REDACTED, but v1.6.8 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/ThalesGroup/crypto11@v1.6.8 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/auth0/go-jwt-middleware/v2 — `github.com/auth0/go-jwt-middleware/v2` is required at v2.3.0 in REDACTED, but v2.3.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/auth0/go-jwt-middleware/v2@v2.3.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/avast/retry-go/v4 — `github.com/avast/retry-go/v4` is required at v4.6.1 in REDACTED, but v4.7.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/avast/retry-go/v4@v4.7.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/dgraph-io/ristretto/v2 — `github.com/dgraph-io/ristretto/v2` is required at v2.4.0 in REDACTED, but v2.4.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/dgraph-io/ristretto/v2@v2.4.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/dgraph-io/ristretto/v2 — `github.com/dgraph-io/ristretto/v2` is required at v2.4.0 in REDACTED, but v2.4.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/dgraph-io/ristretto/v2@v2.4.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/fsnotify/fsnotify — `github.com/fsnotify/fsnotify` is required at v1.9.0 in REDACTED, but v1.10.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/fsnotify/fsnotify@v1.10.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-faker/faker/v4 — `github.com/go-faker/faker/v4` is required at v4.6.0 in REDACTED, but v4.12.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/go-faker/faker/v4@v4.12.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-openapi/jsonpointer — `github.com/go-openapi/jsonpointer` is required at v0.21.2 in REDACTED, but v1.0.2 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/go-openapi/jsonpointer@v1.0.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-openapi/runtime — `github.com/go-openapi/runtime` is required at v0.28.0 in REDACTED, but v0.33.4 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/go-openapi/runtime@v0.33.4 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-sql-driver/mysql — `github.com/go-sql-driver/mysql` is required at v1.9.3 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/go-sql-driver/mysql@v1.10.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gobwas/glob — `github.com/gobwas/glob` is required at v0.2.3 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/gobwas/glob@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gobwas/glob — `github.com/gobwas/glob` is required at v0.2.3 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/gobwas/glob@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/goccy/go-yaml — `github.com/goccy/go-yaml` is required at v1.18.0 in REDACTED, but v1.19.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/goccy/go-yaml@v1.19.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gofrs/flock — `github.com/gofrs/flock` is required at v0.12.1 in REDACTED, but v0.13.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/gofrs/flock@v0.13.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/google/go-jsonnet — `github.com/google/go-jsonnet` is required at v0.21.0 in REDACTED, but v0.22.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/google/go-jsonnet@v0.22.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/jackc/pgx/v5 — `github.com/jackc/pgx/v5` is required at v5.10.0 in REDACTED, but v5.13.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/jackc/pgx/v5@v5.13.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/jackc/pgx/v5 — `github.com/jackc/pgx/v5` is required at v5.10.0 in REDACTED, but v5.13.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/jackc/pgx/v5@v5.13.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/jackc/puddle/v2 — `github.com/jackc/puddle/v2` is required at v2.2.2 in REDACTED, but v2.2.4 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/jackc/puddle/v2@v2.2.4 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/knadh/koanf/maps — `github.com/knadh/koanf/maps` is required at v0.1.2 in REDACTED, but v0.1.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/knadh/koanf/maps@v0.1.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/knadh/koanf/parsers/json — `github.com/knadh/koanf/parsers/json` is required at v0.1.0 in REDACTED, but v1.0.1 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/knadh/koanf/parsers/json@v1.0.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/knadh/koanf/parsers/yaml — `github.com/knadh/koanf/parsers/yaml` is required at v0.1.0 in REDACTED, but v1.1.1 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/knadh/koanf/parsers/yaml@v1.1.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/knadh/koanf/providers/posflag — `github.com/knadh/koanf/providers/posflag` is required at v0.1.0 in REDACTED, but v1.0.2 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/knadh/koanf/providers/posflag@v1.0.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/knadh/koanf/providers/rawbytes — `github.com/knadh/koanf/providers/rawbytes` is required at v0.1.0 in REDACTED, but v1.0.1 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/knadh/koanf/providers/rawbytes@v1.0.1 && go mod tidy` and commit the updated REDACTED and go.sum.
+ 56 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 7 file(s) — `oryx/jsonx/patch.go`, `oryx/otelx/attribute.go`, `oryx/otelx/semconv/context.go`, `oryx/otelx/semconv/events.go`, `oryx/pagination/keysetpagination/paginator.go`, … (+2 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 — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a1eb07-a233-7a38-8394-5de2004ff28a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 2189 · Warnings: 452 · Recommendations: 58 · Info: 81 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 19:41 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.