Public report of ory/kratos, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 23:21 UTC · Survey ID cd_1fc365f78d6241b88411479a1a84fde2
ory/kratos
Measured 16 November 2026, 23:20 UTC, at code version b86338d
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: 83,251 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Production Readiness, 42.9
Findings by how serious they are
113 critical978 serious226 minor
11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 23:20 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 ▸
75of 75 dimensions measured by tools.
1199of 1317 findings point to an exact file and line, so you can open each one in the code. The other 118 concern the repository as a whole, such as missing documentation.
75dimensions across 7 lenses, read from 83,251 lines of product code in 4 projects.
ory/kratos is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because eight passwords or keys sit in the current code and it has uses of packages that aren't listed. It scores 55.7 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 42.9, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 11.0 points. Replacing the five deprecated dependencies comes next, worth about 8.6 points. Raising Production Readiness to 70 would lift the score to about 65.5.
Fifty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nineteen secrets can leak from the build pipeline, and thirteen known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. The eight passwords or keys in the code and the password or key in the code's history need replacing, with the old ones switched off. The eight pipeline steps that run downloads without checking them need each download checked against a known checksum first. The three uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 83,251 lines, about €250,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 42.9 to 70, the lowest score rated Strong, the score would rise from 55.7 to about 65.5.
Code composition: what the lines of code are
Product code 48%Tests 52%
Rebuild cost: about €250,000 · Estimate
Cost to rebuild
€84,000 to €420,000, for 1,399 to 4,438 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problem
High, 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 56. 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: 83,251 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 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Raises the score by about 11.0 points · Low effort · REDACTED Scanning
2
Resolve the 5 Deprecated module finding(s) in Dependency Hygiene.
Resolve the 11 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Raises the score by about 10.8 points · Medium effort · Dependency Hygiene
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €250,000 to build again, about 1.7 person-years of work. Its weakest lens is Production Readiness, at 42.9 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 11.0 points for low effort, because it clears the 8 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 30,697 lines over the last 90 days, which is about 124,493 lines a year. At that pace, the extra work comes to an estimated 12 to 72.2 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.
164 modules, with 575 dependencies between them. 2 loops run through 26 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 124 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/kratos/text uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/text, while a change to com/ory/kratos/text can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/text uses a module listed above it, which is the healthy direction.
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/kratos/ui/node uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/ui/node, while a change to com/ory/kratos/ui/node can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/ui/node uses a module listed above it, which is the healthy direction.
com/ory/kratos/x uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/x, while a change to com/ory/kratos/x can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/x uses a module listed above it, which is the healthy direction.
com/ory/kratos/x uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/x, while a change to com/ory/kratos/x can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/x uses a module listed above it, which is the healthy direction.
com/ory/kratos/x uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/x, while a change to com/ory/kratos/x can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/x uses a module listed above it, which is the healthy direction.
com/ory/kratos/x uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/x, while a change to com/ory/kratos/x can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/x uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/flow uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/selfservice/flow uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/flow uses a module listed above it, which is the healthy direction.
12→14 com/ory/kratos/selfservice/flow uses com/ory/kratos/driver/configpart of a loop✕
Connections
4 pairs of types, where a type in com/ory/kratos/selfservice/flow uses a type in com/ory/kratos/driver/config.
com/ory/kratos/selfservice/flow uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/kratos/driver/config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 com/ory/kratos/selfservice/flow uses com/ory/kratos/identitypart of a loop✕
Connections
3 pairs of types, where a type in com/ory/kratos/selfservice/flow uses a type in com/ory/kratos/identity.
com/ory/kratos/selfservice/flow uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/flow, while a change to com/ory/kratos/selfservice/flow can't break com/ory/kratos/identity.
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/kratos/session uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
com/ory/kratos/session uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/session uses a module listed above it, which is the healthy direction.
13→14 com/ory/kratos/session uses com/ory/kratos/driver/configpart of a loop✕
Connections
3 pairs of types, where a type in com/ory/kratos/session uses a type in com/ory/kratos/driver/config.
com/ory/kratos/session uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/kratos/driver/config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 com/ory/kratos/session uses com/ory/kratos/identitypart of a loop✕
Connections
10 pairs of types, where a type in com/ory/kratos/session uses a type in com/ory/kratos/identity.
com/ory/kratos/session uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/session, while a change to com/ory/kratos/session can't break com/ory/kratos/identity.
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/kratos/driver/config uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/driver/config, while a change to com/ory/kratos/driver/config can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/driver/config uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver/config uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/driver/config, while a change to com/ory/kratos/driver/config can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/driver/config uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver/config uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/driver/config, while a change to com/ory/kratos/driver/config can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/driver/config uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver/config uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/kratos/driver/config, while a change to com/ory/kratos/driver/config can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/kratos/driver/config uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver/config uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/driver/config, while a change to com/ory/kratos/driver/config can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/driver/config uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver/config uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/driver/config, while a change to com/ory/kratos/driver/config can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/driver/config uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/courier uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/courier, while a change to com/ory/kratos/courier can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/courier uses a module listed above it, which is the healthy direction.
com/ory/kratos/hydra uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/hydra, while a change to com/ory/kratos/hydra can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/hydra uses a module listed above it, which is the healthy direction.
com/ory/kratos/hydra uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/hydra, while a change to com/ory/kratos/hydra can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/hydra uses a module listed above it, which is the healthy direction.
com/ory/kratos/hydra uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/hydra, while a change to com/ory/kratos/hydra can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/hydra uses a module listed above it, which is the healthy direction.
com/ory/kratos/hydra uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/hydra, while a change to com/ory/kratos/hydra can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/hydra uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/schema uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/schema, while a change to com/ory/kratos/schema can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/schema uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/errorx uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/errorx, while a change to com/ory/kratos/selfservice/errorx can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/errorx uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/errorx uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/errorx, while a change to com/ory/kratos/selfservice/errorx can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/errorx uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/errorx uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/errorx, while a change to com/ory/kratos/selfservice/errorx can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/errorx uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/errorx uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/errorx, while a change to com/ory/kratos/selfservice/errorx can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/errorx uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/errorx uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/errorx, while a change to com/ory/kratos/selfservice/errorx can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/errorx uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/errorx uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/errorx, while a change to com/ory/kratos/selfservice/errorx can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/errorx uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/identity uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/identity, while a change to com/ory/kratos/identity can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/identity uses a module listed above it, which is the healthy direction.
com/ory/kratos/continuity uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/continuity, while a change to com/ory/kratos/continuity can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/continuity uses a module listed above it, which is the healthy direction.
com/ory/kratos/continuity uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/continuity, while a change to com/ory/kratos/continuity can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/continuity uses a module listed above it, which is the healthy direction.
com/ory/kratos/continuity uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/continuity, while a change to com/ory/kratos/continuity can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/continuity uses a module listed above it, which is the healthy direction.
com/ory/kratos/continuity uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/continuity, while a change to com/ory/kratos/continuity can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/continuity uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/recovery uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/flow/recovery, while a change to com/ory/kratos/selfservice/flow/recovery can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/recovery uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/registration uses a module listed above it, which is the healthy direction.
22→25 com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/selfservice/hookpart of a loop✕
Connections
1 pair of types, where a type in com/ory/kratos/selfservice/flow/registration uses a type in com/ory/kratos/selfservice/hook.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/selfservice/hook, so a change to com/ory/kratos/selfservice/hook can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/selfservice/hook.
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.
22→28 com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/selfservice/flow/loginpart of a loop✕
Connections
2 pairs of types, where a type in com/ory/kratos/selfservice/flow/registration uses a type in com/ory/kratos/selfservice/flow/login.
com/ory/kratos/selfservice/flow/registration uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/flow/registration, while a change to com/ory/kratos/selfservice/flow/registration can't break com/ory/kratos/selfservice/flow/login.
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/kratos/selfservice/flow/verification uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/verification uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/flow/verification, while a change to com/ory/kratos/selfservice/flow/verification can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/verification uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/settings uses a module listed above it, which is the healthy direction.
24→25 com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/selfservice/hookpart of a loop✕
Connections
1 pair of types, where a type in com/ory/kratos/selfservice/flow/settings uses a type in com/ory/kratos/selfservice/hook.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/selfservice/hook, so a change to com/ory/kratos/selfservice/hook can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/selfservice/hook.
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.
24→28 com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/selfservice/flow/loginpart of a loop✕
Connections
1 pair of types, where a type in com/ory/kratos/selfservice/flow/settings uses a type in com/ory/kratos/selfservice/flow/login.
com/ory/kratos/selfservice/flow/settings uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/flow/settings, while a change to com/ory/kratos/selfservice/flow/settings can't break com/ory/kratos/selfservice/flow/login.
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/kratos/selfservice/hook uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow/verification, so a change to com/ory/kratos/selfservice/flow/verification can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/selfservice/flow/verification.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/hook uses a module listed above it, which is the healthy direction.
25→28 com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow/loginpart of a loop✕
Connections
12 pairs of types, where a type in com/ory/kratos/selfservice/hook uses a type in com/ory/kratos/selfservice/flow/login.
com/ory/kratos/selfservice/hook uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/hook, while a change to com/ory/kratos/selfservice/hook can't break com/ory/kratos/selfservice/flow/login.
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/kratos/selfservice/strategy/link uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/selfservice/flow/verification, so a change to com/ory/kratos/selfservice/flow/verification can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/selfservice/flow/verification.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/link uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/link, while a change to com/ory/kratos/selfservice/strategy/link can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/link uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/profile uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/profile, while a change to com/ory/kratos/selfservice/strategy/profile can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/profile uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/flow/login uses com/ory/kratos/selfservice/hook, so a change to com/ory/kratos/selfservice/hook can break com/ory/kratos/selfservice/flow/login, while a change to com/ory/kratos/selfservice/flow/login can't break com/ory/kratos/selfservice/hook.
Position
Below the diagonal: com/ory/kratos/selfservice/flow/login uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/flow/verification, so a change to com/ory/kratos/selfservice/flow/verification can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/flow/verification.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/strategy/link, so a change to com/ory/kratos/selfservice/strategy/link can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/strategy/link.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/persistence/sql uses a module listed above it, which is the healthy direction.
29→37 com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/strategy/codepart of a loop✕
Connections
12 pairs of types, where a type in com/ory/kratos/persistence/sql uses a type in com/ory/kratos/selfservice/strategy/code.
com/ory/kratos/persistence/sql uses com/ory/kratos/selfservice/strategy/code, so a change to com/ory/kratos/selfservice/strategy/code can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/selfservice/strategy/code.
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.
29→38 com/ory/kratos/persistence/sql uses com/ory/kratos/persistencepart of a loop✕
Connections
2 pairs of types, where a type in com/ory/kratos/persistence/sql uses a type in com/ory/kratos/persistence.
com/ory/kratos/persistence/sql uses com/ory/kratos/persistence, so a change to com/ory/kratos/persistence can break com/ory/kratos/persistence/sql, while a change to com/ory/kratos/persistence/sql can't break com/ory/kratos/persistence.
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/kratos/selfservice/strategy/idfirst uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/idfirst uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/idfirst, while a change to com/ory/kratos/selfservice/strategy/idfirst can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/idfirst uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/lookup uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/lookup, while a change to com/ory/kratos/selfservice/strategy/lookup can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/lookup uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/x/sqlxx, so a change to com/ory/x/sqlxx can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/x/sqlxx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/oidc uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/oidc, while a change to com/ory/kratos/selfservice/strategy/oidc can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/oidc uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/passkey uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/passkey, while a change to com/ory/kratos/selfservice/strategy/passkey can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/passkey uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/password uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/password, while a change to com/ory/kratos/selfservice/strategy/password can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/password uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/totp uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/totp, while a change to com/ory/kratos/selfservice/strategy/totp can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/totp uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/webauthn uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/webauthn, while a change to com/ory/kratos/selfservice/strategy/webauthn can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/webauthn uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/text, so a change to com/ory/kratos/text can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/text.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/ui/node, so a change to com/ory/kratos/ui/node can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/ui/node.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in com/ory/kratos/selfservice/strategy/code uses a type in com/ory/kratos/identity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/flow/verification, so a change to com/ory/kratos/selfservice/flow/verification can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/flow/verification.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/selfservice/strategy/code uses com/ory/kratos/persistence/sql, so a change to com/ory/kratos/persistence/sql can break com/ory/kratos/selfservice/strategy/code, while a change to com/ory/kratos/selfservice/strategy/code can't break com/ory/kratos/persistence/sql.
Position
Below the diagonal: com/ory/kratos/selfservice/strategy/code uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/flow/verification, so a change to com/ory/kratos/selfservice/flow/verification can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/flow/verification.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/strategy/link, so a change to com/ory/kratos/selfservice/strategy/link can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/strategy/link.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/persistence uses com/ory/kratos/selfservice/strategy/code, so a change to com/ory/kratos/selfservice/strategy/code can break com/ory/kratos/persistence, while a change to com/ory/kratos/persistence can't break com/ory/kratos/selfservice/strategy/code.
Position
Below the diagonal: com/ory/kratos/persistence uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/selfservice/flow, so a change to com/ory/kratos/selfservice/flow can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/selfservice/flow.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/persistence, so a change to com/ory/kratos/persistence can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/persistence.
Position
Below the diagonal: com/ory/kratos/pkg/testhelpers uses a module listed above it, which is the healthy direction.
39→40 com/ory/kratos/pkg/testhelpers uses com/ory/kratos/driverpart of a loop✕
Connections
2 pairs of types, where a type in com/ory/kratos/pkg/testhelpers uses a type in com/ory/kratos/driver.
com/ory/kratos/pkg/testhelpers uses com/ory/kratos/driver, so a change to com/ory/kratos/driver can break com/ory/kratos/pkg/testhelpers, while a change to com/ory/kratos/pkg/testhelpers can't break com/ory/kratos/driver.
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/kratos/driver uses com/ory/kratos/x/nosurfx, so a change to com/ory/kratos/x/nosurfx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/x/nosurfx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/x/clock, so a change to com/ory/x/clock can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/x/clock.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/x/httprouterx, so a change to com/ory/x/httprouterx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/x/httprouterx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/x/logrusx, so a change to com/ory/x/logrusx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/x/logrusx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/x/otelx, so a change to com/ory/x/otelx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/x/otelx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/x/configx, so a change to com/ory/x/configx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/x/configx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/x/httpx, so a change to com/ory/x/httpx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/x/httpx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/x, so a change to com/ory/kratos/x can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/x.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/session, so a change to com/ory/kratos/session can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/session.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/driver/config, so a change to com/ory/kratos/driver/config can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/driver/config.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/courier, so a change to com/ory/kratos/courier can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/courier.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/hydra, so a change to com/ory/kratos/hydra can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/hydra.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/schema, so a change to com/ory/kratos/schema can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/schema.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/errorx, so a change to com/ory/kratos/selfservice/errorx can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/errorx.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/identity, so a change to com/ory/kratos/identity can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/identity.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/continuity, so a change to com/ory/kratos/continuity can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/continuity.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/flow/recovery, so a change to com/ory/kratos/selfservice/flow/recovery can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/flow/recovery.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/flow/registration, so a change to com/ory/kratos/selfservice/flow/registration can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/flow/registration.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/flow/verification, so a change to com/ory/kratos/selfservice/flow/verification can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/flow/verification.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/flow/settings, so a change to com/ory/kratos/selfservice/flow/settings can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/flow/settings.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/hook, so a change to com/ory/kratos/selfservice/hook can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/hook.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/link, so a change to com/ory/kratos/selfservice/strategy/link can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/link.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/profile, so a change to com/ory/kratos/selfservice/strategy/profile can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/profile.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/flow/login, so a change to com/ory/kratos/selfservice/flow/login can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/flow/login.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/idfirst, so a change to com/ory/kratos/selfservice/strategy/idfirst can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/idfirst.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/lookup, so a change to com/ory/kratos/selfservice/strategy/lookup can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/lookup.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/passkey, so a change to com/ory/kratos/selfservice/strategy/passkey can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/passkey.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/password, so a change to com/ory/kratos/selfservice/strategy/password can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/password.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/totp, so a change to com/ory/kratos/selfservice/strategy/totp can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/totp.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/webauthn, so a change to com/ory/kratos/selfservice/strategy/webauthn can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/webauthn.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/selfservice/strategy/code, so a change to com/ory/kratos/selfservice/strategy/code can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/selfservice/strategy/code.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/persistence, so a change to com/ory/kratos/persistence can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/persistence.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
com/ory/kratos/driver uses com/ory/kratos/pkg/testhelpers, so a change to com/ory/kratos/pkg/testhelpers can break com/ory/kratos/driver, while a change to com/ory/kratos/driver can't break com/ory/kratos/pkg/testhelpers.
Position
Below the diagonal: com/ory/kratos/driver uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 61.4 · Adequate · gated by R10 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
99
High / Critical
A02:2025 — Security Misconfiguration
51
High / Critical
A03:2025 — Software Supply Chain Failures
49
High / Critical
A07:2025 — Authentication Failures
10
High / Critical
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED; Resolve the 11 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene; Resolve the 5 Deprecated module finding(s) in Dependency Hygiene.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
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 — 113
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 — 978
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 — 226
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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 75 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 — 75 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, 1199 of 1317 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 — test/e2e/ (@playwright/test/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`) and a Codecov configuration (codecov.yml, target 60%) shows coverage is measured in your own CI.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 328 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 308 test source file(s) (.go) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `REDACTED` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — 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`, … (+3 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.
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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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. 32 further occurrence(s) are not listed individually; the score already reflects all 72.
Repo exclusion declarations: 14 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
82 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was jsonschemax.listPaths at 62. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being container.translateValidationError at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: ui/container/container.go (container.translateValidationError at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 76 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), Handler.NewLoginFlow (cyclomatic 43), decoderx.decodeURLValues (cyclomatic 43). — 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.
+ 132 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 10 bodies over 60 down to 60 or less in Cognitive Complexity — start with decoderx.decodeURLValues (cognitive 117), jsonschemax.listPaths (cognitive 95), InMemory.Search (cognitive 78). — 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 10 together lifts Cognitive Complexity from 5.0 to about 6.0/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 8 TooManyMethods finding(s) in God Classes — start with strategy.go (3), config.go, registry_default.go. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 MethodTooLong finding(s) in God Classes — start with hook.go (3), persister_identity.go, migrator.go. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 FileTooLong finding(s) in God Classes — start with handler.go (2), persister_identity.go, config.go. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication4.7 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
277 duplicated block group(s) detected. 13.4 % of the production lines (11,117 of 83,251) are in a reported copy. A further 194 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 5 of the 471 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.
+ 156 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 26 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with helpers.go (5), handler.go (3), error.go (2). — One of this dimension's main actionable groups (26 warning-level).
Resolve the 25 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), handler.go (2), provider_github.go (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 20 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with handler.go (5), persister_identity.go (2), calibrate.go. — One of this dimension's main actionable groups (20 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.0 / 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.
4 production modules (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 4 (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 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with flow.go (2), registry_default.go, provider_apple.go. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality8.9 / 10Strong✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
6 skipped, 17 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 328 tests. Measured on the JavaScript/TypeScript suite only — at least 308 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: responds with a HTML response on link click of an API flow if the code is expired · ×17test/e2e/cypress/integration/profiles/verification/verify/errors.spec.ts:96
Resolve the 17 No assertions finding(s) in Test Quality — start with errors.spec.ts (6), success.spec.ts (6), error.spec.ts (3). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 6 Skipped test finding(s) in Test Quality — start with success.spec.ts (3), phone-normalization.spec.ts, error.spec.ts. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d10_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.
89 outdated, 5 author-deprecated direct Go module(s), 11 pinning or checksum defect(s). 168 of 168 direct requirement(s) were graded against proxy.golang.org (0 not served there, 9 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/arbovm/levenshtein · ×11
Resolve the 11 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (5 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.
7 secret(s) detected. 5 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.
REDACTED
What to do
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 255 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 255 package(s) this repository's committed lockfile installs for a consumer — its 11 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 24 `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. 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 18 Hotspot finding(s) in Churn × Complexity Hotspots — start with handler.go (2), strategy.go (2), hook.go (2). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with passkey_schema_extension.go. — 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.6 / 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 322 of the 706 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.
41 deducted task-comment markers across 83251 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.
Resolve the 30 TodoComment finding(s) in Explicit Debt — start with require_verified_address.go (4), web_hook.go (3), REDACTED (2). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 10 FixmeComment finding(s) in Explicit Debt — start with REDACTED (4), container_test.go (2), success.spec.ts (2). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with mailhog.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 6 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
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.
17 naming inconsistencies among 647 declarations measured against a convention their peers follow.
`writeMessagesJson` spells `Json` where 84 names in the project spell it `JSON`cmd/clidoc/main.go:318
`newHttpChannel` spells `Http` where 31 names in the project spell it `HTTP`courier/http_channel.go:41
`formatJsonErrors` spells `Json` where 84 names in the project spell it `JSON`driver/config/config.go:528
`ToUiNodeGroup` spells `Ui` where 58 names in the project spell it `UI`identity/credentials.go:108
`instanceId` spells `Id` where 23 names in the project spell it `ID`oryx/metricsx/middleware.go:52
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 `writeMessagesJson` spells `Json` where 84 names in the project spell it… finding(s) in Naming Consistency — start with main.go. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `newHttpChannel` spells `Http` where 31 names in the project spell it… finding(s) in Naming Consistency — start with http_channel.go. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `formatJsonErrors` spells `Json` where 84 names in the project spell it… finding(s) in Naming Consistency — start with config.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.4 / 10Stronggated by 6 serious findings✓ 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.
6 API inconsistencies among 934 exposed members measured against a convention their peers follow.
`Config.CourierSMTPHeaders` returns a map (`map[K]V`) where its 13 siblings return a slice (`[]T`)driver/config/config.go:1260
`MigrationBox.SelectedMigrations` takes no context.Context; its 6 sibling operations take oneoryx/popx/migration_box.go:240
`testhelpers.NewNetworkUnlessExisting` takes its context.Context at position 2 where 27 members of the package take it firstpkg/testhelpers/network.go:17
`testhelpers.NewNetwork` takes its context.Context at position 2 where 27 members of the package take it firstpkg/testhelpers/network.go:27
`testhelpers.SkipIfNetworkContext` takes its context.Context last where 27 members of the package take it firstpkg/testhelpers/network.go:40
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 `Config.CourierSMTPHeaders` returns a map (`map[K]V`) where its 13… finding(s) in Internal API Consistency — start with config.go. — One of this dimension's main actionable groups (1 warning-level).
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).
Resolve the 1 `testhelpers.NewNetworkUnlessExisting` takes its context.Context at… finding(s) in Internal API Consistency — start with network.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.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
66 domain type(s) cross context boundaries across 3 contexts; they are measured and withheld (not published, not scored). Contexts: courier, selfservice, session.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
2 of 3 build units (Go, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×2package.json:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json, REDACTED. — One of this dimension's main actionable groups (2 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.
78 % of calls cross a namespace and 28 % go through an interface, but 59 % 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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
99 finding(s): 0 critical, 83 high, 12 medium, 4 low. 53 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 15 file(s) — `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, …), `oryx/pagination/keysetpagination/paginator.go` (line 146, line 175), … (+10 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 1 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
+ 13 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 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
No action in Static Analysis (SAST) — all 53 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 (53 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 21 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (19), REDACTED (2). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 12 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED (5). — One of this dimension's main actionable groups (12 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 35 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (26), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (35 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 13 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (13 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.
18 of 322 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is courier/template/testhelpers/testhelpers.go. Counted over 322 of the 706 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with handler.go. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 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.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 2 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.
End-of-life runtime: Node.js 16.nvmrc:1
What to do
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Package `testhelpers` serves requests (request-handler function literals run on a goroutine per request, and every one sees the same package variables and captured values) but writes that shared state outside any lock (called; e.g. `called` in `NewSettingsLoginAcceptAPIServer` at line 154). 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. — REDACTED:154
Package `hooktest` serves requests (request-handler function literals run on a goroutine per request, and every one sees the same package variables and captured values) but writes that shared state outside any lock (s.LastBody; e.g. `s.LastBody` in `NewServer` at line 34). 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. — selfservice/hook/hooktest/web_hook_test_server.go:34
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.
`CourierConfigs` declares 24 methods: `CourierTemplatesRoot`, `CourierTemplatesVerificationInvalid`, `CourierTemplatesVerificationValid`, `CourierTemplatesRecoveryInvalid`, `CourierTemplatesRecoveryValid`, `CourierTemplatesRecoveryCodeInvalid`, `CourierTemplatesRecoveryCodeValid`, `CourierTemplatesVerificationCodeInvalid`, `CourierTemplatesVerificationCodeValid`, `CourierTemplatesLoginCodeValid`, `CourierTemplatesRegistrationCodeValid`, `CourierSMSTemplatesVerificationCodeValid`, `CourierSMSTemplatesRecoveryCodeValid`, `CourierSMSTemplatesLoginCodeValid`, `CourierSMSTemplatesRegistrationCodeValid`, `CourierTemplatesVerifiableAddressChanged`, `CourierSMSTemplatesVerifiableAddressChanged`, `CourierTemplatesAuthenticatorKeyAdded`, `CourierSMSTemplatesAuthenticatorKeyAdded`, `CourierMessageRetries`, `CourierWorkerPullCount`, `CourierWorkerPullWait`, `CourierChannels`, `ClientSMTPNoPrivateIPRanges`. 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. — driver/config/config.go:318
`Registry` declares 16 methods: `Init`, `SetLogger`, `SetJSONNetVMProvider`, `Clock`, `WithCSRFHandler`, `WithCSRFTokenGenerator`, `HealthHandler`, `CookieManager`, `ContinuityCookieManager`, `RegisterPublicRoutes`, `RegisterAdminRoutes`, `Tracer`, `SetTracer`, `CourierConfig`, `SetConfig`, `SetContextualizer`. 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. — driver/registry.go:50
`PrivilegedPool` declares 17 methods: `FindByCredentialsIdentifier`, `DeleteIdentity`, `DeleteIdentities`, `UpdateVerifiableAddress`, `CreateIdentity`, `CreateIdentities`, `UpdateIdentity`, `UpdateIdentityColumns`, `UpdateCredentialsConfig`, `GetIdentityConfidential`, `ListVerifiableAddresses`, `ListRecoveryAddresses`, `HydrateIdentityAssociations`, `InjectTraitsSchemaURL`, `FindIdentityByCredentialIdentifier`, `FindIdentityByWebauthnUserHandle`, `FindIdentityByExternalID`. 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. — identity/pool.go:186
`Persister` declares 21 methods: `GetConnection`, `GetSession`, `ListSessions`, `ListSessionsByIdentity`, `UpsertSession`, `ExtendSession`, `DeleteSession`, `DeleteSessionsByIdentity`, `GetSessionByToken`, `DeleteExpiredSessions`, `DeleteSessionByToken`, `RevokeSessionByToken`, `RevokeSessionById`, `RevokeSession`, `RevokeSessionsIdentityExcept`, `RevokeSessionsByIdentities`, `RevokeSessionsByIDs`, `RevokeAllSessions`, `DeleteSessionsByIdentities`, `DeleteSessionsByIDs`, `DeleteAllSessions`. 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. — session/persistence.go:33
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.
Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.
Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.
Do you agree with this assessment?
ED3 · Event naming7.0 / 10Strong✓ Tool-verified
Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).
Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.
`ErrorEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — oryx/watcherx/event.go:24
`ChangeEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — oryx/watcherx/event.go:28
`RemoveEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — oryx/watcherx/event.go:32
What to do
Name new events in the past tense: they record facts that already happened. Do not rename an event that is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
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.
pkg/client-go/README.md links to `docs/CourierAPI.md#getcouriermessage`, but `pkg/client-go/docs/CourierAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:82
pkg/client-go/README.md links to `docs/FrontendAPI.md#createbrowserloginflow`, but `pkg/client-go/docs/FrontendAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:84
pkg/client-go/README.md links to `docs/IdentityAPI.md#batchpatchidentities`, but `pkg/client-go/docs/IdentityAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:118
pkg/client-go/README.md links to `docs/MetadataAPI.md#getversion`, but `pkg/client-go/docs/MetadataAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:139
pkg/client-go/README.md links to `docs/AdminIdentityImportCredentialsLookupSecret.md`, but `pkg/client-go/docs/AdminIdentityImportCredentialsLookupSecret.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:146
pkg/client-go/README.md links to `docs/AdminIdentityImportCredentialsLookupSecretConfig.md`, but `pkg/client-go/docs/AdminIdentityImportCredentialsLookupSecretConfig.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:147
pkg/client-go/README.md links to `docs/AuthenticatorAssuranceLevel.md`, but `pkg/client-go/docs/AuthenticatorAssuranceLevel.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:148
pkg/client-go/README.md links to `docs/BatchPatchIdentitiesResponse.md`, but `pkg/client-go/docs/BatchPatchIdentitiesResponse.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:149
pkg/client-go/README.md links to `docs/ConsistencyRequestParameters.md`, but `pkg/client-go/docs/ConsistencyRequestParameters.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:150
pkg/client-go/README.md links to `docs/ContinueWith.md`, but `pkg/client-go/docs/ContinueWith.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:151
pkg/client-go/README.md links to `docs/ContinueWithDeviceAuthnPinEntryUi.md`, but `pkg/client-go/docs/ContinueWithDeviceAuthnPinEntryUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:152
pkg/client-go/README.md links to `docs/ContinueWithDeviceAuthnPinEntryUiData.md`, but `pkg/client-go/docs/ContinueWithDeviceAuthnPinEntryUiData.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:153
pkg/client-go/README.md links to `docs/ContinueWithRecoveryUi.md`, but `pkg/client-go/docs/ContinueWithRecoveryUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:154
pkg/client-go/README.md links to `docs/ContinueWithRecoveryUiFlow.md`, but `pkg/client-go/docs/ContinueWithRecoveryUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:155
pkg/client-go/README.md links to `docs/ContinueWithRedirectBrowserTo.md`, but `pkg/client-go/docs/ContinueWithRedirectBrowserTo.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:156
pkg/client-go/README.md links to `docs/ContinueWithSetOrySessionToken.md`, but `pkg/client-go/docs/ContinueWithSetOrySessionToken.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:157
pkg/client-go/README.md links to `docs/ContinueWithSettingsUi.md`, but `pkg/client-go/docs/ContinueWithSettingsUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:158
pkg/client-go/README.md links to `docs/ContinueWithSettingsUiFlow.md`, but `pkg/client-go/docs/ContinueWithSettingsUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:159
pkg/client-go/README.md links to `docs/ContinueWithVerificationUi.md`, but `pkg/client-go/docs/ContinueWithVerificationUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:160
pkg/client-go/README.md links to `docs/ContinueWithVerificationUiFlow.md`, but `pkg/client-go/docs/ContinueWithVerificationUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:161
pkg/client-go/README.md links to `docs/CourierMessageStatus.md`, but `pkg/client-go/docs/CourierMessageStatus.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:162
pkg/client-go/README.md links to `docs/CourierMessageType.md`, but `pkg/client-go/docs/CourierMessageType.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:163
pkg/client-go/README.md links to `docs/CreateFedcmFlowResponse.md`, but `pkg/client-go/docs/CreateFedcmFlowResponse.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:164
pkg/client-go/README.md links to `docs/CreateIdentityBody.md`, but `pkg/client-go/docs/CreateIdentityBody.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:165
pkg/client-go/README.md links to `docs/CreateRecoveryCodeForIdentityBody.md`, but `pkg/client-go/docs/CreateRecoveryCodeForIdentityBody.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/client-go/README.md:166
pkg/httpclient/README.md links to `docs/CourierAPI.md#getcouriermessage`, but `pkg/httpclient/docs/CourierAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:82
pkg/httpclient/README.md links to `docs/FrontendAPI.md#createbrowserloginflow`, but `pkg/httpclient/docs/FrontendAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:84
pkg/httpclient/README.md links to `docs/IdentityAPI.md#batchpatchidentities`, but `pkg/httpclient/docs/IdentityAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:118
pkg/httpclient/README.md links to `docs/MetadataAPI.md#getversion`, but `pkg/httpclient/docs/MetadataAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:139
pkg/httpclient/README.md links to `docs/AdminIdentityImportCredentialsLookupSecret.md`, but `pkg/httpclient/docs/AdminIdentityImportCredentialsLookupSecret.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:146
pkg/httpclient/README.md links to `docs/AdminIdentityImportCredentialsLookupSecretConfig.md`, but `pkg/httpclient/docs/AdminIdentityImportCredentialsLookupSecretConfig.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:147
pkg/httpclient/README.md links to `docs/AuthenticatorAssuranceLevel.md`, but `pkg/httpclient/docs/AuthenticatorAssuranceLevel.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:148
pkg/httpclient/README.md links to `docs/BatchPatchIdentitiesResponse.md`, but `pkg/httpclient/docs/BatchPatchIdentitiesResponse.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:149
pkg/httpclient/README.md links to `docs/ConsistencyRequestParameters.md`, but `pkg/httpclient/docs/ConsistencyRequestParameters.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:150
pkg/httpclient/README.md links to `docs/ContinueWith.md`, but `pkg/httpclient/docs/ContinueWith.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:151
pkg/httpclient/README.md links to `docs/ContinueWithDeviceAuthnPinEntryUi.md`, but `pkg/httpclient/docs/ContinueWithDeviceAuthnPinEntryUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:152
pkg/httpclient/README.md links to `docs/ContinueWithDeviceAuthnPinEntryUiData.md`, but `pkg/httpclient/docs/ContinueWithDeviceAuthnPinEntryUiData.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:153
pkg/httpclient/README.md links to `docs/ContinueWithRecoveryUi.md`, but `pkg/httpclient/docs/ContinueWithRecoveryUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:154
pkg/httpclient/README.md links to `docs/ContinueWithRecoveryUiFlow.md`, but `pkg/httpclient/docs/ContinueWithRecoveryUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:155
pkg/httpclient/README.md links to `docs/ContinueWithRedirectBrowserTo.md`, but `pkg/httpclient/docs/ContinueWithRedirectBrowserTo.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — pkg/httpclient/README.md:156
What to do
Reconcile the README with reality: pkg/client-go/README.md links to `docs/CourierAPI.md#getcouriermessage`, but `pkg/client-go/docs/CourierAPI.md` does not exist; pkg/client-go/README.md links to `docs/FrontendAPI.md#createbrowserloginflow`, but `pkg/client-go/docs/FrontendAPI.md` does not exist; pkg/client-go/README.md links to `docs/IdentityAPI.md#batchpatchidentities`, but `pkg/client-go/docs/IdentityAPI.md` does not exist; pkg/client-go/README.md links to `docs/MetadataAPI.md#getversion`, but `pkg/client-go/docs/MetadataAPI.md` does not exist; pkg/client-go/README.md links to `docs/AdminIdentityImportCredentialsLookupSecret.md`, but `pkg/client-go/docs/AdminIdentityImportCredentialsLookupSecret.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:12
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
`http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×7) — pkg/testhelpers/handler_mock.go:113, pkg/testhelpers/handler_mock.go:119, pkg/testhelpers/handler_mock.go:125, …
What to do
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
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. — persistence/sql/persister_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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety9.6 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
x/webauthnx/js/webauthn.js:103 · x/webauthnx/js/webauthn.js:338 · x/webauthnx/js/webauthn.js:389 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — x/webauthnx/js/webauthn.js:103
x/webauthnx/js/webauthn.js:62 · x/webauthnx/js/webauthn.js:194 · x/webauthnx/js/webauthn.js:265 — 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. — x/webauthnx/js/webauthn.js:62
x/webauthnx/js/webauthn.js:31 · x/webauthnx/js/webauthn.js:84 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — x/webauthnx/js/webauthn.js:31
x/webauthnx/js/webauthn.js:165 · x/webauthnx/js/webauthn.js:231 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — x/webauthnx/js/webauthn.js:165
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
__oryPasskeyLoginAutocompleteInit has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — x/webauthnx/js/webauthn.js:140
__oryPasskeyRegistration has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — x/webauthnx/js/webauthn.js:300
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
1 file(s) (~446 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
112 file(s) (~18303 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — test/e2e
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×2) — test/e2e/cypress/plugins/index.js:8, test/e2e/cypress/plugins/index.js:19
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — test/e2e/playwright/lib/request.ts:4, test/e2e/playwright/lib/config.ts:4, test/e2e/cypress/helpers/oauth2.ts:4
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — package.json:17
Declared in oryx/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — oryx/package.json:9
Declared in test/e2e/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — test/e2e/package.json:31
Only test files import it (first: test/e2e/cypress/support/commands.ts:18) — move it to devDependencies. — package.json:14
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `Caddyfile` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — contrib/quickstart/kratos/cloud/Caddyfile:10
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
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 `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 guard7.0 / 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.
`idx` is the result of a search that answers -1 when nothing is found, and `chain[idx:]` uses it as a bound with no test of `idx` in between. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Test `idx < 0` (or use `strings.Cut`) before using it. — schema/prevalidate.go:135
`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. (×16) — x/cookie.go:57, x/normalize.go:79, x/webauthnx/aaguid/aaguid.go:47, …
`v, _ := applyPRECIS(emailProfile, value, true)` writes the call's error to `_` and then uses `v` as if the call succeeded. When `applyPRECIS` fails, `v` 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 `v` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — x/normalize.go:88
`value, _ = applyPRECIS(phoneProfile, value, true)` writes the call's error to `_` and then uses `value` as if the call succeeded. When `applyPRECIS` fails, `value` 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 `value` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — x/normalize.go:99
`pointer, _ := jsonschemax.JSONPointerToDotNotation(e.InstancePtr)` writes the call's error to `_` and then uses `pointer` as if the call succeeded. When `jsonschemax.JSONPointerToDotNotation` fails, `pointer` 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 `pointer` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×2) — ui/container/container.go:195, ui/container/container.go:215
`if err := json.Unmarshal(cred.Config, &hashedPassword); 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. — selfservice/strategy/password/settings.go:133
`rawResponse, _ := io.ReadAll(body)` writes the call's error to `_` and then uses `rawResponse` as if the call succeeded. When `io.ReadAll` fails, `rawResponse` 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 `rawResponse` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×3) — selfservice/strategy/oidc/provider_amazon.go:121, selfservice/strategy/oidc/provider_amazon.go:128, selfservice/strategy/oidc/provider_uaepass.go:147
`if err := json.Unmarshal(a, &aVal); 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. — selfservice/strategy/oidc/strategy_login.go:205
`if err := json.Unmarshal(b, &bVal); 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. — selfservice/strategy/oidc/strategy_login.go:208
`if _, _, err := s.d.PrivilegedIdentityPool().FindByCredentialsIdentifier(ctx, s.ID(), identity.OIDCUniqueID(provider.Config().ID, claims.Subject)); 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. — selfservice/strategy/oidc/strategy_registration.go:329
`t, ok := t.(courier.EmailTemplate)` failed on this branch, so `t` is the zero value of `courier.EmailTemplate` here, and that is what is reported: the value that did not fit is lost. Report `t` itself (and `%T` of it) instead. — selfservice/strategy/code/code_sender.go:494
`t, ok := t.(courier.SMSTemplate)` failed on this branch, so `t` is the zero value of `courier.SMSTemplate` here, and that is what is reported: the value that did not fit is lost. Report `t` itself (and `%T` of it) instead. — selfservice/strategy/code/code_sender.go:507
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. (×4) — selfservice/flowhelpers/login.go:24, selfservice/flowhelpers/login.go:26, oryx/prometheusx/exemplar.go:41, …
`if sess, err := h.d.SessionManager().FetchFromRequest(ctx, r, session.ExpandNothing, identity.ExpandNothing); 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. — selfservice/flow/registration/handler.go:417
`shouldSkip, _ := strconv.ParseBool(u.Query().Get("skip_settings"))` writes the call's error to `_` and then uses `shouldSkip` as if the call succeeded. When `strconv.ParseBool` fails, `shouldSkip` 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 `shouldSkip` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — selfservice/flow/recovery/flow.go:259
`refresh, _ := strconv.ParseBool(r.URL.Query().Get("refresh"))` writes the call's error to `_` and then uses `refresh` as if the call succeeded. When `strconv.ParseBool` fails, `refresh` 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 `refresh` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — selfservice/flow/login/flow.go:216
`linkableStrategy, ok := strategy.(LinkableStrategy)` failed on this branch, so `linkableStrategy` is the zero value of `LinkableStrategy` here, and that is what is reported: the value that did not fit is lost. Report `strategy` itself (and `%T` of it) instead. — selfservice/flow/login/hook.go:435
`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
`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
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
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 — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 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 JavaScript 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`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. The cause is in the repository, not in our sandbox: package.json has no "start" script, so `npm run start` could not start the app. 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.
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.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 8 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 (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 17 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one; 29 persistence-mapped domain entity/entities (gorm/bun/db/xorm-tagged)
ED1 Handler temporal coupling — no event handlers detected — temporal-coupling check not applicable
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (28 Go aggregate(s) recording domain events (own events-slice append / raise-record))
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 113 test file(s) reach none of 1 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 0% of this repository's production lines — go (83,251 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — go (83,251 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not 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.
X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. 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.
Boundary-crossing change coupling: handler.go ↔ handler.go selfservice/flow/settings/handler.go:1— `selfservice/flow/settings/handler.go` (context selfservice) and `x/webauthnx/handler.go` (context x) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `41ce0760` fix: update swagger bucket annotations; `a14c3f22` feat: add ratelimit buckets to swagger definitions; `7fb085b6` fix: revert Go 1.19 formatting changes (at that commit the file was still `selfservice/strategy/webauthn/handler.go`) — run `git show` on any of them.
Unlisted import 'playwright-core' test/e2e/playwright/lib/request.ts:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'retry' test/e2e/playwright/lib/config.ts:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'uuid' test/e2e/cypress/helpers/oauth2.ts:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
TodoComment test/e2e/playwright/tests/desktop/identifier_first/oidc.login.spec.ts:144— // This is required, because OIDC issues a new session on refresh (TODO), and MySQL does not store sub second timestamps, so we need to wait a bit — 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 selfservice/strategy/password/registration.go:212— // TODO remove me when everyone has migrated. — 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 selfservice/strategy/password/registration.go:228— // TODO end — 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 selfservice/strategy/code/code_sender.go:453— // TODO: this can likely be abstracted by making templates not specific to the channel they're using — 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 selfservice/strategy/code/strategy.go:530— // TODO Remove this normalization once the via parameter is deprecated. — 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 selfservice/strategy/code/strategy_login.go:427— // TODO this section should be removed at some point when we are sure that all identities have a code credential. — 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 selfservice/strategy/code/strategy_verification.go:193— // TODO: In the future, we might want to redirect to a custom URI scheme here, to allow to open an app on the device of — 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 selfservice/hook/require_verified_address.go:64— // TODO remove once flag is removed. — 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 selfservice/hook/require_verified_address.go:88— // TODO remove once flag is removed. — 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 selfservice/hook/require_verified_address.go:71— // END 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 selfservice/hook/require_verified_address.go:93— // END 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 selfservice/hook/show_verification_ui.go:88— // TODO This is a fallback for flows that do not have the appropriate internalContext yet. — 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 selfservice/hook/verification.go:146— // TODO: this is pretty ugly, we should probably have a better way to handle CSRF tokens here. — 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 selfservice/hook/web_hook.go:555— // TODO(@alnr): improve this implementation to redact sensitive data — 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 selfservice/hook/web_hook.go:566— // TODO(@alnr): redact sensitive data — 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 selfservice/hook/web_hook.go:574— // TODO(@alnr): redact sensitive data — 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 selfservice/flow/error.go:58— // TODO: This error could be enhanced by providing a "flow class" (e.g. "Recovery", "Settings", "Verification", "Login", etc.) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment selfservice/flow/settings/hook.go:441— // TODO(jonas): We can likely drop the identity id column entirely, since the session's identity is always loaded and we check the ID matches here. This would simplify the schema and remove a potential source of FK inconsistency. — 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 selfservice/flow/settings/hook.go:489— // TODO: pointer aliasing could cause issues if a downstream hook implementation modifies the identity in-place instead of treating it as immutable. We should either enforce immutability or document this behavior. — 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 selfservice/flow/settings/organizations.go:97— // TODO(jonas): This should actually use the `organization.via` field of the identity schema. — 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 selfservice/flow/registration/sort_test.go:24— // TODO add more test cases. — 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 request/auth.go:89— // TODO add deprecation warning — 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_hmac_test.go:36— // TODO implement me — 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 (5 lines × 2) pkg/registrationhelpers/helpers.go:124— pkg/registrationhelpers/helpers.go:124-128 | pkg/registrationhelpers/helpers.go:148-152 — 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 (5 lines × 2) selfservice/flow/login/error.go:127— selfservice/flow/login/error.go:127-131 | selfservice/flow/registration/error.go:129-133 — `selfservice/flow/login/error.go` and `selfservice/flow/registration/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/error.go:127` 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 (5 lines × 2) selfservice/flow/request.go:98— selfservice/flow/request.go:98-102 | selfservice/strategy/code/strategy_login.go:161-165 — 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 `selfservice/flow/request.go:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) selfservice/strategy/code/strategy_verification.go:393— selfservice/strategy/code/strategy_verification.go:393-397 | selfservice/strategy/link/strategy_verification.go:286-290 — `selfservice/strategy/code/strategy_verification.go` and `selfservice/strategy/link/strategy_verification.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) selfservice/strategy/link/strategy_recovery.go:60— selfservice/strategy/link/strategy_recovery.go:60-64 | selfservice/strategy/link/strategy_verification.go:38-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) selfservice/strategy/oidc/provider_amazon.go:117— selfservice/strategy/oidc/provider_amazon.go:117-121 | selfservice/strategy/oidc/provider_uaepass.go:140-147 — 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 `selfservice/strategy/oidc/provider_amazon.go:117` 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 (5 lines × 2) selfservice/strategy/oidc/strategy_login.go:590— selfservice/strategy/oidc/strategy_login.go:590-594 | selfservice/strategy/oidc/strategy_registration.go:276-280 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) selfservice/strategy/passkey/passkey_login.go:205— selfservice/strategy/passkey/passkey_login.go:205-209 | selfservice/strategy/webauthn/login.go:235-239 — 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 `selfservice/strategy/passkey/passkey_login.go:205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) selfservice/strategy/passkey/passkey_login.go:293— selfservice/strategy/passkey/passkey_login.go:293-297 | selfservice/strategy/totp/login.go:141-145 — 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 `selfservice/strategy/passkey/passkey_login.go:293` 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: `selfservice/strategy/totp/login.go:141` is reached only past guards at line 103 (testing `s.d`) and line 116 (testing `s.d`) that each leave the function early, and `selfservice/strategy/passkey/passkey_login.go:293` reads `s.d` with no such check. What separates these copies is not which lines they run but which PRECONDITION they enforce, so one of them is operating on state the other one refuses. Decide which is intended BEFORE unifying them — extract the shared part and whichever copy is missing the check keeps running unchecked, and if the guard is the correct behaviour then that hole is already live.
Duplicated block (5 lines × 2) selfservice/strategy/passkey/passkey_settings.go:381— selfservice/strategy/passkey/passkey_settings.go:381-385 | selfservice/strategy/webauthn/settings.go:296-300 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) session/handler.go:340— session/handler.go:340-344 | session/handler.go:581-585 — 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 (5 lines × 2) x/require.go:14— x/require.go:14-18 | x/tests.go:14-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) persistence/sql/persister_session.go:42— persistence/sql/persister_session.go:42-46 | persistence/sql/persister_session.go:349-355 — 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 (5 lines × 2) selfservice/flow/registration/error.go:102— selfservice/flow/registration/error.go:102-106 | selfservice/flow/verification/error.go:76-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/registration/error.go:102` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/flow/registration/error.go:108` calls `As`, `NewDuplicateCredentialsError` and `selfservice/flow/verification/error.go:82` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) pkg/registrationhelpers/helpers.go:428— pkg/registrationhelpers/helpers.go:428-432 | pkg/registrationhelpers/helpers.go:435-439 — 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 `pkg/registrationhelpers/helpers.go:428` 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 (5 lines × 2) selfservice/flow/recovery/handler.go:292— selfservice/flow/recovery/handler.go:292-296 | selfservice/flow/verification/handler.go:294-298 — 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 `selfservice/flow/recovery/handler.go:292` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) pkg/registrationhelpers/helpers.go:393— pkg/registrationhelpers/helpers.go:393-397 | pkg/registrationhelpers/helpers.go:402-406 — 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 `pkg/registrationhelpers/helpers.go:393` 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 (5 lines × 2) pkg/registrationhelpers/helpers.go:128— pkg/registrationhelpers/helpers.go:128-132 | pkg/registrationhelpers/helpers.go:140-144 — 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 `pkg/registrationhelpers/helpers.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.
Duplicated block (5 lines × 2) REDACTED:570— REDACTED:570-574 | REDACTED:592-596 — 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:570` 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 (5 lines × 2) pkg/registrationhelpers/helpers.go:256— pkg/registrationhelpers/helpers.go:256-260 | pkg/registrationhelpers/helpers.go:512-516 — 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 `pkg/registrationhelpers/helpers.go:256` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `pkg/registrationhelpers/helpers.go:255` calls `Run` and `pkg/registrationhelpers/helpers.go:510` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) selfservice/strategy/code/strategy_recovery.go:831— selfservice/strategy/code/strategy_recovery.go:831-835 | selfservice/strategy/link/strategy_recovery.go:501-505 — 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 `selfservice/strategy/code/strategy_recovery.go:831` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) selfservice/strategy/code/strategy_registration.go:109— selfservice/strategy/code/strategy_registration.go:109-113 | selfservice/strategy/code/strategy_registration.go:127-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) selfservice/strategy/link/strategy_verification.go:308— selfservice/strategy/link/strategy_verification.go:308-312 | selfservice/strategy/link/strategy_verification.go:332-336 — 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 (5 lines × 2) selfservice/strategy/oidc/strategy.go:515— selfservice/strategy/oidc/strategy.go:515-519 | selfservice/strategy/oidc/strategy.go:537-541 — 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 (5 lines × 2) selfservice/strategy/oidc/strategy.go:529— selfservice/strategy/oidc/strategy.go:529-533 | selfservice/strategy/oidc/strategy.go:545-549 — 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 (6 lines × 2) hash/hasher_argon2.go:54— hash/hasher_argon2.go:54-59 | hash/hasher_pbkdf2.go:37-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `hash/hasher_argon2.go:54` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `hash/hasher_argon2.go:50` calls `Config`, `HasherArgon2` and `hash/hasher_pbkdf2.go:34` 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/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) selfservice/flow/login/handler.go:765— selfservice/flow/login/handler.go:765-770 | selfservice/flow/registration/handler.go:572-577 — `selfservice/flow/login/handler.go` and `selfservice/flow/registration/handler.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/handler.go:765` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) selfservice/hook/web_hook.go:273— selfservice/hook/web_hook.go:273-278 | selfservice/hook/web_hook.go:290-295 — 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 `selfservice/hook/web_hook.go:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) selfservice/strategy/code/code_sender.go:133— selfservice/strategy/code/code_sender.go:133-138 | selfservice/strategy/code/code_sender.go:190-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/code/code_sender.go:133` 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 × 2) selfservice/strategy/oidc/provider_discord.go:73— selfservice/strategy/oidc/provider_discord.go:73-78 | selfservice/strategy/oidc/provider_spotify.go:67-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) selfservice/strategy/oidc/provider_github.go:66— selfservice/strategy/oidc/provider_github.go:66-71 | selfservice/strategy/oidc/provider_slack.go:67-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) selfservice/strategy/oidc/provider_github.go:98— selfservice/strategy/oidc/provider_github.go:98-103 | selfservice/strategy/oidc/provider_github_app.go:85-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/provider_github.go:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/strategy/oidc/provider_github.go:97` calls `Contains` and `selfservice/strategy/oidc/provider_github_app.go:81` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) selfservice/strategy/passkey/passkey_login.go:258— selfservice/strategy/passkey/passkey_login.go:258-263 | selfservice/strategy/webauthn/login.go:261-266 — 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 `selfservice/strategy/passkey/passkey_login.go:258` 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) oryx/httpx/transports.go:31— oryx/httpx/transports.go:31-36 | REDACTED:270-275 — 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) oryx/sqlxx/types.go:259— oryx/sqlxx/types.go:259-264 | selfservice/flow/state.go:118-123 — 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) selfservice/flow/recovery/flow.go:279— selfservice/flow/recovery/flow.go:279-284 | selfservice/strategy/link/token_verification.go:81-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) selfservice/strategy/oidc/provider_apple.go:162— selfservice/strategy/oidc/provider_apple.go:162-167 | selfservice/strategy/oidc/provider_google.go:77-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) selfservice/flow/login/handler.go:773— selfservice/flow/login/handler.go:773-778 | selfservice/flow/registration/handler.go:580-585 — `selfservice/flow/login/handler.go` and `selfservice/flow/registration/handler.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/handler.go:773` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) selfservice/strategy/passkey/passkey_registration.go:98— selfservice/strategy/passkey/passkey_registration.go:98-103 | selfservice/strategy/password/registration.go:197-202 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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) selfservice/hook/session_destroyer.go:40— selfservice/hook/session_destroyer.go:40-45 | selfservice/hook/session_destroyer.go:49-54 — 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 `selfservice/hook/session_destroyer.go:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) selfservice/strategy/oidc/provider_vk.go:65— selfservice/strategy/oidc/provider_vk.go:65-70 | selfservice/strategy/oidc/provider_yandex.go:63-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) persistence/sql/persister_login.go:24— persistence/sql/persister_login.go:24-29 | persistence/sql/persister_registration.go:21-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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. 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) selfservice/strategy/oidc/strategy_login.go:471— selfservice/strategy/oidc/strategy_login.go:471-476 | selfservice/strategy/password/login.go:53-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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_recovery.go:50— persistence/sql/persister_recovery.go:50-55 | persistence/sql/persister_verification.go:49-54 — before extracting anything, compare `persistence/sql/persister_recovery.go` and `persistence/sql/persister_verification.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_recovery.go:50` 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. 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) pkg/testhelpers/selfservice.go:41— pkg/testhelpers/selfservice.go:41-46 | pkg/testhelpers/selfservice.go:49-54 — 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 `pkg/testhelpers/selfservice.go:41` 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, `pkg/testhelpers/selfservice.go:47` calls `MustSet` and `pkg/testhelpers/selfservice.go:39` 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) persistence/sql/batch/test_persister.go:74— persistence/sql/batch/test_persister.go:74-79 | persistence/sql/batch/test_persister.go:89-94 — 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/batch/test_persister.go:74` 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×21
Swallowed exception (caught, then discarded) x/cookie.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) x/normalize.go:79— `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/webauthnx/aaguid/aaguid.go:47— `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) session/manager_http.go:215— `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) session/session.go:338— `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:242— `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:262— `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:282— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) selfservice/strategy/password/settings.go:133— `if err := json.Unmarshal(cred.Config, &hashedPassword); 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) selfservice/strategy/oidc/strategy_login.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) selfservice/strategy/oidc/strategy_login.go:205— `if err := json.Unmarshal(a, &aVal); 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) selfservice/strategy/oidc/strategy_login.go:208— `if err := json.Unmarshal(b, &bVal); 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) selfservice/strategy/oidc/strategy_settings.go:433— `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) selfservice/strategy/code/code_sender.go:523— `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) selfservice/strategy/code/strategy_recovery.go:156— `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) selfservice/flow/recovery/flow.go:256— `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) schema/schema.go:174— `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.
Duplicated block (9 lines × 2) cmd/hashers/argon2/calibrate.go:257— cmd/hashers/argon2/calibrate.go:257-265 | cmd/hashers/argon2/calibrate.go:271-279 — 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) 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/identity/persister_identity.go:1885— persistence/sql/identity/persister_identity.go:1885-1893 | persistence/sql/identity/persister_identity.go:1911-1919 — 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/identity/persister_identity.go:1885` 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_login_code.go:27— persistence/sql/persister_login_code.go:27-35 | persistence/sql/persister_registration_code.go:26-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 `persistence/sql/persister_login_code.go:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) REDACTED:191— REDACTED:191-199 | REDACTED:218-226 — 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) selfservice/flow/recovery/handler.go:135— selfservice/flow/recovery/handler.go:135-143 | selfservice/flow/recovery/handler.go:211-219 — 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 `selfservice/flow/recovery/handler.go:135` 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) selfservice/flow/registration/hook.go:157— selfservice/flow/registration/hook.go:157-165 | selfservice/flow/registration/hook.go:308-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/registration/hook.go:157` 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, `selfservice/flow/registration/hook.go:306` calls `SetAttributes`, `String`, `Sprintf` and `selfservice/flow/registration/hook.go:155` 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 (9 lines × 2) selfservice/flow/settings/error.go:152— selfservice/flow/settings/error.go:152-160 | selfservice/flow/verification/error.go:76-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/settings/error.go:152` 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) selfservice/strategy/code/strategy.go:293— selfservice/strategy/code/strategy.go:293-302 | selfservice/strategy/code/strategy.go:321-329 — 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) selfservice/strategy/oidc/provider_auth0.go:77— selfservice/strategy/oidc/provider_auth0.go:77-85 | selfservice/strategy/oidc/provider_salesforce.go:77-85 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 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) session/handler.go:443— session/handler.go:443-451 | session/handler.go:525-533 — 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 `session/handler.go:443` 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/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) selfservice/flow/recovery/handler.go:122— selfservice/flow/recovery/handler.go:122-130 | selfservice/flow/recovery/handler.go:198-206 — 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 (9 lines × 2) selfservice/flow/login/handler.go:755— selfservice/flow/login/handler.go:755-763 | selfservice/flow/login/test_handler.go:217-225 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/flow/login/handler.go:752` calls `IsTest` and `selfservice/flow/login/test_handler.go:216` 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 (9 lines × 2) selfservice/flow/recovery/handler.go:307— selfservice/flow/recovery/handler.go:307-315 | selfservice/flow/verification/handler.go:309-317 — 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 `selfservice/flow/recovery/handler.go:307` 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/sqlxx/types.go:238— oryx/sqlxx/types.go:238-246 | selfservice/flow/state.go:97-105 — 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 (9 lines × 2) selfservice/strategy/oidc/provider_generic_oidc.go:77— selfservice/strategy/oidc/provider_generic_oidc.go:77-85 | selfservice/strategy/oidc/provider_google.go:52-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) persistence/sql/identity/persister_identity.go:1923— persistence/sql/identity/persister_identity.go:1923-1931 | persistence/sql/identity/persister_identity.go:1950-1958 — 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/identity/persister_identity.go:1923` 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) 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.
Hotspot: persistence/sql/identity/persister_identity.go persistence/sql/identity/persister_identity.go:1126— persistence/sql/identity/persister_identity.go changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in IdentityPersister.ListIdentities at line 1126. 3 of those changes were fix/bug commits, and the other 11 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- persistence/sql/identity/persister_identity.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: oryx/popx/migrator.go oryx/popx/migrator.go:127— oryx/popx/migrator.go changed 4 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:36 +00:00' --until='2026-07-29 09:30:36 +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: selfservice/hook/verify_new_address.go selfservice/hook/verify_new_address.go:72— selfservice/hook/verify_new_address.go changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in VerifyNewAddress.execute at line 72. 2 of those changes were fix/bug commits, and the other 3 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/hook/verify_new_address.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: selfservice/flow/login/handler.go selfservice/flow/login/handler.go:148— selfservice/flow/login/handler.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in Handler.NewLoginFlow at line 148. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/flow/login/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.
Hotspot: selfservice/strategy/code/strategy.go selfservice/strategy/code/strategy.go:250— selfservice/strategy/code/strategy.go changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in Strategy.populateChooseMethodFlow at line 250. 2 of those changes were fix/bug commits, and the other 3 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/code/strategy.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 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in popx.TransactionWithOptions at line 46. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-30..2026-07-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-30 09:30:36 +00:00' --until='2026-07-29 09:30:36 +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: selfservice/strategy/oidc/strategy.go selfservice/strategy/oidc/strategy.go:476— selfservice/strategy/oidc/strategy.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Strategy.HandleCallback at line 476. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/oidc/strategy.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: selfservice/strategy/oidc/strategy_login.go selfservice/strategy/oidc/strategy_login.go:469— selfservice/strategy/oidc/strategy_login.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in Strategy.Login at line 469. 2 of those changes were fix/bug commits, 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/oidc/strategy_login.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: selfservice/strategy/code/strategy_recovery.go selfservice/strategy/code/strategy_recovery.go:162— selfservice/strategy/code/strategy_recovery.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Strategy.Recover at line 162. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/code/strategy_recovery.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: selfservice/flow/settings/hook.go selfservice/flow/settings/hook.go:187— selfservice/flow/settings/hook.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in HookExecutor.PostSettingsHook at line 187. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/flow/settings/hook.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: selfservice/flow/registration/hook.go selfservice/flow/registration/hook.go:117— selfservice/flow/registration/hook.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in HookExecutor.PostRegistrationHook at line 117. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/flow/registration/hook.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: selfservice/flow/registration/handler.go selfservice/flow/registration/handler.go:135— selfservice/flow/registration/handler.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Handler.NewRegistrationFlow at line 135. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/flow/registration/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.
Hotspot: selfservice/strategy/code/code_sender.go selfservice/strategy/code/code_sender.go:74— selfservice/strategy/code/code_sender.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Sender.SendCode at line 74. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/code/code_sender.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: selfservice/hook/verification.go selfservice/hook/verification.go:104— selfservice/hook/verification.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Verifier.do at line 104. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/hook/verification.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: selfservice/strategy/code/strategy_verification.go selfservice/strategy/code/strategy_verification.go:200— selfservice/strategy/code/strategy_verification.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Strategy.verificationHandleFormSubmission at line 200. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/code/strategy_verification.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: courier/email_templates.go courier/email_templates.go:37— courier/email_templates.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in courier.NewEmailTemplateFromMessage at line 37. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- courier/email_templates.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: driver/registry_default_hooks.go driver/registry_default_hooks.go:70— driver/registry_default_hooks.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in driver.getHooks at line 70. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- driver/registry_default_hooks.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: selfservice/hook/require_verified_address.go selfservice/hook/require_verified_address.go:59— selfservice/hook/require_verified_address.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in AddressVerifier.ExecuteLoginPostHook at line 59. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/hook/require_verified_address.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) courier/sms.go:29— courier/sms.go:29-38 | courier/smtp.go:134-143 — 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 `courier/sms.go:29` 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) REDACTED:500— REDACTED:500-509 | oryx/hasherx/hash_comparator.go:195-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:510` calls `validatePbkdf2Params` and `oryx/hasherx/hash_comparator.go:206` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) identity/handler.go:1071— identity/handler.go:1071-1080 | identity/handler.go:1272-1281 — 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 `identity/handler.go:1071` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) persistence/sql/persister_recovery.go:85— persistence/sql/persister_recovery.go:85-94 | persistence/sql/persister_verification.go:83-92 — before extracting anything, compare `persistence/sql/persister_recovery.go` and `persistence/sql/persister_verification.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_recovery.go:85` 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 (10 lines × 2) selfservice/flow/login/strategy.go:40— selfservice/flow/login/strategy.go:40-49 | selfservice/flow/registration/strategy.go:26-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) selfservice/flow/registration/handler.go:565— selfservice/flow/registration/handler.go:565-574 | selfservice/flow/verification/handler.go:302-311 — 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 `selfservice/flow/registration/handler.go:565` 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 (10 lines × 2) selfservice/hook/web_hook.go:169— selfservice/hook/web_hook.go:169-178 | selfservice/hook/web_hook.go:223-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 `selfservice/hook/web_hook.go:169` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) selfservice/hook/web_hook.go:194— selfservice/hook/web_hook.go:194-203 | selfservice/hook/web_hook.go:244-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/hook/web_hook.go:194` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) selfservice/strategy/code/code_sender.go:145— selfservice/strategy/code/code_sender.go:145-154 | selfservice/strategy/code/code_sender.go:202-211 — 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 `selfservice/strategy/code/code_sender.go: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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) selfservice/strategy/code/strategy_recovery.go:882— selfservice/strategy/code/strategy_recovery.go:882-891 | selfservice/strategy/link/strategy_recovery.go:542-551 — 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 `selfservice/strategy/code/strategy_recovery.go:882` 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) selfservice/strategy/lookup/login.go:92— selfservice/strategy/lookup/login.go:92-101 | selfservice/strategy/totp/login.go:96-105 — `selfservice/strategy/lookup/login.go` and `selfservice/strategy/totp/login.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 lines × 2) selfservice/strategy/code/strategy_recovery.go:630— selfservice/strategy/code/strategy_recovery.go:630-639 | selfservice/strategy/code/strategy_recovery.go:702-711 — 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 `selfservice/strategy/code/strategy_recovery.go:630` 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) identity/extension_recovery.go:90— identity/extension_recovery.go:90-99 | identity/extension_verification.go:122-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) selfservice/strategy/oidc/provider_discord.go:61— selfservice/strategy/oidc/provider_discord.go:61-70 | selfservice/strategy/oidc/provider_patreon.go:73-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) text/message_system.go:6— text/message_system.go:6-15 | text/message_validation.go:16-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) cipher/aes.go:60— cipher/aes.go:60-69 | cipher/chacha20.go:60-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cipher/aes.go:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) selfservice/strategy/link/sender.go:75— selfservice/strategy/link/sender.go:75-84 | selfservice/strategy/link/sender.go:133-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/link/sender.go:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `address` to `"Preparing recovery link.")` in one and `"Preparing verification link.")` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) persistence/sql/persister_session.go:654— persistence/sql/persister_session.go:654-663 | persistence/sql/persister_session.go:674-683 — 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_session.go:654` 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.
No assertions: responds with a HTML response on link click of an API flow if the code is expired test/e2e/cypress/integration/profiles/verification/verify/errors.spec.ts:96— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should redirect to return_to after completing verification test/e2e/cypress/integration/profiles/verification/verify/success.spec.ts:132— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is unable to verify the email address if the code is no longer valid test/e2e/cypress/integration/profiles/verification/settings/error.spec.ts:54— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is redirected to after_verification_return_to after verification test/e2e/cypress/integration/profiles/verification/registration/success.spec.ts:66— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is redirected to `return_to` after verification test/e2e/cypress/integration/profiles/verification/registration/success.spec.ts:88— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should be able to sign up, sign out, and then sign in test/e2e/cypress/integration/profiles/oidc/login/success.spec.ts:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should add passkey in settings after password registration test/e2e/cypress/integration/profiles/mobile/passkey/flows.spec.ts:106— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should allow changing other settings and then setting up totp test/e2e/cypress/integration/profiles/mfa/totp.spec.ts:340— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not update without re-auth test/e2e/cypress/integration/profiles/email/settings/errors.spec.ts:216— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not update data because resumable session was removed test/e2e/cypress/integration/profiles/email/settings/errors.spec.ts:231— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fails when CSRF is incorrect test/e2e/cypress/integration/profiles/email/settings/errors.spec.ts:300— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fails when a disallowed return_to url is requested test/e2e/cypress/integration/profiles/email/settings/errors.spec.ts:305— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is unable to log in with the old password test/e2e/cypress/integration/profiles/email/settings/success.spec.ts:81— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is unable to log in with the old email test/e2e/cypress/integration/profiles/email/settings/success.spec.ts:149— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fails when a disallowed return_to url is requested test/e2e/cypress/integration/profiles/email/registration/errors.spec.ts:52— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fails when CSRF cookies are missing test/e2e/cypress/integration/profiles/email/login/error.spec.ts:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fails when a disallowed return_to url is requested test/e2e/cypress/integration/profiles/email/login/error.spec.ts:44— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Duplicated block (8 lines × 2) identity/handler_import.go:257— identity/handler_import.go:257-264 | identity/handler_import.go:302-309 — 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 `identity/handler_import.go:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
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) persistence/sql/identity/persister_identity.go:1935— persistence/sql/identity/persister_identity.go:1935-1942 | persistence/sql/identity/persister_identity.go:1962-1969 — 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/identity/persister_identity.go:1935` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) pkg/testhelpers/selfservice_login.go:183— pkg/testhelpers/selfservice_login.go:183-190 | pkg/testhelpers/selfservice_registration.go:68-75 — 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 `pkg/testhelpers/selfservice_login.go:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) selfservice/strategy/code/strategy_recovery.go:681— selfservice/strategy/code/strategy_recovery.go:681-688 | selfservice/strategy/code/strategy_recovery.go:805-812 — 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) selfservice/strategy/link/strategy_recovery.go:484— selfservice/strategy/link/strategy_recovery.go:484-491 | selfservice/strategy/link/strategy_verification.go:185-192 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) selfservice/strategy/oidc/provider_apple.go:97— selfservice/strategy/oidc/provider_apple.go:97-104 | selfservice/strategy/oidc/provider_generic_oidc.go:88-95 — 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 (8 lines × 2) selfservice/strategy/oidc/provider_facebook.go:94— selfservice/strategy/oidc/provider_facebook.go:94-101 | selfservice/strategy/oidc/provider_yandex.go:78-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 `selfservice/strategy/oidc/provider_facebook.go:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) selfservice/strategy/oidc/strategy_login.go:503— selfservice/strategy/oidc/strategy_login.go:503-510 | selfservice/strategy/oidc/strategy_registration.go:183-190 — 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 `selfservice/strategy/oidc/strategy_login.go:503` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) selfservice/strategy/oidc/strategy_registration.go:276— selfservice/strategy/oidc/strategy_registration.go:276-283 | selfservice/strategy/oidc/strategy_settings.go:483-490 — 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 `selfservice/strategy/oidc/strategy_registration.go:276` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) 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) pkg/testhelpers/selfservice_recovery.go:97— pkg/testhelpers/selfservice_recovery.go:97-104 | pkg/testhelpers/selfservice_verification.go:189-196 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) driver/registry_default.go:591— driver/registry_default.go:591-598 | oryx/cookiex/legacy_securecookie.go:35-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) selfservice/flow/flow_identity_schema.go:19— selfservice/flow/flow_identity_schema.go:19-26 | selfservice/flow/state.go:108-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) selfservice/strategy/passkey/passkey_settings.go:302— selfservice/strategy/passkey/passkey_settings.go:302-309 | selfservice/strategy/webauthn/settings.go:216-223 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) cmd/daemon/serve.go:108— cmd/daemon/serve.go:108-115 | cmd/daemon/serve.go:193-200 — 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) session/handler.go:263— session/handler.go:263-270 | session/handler.go:891-898 — 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 `session/handler.go:263` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) REDACTED:745— REDACTED:745-755 | REDACTED:795-805 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) 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) persistence/sql/persister_session.go:93— persistence/sql/persister_session.go:93-103 | persistence/sql/persister_session.go:150-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) pkg/testhelpers/selfservice_verification.go:44— pkg/testhelpers/selfservice_verification.go:44-54 | pkg/testhelpers/selfservice_verification.go:70-80 — 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 `pkg/testhelpers/selfservice_verification.go:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `pkg/testhelpers/selfservice_verification.go:40` calls `GetProvider`, `Get` and `pkg/testhelpers/selfservice_verification.go:65` 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) selfservice/flow/login/flow.go:335— selfservice/flow/login/flow.go:335-345 | selfservice/flow/recovery/flow.go:322-332 — 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 `selfservice/flow/login/flow.go:335` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) selfservice/flow/login/handler.go:576— selfservice/flow/login/handler.go:576-586 | selfservice/flow/registration/handler.go:383-393 — `selfservice/flow/login/handler.go` and `selfservice/flow/registration/handler.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/handler.go:576` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) selfservice/strategy/oidc/provider_gitlab.go:57— selfservice/strategy/oidc/provider_gitlab.go:57-67 | selfservice/strategy/oidc/provider_netid.go:62-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/provider_gitlab.go:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/strategy/oidc/provider_gitlab.go:69` calls `OAuth2`, `oauth2` and `selfservice/strategy/oidc/provider_netid.go:74` 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) selfservice/strategy/passkey/passkey_settings.go:102— selfservice/strategy/passkey/passkey_settings.go:102-112 | selfservice/strategy/webauthn/settings.go:392-402 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:102` 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) selfservice/strategy/passkey/passkey_settings.go:197— selfservice/strategy/passkey/passkey_settings.go:197-207 | selfservice/strategy/webauthn/settings.go:134-144 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:197` 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) selfservice/strategy/password/settings.go:95— selfservice/strategy/password/settings.go:95-105 | selfservice/strategy/totp/settings.go:108-118 — `selfservice/strategy/password/settings.go` and `selfservice/strategy/totp/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 59 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/password/settings.go:95` 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) selfservice/strategy/passkey/passkey_login.go:223— selfservice/strategy/passkey/passkey_login.go:223-233 | selfservice/strategy/webauthn/login.go:271-281 — 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 `selfservice/strategy/passkey/passkey_login.go:223` 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) persistence/sql/identity/persister_identity.go:98— persistence/sql/identity/persister_identity.go:98-108 | persistence/sql/identity/persister_identity.go:112-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/identity/persister_identity.go:98` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (11 lines × 2) persistence/sql/persister_courier.go:173— persistence/sql/persister_courier.go:173-186 | persistence/sql/persister_login.go:80-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_courier.go:173` 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 (11 lines × 2) persistence/sql/persister_sessiontokenexchanger.go:52— persistence/sql/persister_sessiontokenexchanger.go:52-63 | persistence/sql/persister_sessiontokenexchanger.go:70-80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) REDACTED:41— REDACTED:41-51 | REDACTED:92-102 — 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:41` 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) 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/snapshotx/snapshot.go:106— oryx/snapshotx/snapshot.go:106-112 | pkg/testhelpers/snapshot.go:16-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) pkg/testhelpers/http.go:105— pkg/testhelpers/http.go:105-113 | pkg/testhelpers/http.go:149-155 — 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 `pkg/testhelpers/http.go:105` 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 (7 lines × 2) REDACTED:161— REDACTED:161-167 | REDACTED:179-185 — 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:161` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) selfservice/flow/registration/hook.go:135— selfservice/flow/registration/hook.go:135-141 | selfservice/flow/registration/hook.go:281-287 — 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 `selfservice/flow/registration/hook.go:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/flow/registration/hook.go:291` calls `SetAttributes`, `String`, `Sprintf` and `selfservice/flow/registration/hook.go:144` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) selfservice/strategy/oidc/provider_auth0.go:47— selfservice/strategy/oidc/provider_auth0.go:47-53 | selfservice/strategy/oidc/provider_salesforce.go:47-53 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) selfservice/strategy/oidc/provider_gitlab.go:99— selfservice/strategy/oidc/provider_gitlab.go:99-105 | selfservice/strategy/oidc/provider_netid.go:108-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. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/provider_gitlab.go:99` 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 (7 lines × 2) selfservice/strategy/oidc/strategy_registration.go:267— selfservice/strategy/oidc/strategy_registration.go:267-273 | selfservice/strategy/oidc/strategy_settings.go:473-479 — 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 `selfservice/strategy/oidc/strategy_registration.go:267` 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) selfservice/strategy/passkey/passkey_registration.go:127— selfservice/strategy/passkey/passkey_registration.go:127-133 | REDACTED:131-137 — 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 `selfservice/strategy/passkey/passkey_registration.go:127` 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) selfservice/strategy/oidc/strategy.go:451— selfservice/strategy/oidc/strategy.go:451-457 | selfservice/strategy/oidc/strategy.go:729-735 — 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) selfservice/flow/flow.go:32— selfservice/flow/flow.go:32-38 | selfservice/flow/settings/strategy_helper.go:111-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) courier/template/testhelpers/testhelpers.go:108— courier/template/testhelpers/testhelpers.go:108-115 | courier/template/testhelpers/testhelpers.go:143-149 — 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 `courier/template/testhelpers/testhelpers.go:108` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) persistence/sql/persister_sessiontokenexchanger.go:85— persistence/sql/persister_sessiontokenexchanger.go:85-91 | persistence/sql/persister_sessiontokenexchanger.go:118-124 — 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 (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) selfservice/strategy/code/strategy_verification.go:417— selfservice/strategy/code/strategy_verification.go:417-423 | selfservice/strategy/code/strategy_verification.go:445-451 — 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 (7 lines × 2) REDACTED:197— REDACTED:197-203 | REDACTED:217-223 — 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×14
Edited copy of a member (14 corresponding lines) selfservice/strategy/oidc/provider_auth0.go:131— selfservice/strategy/oidc/provider_auth0.go:131-144 | selfservice/strategy/oidc/provider_salesforce.go:131-144 — 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) selfservice/strategy/code/strategy_recovery.go:830— selfservice/strategy/code/strategy_recovery.go:830-843 | selfservice/strategy/link/strategy_recovery.go:500-513 — 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) selfservice/flow/verification/handler.go:164— selfservice/flow/verification/handler.go:164-177 | selfservice/flow/verification/handler.go:214-228 — 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) persistence/sql/persister_continuity.go:31— persistence/sql/persister_continuity.go:31-46 | persistence/sql/persister_continuity.go:59-72 — 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) selfservice/strategy/oidc/provider_generic_oidc.go:62— selfservice/strategy/oidc/provider_generic_oidc.go:62-75 | selfservice/strategy/oidc/provider_google.go:35-50 — 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) selfservice/flow/login/flow.go:334— selfservice/flow/login/flow.go:334-349 | selfservice/flow/recovery/flow.go:321-334 — 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) request/builder.go:217— request/builder.go:217-230 | request/builder.go:258-271 — 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) driver/config/config.go:598— driver/config/config.go:598-611 | driver/config/config.go:617-634 — 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) selfservice/flow/recovery/flow.go:188— selfservice/flow/recovery/flow.go:188-201 | selfservice/flow/verification/flow.go:185-198 — 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) x/events/events.go:532— x/events/events.go:532-547 | x/events/events.go:549-562 — 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.
Edited copy of a member (14 corresponding lines) courier/message.go:85— courier/message.go:85-98 | oryx/sqlxx/types.go:30-43 — 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) identity/credentials_code.go:77— identity/credentials_code.go:77-91 | courier/message.go:155-168 — 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) examples/go/selfservice/settings/main.go:35— examples/go/selfservice/settings/main.go:35-48 | examples/go/selfservice/settings/main.go:50-65 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) hydra/hydra.go:113— hydra/hydra.go:113-126 | hydra/hydra.go:153-166 — 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 (14 lines × 2) identity/handler_import.go:275— identity/handler_import.go:275-288 | identity/handler_import.go:319-332 — 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 `identity/handler_import.go:275` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) oryx/sqlxx/batch/create.go:75— oryx/sqlxx/batch/create.go:75-88 | persistence/sql/batch/create.go:107-120 — before extracting anything, compare `oryx/sqlxx/batch/create.go` and `persistence/sql/batch/create.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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/batch/create.go:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) persistence/sql/persister_recovery.go:109— persistence/sql/persister_recovery.go:109-122 | persistence/sql/persister_verification.go:107-120 — before extracting anything, compare `persistence/sql/persister_recovery.go` and `persistence/sql/persister_verification.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_recovery.go:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) REDACTED:55— REDACTED:55-68 | REDACTED:74-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also 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, `REDACTED:89` calls `ReplaceAll` and `REDACTED:69` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) selfservice/flow/login/error.go:195— selfservice/flow/login/error.go:195-208 | selfservice/flow/registration/error.go:205-218 — `selfservice/flow/login/error.go` and `selfservice/flow/registration/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/error.go:195` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) selfservice/flow/recovery/error.go:174— selfservice/flow/recovery/error.go:174-187 | selfservice/flow/verification/error.go:162-175 — `selfservice/flow/recovery/error.go` and `selfservice/flow/verification/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/recovery/error.go:174` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) selfservice/flow/recovery/flow.go:237— selfservice/flow/recovery/flow.go:237-250 | selfservice/flow/verification/flow.go:263-276 — `selfservice/flow/recovery/flow.go` and `selfservice/flow/verification/flow.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 34 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) selfservice/hook/verification.go:196— selfservice/hook/verification.go:196-209 | selfservice/hook/verify_new_address.go:196-209 — 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 `selfservice/hook/verification.go:196` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) selfservice/strategy/code/code_sender.go:429— selfservice/strategy/code/code_sender.go:429-442 | selfservice/strategy/link/sender.go:224-237 — 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 `selfservice/strategy/code/code_sender.go:429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `err` to `= s.deps.IdentityPool().FindVerifiableAddressByValue(ctx` in one and `= s.r.IdentityPool().FindVerifiableAddressByValue(ctx` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) selfservice/strategy/passkey/passkey_login.go:308— selfservice/strategy/passkey/passkey_login.go:308-321 | selfservice/strategy/webauthn/login.go:58-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) selfservice/strategy/passkey/passkey_settings.go:317— selfservice/strategy/passkey/passkey_settings.go:317-330 | selfservice/strategy/webauthn/settings.go:231-244 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:317` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) REDACTED:331— REDACTED:331-344 | REDACTED:351-364 — 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 (14 lines × 2) selfservice/strategy/passkey/passkey_settings.go:333— selfservice/strategy/passkey/passkey_settings.go:333-346 | selfservice/strategy/webauthn/settings.go:247-260 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×11
Dependency pinned to a stale untagged commit: github.com/arbovm/levenshtein — Direct dependency `github.com/arbovm/levenshtein` is required at `v0.0.0-20160628152529-48b4e1c0c4d0` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2016-06-28, 10.4 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/arbovm/levenshtein` and has not moved this requirement in 10.4 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/arbovm/levenshtein` 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/davecgh/go-spew — Direct dependency `github.com/davecgh/go-spew` is required at `v1.1.2-0.20180830191138-d8f796af33cc` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2018-08-30, 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/davecgh/go-spew` 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/davecgh/go-spew` 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/golang/gddo — Direct dependency `github.com/golang/gddo` is required at `v0.0.0-20190904175337-72a348e765d2` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2019-09-04, 7.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/golang/gddo` and has not moved this requirement in 7.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/golang/gddo` 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/ory/graceful — Direct dependency `github.com/ory/graceful` is required at `v0.1.4-0.20230301144740-e222150c51d0` 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/ory/graceful` 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/ory/graceful` 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/phayes/freeport — Direct dependency `github.com/phayes/freeport` is required at `v0.0.0-20220201140144-74d24b5ae9f5` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-02-01, 4.8 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/phayes/freeport` and has not moved this requirement in 4.8 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/phayes/freeport` 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/ian-kent/go-log — Direct dependency `github.com/ian-kent/go-log` is required at `v0.0.0-20160113211217-5731446c36ab` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2016-01-13, 10.8 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/ian-kent/go-log` and has not moved this requirement in 10.8 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/ian-kent/go-log` 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.
FixmeComment selfservice/strategy/profile/registration.go:206— // FIXME In this scenario we are on the first step of the registration flow and the user clicked on "continue". — 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.
FixmeComment selfservice/strategy/profile/registration.go:207— // FIXME The appropriate solution would be to also have `screen=credential-selection` available, but that — 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.
FixmeComment selfservice/strategy/profile/registration.go:208— // FIXME is not the case right now. So instead, we fall back. — 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.
FixmeComment selfservice/strategy/profile/registration.go:214— // FIXME remove this at some point. — 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.
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.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×10
Edited copy of a member (16 corresponding lines) REDACTED:155— REDACTED:155-170 | REDACTED:172-188 — 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) selfservice/flow/recovery/error.go:172— selfservice/flow/recovery/error.go:172-187 | selfservice/flow/verification/error.go:160-175 — 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) selfservice/strategy/lookup/settings.go:365— selfservice/strategy/lookup/settings.go:365-382 | selfservice/strategy/oidc/strategy_settings.go:608-623 — 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) selfservice/flow/login/error.go:193— selfservice/flow/login/error.go:193-208 | selfservice/flow/registration/error.go:203-218 — 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) selfservice/flow/recovery/hook.go:26— selfservice/flow/recovery/hook.go:26-41 | selfservice/flow/verification/hook.go:26-41 — 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) persistence/sql/persister_sessiontokenexchanger.go:48— persistence/sql/persister_sessiontokenexchanger.go:48-64 | persistence/sql/persister_sessiontokenexchanger.go:66-81 — 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) persistence/sql/persister_recovery.go:57— persistence/sql/persister_recovery.go:57-73 | persistence/sql/persister_verification.go:56-71 — 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) selfservice/strategy/password/strategy.go:85— selfservice/strategy/password/strategy.go:85-101 | selfservice/strategy/totp/strategy.go:88-103 — 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) REDACTED:303— REDACTED:303-318 | REDACTED:353-375 — 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) identity/credentials_webauthn.go:63— identity/credentials_webauthn.go:63-78 | identity/credentials_webauthn.go:86-102 — 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.
Duplicated block (7 lines × 3) persistence/sql/persister_login.go:34— persistence/sql/persister_login.go:34-40 | persistence/sql/persister_registration.go:31-37 | persistence/sql/persister_settings.go:54-60 — 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 `persistence/sql/persister_login.go:34` 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. 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 × 3) selfservice/flow/recovery/flow.go:161— selfservice/flow/recovery/flow.go:161-167 | selfservice/flow/registration/flow.go:184-190 | selfservice/flow/verification/flow.go:158-164 — `selfservice/flow/recovery/flow.go` and `selfservice/flow/verification/flow.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 34 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 3) selfservice/hook/require_verified_address.go:131— selfservice/hook/require_verified_address.go:131-137 | selfservice/hook/verification.go:182-188 | selfservice/hook/verify_new_address.go:167-173 — 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 `selfservice/hook/require_verified_address.go:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (7 lines × 3) selfservice/hook/web_hook.go:143— selfservice/hook/web_hook.go:143-149 | selfservice/hook/web_hook.go:194-200 | selfservice/hook/web_hook.go:244-250 — 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 `selfservice/hook/web_hook.go:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) selfservice/strategy/passkey/passkey_settings.go:181— selfservice/strategy/passkey/passkey_settings.go:181-187 | selfservice/strategy/totp/settings.go:93-99 | selfservice/strategy/webauthn/settings.go:118-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:181` 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 (7 lines × 3) identity/identity.go:185— identity/identity.go:185-191 | oryx/sqlxx/types.go:418-424 | oryx/sqlxx/types.go:453-459 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) oryx/sqlxx/types.go:340— oryx/sqlxx/types.go:340-346 | session/session.go:409-415 | session/session.go:430-436 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) selfservice/strategy/oidc/provider_auth0.go:90— selfservice/strategy/oidc/provider_auth0.go:90-97 | selfservice/strategy/oidc/provider_dingtalk.go:90-96 | selfservice/strategy/oidc/provider_salesforce.go:90-97 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 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 `selfservice/strategy/oidc/provider_auth0.go:90` 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 × 3) selfservice/strategy/lookup/settings.go:123— selfservice/strategy/lookup/settings.go:123-129 | selfservice/strategy/passkey/passkey_settings.go:195-201 | selfservice/strategy/webauthn/settings.go:132-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/settings.go:123` 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 × 3) selfservice/strategy/lookup/login.go:95— selfservice/strategy/lookup/login.go:95-101 | selfservice/strategy/password/login.go:56-62 | selfservice/strategy/totp/login.go:99-105 — `selfservice/strategy/lookup/login.go` and `selfservice/strategy/totp/login.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/login.go:95` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) REDACTED:443— REDACTED:443-455 | oryx/hasherx/hash_comparator.go:143-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) persistence/sql/persister_session.go:333— persistence/sql/persister_session.go:333-345 | persistence/sql/persister_session.go:399-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 `persistence/sql/persister_session.go:333` 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 (13 lines × 2) selfservice/strategy/lookup/settings.go:331— selfservice/strategy/lookup/settings.go:331-343 | selfservice/strategy/totp/settings.go:245-257 — `selfservice/strategy/lookup/settings.go` and `selfservice/strategy/totp/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 47 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) selfservice/strategy/oidc/provider_auth0.go:58— selfservice/strategy/oidc/provider_auth0.go:58-70 | selfservice/strategy/oidc/provider_salesforce.go:58-70 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 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 `selfservice/strategy/oidc/provider_auth0.go:58` 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 (13 lines × 2) selfservice/strategy/oidc/provider_auth0.go:113— selfservice/strategy/oidc/provider_auth0.go:113-125 | selfservice/strategy/oidc/provider_salesforce.go:113-125 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 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 `selfservice/strategy/oidc/provider_auth0.go:113` 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 (13 lines × 2) selfservice/strategy/oidc/strategy_login.go:130— selfservice/strategy/oidc/strategy_login.go:130-142 | selfservice/strategy/oidc/strategy_registration.go:365-377 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) selfservice/strategy/passkey/passkey_login.go:68— selfservice/strategy/passkey/passkey_login.go:68-80 | selfservice/strategy/passkey/passkey_login.go:345-357 — 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 (13 lines × 2) selfservice/strategy/link/strategy_recovery.go:419— selfservice/strategy/link/strategy_recovery.go:419-431 | selfservice/strategy/link/strategy_recovery.go:449-461 — 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 `selfservice/strategy/link/strategy_recovery.go:419` 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 (13 lines × 2) selfservice/strategy/link/strategy_verification.go:315— selfservice/strategy/link/strategy_verification.go:315-327 | selfservice/strategy/link/strategy_verification.go:346-358 — 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 `selfservice/strategy/link/strategy_verification.go:315` 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.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×9
Discarded error (assigned to `_`, then its result used) x/normalize.go:88— `v, _ := applyPRECIS(emailProfile, value, true)` writes the call's error to `_` and then uses `v` as if the call succeeded. When `applyPRECIS` fails, `v` 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 `v` (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) x/normalize.go:99— `value, _ = applyPRECIS(phoneProfile, value, true)` writes the call's error to `_` and then uses `value` as if the call succeeded. When `applyPRECIS` fails, `value` 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 `value` (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) ui/container/container.go:195— `pointer, _ := jsonschemax.JSONPointerToDotNotation(e.InstancePtr)` writes the call's error to `_` and then uses `pointer` as if the call succeeded. When `jsonschemax.JSONPointerToDotNotation` fails, `pointer` 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 `pointer` (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) ui/container/container.go:215— `pointer, _ := jsonschemax.JSONPointerToDotNotation(e.InstancePtr)` writes the call's error to `_` and then uses `pointer` as if the call succeeded. When `jsonschemax.JSONPointerToDotNotation` fails, `pointer` 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 `pointer` (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) selfservice/strategy/oidc/provider_amazon.go:121— `rawResponse, _ := io.ReadAll(body)` writes the call's error to `_` and then uses `rawResponse` as if the call succeeded. When `io.ReadAll` fails, `rawResponse` 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 `rawResponse` (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) selfservice/strategy/oidc/provider_amazon.go:128— `rawResponse, _ := io.ReadAll(body)` writes the call's error to `_` and then uses `rawResponse` as if the call succeeded. When `io.ReadAll` fails, `rawResponse` 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 `rawResponse` (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) selfservice/strategy/oidc/provider_uaepass.go:147— `rawResponse, _ := io.ReadAll(body)` writes the call's error to `_` and then uses `rawResponse` as if the call succeeded. When `io.ReadAll` fails, `rawResponse` 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 `rawResponse` (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) selfservice/flow/recovery/flow.go:259— `shouldSkip, _ := strconv.ParseBool(u.Query().Get("skip_settings"))` writes the call's error to `_` and then uses `shouldSkip` as if the call succeeded. When `strconv.ParseBool` fails, `shouldSkip` 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 `shouldSkip` (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) selfservice/flow/login/flow.go:216— `refresh, _ := strconv.ParseBool(r.URL.Query().Get("refresh"))` writes the call's error to `_` and then uses `refresh` as if the call succeeded. When `strconv.ParseBool` fails, `refresh` 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 `refresh` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
TooManyMethods: Config driver/config/config.go:308— TooManyMethods — 160 methods. The bar is 30 methods; this is 130 over it, 5.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RegistryDefault driver/registry_default.go:78— TooManyMethods — 135 methods, declared across 9 files: driver/registry_default.go (83), driver/registry_default_verification.go (11), driver/registry_default_hooks.go (9), driver/registry_default_recovery.go (9), +5 more file(s). The bar is 30 methods; this is 105 over it, 4.50× 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:50— TooManyMethods — 106 methods, declared across 18 files: sql/persister_session.go (23), sql/persister.go (11), sql/persister_courier.go (8), sql/persister_recovery.go (7), +14 more file(s). The bar is 30 methods; this is 76 over it, 3.53× 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: Strategy selfservice/strategy/code/strategy.go:125— TooManyMethods — 68 methods, declared across 6 files: code/strategy_login.go (18), code/strategy_recovery.go (17), code/strategy_verification.go (12), code/strategy.go (9), +2 more file(s). The bar is 30 methods; this is 38 over it, 2.27× 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: Strategy selfservice/strategy/oidc/strategy.go:150— TooManyMethods — 64 methods, declared across 6 files: oidc/strategy.go (23), oidc/strategy_settings.go (15), oidc/strategy_registration.go (12), oidc/strategy_login.go (9), +2 more file(s). The bar is 30 methods; this is 34 over it, 2.13× 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: IdentityPersister persistence/sql/identity/persister_identity.go:62— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Strategy selfservice/strategy/webauthn/strategy.go:79— TooManyMethods — 37 methods, declared across 5 files: webauthn/login.go (14), webauthn/settings.go (9), REDACTED (7), webauthn/strategy.go (6), +1 more file(s). The bar is 30 methods; this is 7 over it, 1.23× 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: Strategy selfservice/strategy/passkey/passkey_strategy.go:79— TooManyMethods — 36 methods, declared across 5 files: passkey/passkey_login.go (9), passkey/passkey_registration.go (9), passkey/passkey_settings.go (9), passkey/passkey_strategy.go (6), +1 more file(s). The bar is 30 methods; this is 6 over it, 1.20× 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.
MethodTooLong: HookExecutor.PostLoginHook selfservice/flow/login/hook.go:128— MethodTooLong — PostLoginHook runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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: HookExecutor.PostRegistrationHook selfservice/flow/registration/hook.go:117— MethodTooLong — PostRegistrationHook 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.
MethodTooLong: HookExecutor.PostSettingsHook selfservice/flow/settings/hook.go:187— MethodTooLong — PostSettingsHook runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: IdentityPersister.ListIdentities persistence/sql/identity/persister_identity.go:1126— MethodTooLong — ListIdentities runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: Handler.NewLoginFlow selfservice/flow/login/handler.go:148— MethodTooLong — NewLoginFlow runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Sender.SendCode selfservice/strategy/code/code_sender.go:74— MethodTooLong — SendCode runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Strategy.HandleCallback selfservice/strategy/oidc/strategy.go:476— MethodTooLong — HandleCallback runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×8
Edited copy of a member (12 corresponding lines) persistence/sql/persister_sessiontokenexchanger.go:83— persistence/sql/persister_sessiontokenexchanger.go:83-94 | persistence/sql/persister_sessiontokenexchanger.go:116-127 — 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) selfservice/strategy/lookup/strategy.go:89— selfservice/strategy/lookup/strategy.go:89-103 | selfservice/strategy/passkey/passkey_strategy.go:106-117 — 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) hash/hash_limits.go:79— hash/hash_limits.go:79-90 | hash/hash_limits.go:92-103 — 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) selfservice/strategy/passkey/passkey_registration.go:253— selfservice/strategy/passkey/passkey_registration.go:253-264 | selfservice/strategy/webauthn/validate.go:13-24 — 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) schema/errors.go:21— schema/errors.go:21-32 | schema/errors.go:119-130 — 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) courier/template/email/authenticator_key_added.go:15— courier/template/email/authenticator_key_added.go:15-26 | courier/template/sms/authenticator_key_added.go:15-27 — 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) courier/template/email/verifiable_address_changed.go:15— courier/template/email/verifiable_address_changed.go:15-26 | courier/template/sms/verifiable_address_changed.go:15-27 — 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.
FileTooLong: identity/persister_identity.go persistence/sql/identity/persister_identity.go— FileTooLong — 1234 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: IdentityPersister (37 blocks, 62-2105). The bar is 500 significant lines; this is 734 over it, 2.47× 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/config.go driver/config/config.go— FileTooLong — 1111 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: Config (160 blocks, 457-1732). The bar is 500 significant lines; this is 611 over it, 2.22× 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: oidc/strategy.go selfservice/strategy/oidc/strategy.go— FileTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: Strategy (23 blocks, 150-997). The bar is 500 significant lines; this is 130 over it, 1.26× 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: identity/handler.go identity/handler.go— FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: Handler (13 blocks, 77-1527). The bar is 500 significant lines; this is 95 over it, 1.19× 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: driver/registry_default.go driver/registry_default.go— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: RegistryDefault (70 blocks, 78-957). The bar is 500 significant lines; this is 38 over it, 1.08× 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: session/handler.go session/handler.go— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: Handler (18 blocks, 97-1371). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: code/strategy_recovery.go selfservice/strategy/code/strategy_recovery.go— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: Strategy (17 blocks, 44-900). The bar is 500 significant lines; this is 6 over it, 1.01× 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×7
Edited copy of a member (10 corresponding lines) REDACTED:784— REDACTED:784-793 | REDACTED:801-810 — 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/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) driver/registry_default_recovery.go:33— driver/registry_default_recovery.go:33-42 | driver/registry_default_verification.go:67-76 — 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) selfservice/flow/login/handler.go:328— selfservice/flow/login/handler.go:328-337 | selfservice/flow/registration/handler.go:203-212 — 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) selfservice/strategy/code/strategy_login.go:79— selfservice/strategy/code/strategy_login.go:79-89 | selfservice/strategy/webauthn/strategy.go:128-137 — 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) text/message_login.go:134— text/message_login.go:134-143 | text/message_settings.go:160-169 — 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 (12 lines × 2) cmd/daemon/serve.go:135— cmd/daemon/serve.go:135-146 | cmd/daemon/serve.go:221-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 `cmd/daemon/serve.go:135` 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) selfservice/flow/registration/hook.go:144— selfservice/flow/registration/hook.go:144-155 | selfservice/flow/registration/hook.go:293-304 — 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 `selfservice/flow/registration/hook.go:144` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) selfservice/strategy/passkey/passkey_login.go:94— selfservice/strategy/passkey/passkey_login.go:94-105 | selfservice/strategy/passkey/passkey_login.go:360-371 — 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 `selfservice/strategy/passkey/passkey_login.go:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) selfservice/strategy/passkey/passkey_settings.go:160— selfservice/strategy/passkey/passkey_settings.go:160-171 | selfservice/strategy/webauthn/settings.go:335-346 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) selfservice/strategy/passkey/passkey_settings.go:280— selfservice/strategy/passkey/passkey_settings.go:280-291 | selfservice/strategy/webauthn/settings.go:191-202 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:280` 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) selfservice/strategy/oidc/provider_auth0.go:133— selfservice/strategy/oidc/provider_auth0.go:133-144 | selfservice/strategy/oidc/provider_salesforce.go:133-144 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) cmd/daemon/serve.go:64— cmd/daemon/serve.go:64-75 | cmd/daemon/serve.go:164-176 — 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 `cmd/daemon/serve.go:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
Outbound HTTP without resilience pkg/testhelpers/handler_mock.go:113— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience pkg/testhelpers/handler_mock.go:119— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience pkg/testhelpers/handler_mock.go:125— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience pkg/testhelpers/http.go:20— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience pkg/testhelpers/http.go:32— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience pkg/testhelpers/selfservice.go:231— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:131— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Skipped test: (unnamed test) test/e2e/playwright/tests/desktop/regression/phone-normalization.spec.ts:24— Skipped — switched off by test.skip
Skipped test: should not update the traits until the email has been verified and the old email has accepted the change test/e2e/cypress/integration/profiles/verification/settings/error.spec.ts:90— Skipped — switched off by xit
Skipped test: should should be able to allow or deny (and revert?) the address change test/e2e/cypress/integration/profiles/verification/settings/success.spec.ts:64— Skipped — switched off by xit
Skipped test: sends the warning email on double sign up test/e2e/cypress/integration/profiles/verification/registration/success.spec.ts:56— Skipped — switched off by xit
Skipped test: should not show an immediate error when a recovery address already exists test/e2e/cypress/integration/profiles/recovery/settings/success.spec.ts:61— Skipped — switched off by xit
Skipped test: should use webauthn credential as passkey test/e2e/cypress/integration/profiles/passwordless/flows.spec.ts:144— Skipped — switched off by xit
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (5 members, 50+ identical tokens) selfservice/flow/login/flow.go:193— selfservice/flow/login/flow.go:193-241 | selfservice/flow/recovery/flow.go:135-186 | selfservice/flow/registration/flow.go:150-201 | selfservice/flow/settings/flow.go:146-183 | selfservice/flow/verification/flow.go:139-183 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) selfservice/strategy/code/strategy_recovery.go:53— selfservice/strategy/code/strategy_recovery.go:53-85 | selfservice/strategy/code/strategy_recovery.go:474-550 | selfservice/strategy/code/strategy_recovery.go:552-639 | selfservice/strategy/code/strategy_recovery.go:641-711 | selfservice/strategy/code/strategy_recovery.go:768-828 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) selfservice/strategy/lookup/login.go:90— selfservice/strategy/lookup/login.go:90-171 | selfservice/strategy/passkey/passkey_login.go:158-188 | selfservice/strategy/passkey/passkey_login.go:190-219 | selfservice/strategy/webauthn/login.go:152-192 | selfservice/strategy/webauthn/login.go:194-249 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) selfservice/strategy/lookup/settings.go:101— selfservice/strategy/lookup/settings.go:101-135 | selfservice/strategy/passkey/passkey_settings.go:173-207 | selfservice/strategy/password/settings.go:78-105 | selfservice/strategy/totp/settings.go:85-118 | selfservice/strategy/webauthn/settings.go:106-144 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) selfservice/strategy/lookup/strategy.go:33— selfservice/strategy/lookup/strategy.go:33-81 | selfservice/strategy/passkey/passkey_strategy.go:31-79 | selfservice/strategy/password/strategy.go:33-81 | selfservice/strategy/totp/strategy.go:32-80 | selfservice/strategy/webauthn/strategy.go:31-79 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) selfservice/strategy/passkey/passkey_settings.go:430— selfservice/strategy/passkey/passkey_settings.go:430-444 | selfservice/strategy/password/settings.go:228-242 | selfservice/strategy/profile/strategy.go:253-278 | selfservice/strategy/totp/settings.go:302-316 | selfservice/strategy/webauthn/settings.go:414-428 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×6
Edited copy of a member (9 corresponding lines) selfservice/strategy/link/strategy_recovery.go:59— selfservice/strategy/link/strategy_recovery.go:59-68 | selfservice/strategy/link/strategy_verification.go:37-45 — 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) selfservice/flow/login/flow.go:320— selfservice/flow/login/flow.go:320-328 | selfservice/flow/registration/flow.go:285-293 — 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) pkg/testhelpers/selfservice_recovery.go:96— pkg/testhelpers/selfservice_recovery.go:96-104 | pkg/testhelpers/selfservice_verification.go:188-196 — 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) driver/registry_default_recovery.go:47— driver/registry_default_recovery.go:47-55 | driver/registry_default_verification.go:57-65 — 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) x/webauthnx/nodes.go:23— x/webauthnx/nodes.go:23-31 | x/webauthnx/nodes.go:49-57 — 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) 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.
Duplicated block (16 lines × 2) driver/config/config.go:1135— driver/config/config.go:1135-1150 | driver/config/config.go:1159-1174 — 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 `driver/config/config.go:1135` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) oryx/httpx/url.go:14— oryx/httpx/url.go:14-29 | x/http.go:68-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) selfservice/flow/login/hook.go:111— selfservice/flow/login/hook.go:111-126 | selfservice/flow/settings/hook.go:170-185 — 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 `selfservice/flow/login/hook.go:111` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) selfservice/hook/require_verified_address.go:131— selfservice/hook/require_verified_address.go:131-146 | selfservice/hook/verification.go:182-197 — 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 `selfservice/hook/require_verified_address.go:131` 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 (16 lines × 2) selfservice/strategy/code/strategy_login.go:533— selfservice/strategy/code/strategy_login.go:533-548 | selfservice/strategy/code/strategy_registration.go:241-256 — 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 (16 lines × 2) REDACTED:237— REDACTED:237-252 | REDACTED:277-292 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:237` 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.
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: 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: github.com/lestrrat-go/jwx/v2 — `github.com/lestrrat-go/jwx/v2` is required at v2.1.1 in REDACTED, and its author has DEPRECATED the module: "github.com/lestrrat-go/jwx/v2 is no longer maintained. Use github.com/lestrrat-go/jwx/v4 or github.com/lestrrat-go/jwx/v3 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: registrationhelpers.AssertCommonErrorCases pkg/registrationhelpers/helpers.go:279— FunctionTooLong — AssertCommonErrorCases runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: 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: main.init cmd/clidoc/main.go:44— FunctionTooLong — init runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: argon2.newCalibrateCmd cmd/hashers/argon2/calibrate.go:75— FunctionTooLong — newCalibrateCmd runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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 (37 corresponding lines) · ×5
Edited copy of a member (37 corresponding lines) selfservice/strategy/oidc/provider_facebook.go:67— selfservice/strategy/oidc/provider_facebook.go:67-139 | selfservice/strategy/oidc/provider_gitlab.go:73-109 — 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) pkg/testhelpers/selfservice_login.go:163— pkg/testhelpers/selfservice_login.go:163-206 | pkg/testhelpers/selfservice_registration.go:50-86 — 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) hash/hasher_argon2.go:49— hash/hasher_argon2.go:49-87 | hash/hasher_pbkdf2.go:34-70 — 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) request/builder.go:139— request/builder.go:139-175 | request/builder.go:177-215 — 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 (31 corresponding lines) · ×5
Edited copy of a member (31 corresponding lines) selfservice/strategy/code/strategy_verification.go:144— selfservice/strategy/code/strategy_verification.go:144-174 | selfservice/strategy/link/strategy_verification.go:127-162 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) selfservice/flow/recovery/hook.go:86— selfservice/flow/recovery/hook.go:86-120 | selfservice/flow/verification/hook.go:100-130 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) selfservice/strategy/lookup/login.go:29— selfservice/strategy/lookup/login.go:29-59 | selfservice/strategy/totp/login.go:28-58 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) REDACTED:564— REDACTED:564-594 | REDACTED:727-759 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) selfservice/flow/recovery/handler.go:30— selfservice/flow/recovery/handler.go:30-60 | selfservice/flow/verification/handler.go:32-67 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) session/handler.go:339— session/handler.go:339-351 | session/handler.go:580-593 — 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) x/redir/port_redirect.go:15— x/redir/port_redirect.go:15-27 | x/redir/port_redirect.go:29-41 — 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_session.go:312— persistence/sql/persister_session.go:312-324 | persistence/sql/persister_session.go:458-470 — 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) hash/hasher.go:11— hash/hasher.go:11-23 | oryx/hasherx/hasher.go:8-20 — 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) examples/go/identity/create/main.go:19— examples/go/identity/create/main.go:19-32 | examples/go/identity/update/main.go:19-31 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (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 (21 lines × 2) persistence/sql/identity/persister_identity.go:212— persistence/sql/identity/persister_identity.go:212-232 | persistence/sql/identity/persister_identity.go:289-309 — 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 (21 lines × 2) selfservice/flow/login/hook.go:291— selfservice/flow/login/hook.go:291-311 | selfservice/flow/login/hook.go:346-366 — 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 `selfservice/flow/login/hook.go:291` 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 (21 lines × 2) selfservice/strategy/oidc/provider_github.go:73— selfservice/strategy/oidc/provider_github.go:73-93 | selfservice/strategy/oidc/provider_github_app.go:61-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/strategy/oidc/provider_github.go:97` calls `Contains` and `selfservice/strategy/oidc/provider_github_app.go:85` 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 (21 lines × 2) selfservice/strategy/oidc/provider_auth0.go:90— selfservice/strategy/oidc/provider_auth0.go:90-110 | selfservice/strategy/oidc/provider_salesforce.go:90-110 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (17 lines × 2) REDACTED:463— REDACTED:463-479 | REDACTED:511-527 — 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:463` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) oryx/sqlxx/batch/create.go:47— oryx/sqlxx/batch/create.go:47-63 | persistence/sql/batch/create.go:72-88 — before extracting anything, compare `oryx/sqlxx/batch/create.go` and `persistence/sql/batch/create.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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 (17 lines × 2) selfservice/hook/verification.go:168— selfservice/hook/verification.go:168-184 | selfservice/hook/verify_new_address.go:153-169 — 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 (17 lines × 2) selfservice/strategy/link/sender.go:87— selfservice/strategy/link/sender.go:87-103 | selfservice/strategy/link/sender.go:145-161 — 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 `selfservice/strategy/link/sender.go:87` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `address` to `"Preparing recovery link.")` in one and `"Preparing verification link.")` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) selfservice/strategy/oidc/strategy_login.go:555— selfservice/strategy/oidc/strategy_login.go:555-571 | selfservice/strategy/oidc/strategy_registration.go:238-254 — 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 `selfservice/strategy/oidc/strategy_login.go:555` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) pkg/registrationhelpers/helpers.go:325— pkg/registrationhelpers/helpers.go:325-329 | pkg/registrationhelpers/helpers.go:374-378 | pkg/registrationhelpers/helpers.go:403-407 — 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 `pkg/registrationhelpers/helpers.go:325` 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) pkg/testhelpers/selfservice_recovery.go:131— pkg/testhelpers/selfservice_recovery.go:131-135 | REDACTED:272-276 | pkg/testhelpers/selfservice_verification.go:224-228 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/testhelpers/selfservice_recovery.go:131` 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 (5 lines × 3) selfservice/flow/login/hook.go:191— selfservice/flow/login/hook.go:191-195 | selfservice/flow/registration/hook.go:135-139 | selfservice/flow/registration/hook.go:281-285 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/hook.go:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) pkg/registrationhelpers/helpers.go:308— pkg/registrationhelpers/helpers.go:308-312 | pkg/registrationhelpers/helpers.go:357-361 | pkg/registrationhelpers/helpers.go:385-389 — 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 `pkg/registrationhelpers/helpers.go:308` 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) selfservice/strategy/lookup/login.go:167— selfservice/strategy/lookup/login.go:167-171 | selfservice/strategy/passkey/passkey_login.go:293-297 | selfservice/strategy/totp/login.go:141-145 — `selfservice/strategy/lookup/login.go` and `selfservice/strategy/totp/login.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/login.go:167` 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.
Low cohesion: RegistryDefault (LCOM4 25) driver/registry_default.go:78— RegistryDefault's methods fall into 25 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 25 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: Flow (LCOM4 4) selfservice/flow/recovery/flow.go:41— Flow's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Flow (LCOM4 4) selfservice/flow/verification/flow.go:43— Flow's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ProviderApple (LCOM4 4) selfservice/strategy/oidc/provider_apple.go:23— ProviderApple's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: 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.
ClassTooLong: IdentityPersister persistence/sql/identity/persister_identity.go:62— ClassTooLong — 858 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods, 37 blocks, lines 62-2105. The bar is 400 significant lines; this is 458 over it, 2.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Config driver/config/config.go:308— ClassTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded), 160 methods, 160 blocks, lines 457-1732. The bar is 400 significant lines; this is 295 over it, 1.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RegistryDefault driver/registry_default.go:78— ClassTooLong — 498 significant lines (blank, comment-only and punctuation-only lines excluded), 135 methods, 70 blocks, lines 78-957. The bar is 400 significant lines; this is 98 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Strategy selfservice/strategy/oidc/strategy.go:150— ClassTooLong — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods, 23 blocks, lines 150-997. The bar is 400 significant lines; this is 58 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) selfservice/strategy/idfirst/strategy_login.go:173— selfservice/strategy/idfirst/strategy_login.go:173-192 | selfservice/strategy/passkey/passkey_login.go:44-127 | selfservice/strategy/password/login.go:183-200 | selfservice/strategy/webauthn/login.go:351-384 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) selfservice/strategy/oidc/provider_auth0.go:46— selfservice/strategy/oidc/provider_auth0.go:46-70 | selfservice/strategy/oidc/provider_gitlab.go:45-67 | selfservice/strategy/oidc/provider_netid.go:56-72 | selfservice/strategy/oidc/provider_salesforce.go:46-70 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) selfservice/strategy/passkey/passkey_settings.go:416— selfservice/strategy/passkey/passkey_settings.go:416-428 | selfservice/strategy/password/settings.go:107-119 | selfservice/strategy/totp/settings.go:120-132 | selfservice/strategy/webauthn/settings.go:146-158 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) x/events/events.go:333— x/events/events.go:333-349 | x/events/events.go:351-367 | x/events/events.go:369-386 | x/events/events.go:418-436 — 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 (26 corresponding lines) · ×4
Edited copy of a member (26 corresponding lines) identity/handler.go:384— identity/handler.go:384-409 | identity/handler.go:436-466 — 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) persistence/sql/identity/persister_identity.go:1921— persistence/sql/identity/persister_identity.go:1921-1946 | persistence/sql/identity/persister_identity.go:1948-1973 — 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) pkg/testhelpers/selfservice_recovery.go:53— pkg/testhelpers/selfservice_recovery.go:53-78 | pkg/testhelpers/selfservice_verification.go:140-170 — 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 (18 corresponding lines) · ×4
Edited copy of a member (18 corresponding lines) REDACTED:54— REDACTED:54-71 | REDACTED:73-92 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) session/handler.go:1324— session/handler.go:1324-1348 | session/handler.go:1354-1371 — 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) selfservice/flow/recovery/strategy.go:40— selfservice/flow/recovery/strategy.go:40-57 | selfservice/flow/verification/strategy.go:44-62 — 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) selfservice/strategy/passkey/passkey_registration.go:296— selfservice/strategy/passkey/passkey_registration.go:296-313 | REDACTED:254-272 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) selfservice/strategy/code/strategy_registration.go:104— selfservice/strategy/code/strategy_registration.go:104-119 | selfservice/strategy/code/strategy_registration.go:121-135 — 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.
Edited copy of a member (15 corresponding lines) courier/template/email/verification_code_valid.go:15— courier/template/email/verification_code_valid.go:15-30 | courier/template/email/verification_valid.go:15-29 — 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/sqlxx/batch/create.go:30— oryx/sqlxx/batch/create.go:30-44 | persistence/sql/batch/create.go:30-51 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×4
Edited copies of one member (3 members, 16+ corresponding lines) pkg/testhelpers/selfservice_login.go:278— pkg/testhelpers/selfservice_login.go:278-295 | pkg/testhelpers/selfservice_registration.go:135-150 | REDACTED:221-237 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) driver/registry_default.go:372— driver/registry_default.go:372-387 | driver/registry_default.go:400-416 | driver/registry_default_settings.go:64-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) ui/node/attributes.go:400— ui/node/attributes.go:400-415 | ui/node/attributes.go:417-432 | ui/node/attributes.go:447-466 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) courier/template/email/login_code_valid.go:16— courier/template/email/login_code_valid.go:16-31 | courier/template/sms/login_code_valid.go:15-31 | courier/template/sms/registration_code_valid.go:15-31 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×4
Edited copy of a member (21 corresponding lines) REDACTED:568— REDACTED:568-588 | REDACTED:590-612 — 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) courier/template/load_template.go:148— courier/template/load_template.go:148-168 | courier/template/load_template.go:170-190 — 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) selfservice/flow/login/error.go:58— selfservice/flow/login/error.go:58-78 | selfservice/flow/registration/error.go:48-68 — 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) examples/go/selfservice/recovery/main.go:19— examples/go/selfservice/recovery/main.go:19-39 | examples/go/selfservice/verification/main.go:19-39 — 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.
Duplicated block (15 lines × 2) cmd/clidoc/main.go:302— cmd/clidoc/main.go:302-316 | cmd/clidoc/main.go:321-335 — 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 `cmd/clidoc/main.go:302` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) persistence/sql/identity/persister_identity.go:494— persistence/sql/identity/persister_identity.go:494-508 | persistence/sql/identity/persister_identity.go:734-748 — 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/identity/persister_identity.go:494` 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) selfservice/strategy/code/strategy_verification.go:350— selfservice/strategy/code/strategy_verification.go:350-364 | selfservice/strategy/link/strategy_verification.go:242-256 — `selfservice/strategy/code/strategy_verification.go` and `selfservice/strategy/link/strategy_verification.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/code/strategy_verification.go:350` 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 (15 lines × 2) selfservice/strategy/passkey/passkey_settings.go:388— selfservice/strategy/passkey/passkey_settings.go:388-402 | selfservice/strategy/webauthn/settings.go:303-317 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/strategy/webauthn/settings.go:318` calls `Config`, `WebAuthnForPasswordless` and `selfservice/strategy/passkey/passkey_settings.go:405` 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 (9 lines × 3) selfservice/hook/web_hook.go:131— selfservice/hook/web_hook.go:131-139 | selfservice/hook/web_hook.go:157-165 | selfservice/hook/web_hook.go:207-215 — 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 `selfservice/hook/web_hook.go:131` 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 (9 lines × 3) selfservice/strategy/passkey/passkey_settings.go:106— selfservice/strategy/passkey/passkey_settings.go:106-114 | selfservice/strategy/webauthn/login.go:90-98 | selfservice/strategy/webauthn/settings.go:396-404 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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) driver/registry_default.go:389— driver/registry_default.go:389-398 | driver/registry_default.go:456-464 | driver/registry_default_settings.go:83-91 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) pkg/testhelpers/selfservice_recovery.go:80— pkg/testhelpers/selfservice_recovery.go:80-88 | REDACTED:74-82 | pkg/testhelpers/selfservice_verification.go:172-180 — 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.
Swallowed exception (empty catch) selfservice/flowhelpers/login.go:24— 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) selfservice/flowhelpers/login.go:26— 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: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.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×3
Edited copy of a member (28 corresponding lines) persistence/sql/identity/persister_identity.go:481— persistence/sql/identity/persister_identity.go:481-508 | persistence/sql/identity/persister_identity.go:719-748 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) driver/registry_default.go:181— driver/registry_default.go:181-208 | driver/registry_default.go:210-239 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) selfservice/strategy/oidc/strategy_registration.go:135— selfservice/strategy/oidc/strategy_registration.go:135-162 | selfservice/strategy/oidc/strategy_settings.go:62-89 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) REDACTED:234— REDACTED:234-252 | REDACTED:274-292 — 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) pkg/testhelpers/selfservice_recovery.go:117— pkg/testhelpers/selfservice_recovery.go:117-135 | pkg/testhelpers/selfservice_verification.go:209-228 — 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 (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) pkg/testhelpers/errorx.go:63— pkg/testhelpers/errorx.go:63-73 | pkg/testhelpers/errorx.go:80-90 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) oryx/snapshotx/snapshot.go:105— oryx/snapshotx/snapshot.go:105-115 | pkg/testhelpers/snapshot.go:15-29 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) selfservice/flow/login/handler.go:80— selfservice/flow/login/handler.go:80-95 | selfservice/flow/verification/handler.go:71-81 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
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) pkg/registrationhelpers/helpers.go:50— pkg/registrationhelpers/helpers.go:50-57 | pkg/settingshelpers/helpers.go:18-25 — 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) pkg/testhelpers/http.go:115— pkg/testhelpers/http.go:115-128 | pkg/testhelpers/http.go:136-143 — 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 (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) persistence/sql/persister_recovery.go:124— persistence/sql/persister_recovery.go:124-130 | persistence/sql/persister_verification.go:122-129 — 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) persistence/sql/persister_recovery.go:28— persistence/sql/persister_recovery.go:28-34 | persistence/sql/persister_verification.go:25-33 — 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/sqlxx/types.go:331— oryx/sqlxx/types.go:331-337 | session/session.go:397-406 — 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 copies of one member (3 members, 12+ corresponding lines) · ×3
Edited copies of one member (3 members, 12+ corresponding lines) selfservice/strategy/oidc/provider_discord.go:44— selfservice/strategy/oidc/provider_discord.go:44-55 | selfservice/strategy/oidc/provider_patreon.go:56-67 | selfservice/strategy/oidc/provider_slack.go:43-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) selfservice/strategy/oidc/provider_uaepass.go:83— selfservice/strategy/oidc/provider_uaepass.go:83-95 | selfservice/strategy/oidc/provider_vk.go:43-54 | selfservice/strategy/oidc/provider_yandex.go:41-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) REDACTED:190— REDACTED:190-202 | REDACTED:204-215 | REDACTED:217-229 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (10 lines × 3) hash/hasher_argon2.go:78— hash/hasher_argon2.go:78-87 | oryx/hasherx/hasher_argon2.go:104-113 | oryx/hasherx/hasher_pbkdf2.go:72-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `hash/hasher_argon2.go:78` 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 × 3) selfservice/flow/login/hook.go:318— selfservice/flow/login/hook.go:318-327 | selfservice/flow/login/hook.go:372-381 | selfservice/flow/registration/hook.go:353-362 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. 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 × 3) REDACTED:235— REDACTED:235-244 | REDACTED:255-264 | REDACTED:275-284 — 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 × 4) selfservice/strategy/passkey/passkey_settings.go:182— selfservice/strategy/passkey/passkey_settings.go:182-187 | selfservice/strategy/password/settings.go:91-96 | selfservice/strategy/totp/settings.go:94-99 | selfservice/strategy/webauthn/settings.go:119-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:182` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/strategy/password/settings.go:87` calls `handleSettingsError`, `MethodEnabledAndAllowedFromRequest`, `GetFlowName` and `selfservice/strategy/totp/settings.go:93` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) selfservice/flow/login/flow.go:264— selfservice/flow/login/flow.go:264-269 | selfservice/flow/registration/flow.go:219-224 | selfservice/flow/verification/flow.go:278-283 | selfservice/strategy/link/token_recovery.go:105-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (6 lines × 4) selfservice/strategy/code/code_login.go:68— selfservice/strategy/code/code_login.go:68-73 | selfservice/strategy/code/code_recovery.go:99-104 | selfservice/strategy/code/code_registration.go:66-71 | selfservice/strategy/code/code_verification.go:64-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (6 lines × 3) selfservice/flow/recovery/error.go:179— selfservice/flow/recovery/error.go:179-184 | selfservice/flow/settings/error.go:279-284 | selfservice/flow/verification/error.go:167-172 — `selfservice/flow/recovery/error.go` and `selfservice/flow/verification/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/recovery/error.go:179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) selfservice/flow/recovery/handler.go:315— selfservice/flow/recovery/handler.go:315-320 | selfservice/flow/settings/handler.go:503-508 | selfservice/flow/verification/handler.go:317-322 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/recovery/handler.go:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 3) selfservice/hook/web_hook.go:257— selfservice/hook/web_hook.go:257-262 | selfservice/hook/web_hook.go:273-278 | selfservice/hook/web_hook.go:290-295 — 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 `selfservice/hook/web_hook.go:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also 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 an error that is nil on this path) · ×3
Lost error (reports an error that is nil on this path) selfservice/strategy/oidc/strategy_registration.go:329— `if _, _, err := s.d.PrivilegedIdentityPool().FindByCredentialsIdentifier(ctx, s.ID(), identity.OIDCUniqueID(provider.Config().ID, claims.Subject)); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here.
Lost error (reports an error that is nil on this path) selfservice/flow/registration/handler.go:417— `if sess, err := h.d.SessionManager().FetchFromRequest(ctx, r, session.ExpandNothing, identity.ExpandNothing); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here.
Lost error (reports an error that is nil on this path) 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.
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) selfservice/strategy/code/code_sender.go:494— `t, ok := t.(courier.EmailTemplate)` failed on this branch, so `t` is the zero value of `courier.EmailTemplate` here, and that is what is reported: the value that did not fit is lost. Report `t` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) selfservice/strategy/code/code_sender.go:507— `t, ok := t.(courier.SMSTemplate)` failed on this branch, so `t` is the zero value of `courier.SMSTemplate` here, and that is what is reported: the value that did not fit is lost. Report `t` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) selfservice/flow/login/hook.go:435— `linkableStrategy, ok := strategy.(LinkableStrategy)` failed on this branch, so `linkableStrategy` is the zero value of `LinkableStrategy` here, and that is what is reported: the value that did not fit is lost. Report `strategy` itself (and `%T` of it) instead.
Stateful package: testhelpers REDACTED:154— Package `testhelpers` serves requests (request-handler function literals run on a goroutine per request, and every one sees the same package variables and captured values) but writes that shared state outside any lock (called; e.g. `called` in `NewSettingsLoginAcceptAPIServer` at line 154). 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 package: hooktest selfservice/hook/hooktest/web_hook_test_server.go:34— Package `hooktest` serves requests (request-handler function literals run on a goroutine per request, and every one sees the same package variables and captured values) but writes that shared state outside any lock (s.LastBody; e.g. `s.LastBody` in `NewServer` at line 34). 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.
Strategy.Login (cyclomatic 24) selfservice/strategy/code/strategy_login.go:176— Strategy.Login 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.
Strategy.Login (cyclomatic 24) selfservice/strategy/oidc/strategy_login.go:469— Strategy.Login has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
batch.buildInsertQueryValues (cognitive 29) persistence/sql/batch/create.go:144— batch.buildInsertQueryValues has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 3 (5 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
Strategy.Login (cognitive 28) selfservice/strategy/code/strategy_login.go:176— Strategy.Login has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 4, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.Login (cognitive 28) selfservice/strategy/oidc/strategy_login.go:469— Strategy.Login has cognitive complexity 28 (threshold 15). Drivers by points: if/else 24 (27 pts), 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, 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.
ErrorHandler.WriteFlowError (cognitive 20) selfservice/flow/login/error.go:103— ErrorHandler.WriteFlowError has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 3 (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.
ErrorHandler.WriteFlowError (cognitive 20) selfservice/flow/verification/error.go:68— ErrorHandler.WriteFlowError has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: RegistryDefault driver/registry_default.go:78— TooManyFields — 63 stored fields beside 135 methods. The bar is 30 stored fields; this is 33 over it, 2.10× 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: AndroidAuthorizationList selfservice/strategy/deviceauthn/attestation.go:44— TooManyFields — 34 stored fields. The bar is 30 stored fields; this is 4 over it, 1.13× 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.
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) selfservice/strategy/idfirst/strategy_login.go:45— selfservice/strategy/idfirst/strategy_login.go:45-163 | selfservice/strategy/password/login.go:51-127 | selfservice/strategy/password/registration.go:89-162 | selfservice/strategy/profile/registration.go:261-328 | selfservice/strategy/totp/login.go:94-145 | REDACTED:96-196 — 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) selfservice/strategy/lookup/settings.go:149— selfservice/strategy/lookup/settings.go:149-184 | selfservice/strategy/passkey/passkey_settings.go:252-277 | selfservice/strategy/password/settings.go:152-215 | selfservice/strategy/profile/strategy.go:162-194 | selfservice/strategy/totp/settings.go:134-169 | selfservice/strategy/webauthn/settings.go:164-188 — 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 (47 corresponding lines) · ×2
Edited copy of a member (47 corresponding lines) selfservice/strategy/lookup/settings.go:282— selfservice/strategy/lookup/settings.go:282-328 | selfservice/strategy/totp/settings.go:171-228 — 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.
Edited copy of a member (47 corresponding lines) selfservice/strategy/code/strategy_login.go:277— selfservice/strategy/code/strategy_login.go:277-331 | selfservice/strategy/code/strategy_login.go:333-379 — 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 copy of a member (57 corresponding lines) · ×2
Edited copy of a member (57 corresponding lines) selfservice/strategy/code/strategy_login.go:516— selfservice/strategy/code/strategy_login.go:516-572 | selfservice/strategy/code/strategy_registration.go:212-279 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (57 corresponding lines) oryx/sqlxx/batch/create.go:113— oryx/sqlxx/batch/create.go:113-169 | persistence/sql/batch/create.go:144-203 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×2
Edited copy of a member (41 corresponding lines) selfservice/strategy/oidc/provider_github.go:65— selfservice/strategy/oidc/provider_github.go:65-114 | selfservice/strategy/oidc/provider_github_app.go:60-100 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (41 corresponding lines) selfservice/strategy/code/code_login.go:21— selfservice/strategy/code/code_login.go:21-62 | selfservice/strategy/code/code_registration.go:20-60 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) selfservice/flow/recovery/handler.go:121— selfservice/flow/recovery/handler.go:121-149 | selfservice/flow/recovery/handler.go:197-226 — 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 (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 copies of one member (3 members, 22+ corresponding lines) · ×2
Edited copies of one member (3 members, 22+ corresponding lines) pkg/testhelpers/selfservice_login.go:335— pkg/testhelpers/selfservice_login.go:335-362 | pkg/testhelpers/selfservice_registration.go:181-202 | REDACTED:250-276 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 22+ corresponding lines) selfservice/flow/error.go:193— selfservice/flow/error.go:193-214 | selfservice/flow/login/hook.go:105-126 | selfservice/flow/settings/hook.go:156-185 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
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.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) driver/registry_default_registration.go:24— driver/registry_default_registration.go:24-44 | driver/registry_default_settings.go:22-41 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) selfservice/flow/recovery/hook.go:59— selfservice/flow/recovery/hook.go:59-78 | selfservice/flow/verification/hook.go:59-78 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×2
Edited copies of one member (3 members, 18+ corresponding lines) selfservice/flow/login/error.go:84— selfservice/flow/login/error.go:84-101 | selfservice/flow/registration/error.go:74-91 | selfservice/flow/settings/error.go:121-139 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 18+ corresponding lines) REDACTED:224— REDACTED:224-241 | REDACTED:243-263 | REDACTED:265-285 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 11+ corresponding lines) · ×2
Edited copies of one member (5 members, 11+ corresponding lines) pkg/testhelpers/selfservice_login.go:32— pkg/testhelpers/selfservice_login.go:32-42 | pkg/testhelpers/selfservice_recovery.go:27-37 | pkg/testhelpers/selfservice_registration.go:33-43 | REDACTED:32-42 | pkg/testhelpers/selfservice_verification.go:85-95 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 11+ corresponding lines) text/message_login.go:145— text/message_login.go:145-155 | text/message_recovery.go:13-23 | text/message_registration.go:57-67 | text/message_settings.go:14-24 | text/message_verification.go:13-23 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) selfservice/strategy/oidc/strategy_settings.go:91— selfservice/strategy/oidc/strategy_settings.go:91-114 | selfservice/strategy/oidc/strategy_settings.go:116-145 — 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 (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) pkg/testhelpers/http.go:96— pkg/testhelpers/http.go:96-113 | pkg/testhelpers/selfservice.go:212-228 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
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 copies of one member (5 members, 7+ corresponding lines) · ×2
Edited copies of one member (5 members, 7+ corresponding lines) selfservice/flow/login/handler.go:97— selfservice/flow/login/handler.go:97-106 | selfservice/flow/recovery/handler.go:86-92 | selfservice/flow/registration/handler.go:101-107 | selfservice/flow/settings/handler.go:154-162 | selfservice/flow/verification/handler.go:83-90 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 7+ corresponding lines) persistence/sql/persister_continuity.go:23— persistence/sql/persister_continuity.go:23-29 | persistence/sql/persister_courier.go:28-35 | persistence/sql/persister_login.go:23-30 | persistence/sql/persister_registration.go:20-27 | persistence/sql/persister_settings.go:24-31 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×2
Edited copies of one member (3 members, 8+ corresponding lines) selfservice/hook/session_destroyer.go:38— selfservice/hook/session_destroyer.go:38-45 | selfservice/hook/session_destroyer.go:47-54 | selfservice/hook/session_destroyer.go:56-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) driver/registry_default.go:466— driver/registry_default.go:466-473 | driver/registry_default_recovery.go:57-64 | driver/registry_default_verification.go:78-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 3+ corresponding lines) · ×2
Edited copies of one member (8 members, 3+ corresponding lines) courier/template/email/authenticator_key_added.go:41— courier/template/email/authenticator_key_added.go:41-43 | courier/template/email/recovery_invalid.go:41-43 | courier/template/email/recovery_valid.go:44-46 | courier/template/email/verifiable_address_changed.go:41-43 | courier/template/email/verification_code_invalid.go:49-59 | courier/template/email/verification_code_valid.go:54-63 | courier/template/email/verification_invalid.go:41-43 | courier/template/email/verification_valid.go:45-47 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
Edited copies of one member (8 members, 3+ corresponding lines) courier/template/email/authenticator_key_added.go:45— courier/template/email/authenticator_key_added.go:45-47 | courier/template/email/recovery_invalid.go:45-47 | courier/template/email/recovery_valid.go:48-50 | courier/template/email/verifiable_address_changed.go:45-47 | courier/template/email/verification_code_invalid.go:61-71 | courier/template/email/verification_code_valid.go:65-74 | courier/template/email/verification_invalid.go:45-47 | courier/template/email/verification_valid.go:49-51 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
Duplicated block (28 lines × 2) selfservice/strategy/lookup/strategy.go:54— selfservice/strategy/lookup/strategy.go:54-81 | selfservice/strategy/password/strategy.go:54-81 — 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 `selfservice/strategy/lookup/strategy.go:54` 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 (28 lines × 2) selfservice/strategy/passkey/passkey_registration.go:224— selfservice/strategy/passkey/passkey_registration.go:224-251 | selfservice/strategy/passkey/passkey_registration.go:267-294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) identity/handler.go:386— identity/handler.go:386-409 | identity/handler.go:443-466 — 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 `identity/handler.go:386` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) selfservice/strategy/lookup/login.go:31— selfservice/strategy/lookup/login.go:31-54 | selfservice/strategy/totp/login.go:30-53 — `selfservice/strategy/lookup/login.go` and `selfservice/strategy/totp/login.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (22 lines × 2) selfservice/strategy/code/strategy.go:57— selfservice/strategy/code/strategy.go:57-78 | selfservice/strategy/link/strategy.go:30-51 — 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 `selfservice/strategy/code/strategy.go:57` 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 (22 lines × 2) selfservice/strategy/profile/registration.go:238— selfservice/strategy/profile/registration.go:238-259 | selfservice/strategy/profile/registration.go:307-328 — 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 `selfservice/strategy/profile/registration.go:238` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) selfservice/flow/login/error.go:173— selfservice/flow/login/error.go:173-191 | selfservice/flow/registration/error.go:183-201 — `selfservice/flow/login/error.go` and `selfservice/flow/registration/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/error.go:173` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) persistence/sql/persister_session.go:497— persistence/sql/persister_session.go:497-515 | persistence/sql/persister_session.go:520-538 — 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_session.go:497` 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 (18 lines × 2) selfservice/strategy/passkey/passkey_settings.go:55— selfservice/strategy/passkey/passkey_settings.go:55-72 | selfservice/strategy/webauthn/settings.go:356-373 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:55` 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 (18 lines × 2) selfservice/strategy/passkey/passkey_settings.go:357— selfservice/strategy/passkey/passkey_settings.go:357-374 | selfservice/strategy/webauthn/settings.go:268-285 — `selfservice/strategy/passkey/passkey_settings.go` and `selfservice/strategy/webauthn/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 21 separate duplicated blocks between them, totalling at least 227 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:357` 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–12 lines × 2) selfservice/flow/login/handler.go:634— selfservice/flow/login/handler.go:634-644 | selfservice/flow/registration/handler.go:456-467 — `selfservice/flow/login/handler.go` and `selfservice/flow/registration/handler.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/handler.go:634` 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 (11–12 lines × 2) selfservice/strategy/oidc/strategy_registration.go:142— selfservice/strategy/oidc/strategy_registration.go:142-152 | selfservice/strategy/oidc/strategy_settings.go:69-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/strategy_registration.go:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) selfservice/strategy/lookup/settings.go:152— selfservice/strategy/lookup/settings.go:152-161 | selfservice/strategy/passkey/passkey_settings.go:255-264 | selfservice/strategy/totp/settings.go:136-145 | selfservice/strategy/webauthn/settings.go:167-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/settings.go:152` 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 (10 lines × 4) x/events/events.go:337— x/events/events.go:337-346 | x/events/events.go:355-364 | x/events/events.go:373-382 | x/events/events.go:424-433 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `x/events/events.go:337` 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, `x/events/events.go:422` calls `attLoginRequestedAAL`, `attLoginRequestedPrivilegedSession` and `x/events/events.go:336` 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 (8 lines × 4) selfservice/flow/login/error.go:194— selfservice/flow/login/error.go:194-201 | selfservice/flow/recovery/error.go:173-180 | selfservice/flow/registration/error.go:204-211 | selfservice/flow/verification/error.go:161-168 — `selfservice/flow/login/error.go` and `selfservice/flow/registration/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 × 4) selfservice/strategy/idfirst/strategy_login.go:177— selfservice/strategy/idfirst/strategy_login.go:177-184 | selfservice/strategy/passkey/passkey_login.go:50-57 | selfservice/strategy/password/login.go:185-192 | selfservice/strategy/webauthn/login.go:357-364 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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, `selfservice/strategy/idfirst/strategy_login.go:173` calls `PopulateLoginMethodIdentifierFirstIdentification`, `SetCSRF`, `GenerateCSRFToken` and `selfservice/strategy/webauthn/login.go:354` 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 (4–6 lines × 5) selfservice/strategy/oidc/provider_facebook.go:86— selfservice/strategy/oidc/provider_facebook.go:86-91 | selfservice/strategy/oidc/provider_microsoft.go:95-100 | selfservice/strategy/oidc/provider_netid.go:86-89 | selfservice/strategy/oidc/provider_vk.go:72-77 | selfservice/strategy/oidc/provider_yandex.go:70-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/provider_facebook.go:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/strategy/oidc/provider_facebook.go:92` calls `WithStack`, `ErrUpstreamError`, `WithWrap` and `selfservice/strategy/oidc/provider_netid.go:89` 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 (4–6 lines × 5) selfservice/strategy/lookup/login.go:108— selfservice/strategy/lookup/login.go:108-111 | selfservice/strategy/passkey/passkey_login.go:176-181 | selfservice/strategy/passkey/passkey_login.go:193-196 | selfservice/strategy/webauthn/login.go:176-181 | selfservice/strategy/webauthn/login.go:200-203 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/login.go:108` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 4) selfservice/flow/login/error.go:149— selfservice/flow/login/error.go:149-153 | selfservice/flow/recovery/error.go:154-158 | selfservice/flow/registration/error.go:157-161 | selfservice/flow/verification/error.go:142-146 — `selfservice/flow/login/error.go` and `selfservice/flow/registration/error.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/flow/login/error.go:149` 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 × 4) selfservice/flow/registration/hook.go:147— selfservice/flow/registration/hook.go:147-152 | selfservice/flow/registration/hook.go:161-165 | selfservice/flow/registration/hook.go:296-301 | selfservice/flow/registration/hook.go:312-316 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/flow/registration/hook.go:291` calls `SetAttributes`, `String`, `Sprintf` and `selfservice/flow/registration/hook.go:143` 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 (3–5 lines × 3) selfservice/strategy/lookup/settings.go:107— selfservice/strategy/lookup/settings.go:107-109 | selfservice/strategy/password/settings.go:84-88 | selfservice/strategy/totp/settings.go:91-95 — `selfservice/strategy/lookup/settings.go` and `selfservice/strategy/totp/settings.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 47 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/settings.go:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/strategy/lookup/settings.go:110` calls `handleSettingsError` and `selfservice/strategy/totp/settings.go:95` 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 (3–5 lines × 3) session/handler.go:729— session/handler.go:729-733 | session/handler.go:799-803 | session/handler.go:880-882 — 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 `session/handler.go:880` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
Unused dependency 'license-checker' package.json:17— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'license-checker' oryx/package.json:9— Declared in oryx/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X28 · Index access outside its own emptiness guard· Index access outside its own emptiness guard · ×2
Index access outside its own emptiness guard schema/prevalidate.go:135— `idx` is the result of a search that answers -1 when nothing is found, and `chain[idx:]` uses it as a bound with no test of `idx` in between. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Test `idx < 0` (or use `strings.Cut`) before using it.
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.
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.
Handler.NewLoginFlow (cyclomatic 43) selfservice/flow/login/handler.go:148— Handler.NewLoginFlow 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.
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.
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.
IdentityPersister.ListIdentities (cyclomatic 37) persistence/sql/identity/persister_identity.go:1126— IdentityPersister.ListIdentities has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 9 of the 37 points are its own statements and the rest belongs to one function literal inside it that branches (line 1149). 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.
HookExecutor.PostRegistrationHook (cyclomatic 35) selfservice/flow/registration/hook.go:117— HookExecutor.PostRegistrationHook 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.
IdentityPersister.CreateIdentities (cyclomatic 34) persistence/sql/identity/persister_identity.go:795— IdentityPersister.CreateIdentities has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to one function literal inside it that branches (line 832). 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.
HookExecutor.PostLoginHook (cyclomatic 33) selfservice/flow/login/hook.go:128— HookExecutor.PostLoginHook has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
argon2.newCalibrateCmd (cyclomatic 30) cmd/hashers/argon2/calibrate.go:75— argon2.newCalibrateCmd has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to one function literal inside it that branches (line 94). 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.
Manager.findExistingAuthMethod (cyclomatic 30) REDACTED:261— Manager.findExistingAuthMethod has cyclomatic complexity 30 (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.
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.
Handler.updateVerificationFlow (cyclomatic 29) selfservice/flow/verification/handler.go:419— Handler.updateVerificationFlow 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.
VerifyNewAddress.execute (cyclomatic 28) selfservice/hook/verify_new_address.go:72— VerifyNewAddress.execute 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.
courier.NewEmailTemplateFromMessage (cyclomatic 27) courier/email_templates.go:37— courier.NewEmailTemplateFromMessage 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.
RegistryDefault.Init (cyclomatic 27) driver/registry_default.go:669— RegistryDefault.Init has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 704). 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.
HookExecutor.PostSettingsHook (cyclomatic 27) selfservice/flow/settings/hook.go:187— HookExecutor.PostSettingsHook 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.
Strategy.HandleCallback (cyclomatic 27) selfservice/strategy/oidc/strategy.go:476— Strategy.HandleCallback 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.
Strategy.UpdateIdentityFromClaims (cyclomatic 27) selfservice/strategy/oidc/strategy_login.go:218— Strategy.UpdateIdentityFromClaims 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.
argon2.runLoadTest (cyclomatic 26) cmd/hashers/argon2/loadtest.go:105— argon2.runLoadTest has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 157, 122, 188, …). 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.
SMTPChannel.Dispatch (cyclomatic 26) courier/smtp_channel.go:58— SMTPChannel.Dispatch 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.
x.IsValidNumber (cyclomatic 26) x/json_number.go:9— x.IsValidNumber has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
corpx.registerFakes (cyclomatic 25) REDACTED:30— corpx.registerFakes has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
driver.getHooks (cyclomatic 25) driver/registry_default_hooks.go:70— driver.getHooks has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ErrorHandler.WriteFlowError (cyclomatic 24) selfservice/flow/settings/error.go:141— ErrorHandler.WriteFlowError has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebHook.execute (cyclomatic 24) selfservice/hook/web_hook.go:302— WebHook.execute has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 318). 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.
Strategy.ProcessLogin (cyclomatic 24) selfservice/strategy/oidc/strategy_login.go:334— Strategy.ProcessLogin 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.
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.
Strategy.populateChooseMethodFlow (cyclomatic 23) selfservice/strategy/code/strategy.go:250— Strategy.populateChooseMethodFlow has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.Login (cyclomatic 23) selfservice/strategy/idfirst/strategy_login.go:45— Strategy.Login has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.validateAllMessages (cyclomatic 22) cmd/clidoc/main.go:337— main.validateAllMessages has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IdentityPersister.UpdateIdentity (cyclomatic 22) persistence/sql/identity/persister_identity.go:1668— IdentityPersister.UpdateIdentity has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 1693). 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.
HookExecutor.ApplyPendingTraitsChange (cyclomatic 22) selfservice/flow/settings/hook.go:402— HookExecutor.ApplyPendingTraitsChange has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 426). 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.
Strategy.Recover (cyclomatic 22) selfservice/strategy/code/strategy_recovery.go:162— Strategy.Recover has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.Register (cyclomatic 22) selfservice/strategy/oidc/strategy_registration.go:164— Strategy.Register has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
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.
hook.parseWebhookResponse (cyclomatic 21) selfservice/hook/web_hook.go:455— hook.parseWebhookResponse has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Verifier.do (cyclomatic 21) selfservice/hook/verification.go:104— Verifier.do has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.populateEmailSentFlow (cyclomatic 21) selfservice/strategy/code/strategy.go:365— Strategy.populateEmailSentFlow has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ManagerHTTP.DoesSessionSatisfy (cyclomatic 21) session/manager_http.go:337— ManagerHTTP.DoesSessionSatisfy has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.updateLoginFlow (cyclomatic 20) selfservice/flow/login/handler.go:894— Handler.updateLoginFlow has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ErrorHandler.WriteFlowError (cyclomatic 20) selfservice/flow/registration/error.go:93— ErrorHandler.WriteFlowError has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AddressVerifier.ExecuteLoginPostHook (cyclomatic 20) selfservice/hook/require_verified_address.go:59— AddressVerifier.ExecuteLoginPostHook has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.verificationHandleFormSubmission (cyclomatic 20) selfservice/strategy/code/strategy_verification.go:200— Strategy.verificationHandleFormSubmission has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.verificationUseCode (cyclomatic 20) selfservice/strategy/code/strategy_verification.go:298— Strategy.verificationUseCode has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.PopulateSettingsMethod (cyclomatic 20) selfservice/strategy/oidc/strategy_settings.go:158— Strategy.PopulateSettingsMethod has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
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.
Strategy.ValidateCallback (cyclomatic 19) selfservice/strategy/oidc/strategy.go:348— Strategy.ValidateCallback 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.
Strategy.populateAccountLinkingUI (cyclomatic 19) selfservice/strategy/oidc/strategy.go:787— Strategy.populateAccountLinkingUI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.Settings (cyclomatic 19) selfservice/strategy/oidc/strategy_settings.go:315— Strategy.Settings has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.Register (cyclomatic 19) REDACTED:96— Strategy.Register 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.
IdentityPersister.UpdateCredentialsConfig (cyclomatic 18) persistence/sql/identity/persister_identity.go:1405— IdentityPersister.UpdateCredentialsConfig has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 1458). 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.
ErrorHandler.WriteFlowError (cyclomatic 18) selfservice/flow/login/error.go:103— ErrorHandler.WriteFlowError 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.
Strategy.FastLogin1FA (cyclomatic 18) selfservice/strategy/code/strategy_login.go:277— Strategy.FastLogin1FA 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.
Strategy.recoveryIssueSession (cyclomatic 18) selfservice/strategy/code/strategy_recovery.go:260— Strategy.recoveryIssueSession 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.
Strategy.verificationUseToken (cyclomatic 18) selfservice/strategy/link/strategy_verification.go:201— Strategy.verificationUseToken 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.
Strategy.HandleError (cyclomatic 18) selfservice/strategy/oidc/strategy.go:702— Strategy.HandleError 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.
Strategy.Register (cyclomatic 18) selfservice/strategy/passkey/passkey_registration.go:96— Strategy.Register 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.
DefaultPasswordValidator.validate (cyclomatic 18) REDACTED:185— DefaultPasswordValidator.validate 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.
Nodes.SortBySchema (cyclomatic 18) ui/node/node.go:264— Nodes.SortBySchema has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 314, 285). 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.
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.
Identity.WithDeclassifiedCredentials (cyclomatic 17) identity/identity.go:480— Identity.WithDeclassifiedCredentials has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 498). 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.
IdentityPersister.createIdentityCredentials (cyclomatic 17) persistence/sql/identity/persister_identity.go:367— IdentityPersister.createIdentityCredentials 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.
preValidator.walk (cyclomatic 17) schema/prevalidate.go:66— preValidator.walk 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.
ErrorHandler.WriteFlowError (cyclomatic 17) selfservice/flow/recovery/error.go:70— ErrorHandler.WriteFlowError 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.
Handler.NewRegistrationFlow (cyclomatic 17) selfservice/flow/registration/handler.go:135— Handler.NewRegistrationFlow 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.
Tokenizer.TokenizeSession (cyclomatic 17) session/tokenizer.go:75— Tokenizer.TokenizeSession 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.
Handler.deleteIdentityCredentials (cyclomatic 16) identity/handler.go:1408— Handler.deleteIdentityCredentials has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler.importCredentials (cyclomatic 16) identity/handler_import.go:18— Handler.importCredentials has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Sender.SendCode (cyclomatic 16) selfservice/strategy/code/code_sender.go:74— Sender.SendCode has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.FastLogin2FA (cyclomatic 16) selfservice/strategy/code/strategy_login.go:333— Strategy.FastLogin2FA has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.loginVerifyCode (cyclomatic 16) selfservice/strategy/code/strategy_login.go:582— Strategy.loginVerifyCode has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.Login (cyclomatic 16) selfservice/strategy/lookup/login.go:90— Strategy.Login 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.
oidc.CountActiveFirstFactorCredentials (cyclomatic 16) selfservice/strategy/oidc/strategy.go:173— oidc.CountActiveFirstFactorCredentials has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strategy.continueSettingsFlowAdd (cyclomatic 16) selfservice/strategy/webauthn/settings.go:246— Strategy.continueSettingsFlowAdd 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.
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: selfservice/strategy/passkey/passkey_schema_extension.go selfservice/strategy/passkey/passkey_schema_extension.go:77— selfservice/strategy/passkey/passkey_schema_extension.go changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is Strategy.PasskeyDisplayNameFromSchema at line 77), 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: skip passkey method on registration when identity schema lacks a display name trait”; “fix: keep first non-empty trait when resolving display name”; “fix: support multiple display-name traits in identity schemas”. 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:36 +00:00' --until='2026-07-29 09:30:36 +00:00' --full-history --no-merges -- selfservice/strategy/passkey/passkey_schema_extension.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 pkg/testhelpers/mailhog.go:35— // hacky but should silence most MailHog logs during tests — 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.
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.
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.
IdentityPersister.CreateIdentities (cognitive 75) persistence/sql/identity/persister_identity.go:795— IdentityPersister.CreateIdentities has cognitive complexity 75 (threshold 15). Drivers by points: if/else 30 (51 pts), loops 10 (24 pts) (nesting depth added 35). Most of this is not in the body itself: 13 of the 75 points are its own statements and the rest belongs to one function literal inside it that branches (line 832). 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.
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.
main.validateAllMessages (cognitive 66) cmd/clidoc/main.go:337— main.validateAllMessages has cognitive complexity 66 (threshold 15). Drivers by points: if/else 11 (43 pts), loops 7 (19 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 46). 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.
Handler.NewLoginFlow (cognitive 65) selfservice/flow/login/handler.go:148— Handler.NewLoginFlow has cognitive complexity 65 (threshold 15). Drivers by points: if/else 24 (38 pts), match/switch 6 (17 pts), boolean chains 4, jumps 3, loops 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.ProcessLogin (cognitive 64) selfservice/strategy/oidc/strategy_login.go:334— Strategy.ProcessLogin has cognitive complexity 64 (threshold 15). Drivers by points: if/else 18 (58 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 42). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
HookExecutor.PostLoginHook (cognitive 61) selfservice/flow/login/hook.go:128— HookExecutor.PostLoginHook has cognitive complexity 61 (threshold 15). Drivers by points: if/else 30 (59 pts), boolean chains 1, loops 1 (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.
HookExecutor.PostRegistrationHook (cognitive 60) selfservice/flow/registration/hook.go:117— HookExecutor.PostRegistrationHook has cognitive complexity 60 (threshold 15). Drivers by points: if/else 29 (53 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Manager.findExistingAuthMethod (cognitive 55) REDACTED:261— Manager.findExistingAuthMethod has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (39 pts), loops 5 (11 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IdentityPersister.ListIdentities (cognitive 55) persistence/sql/identity/persister_identity.go:1126— IdentityPersister.ListIdentities has cognitive complexity 55 (threshold 15). Drivers by points: if/else 27 (40 pts), loops 6 (12 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 20). Most of this is not in the body itself: 14 of the 55 points are its own statements and the rest belongs to one function literal inside it that branches (line 1149). 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.
Strategy.populateChooseMethodFlow (cognitive 55) selfservice/strategy/code/strategy.go:250— Strategy.populateChooseMethodFlow has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (44 pts), loops 3 (9 pts), boolean chains 1, match/switch 1 (nesting depth added 34). 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.
Handler.updateVerificationFlow (cognitive 53) selfservice/flow/verification/handler.go:419— Handler.updateVerificationFlow has cognitive complexity 53 (threshold 15). Drivers by points: if/else 22 (47 pts), boolean chains 5, loops 1 (nesting depth added 25). 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.
argon2.newCalibrateCmd (cognitive 51) cmd/hashers/argon2/calibrate.go:75— argon2.newCalibrateCmd has cognitive complexity 51 (threshold 15). Drivers by points: if/else 20 (40 pts), loops 6 (7 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 22). None of this is in the body itself: all 51 points belong to one function literal inside it that branches (line 94). 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.
driver.getHooks (cognitive 50) driver/registry_default_hooks.go:70— driver.getHooks has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (43 pts), loops 2 (4 pts), match/switch 1 (2 pts), jumps 1 (nesting depth added 32). 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.
Identity.WithDeclassifiedCredentials (cognitive 48) identity/identity.go:480— Identity.WithDeclassifiedCredentials has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (41 pts), loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 33). Most of this is not in the body itself: 11 of the 48 points are its own statements and the rest belongs to one function literal inside it that branches (line 498). 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.
Strategy.HandleError (cognitive 45) selfservice/strategy/oidc/strategy.go:702— Strategy.HandleError has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (39 pts), loops 1 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 28). 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.
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.
Strategy.HandleCallback (cognitive 43) selfservice/strategy/oidc/strategy.go:476— Strategy.HandleCallback has cognitive complexity 43 (threshold 15). Drivers by points: if/else 22 (41 pts), match/switch 2 (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.
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.
Strategy.verificationUseCode (cognitive 41) selfservice/strategy/code/strategy_verification.go:298— Strategy.verificationUseCode has cognitive complexity 41 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hook.parseWebhookResponse (cognitive 40) selfservice/hook/web_hook.go:455— hook.parseWebhookResponse has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19 (35 pts), loops 2 (5 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.
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.
HookExecutor.PostSettingsHook (cognitive 38) selfservice/flow/settings/hook.go:187— HookExecutor.PostSettingsHook has cognitive complexity 38 (threshold 15). Drivers by points: if/else 21 (32 pts), loops 3, match/switch 1 (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.
Strategy.populateEmailSentFlow (cognitive 38) selfservice/strategy/code/strategy.go:365— Strategy.populateEmailSentFlow has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 4, loops 2 (4 pts), match/switch 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.UpdateIdentityFromClaims (cognitive 37) selfservice/strategy/oidc/strategy_login.go:218— Strategy.UpdateIdentityFromClaims has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 6 (9 pts), boolean chains 4 (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.
Verifier.do (cognitive 36) selfservice/hook/verification.go:104— Verifier.do has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 3, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.verificationUseToken (cognitive 36) selfservice/strategy/link/strategy_verification.go:201— Strategy.verificationUseToken has cognitive complexity 36 (threshold 15). Drivers by points: if/else 20 (35 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.PopulateSettingsMethod (cognitive 36) selfservice/strategy/oidc/strategy_settings.go:158— Strategy.PopulateSettingsMethod has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (27 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IdentityPersister.UpdateIdentity (cognitive 35) persistence/sql/identity/persister_identity.go:1668— IdentityPersister.UpdateIdentity has cognitive complexity 35 (threshold 15). Drivers by points: if/else 20 (32 pts), loops 2, boolean chains 1 (nesting depth added 12). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to one function literal inside it that branches (line 1693). 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.
SMTPChannel.Dispatch (cognitive 34) courier/smtp_channel.go:58— SMTPChannel.Dispatch has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 5, loops 3 (4 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddressVerifier.ExecuteLoginPostHook (cognitive 34) selfservice/hook/require_verified_address.go:59— AddressVerifier.ExecuteLoginPostHook has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (30 pts), loops 3 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManagerHTTP.DoesSessionSatisfy (cognitive 34) session/manager_http.go:337— ManagerHTTP.DoesSessionSatisfy has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
courier.DispatchQueue (cognitive 33) courier/courier_dispatcher.go:99— courier.DispatchQueue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (29 pts), loops 2 (4 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorHandler.WriteFlowError (cognitive 33) selfservice/flow/settings/error.go:141— ErrorHandler.WriteFlowError has cognitive complexity 33 (threshold 15). Drivers by points: if/else 25 (31 pts), boolean chains 2 (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, 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.
Strategy.Login (cognitive 33) selfservice/strategy/idfirst/strategy_login.go:45— Strategy.Login has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (30 pts), loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebHook.execute (cognitive 32) selfservice/hook/web_hook.go:302— WebHook.execute has cognitive complexity 32 (threshold 15). Drivers by points: if/else 20 (27 pts), boolean chains 5 (nesting depth added 7). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to one function literal inside it that branches (line 318). 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.
oidc.CountActiveFirstFactorCredentials (cognitive 32) selfservice/strategy/oidc/strategy.go:173— oidc.CountActiveFirstFactorCredentials has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 3 (8 pts), boolean chains 4 (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.
Strategy.populateAccountLinkingUI (cognitive 32) selfservice/strategy/oidc/strategy.go:787— Strategy.populateAccountLinkingUI has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (4 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
argon2.runLoadTest (cognitive 31) cmd/hashers/argon2/loadtest.go:105— argon2.runLoadTest has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 5 (9 pts), loops 3 (nesting depth added 13). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 122, 157, 188, …). 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.
preValidator.walk (cognitive 31) schema/prevalidate.go:66— preValidator.walk has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 3 (7 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 18). 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.
VerifyNewAddress.execute (cognitive 31) selfservice/hook/verify_new_address.go:72— VerifyNewAddress.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 24 (28 pts), boolean chains 3 (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.
Strategy.verificationHandleFormSubmission (cognitive 31) selfservice/strategy/code/strategy_verification.go:200— Strategy.verificationHandleFormSubmission has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Container.ParseError (cognitive 31) ui/container/container.go:180— Container.ParseError has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 4 (10 pts), match/switch 2 (4 pts) (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.
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.
Handler.updateLoginFlow (cognitive 29) selfservice/flow/login/handler.go:894— Handler.updateLoginFlow has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 2, jumps 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sender.SendCode (cognitive 29) selfservice/strategy/code/code_sender.go:74— Sender.SendCode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 3 (8 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IdentityPersister.createIdentityCredentials (cognitive 28) persistence/sql/identity/persister_identity.go:367— IdentityPersister.createIdentityCredentials has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HookExecutor.ApplyPendingTraitsChange (cognitive 28) selfservice/flow/settings/hook.go:402— HookExecutor.ApplyPendingTraitsChange has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 4, loops 2 (nesting depth added 7). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 426). 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.
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.
courier.NewEmailTemplateFromMessage (cognitive 27) courier/email_templates.go:37— courier.NewEmailTemplateFromMessage has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (26 pts), match/switch 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RegistryDefault.Init (cognitive 27) driver/registry_default.go:669— RegistryDefault.Init has cognitive complexity 27 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 4, loops 1 (nesting depth added 2). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 704). 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.
ErrorHandler.WriteFlowError (cognitive 27) selfservice/flow/recovery/error.go:70— ErrorHandler.WriteFlowError has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.createBrowserRegistrationFlow (cognitive 27) selfservice/flow/registration/handler.go:374— Handler.createBrowserRegistrationFlow has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 1 (nesting depth added 14). 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.
Strategy.Register (cognitive 26) selfservice/strategy/oidc/strategy_registration.go:164— Strategy.Register has cognitive complexity 26 (threshold 15). Drivers by points: if/else 22 (25 pts), 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, 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.
x.IsValidNumber (cognitive 26) x/json_number.go:9— x.IsValidNumber has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 8, loops 3 (6 pts), match/switch 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.
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.
Strategy.findIdentityForIdentifier (cognitive 25) selfservice/strategy/code/strategy_login.go:402— Strategy.findIdentityForIdentifier has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.ValidateCallback (cognitive 25) selfservice/strategy/oidc/strategy.go:348— Strategy.ValidateCallback has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 2 (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.
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.
Strategy.Settings (cognitive 24) selfservice/strategy/oidc/strategy_settings.go:315— Strategy.Settings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 2, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaExtensionCredentials.Run (cognitive 23) identity/extension_credentials.go:56— SchemaExtensionCredentials.Run has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 1 (nesting depth added 10). Of this number, 21 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.
Handler.createBrowserLoginFlow (cognitive 23) selfservice/flow/login/handler.go:570— Handler.createBrowserLoginFlow has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.FastLogin1FA (cognitive 23) selfservice/strategy/code/strategy_login.go:277— Strategy.FastLogin1FA has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, loops 1 (2 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.
Strategy.recoveryIssueSession (cognitive 23) selfservice/strategy/code/strategy_recovery.go:260— Strategy.recoveryIssueSession has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (20 pts), match/switch 2 (3 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, 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.
Strategy.alreadyAuthenticated (cognitive 23) selfservice/strategy/oidc/strategy.go:445— Strategy.alreadyAuthenticated has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (23 pts) (nesting depth added 15). 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.
Tokenizer.TokenizeSession (cognitive 23) session/tokenizer.go:75— Tokenizer.TokenizeSession has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (23 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.
corpx.registerFakes (cognitive 22) REDACTED:30— corpx.registerFakes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17, loops 3 (4 pts), match/switch 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
Handler.batchPatchIdentities (cognitive 22) identity/handler.go:885— Handler.batchPatchIdentities has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.importCredentials (cognitive 22) identity/handler_import.go:18— Handler.importCredentials has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (22 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.
IdentityPersister.UpdateCredentialsConfig (cognitive 22) persistence/sql/identity/persister_identity.go:1405— IdentityPersister.UpdateCredentialsConfig has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 1, loops 1 (nesting depth added 5). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 1458). 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.
ErrorHandler.WriteFlowError (cognitive 22) selfservice/flow/registration/error.go:93— ErrorHandler.WriteFlowError has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 3 (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.
Strategy.FastLogin2FA (cognitive 22) selfservice/strategy/code/strategy_login.go:333— Strategy.FastLogin2FA has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 3, loops 1 (2 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.
Strategy.Recover (cognitive 22) selfservice/strategy/code/strategy_recovery.go:162— Strategy.Recover has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.Login (cognitive 22) selfservice/strategy/password/login.go:51— Strategy.Login has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (22 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.
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.
migrate.normalizeTable (cognitive 21) cmd/migrate/normalize_phone_handler.go:162— migrate.normalizeTable has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaExtensionRecovery.Run (cognitive 21) identity/extension_recovery.go:29— SchemaExtensionRecovery.Run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Handler.deleteIdentityCredentials (cognitive 21) identity/handler.go:1408— Handler.deleteIdentityCredentials has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 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.
Handler.NewRegistrationFlow (cognitive 21) selfservice/flow/registration/handler.go:135— Handler.NewRegistrationFlow has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.registrationVerifyCode (cognitive 21) selfservice/strategy/code/strategy_registration.go:281— Strategy.registrationVerifyCode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 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.
ProviderApple.DecodeQuery (cognitive 21) selfservice/strategy/oidc/provider_apple.go:132— ProviderApple.DecodeQuery has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (21 pts) (nesting depth added 14). 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.
Strategy.unlinkProvider (cognitive 21) selfservice/strategy/oidc/strategy_settings.go:536— Strategy.unlinkProvider has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 2 (4 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, 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.
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.
config.New (cognitive 20) driver/config/config.go:398— config.New has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (20 pts) (nesting depth added 10). Of this number, 18 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.
Strategy.handleConflictingIdentity (cognitive 20) selfservice/strategy/oidc/strategy_login.go:104— Strategy.handleConflictingIdentity has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Nodes.SortBySchema (cognitive 20) ui/node/node.go:264— Nodes.SortBySchema has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, loops 2 (nesting depth added 4). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 314, 285). 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.
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.
sql.useOneTimeCode (cognitive 19) persistence/sql/persister_code.go:43— sql.useOneTimeCode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 3 (4 pts), jumps 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 72). 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.
Persister.UpsertSession (cognitive 19) persistence/sql/persister_session.go:239— Persister.UpsertSession has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (18 pts), loops 1 (nesting depth added 5). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 262, 251). 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.
Strategy.loginVerifyCode (cognitive 19) selfservice/strategy/code/strategy_login.go:582— Strategy.loginVerifyCode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.retryRecoveryFlow (cognitive 19) selfservice/strategy/code/strategy_recovery.go:409— Strategy.retryRecoveryFlow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.Login (cognitive 19) selfservice/strategy/lookup/login.go:90— Strategy.Login has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (18 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Strategy.PopulateLoginMethodFirstFactorRefresh (cognitive 19) selfservice/strategy/oidc/strategy_login.go:599— Strategy.PopulateLoginMethodFirstFactorRefresh has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (7 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultPasswordValidator.validate (cognitive 19) REDACTED:185— DefaultPasswordValidator.validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.Register (cognitive 19) REDACTED:96— Strategy.Register has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17 (18 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.
Strategy.countCredentials (cognitive 19) selfservice/strategy/webauthn/strategy.go:91— Strategy.countCredentials has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Manager.Continue (cognitive 18) continuity/manager.go:126— Manager.Continue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3 (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.
identity.UpgradeCodeCredentials (cognitive 18) identity/credentials_migrate.go:79— identity.UpgradeCodeCredentials has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 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.
PasswordMigration.Execute (cognitive 18) selfservice/hook/password_migration_hook.go:48— PasswordMigration.Execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.Register (cognitive 18) selfservice/strategy/passkey/passkey_registration.go:96— Strategy.Register has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16 (17 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.
text.NewErrorValidationDuplicateCredentialsWithHints (cognitive 18) text/message_validation.go:308— text.NewErrorValidationDuplicateCredentialsWithHints has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), match/switch 1 (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.
x.TypeMap (cognitive 18) x/map_json.go:20— x.TypeMap has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
identity.parseListIdentitiesParameters (cognitive 17) identity/handler.go:187— identity.parseListIdentitiesParameters has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
identity.findFirstConflict (cognitive 17) REDACTED:146— identity.findFirstConflict has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (4 pts) (nesting depth added 6). 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.
Manager.ConflictingIdentity (cognitive 17) REDACTED:201— Manager.ConflictingIdentity has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts) (nesting depth added 6). Of this number, 10 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schema.NewExtensionRunner (cognitive 17) schema/extension.go:96— schema.NewExtensionRunner has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (4 pts) (nesting depth added 6). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 114, 138). 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.
Strategy.continueSettingsFlow (cognitive 17) selfservice/strategy/lookup/settings.go:149— Strategy.continueSettingsFlow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.showCredentialsSelection (cognitive 17) selfservice/strategy/profile/registration.go:261— Strategy.showCredentialsSelection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 1, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
ManagerHTTP.IssueCookie (cognitive 17) session/manager_http.go:142— ManagerHTTP.IssueCookie has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 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.
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.
identities.ValidateIdentity (cognitive 16) cmd/identities/validate.go:83— identities.ValidateIdentity has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
identity.CredentialsEqual (cognitive 16) identity/credentials.go:289— identity.CredentialsEqual has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
batch.buildInsertQueryArgs (cognitive 16) persistence/sql/batch/create.go:71— batch.buildInsertQueryArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
testhelpers.MockSessionCreateHandlerWithIdentityAndAMR (cognitive 16) pkg/testhelpers/handler_mock.go:185— testhelpers.MockSessionCreateHandlerWithIdentityAndAMR has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 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.
testhelpers.serveSMTP (cognitive 16) pkg/testhelpers/mailhog.go:73— testhelpers.serveSMTP has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 1 (2 pts), 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.
Handler.ReadSchema (cognitive 16) schema/handler.go:228— Handler.ReadSchema has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
hook.computeNotifyTargets (cognitive 16) selfservice/hook/notify_previous_addresses.go:79— hook.computeNotifyTargets has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 3 (7 pts), match/switch 1 (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Strategy.PopulateMethod (cognitive 16) selfservice/strategy/code/strategy.go:199— Strategy.PopulateMethod has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.recoveryUseToken (cognitive 16) selfservice/strategy/link/strategy_recovery.go:363— Strategy.recoveryUseToken has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.processRegistration (cognitive 16) selfservice/strategy/oidc/strategy_registration.go:325— Strategy.processRegistration has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strategy.continueSettingsFlowAdd (cognitive 16) selfservice/strategy/webauthn/settings.go:246— Strategy.continueSettingsFlowAdd has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
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· `Config.CourierSMTPHeaders` returns a map (`map[K]V`) where its 13 siblings return a slice (`[]T`) · ×1
`Config.CourierSMTPHeaders` returns a map (`map[K]V`) where its 13 siblings return a slice (`[]T`) driver/config/config.go:1260— 13 of 14 collection-returning members of `Config` return a slice (`[]T`) (13 of 14). Siblings: Config.ClientHTTPPrivateIPExceptionURLs (driver/config/config.go:685); Config.SelfServiceFlowLoginBeforeHooks (driver/config/config.go:770); Config.SelfServiceFlowRecoveryBeforeHooks (driver/config/config.go:774); Config.SelfServiceFlowVerificationBeforeHooks (driver/config/config.go:778); Config.SelfServiceFlowSettingsBeforeHooks (driver/config/config.go:790). Return a slice (`[]T`). [rule A4]
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]
D22 · Internal API Consistency· `testhelpers.NewNetworkUnlessExisting` takes its context.Context at position 2 where 27 members of the package take it first · ×1
`testhelpers.NewNetworkUnlessExisting` takes its context.Context at position 2 where 27 members of the package take it first pkg/testhelpers/network.go:17— 27 of 30 members of package testhelpers with a context take it as the first parameter, the context package's own rule (27 of 30). Siblings: testhelpers.WithDefaultIdentitySchema (pkg/testhelpers/config.go:31); testhelpers.WithAddIdentitySchema (pkg/testhelpers/config.go:50); testhelpers.WithDefaultIdentitySchemaFromRaw (pkg/testhelpers/config.go:81); testhelpers.CourierExpectMessage (pkg/testhelpers/courier.go:19); testhelpers.InitializeLoginFlowViaBrowserCtx (pkg/testhelpers/selfservice_login.go:163). Move `ctx context.Context` to the front of the parameter list. [rule A2]
D22 · Internal API Consistency· `testhelpers.NewNetwork` takes its context.Context at position 2 where 27 members of the package take it first · ×1
`testhelpers.NewNetwork` takes its context.Context at position 2 where 27 members of the package take it first pkg/testhelpers/network.go:27— 27 of 30 members of package testhelpers with a context take it as the first parameter, the context package's own rule (27 of 30). Siblings: testhelpers.WithDefaultIdentitySchema (pkg/testhelpers/config.go:31); testhelpers.WithAddIdentitySchema (pkg/testhelpers/config.go:50); testhelpers.WithDefaultIdentitySchemaFromRaw (pkg/testhelpers/config.go:81); testhelpers.CourierExpectMessage (pkg/testhelpers/courier.go:19); testhelpers.InitializeLoginFlowViaBrowserCtx (pkg/testhelpers/selfservice_login.go:163). Move `ctx context.Context` to the front of the parameter list. [rule A2]
D22 · Internal API Consistency· `testhelpers.SkipIfNetworkContext` takes its context.Context last where 27 members of the package take it first · ×1
`testhelpers.SkipIfNetworkContext` takes its context.Context last where 27 members of the package take it first pkg/testhelpers/network.go:40— 27 of 30 members of package testhelpers with a context take it as the first parameter, the context package's own rule (27 of 30). Siblings: testhelpers.WithDefaultIdentitySchema (pkg/testhelpers/config.go:31); testhelpers.WithAddIdentitySchema (pkg/testhelpers/config.go:50); testhelpers.WithDefaultIdentitySchemaFromRaw (pkg/testhelpers/config.go:81); testhelpers.CourierExpectMessage (pkg/testhelpers/courier.go:19); testhelpers.InitializeLoginFlowViaBrowserCtx (pkg/testhelpers/selfservice_login.go:163). Move `ctx context.Context` to the front of the parameter list. [rule A2]
D22 · Internal API Consistency· `flow.NextState` signals absence with a bare `T` (the zero value when absent) where its 3 sibling single-key reads use a nil `*T` · ×1
`flow.NextState` signals absence with a bare `T` (the zero value when absent) where its 3 sibling single-key reads use a nil `*T` selfservice/flow/state.go:79— 3 of 4 single-key reads of `package flow` return a nil `*T` (3 of 4). Siblings: flow.NewContinueWithSetToken (selfservice/flow/continue_with.go:51); flow.NewContinueWithRedirectBrowserTo (selfservice/flow/continue_with.go:260); flow.NewBrowserLocationChangeRequiredError (selfservice/flow/error.go:179). Return a nil `*T` like its siblings. [rule A5]
Near-duplicate member pair (52 shared lines) selfservice/strategy/passkey/passkey_settings.go:332— selfservice/strategy/passkey/passkey_settings.go:332-414 | selfservice/strategy/webauthn/settings.go:246-332 — These two members are variants of one another: 52 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.
Near-duplicate member pair (48 shared lines) cmd/daemon/serve.go:56— cmd/daemon/serve.go:56-154 | cmd/daemon/serve.go:156-240 — These two members are variants of one another: 48 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.
Near-duplicate member pair (43 shared lines) selfservice/strategy/oidc/provider_auth0.go:76— selfservice/strategy/oidc/provider_auth0.go:76-125 | selfservice/strategy/oidc/provider_salesforce.go:76-125 — These two members are variants of one another: 43 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.
Near-duplicate member pair (34 shared lines) selfservice/strategy/passkey/passkey_settings.go:279— selfservice/strategy/passkey/passkey_settings.go:279-330 | selfservice/strategy/webauthn/settings.go:190-244 — 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.
Near-duplicate member pair (30 shared lines) selfservice/strategy/oidc/strategy_login.go:469— selfservice/strategy/oidc/strategy_login.go:469-597 | selfservice/strategy/oidc/strategy_registration.go:164-283 — These two members are variants of one another: 30 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.
Near-duplicate member pair (29 shared lines) selfservice/flow/login/error.go:103— selfservice/flow/login/error.go:103-191 | selfservice/flow/registration/error.go:100-201 — These two members are variants of one another: 29 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (103 corresponding lines) · ×1
Edited copy of a member (103 corresponding lines) selfservice/strategy/code/strategy_verification.go:298— selfservice/strategy/code/strategy_verification.go:298-410 | selfservice/strategy/link/strategy_verification.go:201-303 — These two members are one piece of code written twice and then edited apart: 103 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (85 corresponding lines) · ×1
Edited copy of a member (85 corresponding lines) selfservice/flow/recovery/error.go:76— selfservice/flow/recovery/error.go:76-170 | selfservice/flow/verification/error.go:74-158 — These two members are one piece of code written twice and then edited apart: 85 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) selfservice/flow/login/handler.go:728— selfservice/flow/login/handler.go:728-797 | selfservice/flow/registration/handler.go:545-604 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) selfservice/strategy/oidc/provider_amazon.go:102— selfservice/strategy/oidc/provider_amazon.go:102-141 | selfservice/strategy/oidc/provider_uaepass.go:118-182 — 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) selfservice/flow/recovery/handler.go:290— selfservice/flow/recovery/handler.go:290-328 | selfservice/flow/verification/handler.go:292-330 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) selfservice/strategy/oidc/provider_vk.go:64— selfservice/strategy/oidc/provider_vk.go:64-134 | selfservice/strategy/oidc/provider_yandex.go:62-115 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) selfservice/strategy/link/strategy_recovery.go:463— selfservice/strategy/link/strategy_recovery.go:463-498 | selfservice/strategy/link/strategy_verification.go:164-199 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) persistence/sql/persister_recovery.go:75— persistence/sql/persister_recovery.go:75-122 | persistence/sql/persister_verification.go:73-120 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) persistence/sql/identity/persister_identity.go:162— persistence/sql/identity/persister_identity.go:162-235 | persistence/sql/identity/persister_identity.go:237-322 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 52+ corresponding lines) · ×1
Edited copies of one member (3 members, 52+ corresponding lines) selfservice/strategy/code/code_sender.go:351— selfservice/strategy/code/code_sender.go:351-409 | selfservice/strategy/link/sender.go:64-115 | selfservice/strategy/link/sender.go:122-174 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 52 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 (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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) oryx/sqlxx/batch/create.go:46— oryx/sqlxx/batch/create.go:46-111 | persistence/sql/batch/create.go:71-142 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) identity/handler_import.go:254— identity/handler_import.go:254-297 | identity/handler_import.go:299-340 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) oryx/tlsx/cert.go:358— oryx/tlsx/cert.go:358-401 | REDACTED:179-225 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) selfservice/strategy/passkey/passkey_registration.go:315— selfservice/strategy/passkey/passkey_registration.go:315-378 | REDACTED:198-232 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) selfservice/strategy/link/strategy_recovery.go:433— selfservice/strategy/link/strategy_recovery.go:433-461 | selfservice/strategy/link/strategy_verification.go:305-327 | selfservice/strategy/link/strategy_verification.go:329-358 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 30+ corresponding lines) · ×1
Edited copies of one member (3 members, 30+ corresponding lines) REDACTED:442— REDACTED:442-479 | REDACTED:493-527 | REDACTED:531-560 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) persistence/sql/persister_recovery_code.go:20— persistence/sql/persister_recovery_code.go:20-51 | persistence/sql/persister_verification_code.go:21-54 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) pkg/testhelpers/selfservice_verification.go:33— pkg/testhelpers/selfservice_verification.go:33-57 | pkg/testhelpers/selfservice_verification.go:59-83 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) cmd/cleanup/sql.go:20— cmd/cleanup/sql.go:20-49 | cmd/migrate/normalize_phone.go:16-55 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) driver/config/config.go:1126— driver/config/config.go:1126-1150 | driver/config/config.go:1152-1174 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) persistence/sql/identity/persister_identity.go:96— persistence/sql/identity/persister_identity.go:96-108 | persistence/sql/identity/persister_identity.go:110-122 | persistence/sql/identity/persister_identity.go:567-582 | persistence/sql/identity/persister_identity.go:1902-1919 — 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 (93 corresponding lines) · ×1
Edited copy of a member (93 corresponding lines) selfservice/flow/recovery/flow.go:41— selfservice/flow/recovery/flow.go:41-133 | selfservice/flow/verification/flow.go:43-137 — These two members are one piece of code written twice and then edited apart: 93 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 19+ corresponding lines) · ×1
Edited copies of one member (5 members, 19+ corresponding lines) persistence/sql/persister_courier.go:147— persistence/sql/persister_courier.go:147-166 | persistence/sql/persister_courier.go:168-186 | persistence/sql/persister_login.go:71-90 | persistence/sql/persister_session.go:326-345 | persistence/sql/persister_session.go:392-411 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) persistence/sql/persister_session.go:652— persistence/sql/persister_session.go:652-669 | persistence/sql/persister_session.go:672-689 | persistence/sql/persister_session.go:694-707 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) persistence/sql/persister_continuity.go:48— persistence/sql/persister_continuity.go:48-57 | persistence/sql/persister_courier.go:188-201 | persistence/sql/persister_recovery.go:36-46 | persistence/sql/persister_registration.go:39-50 | persistence/sql/persister_settings.go:33-50 | persistence/sql/persister_verification.go:35-45 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 15+ corresponding lines) · ×1
Edited copies of one member (7 members, 15+ corresponding lines) persistence/sql/persister_continuity.go:74— persistence/sql/persister_continuity.go:74-88 | persistence/sql/persister_login.go:92-106 | persistence/sql/persister_recovery.go:132-146 | persistence/sql/persister_registration.go:52-66 | persistence/sql/persister_session.go:709-724 | persistence/sql/persister_settings.go:62-76 | persistence/sql/persister_verification.go:131-145 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) selfservice/flow/request.go:88— selfservice/flow/request.go:88-107 | selfservice/strategy/code/strategy_recovery.go:881-900 | selfservice/strategy/code/strategy_verification.go:44-63 | selfservice/strategy/link/strategy_verification.go:56-75 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 12+ corresponding lines) · ×1
Edited copies of one member (7 members, 12+ corresponding lines) selfservice/hook/web_hook.go:141— selfservice/hook/web_hook.go:141-153 | selfservice/hook/web_hook.go:167-178 | selfservice/hook/web_hook.go:192-203 | selfservice/hook/web_hook.go:217-232 | selfservice/hook/web_hook.go:234-253 | selfservice/hook/web_hook.go:268-283 | selfservice/hook/web_hook.go:285-300 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) selfservice/hook/web_hook.go:129— selfservice/hook/web_hook.go:129-139 | selfservice/hook/web_hook.go:155-165 | selfservice/hook/web_hook.go:205-215 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) selfservice/strategy/passkey/passkey_registration.go:73— selfservice/strategy/passkey/passkey_registration.go:73-88 | selfservice/strategy/password/registration.go:70-83 | selfservice/strategy/profile/registration.go:330-341 | REDACTED:75-90 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 7+ corresponding lines) · ×1
Edited copies of one member (6 members, 7+ corresponding lines) persistence/sql/persister_login.go:32— persistence/sql/persister_login.go:32-40 | persistence/sql/persister_pending_traits_change.go:75-81 | persistence/sql/persister_recovery.go:48-55 | persistence/sql/persister_registration.go:29-37 | persistence/sql/persister_settings.go:52-60 | persistence/sql/persister_verification.go:47-54 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) selfservice/strategy/code/strategy_recovery.go:845— selfservice/strategy/code/strategy_recovery.go:845-864 | selfservice/strategy/link/strategy_recovery.go:515-530 | selfservice/strategy/link/strategy_verification.go:78-92 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 4+ corresponding lines) · ×1
Edited copies of one member (8 members, 4+ corresponding lines) courier/template/email/authenticator_key_added.go:36— courier/template/email/authenticator_key_added.go:36-39 | courier/template/email/recovery_invalid.go:35-39 | courier/template/email/recovery_valid.go:38-42 | courier/template/email/verifiable_address_changed.go:36-39 | courier/template/email/verification_code_invalid.go:35-47 | courier/template/email/verification_code_valid.go:40-52 | courier/template/email/verification_invalid.go:35-39 | courier/template/email/verification_valid.go:39-43 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) courier/template/email/login_code_valid.go:41— courier/template/email/login_code_valid.go:41-45 | courier/template/email/recovery_code_valid.go:40-44 | courier/template/email/registration_code_valid.go:41-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 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) persistence/sql/persister_login_code.go:84— persistence/sql/persister_login_code.go:84-89 | persistence/sql/persister_recovery_code.go:80-85 | persistence/sql/persister_registration_code.go:72-77 | persistence/sql/persister_verification_code.go:76-81 — 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 (5 members, 9+ corresponding lines) · ×1
Edited copies of one member (5 members, 9+ corresponding lines) selfservice/strategy/oidc/provider_amazon.go:65— selfservice/strategy/oidc/provider_amazon.go:65-73 | selfservice/strategy/oidc/provider_github.go:47-55 | selfservice/strategy/oidc/provider_github_app.go:42-50 | selfservice/strategy/oidc/provider_linkedin.go:87-95 | selfservice/strategy/oidc/provider_spotify.go:48-56 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) courier/template/email/login_code_valid.go:47— courier/template/email/login_code_valid.go:47-49 | courier/template/email/recovery_code_invalid.go:44-46 | courier/template/email/recovery_code_valid.go:46-48 | courier/template/email/registration_code_valid.go:47-49 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) selfservice/strategy/code/code_verification.go:18— selfservice/strategy/code/code_verification.go:18-53 | selfservice/strategy/link/token_verification.go:21-53 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (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.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) selfservice/strategy/code/code_sender.go:34— selfservice/strategy/code/code_sender.go:34-64 | selfservice/strategy/link/sender.go:27-53 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) cmd/identities/delete.go:16— cmd/identities/delete.go:16-25 | cmd/identities/get.go:25-34 | cmd/identities/import.go:19-28 | cmd/identities/validate.go:27-37 — 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 (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) selfservice/strategy/idfirst/strategy_login.go:34— selfservice/strategy/idfirst/strategy_login.go:34-43 | selfservice/strategy/lookup/login.go:61-70 | selfservice/strategy/passkey/passkey_login.go:129-138 | selfservice/strategy/totp/login.go:60-69 | selfservice/strategy/webauthn/login.go:113-122 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) text/message_login.go:122— text/message_login.go:122-132 | text/message_registration.go:21-31 | text/message_settings.go:149-158 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) oryx/proxy/proxy.go:293— oryx/proxy/proxy.go:293-296 | selfservice/hook/web_hook.go:549-552 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) selfservice/flow/login/organizations.go:15— selfservice/flow/login/organizations.go:15-18 | selfservice/flow/registration/oragnizations.go:12-15 | selfservice/flow/settings/organizations.go:19-22 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
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.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) pkg/testhelpers/selfservice_login.go:316— pkg/testhelpers/selfservice_login.go:316-318 | pkg/testhelpers/selfservice_registration.go:163-165 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (31 lines × 3) selfservice/strategy/passkey/passkey_strategy.go:31— selfservice/strategy/passkey/passkey_strategy.go:31-61 | selfservice/strategy/totp/strategy.go:39-69 | selfservice/strategy/webauthn/strategy.go:37-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_strategy.go:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 4) selfservice/strategy/lookup/strategy.go:45— selfservice/strategy/lookup/strategy.go:45-74 | selfservice/strategy/passkey/passkey_strategy.go:36-65 | selfservice/strategy/totp/strategy.go:44-73 | selfservice/strategy/webauthn/strategy.go:42-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (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 (25 lines × 2) persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:176— persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:176-200 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:213-237 — 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/migrations/go/20251105000000000000_identity_id_not_null_fks.go:176` 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 (20 lines × 2) oryx/sqlxx/batch/create.go:146— oryx/sqlxx/batch/create.go:146-165 | persistence/sql/batch/create.go:176-195 — before extracting anything, compare `oryx/sqlxx/batch/create.go` and `persistence/sql/batch/create.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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/batch/create.go:146` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) cmd/daemon/serve.go:118— cmd/daemon/serve.go:118-133 | cmd/daemon/serve.go:203-219 — 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 `cmd/daemon/serve.go:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–17 lines × 2) request/builder.go:140— request/builder.go:140-156 | request/builder.go:178-191 — 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 `request/builder.go:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 3) selfservice/strategy/code/strategy_verification.go:48— selfservice/strategy/code/strategy_verification.go:48-63 | selfservice/strategy/link/strategy_recovery.go:545-560 | selfservice/strategy/link/strategy_verification.go:60-75 — `selfservice/strategy/code/strategy_verification.go` and `selfservice/strategy/link/strategy_verification.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/code/strategy_verification.go:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13–16 lines × 2) selfservice/strategy/oidc/provider_generic_oidc.go:106— selfservice/strategy/oidc/provider_generic_oidc.go:106-118 | selfservice/strategy/oidc/provider_jackson.go:93-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/provider_generic_oidc.go:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14–15 lines × 2) persistence/sql/persister_recovery.go:59— persistence/sql/persister_recovery.go:59-73 | persistence/sql/persister_verification.go:58-71 — before extracting anything, compare `persistence/sql/persister_recovery.go` and `persistence/sql/persister_verification.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `persistence/sql/persister_recovery.go:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10–15 lines × 2) selfservice/flow/recovery/error.go:155— selfservice/flow/recovery/error.go:155-164 | selfservice/flow/recovery/handler.go:459-473 — 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 `selfservice/flow/recovery/error.go:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) selfservice/flow/login/flow.go:197— selfservice/flow/login/flow.go:197-209 | selfservice/flow/recovery/flow.go:138-150 | selfservice/flow/registration/flow.go:154-166 | selfservice/flow/settings/flow.go:150-162 | selfservice/flow/verification/flow.go:142-154 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/flow/login/flow.go:196` calls `SelfServiceFlowLoginRequestLifespan`, `Context` and `selfservice/flow/recovery/flow.go:137` 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 × 3) selfservice/flow/registration/flow.go:296— selfservice/flow/registration/flow.go:296-308 | selfservice/flow/settings/flow.go:249-261 | selfservice/flow/verification/flow.go:348-360 — `selfservice/flow/registration/flow.go` and `selfservice/flow/settings/flow.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (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 (2–13 lines × 4) selfservice/strategy/lookup/settings.go:119— selfservice/strategy/lookup/settings.go:119-120 | selfservice/strategy/passkey/passkey_settings.go:179-191 | selfservice/strategy/totp/settings.go:103-104 | selfservice/strategy/webauthn/settings.go:116-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/settings.go:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `selfservice/strategy/passkey/passkey_settings.go:191` calls `SettingsStrategyID` and `selfservice/strategy/totp/settings.go:104` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 4) selfservice/strategy/passkey/passkey_settings.go:417— selfservice/strategy/passkey/passkey_settings.go:417-428 | selfservice/strategy/password/settings.go:108-119 | selfservice/strategy/totp/settings.go:121-132 | selfservice/strategy/webauthn/settings.go:147-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 3) x/events/events.go:334— x/events/events.go:334-345 | x/events/events.go:352-363 | x/events/events.go:370-381 — 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 `x/events/events.go:334` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 4) selfservice/strategy/passkey/passkey_settings.go:434— selfservice/strategy/passkey/passkey_settings.go:434-444 | selfservice/strategy/password/settings.go:232-242 | selfservice/strategy/totp/settings.go:306-316 | selfservice/strategy/webauthn/settings.go:418-428 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:434` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–11 lines × 3) selfservice/strategy/idfirst/strategy_login.go:177— selfservice/strategy/idfirst/strategy_login.go:177-184 | selfservice/strategy/password/login.go:185-192 | selfservice/strategy/webauthn/login.go:357-367 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/webauthn/login.go:357` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/strategy/idfirst/strategy_login.go:173` calls `PopulateLoginMethodIdentifierFirstIdentification`, `SetCSRF`, `GenerateCSRFToken` and `selfservice/strategy/webauthn/login.go:354` 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 × 3) selfservice/strategy/passkey/passkey_login.go:386— selfservice/strategy/passkey/passkey_login.go:386-396 | selfservice/strategy/passkey/passkey_login.go:417-427 | selfservice/strategy/passkey/passkey_login.go:453-463 — 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 `selfservice/strategy/passkey/passkey_login.go:386` 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–10 lines × 2) selfservice/strategy/code/code_sender.go:387— selfservice/strategy/code/code_sender.go:387-395 | selfservice/strategy/code/strategy_verification.go:480-489 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–10 lines × 2) selfservice/strategy/code/strategy.go:305— selfservice/strategy/code/strategy.go:305-311 | selfservice/strategy/code/strategy.go:332-341 — 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–9 lines × 4) selfservice/strategy/oidc/provider_auth0.go:59— selfservice/strategy/oidc/provider_auth0.go:59-67 | selfservice/strategy/oidc/provider_gitlab.go:58-65 | selfservice/strategy/oidc/provider_netid.go:63-70 | selfservice/strategy/oidc/provider_salesforce.go:59-67 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 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 (6–8 lines × 2) selfservice/flow/login/hook.go:154— selfservice/flow/login/hook.go:154-161 | selfservice/flow/registration/hook.go:230-235 — 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 `selfservice/flow/login/hook.go:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/flow/registration/hook.go:226` calls `WithoutCancel`, `WithContext` and `selfservice/flow/login/hook.go:152` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 2) selfservice/strategy/oidc/strategy_registration.go:384— selfservice/strategy/oidc/strategy_registration.go:384-390 | selfservice/strategy/oidc/strategy_settings.go:515-522 — 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 `selfservice/strategy/oidc/strategy_registration.go:384` 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 (7 lines × 4) selfservice/strategy/oidc/provider_dingtalk.go:99— selfservice/strategy/oidc/provider_dingtalk.go:99-105 | selfservice/strategy/oidc/provider_dingtalk.go:142-148 | selfservice/strategy/oidc/provider_facebook.go:94-100 | selfservice/strategy/oidc/provider_yandex.go:78-84 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/oidc/provider_dingtalk.go:99` 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 (46 lines × 2) pkg/registrationhelpers/helpers.go:291— pkg/registrationhelpers/helpers.go:291-336 | pkg/registrationhelpers/helpers.go:340-385 — 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 `pkg/registrationhelpers/helpers.go:291` 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 × 6) selfservice/strategy/lookup/settings.go:152— selfservice/strategy/lookup/settings.go:152-157 | selfservice/strategy/passkey/passkey_settings.go:255-260 | selfservice/strategy/password/settings.go:154-159 | selfservice/strategy/profile/strategy.go:164-169 | selfservice/strategy/totp/settings.go:136-141 | selfservice/strategy/webauthn/settings.go:167-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/lookup/settings.go:152` 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 (3–6 lines × 5) selfservice/strategy/code/strategy_recovery.go:63— selfservice/strategy/code/strategy_recovery.go:63-65 | selfservice/strategy/code/strategy_recovery.go:509-514 | selfservice/strategy/code/strategy_recovery.go:576-581 | selfservice/strategy/code/strategy_recovery.go:668-670 | selfservice/strategy/code/strategy_recovery.go:793-795 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/code/strategy_recovery.go:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/strategy/code/strategy_recovery.go:506` calls `RecoveryFlowPersister`, `UpdateRecoveryFlow`, `Context` and `selfservice/strategy/code/strategy_recovery.go:575` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 12) selfservice/strategy/oidc/provider_auth0.go:97— selfservice/strategy/oidc/provider_auth0.go:97-104 | selfservice/strategy/oidc/provider_dingtalk.go:96-103 | selfservice/strategy/oidc/provider_dingtalk.go:139-146 | selfservice/strategy/oidc/provider_facebook.go:91-98 | selfservice/strategy/oidc/provider_gitlab.go:93-100 | selfservice/strategy/oidc/provider_lark.go:91-98 | selfservice/strategy/oidc/provider_netid.go:87-94 | selfservice/strategy/oidc/provider_patreon.go:97-104 | selfservice/strategy/oidc/provider_salesforce.go:97-104 | selfservice/strategy/oidc/provider_vk.go:77-84 | selfservice/strategy/oidc/provider_x.go:120-127 | selfservice/strategy/oidc/provider_yandex.go:75-82 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `selfservice/strategy/oidc/provider_auth0.go:94` calls `Add` and `selfservice/strategy/oidc/provider_facebook.go:88` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 5) selfservice/strategy/passkey/passkey_settings.go:434— selfservice/strategy/passkey/passkey_settings.go:434-438 | selfservice/strategy/password/settings.go:232-236 | selfservice/strategy/profile/strategy.go:256-263 | selfservice/strategy/totp/settings.go:306-310 | selfservice/strategy/webauthn/settings.go:418-422 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/passkey/passkey_settings.go:434` 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 (3–5 lines × 6) selfservice/strategy/idfirst/strategy_login.go:66— selfservice/strategy/idfirst/strategy_login.go:66-68 | selfservice/strategy/password/login.go:71-73 | selfservice/strategy/password/registration.go:103-107 | selfservice/strategy/profile/registration.go:267-269 | selfservice/strategy/totp/login.go:114-116 | REDACTED:111-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `selfservice/strategy/idfirst/strategy_login.go:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 4) selfservice/flow/login/flow.go:300— selfservice/flow/login/flow.go:300-308 | selfservice/flow/recovery/flow.go:301-309 | selfservice/flow/registration/flow.go:259-267 | selfservice/flow/settings/flow.go:224-232 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (7 lines × 6) selfservice/flow/login/hook.go:77— selfservice/flow/login/hook.go:77-83 | selfservice/flow/recovery/hook.go:43-49 | selfservice/flow/registration/hook.go:59-65 | selfservice/flow/settings/hook.go:124-130 | selfservice/flow/settings/hook.go:132-138 | selfservice/flow/verification/hook.go:43-49 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 4) selfservice/flow/login/hook.go:393— selfservice/flow/login/hook.go:393-405 | selfservice/flow/recovery/hook.go:122-134 | selfservice/flow/registration/hook.go:384-396 | selfservice/flow/verification/hook.go:86-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (34 lines × 3) persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:92— persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:92-125 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:188-222 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:225-258 — 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/migrations/go/20251105000000000000_identity_id_not_null_fks.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.
Duplicated block (22 lines × 6) persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:29— persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:29-51 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:67-89 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:104-125 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:163-185 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:200-222 | persistence/sql/migrations/go/20251105000000000000_identity_id_not_null_fks.go:237-258 — all 6 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/migrations/go/20251105000000000000_identity_id_not_null_fks.go:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) selfservice/strategy/oidc/provider_auth0.go:48— selfservice/strategy/oidc/provider_auth0.go:48-55 | selfservice/strategy/oidc/provider_gitlab.go:47-54 | selfservice/strategy/oidc/provider_salesforce.go:48-55 — before extracting anything, compare `selfservice/strategy/oidc/provider_auth0.go` and `selfservice/strategy/oidc/provider_salesforce.go` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 108 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.
End-of-life runtime: Node.js 16 .nvmrc:1— .nvmrc declares Node.js 16 as this project's version file, and Node.js 16, support ended 2023-09-11. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-09-11 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
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.
Duplicated block (31 lines × 3 locations) x/webauthnx/js/webauthn.js:103— x/webauthnx/js/webauthn.js:103 · x/webauthnx/js/webauthn.js:338 · x/webauthnx/js/webauthn.js:389 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 3 locations) x/webauthnx/js/webauthn.js:62— x/webauthnx/js/webauthn.js:62 · x/webauthnx/js/webauthn.js:194 · x/webauthnx/js/webauthn.js:265 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 2 locations) x/webauthnx/js/webauthn.js:31— x/webauthnx/js/webauthn.js:31 · x/webauthnx/js/webauthn.js:84 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) x/webauthnx/js/webauthn.js:165— x/webauthnx/js/webauthn.js:165 · x/webauthnx/js/webauthn.js:231 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function __oryPasskeyLoginAutocompleteInit (cyclomatic 12, cognitive 9) x/webauthnx/js/webauthn.js:140— __oryPasskeyLoginAutocompleteInit has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function __oryPasskeyRegistration (cyclomatic 11, cognitive 12) x/webauthnx/js/webauthn.js:300— __oryPasskeyRegistration has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Unused dependency 'json-schema-to-typescript' test/e2e/package.json:31— Declared in test/e2e/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
README/code drift pkg/client-go/README.md:82— pkg/client-go/README.md links to `docs/CourierAPI.md#getcouriermessage`, but `pkg/client-go/docs/CourierAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:84— pkg/client-go/README.md links to `docs/FrontendAPI.md#createbrowserloginflow`, but `pkg/client-go/docs/FrontendAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:118— pkg/client-go/README.md links to `docs/IdentityAPI.md#batchpatchidentities`, but `pkg/client-go/docs/IdentityAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:139— pkg/client-go/README.md links to `docs/MetadataAPI.md#getversion`, but `pkg/client-go/docs/MetadataAPI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:146— pkg/client-go/README.md links to `docs/AdminIdentityImportCredentialsLookupSecret.md`, but `pkg/client-go/docs/AdminIdentityImportCredentialsLookupSecret.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:147— pkg/client-go/README.md links to `docs/AdminIdentityImportCredentialsLookupSecretConfig.md`, but `pkg/client-go/docs/AdminIdentityImportCredentialsLookupSecretConfig.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:148— pkg/client-go/README.md links to `docs/AuthenticatorAssuranceLevel.md`, but `pkg/client-go/docs/AuthenticatorAssuranceLevel.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:149— pkg/client-go/README.md links to `docs/BatchPatchIdentitiesResponse.md`, but `pkg/client-go/docs/BatchPatchIdentitiesResponse.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:150— pkg/client-go/README.md links to `docs/ConsistencyRequestParameters.md`, but `pkg/client-go/docs/ConsistencyRequestParameters.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:151— pkg/client-go/README.md links to `docs/ContinueWith.md`, but `pkg/client-go/docs/ContinueWith.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:152— pkg/client-go/README.md links to `docs/ContinueWithDeviceAuthnPinEntryUi.md`, but `pkg/client-go/docs/ContinueWithDeviceAuthnPinEntryUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:153— pkg/client-go/README.md links to `docs/ContinueWithDeviceAuthnPinEntryUiData.md`, but `pkg/client-go/docs/ContinueWithDeviceAuthnPinEntryUiData.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:154— pkg/client-go/README.md links to `docs/ContinueWithRecoveryUi.md`, but `pkg/client-go/docs/ContinueWithRecoveryUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:155— pkg/client-go/README.md links to `docs/ContinueWithRecoveryUiFlow.md`, but `pkg/client-go/docs/ContinueWithRecoveryUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:156— pkg/client-go/README.md links to `docs/ContinueWithRedirectBrowserTo.md`, but `pkg/client-go/docs/ContinueWithRedirectBrowserTo.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:157— pkg/client-go/README.md links to `docs/ContinueWithSetOrySessionToken.md`, but `pkg/client-go/docs/ContinueWithSetOrySessionToken.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:158— pkg/client-go/README.md links to `docs/ContinueWithSettingsUi.md`, but `pkg/client-go/docs/ContinueWithSettingsUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:159— pkg/client-go/README.md links to `docs/ContinueWithSettingsUiFlow.md`, but `pkg/client-go/docs/ContinueWithSettingsUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:160— pkg/client-go/README.md links to `docs/ContinueWithVerificationUi.md`, but `pkg/client-go/docs/ContinueWithVerificationUi.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:161— pkg/client-go/README.md links to `docs/ContinueWithVerificationUiFlow.md`, but `pkg/client-go/docs/ContinueWithVerificationUiFlow.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:162— pkg/client-go/README.md links to `docs/CourierMessageStatus.md`, but `pkg/client-go/docs/CourierMessageStatus.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:163— pkg/client-go/README.md links to `docs/CourierMessageType.md`, but `pkg/client-go/docs/CourierMessageType.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:164— pkg/client-go/README.md links to `docs/CreateFedcmFlowResponse.md`, but `pkg/client-go/docs/CreateFedcmFlowResponse.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:165— pkg/client-go/README.md links to `docs/CreateIdentityBody.md`, but `pkg/client-go/docs/CreateIdentityBody.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift pkg/client-go/README.md:166— pkg/client-go/README.md links to `docs/CreateRecoveryCodeForIdentityBody.md`, but `pkg/client-go/docs/CreateRecoveryCodeForIdentityBody.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Orphaned file courier/template/testhelpers/testhelpers.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 selfservice/strategy/oidc/provider_dingtalk.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 selfservice/strategy/oidc/provider_salesforce.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 selfservice/strategy/oidc/provider_facebook.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 selfservice/flow/state.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 oryx/urlx/extract.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 selfservice/flow/verification/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 selfservice/strategy/oidc/provider_patreon.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 selfservice/strategy/oidc/provider_lark.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 persistence/sql/persister_login_code.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 selfservice/strategy/oidc/provider_yandex.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 persistence/sql/persister_verification_code.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 persistence/sql/persister_recovery_code.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 persistence/sql/persister_registration_code.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 selfservice/strategy/oidc/provider_github_app.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 selfservice/strategy/code/code_registration.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 selfservice/strategy/oidc/provider_discord.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 embedx/embedx.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate 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 selfservice/strategy/idfirst/strategy_login.go:128— `!didPopulate && !s.d.Config().SecurityAccountEnumerationMitigate(ctx)` appears character-identically in 2 files — selfservice/strategy/idfirst/strategy_login.go, selfservice/strategy/profile/registration.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 selfservice/strategy/oidc/strategy_login.go:503— `!strings.EqualFold(strings.ToLower(p.Method), s.SettingsStrategyID()) && p.Method != ""` appears character-identically in 2 files — selfservice/strategy/oidc/strategy_login.go, selfservice/strategy/oidc/strategy_registration.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 selfservice/flow/login/handler.go:764— `ar.Type == flow.TypeBrowser && !nosurf.VerifyToken(h.d.GenerateCSRFToken(r), ar.CSRFToken)` appears character-identically in 2 files — selfservice/flow/login/handler.go, selfservice/flow/registration/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 selfservice/strategy/passkey/passkey_login.go:451— `count > 0 || s.d.Config().SecurityAccountEnumerationMitigate(ctx)` appears character-identically in 2 files — selfservice/strategy/passkey/passkey_login.go, selfservice/strategy/password/login.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 selfservice/hook/verify_new_address.go:113— `err != nil && !errors.Is(err, sqlcon.ErrNoRows())` appears character-identically in 4 files — selfservice/hook/verify_new_address.go, selfservice/strategy/code/strategy_recovery.go, selfservice/strategy/passkey/passkey_settings.go, selfservice/strategy/webauthn/settings.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 selfservice/strategy/code/strategy_verification.go:339— `errors.Is(applyErr, identity.ErrConcurrentModification) || errors.Is(applyErr, settings.ErrPendingTraitsChangeSessionInvalid)` appears character-identically in 2 files — selfservice/strategy/code/strategy_verification.go, selfservice/strategy/link/strategy_verification.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 selfservice/strategy/code/code_sender.go:442— `f.OAuth2LoginChallenge != "" && f.HydraLoginRequest == nil` appears character-identically in 2 files — selfservice/strategy/code/code_sender.go, selfservice/strategy/link/sender.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 selfservice/flow/login/error.go:129— `f.Type == flow.TypeAPI || x.IsJSONRequest(r)` appears character-identically in 4 files — selfservice/flow/login/error.go, selfservice/flow/registration/error.go, selfservice/flow/settings/error.go, selfservice/flow/settings/strategy_helper.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 selfservice/flow/login/error.go:153— `f.Type == flow.TypeBrowser && !x.IsJSONRequest(r)` appears character-identically in 7 files — selfservice/flow/login/error.go, selfservice/flow/recovery/error.go, selfservice/flow/recovery/handler.go, selfservice/flow/registration/error.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 identity/extension_recovery.go:94— `has.Via == needle.Via && x.GracefulNormalization(has.Value) == normalizedNeedle` appears character-identically in 2 files — identity/extension_recovery.go, identity/extension_verification.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 selfservice/strategy/passkey/passkey_login.go:171— `len(p.Login) > 0 || p.Method == s.SettingsStrategyID()` appears character-identically in 2 files — selfservice/strategy/passkey/passkey_login.go, selfservice/strategy/webauthn/login.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 selfservice/flow/recovery/error.go:182— `rr.Type == flow.TypeAPI || x.IsJSONRequest(r)` appears character-identically in 3 files — selfservice/flow/recovery/error.go, selfservice/flow/settings/error.go, selfservice/flow/verification/error.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 selfservice/strategy/oidc/strategy_login.go:133— `verifiable.Via == verified.Via && verifiable.Value == verified.Value` appears character-identically in 2 files — selfservice/strategy/oidc/strategy_login.go, selfservice/strategy/oidc/strategy_registration.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.
Fat interface: CourierConfigs (24 methods) driver/config/config.go:318— `CourierConfigs` declares 24 methods: `CourierTemplatesRoot`, `CourierTemplatesVerificationInvalid`, `CourierTemplatesVerificationValid`, `CourierTemplatesRecoveryInvalid`, `CourierTemplatesRecoveryValid`, `CourierTemplatesRecoveryCodeInvalid`, `CourierTemplatesRecoveryCodeValid`, `CourierTemplatesVerificationCodeInvalid`, `CourierTemplatesVerificationCodeValid`, `CourierTemplatesLoginCodeValid`, `CourierTemplatesRegistrationCodeValid`, `CourierSMSTemplatesVerificationCodeValid`, `CourierSMSTemplatesRecoveryCodeValid`, `CourierSMSTemplatesLoginCodeValid`, `CourierSMSTemplatesRegistrationCodeValid`, `CourierTemplatesVerifiableAddressChanged`, `CourierSMSTemplatesVerifiableAddressChanged`, `CourierTemplatesAuthenticatorKeyAdded`, `CourierSMSTemplatesAuthenticatorKeyAdded`, `CourierMessageRetries`, `CourierWorkerPullCount`, `CourierWorkerPullWait`, `CourierChannels`, `ClientSMTPNoPrivateIPRanges`. 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: Registry (16 methods) driver/registry.go:50— `Registry` declares 16 methods: `Init`, `SetLogger`, `SetJSONNetVMProvider`, `Clock`, `WithCSRFHandler`, `WithCSRFTokenGenerator`, `HealthHandler`, `CookieManager`, `ContinuityCookieManager`, `RegisterPublicRoutes`, `RegisterAdminRoutes`, `Tracer`, `SetTracer`, `CourierConfig`, `SetConfig`, `SetContextualizer`. 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: PrivilegedPool (17 methods) identity/pool.go:186— `PrivilegedPool` declares 17 methods: `FindByCredentialsIdentifier`, `DeleteIdentity`, `DeleteIdentities`, `UpdateVerifiableAddress`, `CreateIdentity`, `CreateIdentities`, `UpdateIdentity`, `UpdateIdentityColumns`, `UpdateCredentialsConfig`, `GetIdentityConfidential`, `ListVerifiableAddresses`, `ListRecoveryAddresses`, `HydrateIdentityAssociations`, `InjectTraitsSchemaURL`, `FindIdentityByCredentialIdentifier`, `FindIdentityByWebauthnUserHandle`, `FindIdentityByExternalID`. 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: Persister (21 methods) session/persistence.go:33— `Persister` declares 21 methods: `GetConnection`, `GetSession`, `ListSessions`, `ListSessionsByIdentity`, `UpsertSession`, `ExtendSession`, `DeleteSession`, `DeleteSessionsByIdentity`, `GetSessionByToken`, `DeleteExpiredSessions`, `DeleteSessionByToken`, `RevokeSessionByToken`, `RevokeSessionById`, `RevokeSession`, `RevokeSessionsIdentityExcept`, `RevokeSessionsByIdentities`, `RevokeSessionsByIDs`, `RevokeAllSessions`, `DeleteSessionsByIdentities`, `DeleteSessionsByIDs`, `DeleteAllSessions`. 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.
ED3 · Event naming· Event not named in past tense · ×3
Event not named in past tense: ErrorEvent oryx/watcherx/event.go:24— `ErrorEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe.
Event not named in past tense: ChangeEvent oryx/watcherx/event.go:28— `ChangeEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe.
Event not named in past tense: RemoveEvent oryx/watcherx/event.go:32— `RemoveEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion package.json:1— `(repository root)` (63562 LoC, 746 module-visible types across 96 directories) overshoots its size bounds. 2 of 3 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— `oryx` (19995 LoC, 288 module-visible types across 78 directories) overshoots its size bounds. 2 of 3 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.
Silent fallback default on error selfservice/strategy/code/code_sender.go:523— `requestURLDomain` 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.
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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: identity/validator.go, selfservice/flow/login/test_handler.go, schema/prevalidate.go, x/normalize.go, schema/loader.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 322 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; 322 of the 706 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/proxy/proxy.go, cmd/identities/get.go, oryx/cmdx/printing.go, oryx/pagination/paginationplanner/planner.go, oryx/sqlxx/sqlxx.go, selfservice/strategy/oidc/provider_jackson.go.
No ADRs found main.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 `main.go` makes this repository a deployable product (line 5).
D21 · Naming Consistency· `writeMessagesJson` spells `Json` where 84 names in the project spell it `JSON` · ×1
`writeMessagesJson` spells `Json` where 84 names in the project spell it `JSON` cmd/clidoc/main.go:318— 84 of 86 names in project github.com/ory/kratos spell the token `JSON` (84 of 86; unit: names in project github.com/ory/kratos containing `JSON`). Peers: MessageStatus.MarshalJSON (courier/message.go:78); MessageStatus.UnmarshalJSON (courier/message.go:85); MessageType.MarshalJSON (courier/message.go:148); MessageType.UnmarshalJSON (courier/message.go:155); AuthenticatorKeyAdded.MarshalJSON (courier/template/email/authenticator_key_added.go:49). Rename to `writeMessagesJSON`. [rule N6]
D21 · Naming Consistency· `newHttpChannel` spells `Http` where 31 names in the project spell it `HTTP` · ×1
`newHttpChannel` spells `Http` where 31 names in the project spell it `HTTP` courier/http_channel.go:41— 31 of 33 names in project github.com/ory/kratos spell the token `HTTP` (31 of 33; unit: names in project github.com/ory/kratos containing `HTTP`). Peers: config.ViperKeyCourierHTTPRequestConfig (driver/config/config.go:77); config.ViperKeyClientHTTPNoPrivateIPRanges (driver/config/config.go:210); config.ViperKeyClientHTTPPrivateIPExceptionURLs (driver/config/config.go:211); Config.ClientHTTPNoPrivateIPRanges (driver/config/config.go:681); Config.ClientHTTPPrivateIPExceptionURLs (driver/config/config.go:685). Rename to `newHTTPChannel`. [rule N6]
D21 · Naming Consistency· `formatJsonErrors` spells `Json` where 84 names in the project spell it `JSON` · ×1
`formatJsonErrors` spells `Json` where 84 names in the project spell it `JSON` driver/config/config.go:528— 84 of 86 names in project github.com/ory/kratos spell the token `JSON` (84 of 86; unit: names in project github.com/ory/kratos containing `JSON`). Peers: MessageStatus.MarshalJSON (courier/message.go:78); MessageStatus.UnmarshalJSON (courier/message.go:85); MessageType.MarshalJSON (courier/message.go:148); MessageType.UnmarshalJSON (courier/message.go:155); AuthenticatorKeyAdded.MarshalJSON (courier/template/email/authenticator_key_added.go:49). Rename to `formatJSONErrors`. [rule N6]
D21 · Naming Consistency· `ToUiNodeGroup` spells `Ui` where 58 names in the project spell it `UI` · ×1
`ToUiNodeGroup` spells `Ui` where 58 names in the project spell it `UI` identity/credentials.go:108— 58 of 59 names in project github.com/ory/kratos spell the token `UI` (58 of 59; unit: names in project github.com/ory/kratos containing `UI`). Peers: config.ViperKeyUseLegacyShowVerificationUI (driver/config/config.go:109); config.ViperKeySelfServiceRegistrationUI (driver/config/config.go:126); config.ViperKeySelfServiceLoginUI (driver/config/config.go:130); config.ViperKeySelfServiceErrorUI (driver/config/config.go:137); config.ViperKeySelfServiceRecoveryUI (driver/config/config.go:150). Rename to `ToUINodeGroup`. [rule N6]
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]
D21 · Naming Consistency· `FormMethodIsPOST` spells `POST` where 64 names in the project spell it `Post` · ×1
`FormMethodIsPOST` spells `POST` where 64 names in the project spell it `Post` pkg/registrationhelpers/helpers.go:79— 64 of 65 names in project github.com/ory/kratos spell the token `Post` (64 of 65; unit: names in project github.com/ory/kratos containing `Post`). Peers: RegistryDefault.PostRegistrationPostPersistHooks (driver/registry_default_registration.go:24); RegistryDefault.PostSettingsPostPersistHooks (driver/registry_default_settings.go:22); hydra.FakePostLoginURL (hydra/fake.go:17); testhelpers.NewPostRequest (pkg/testhelpers/http.go:55); testhelpers.HTTPPostForm (pkg/testhelpers/http.go:115). Rename to `FormMethodIsPost`. [rule N6]
D21 · Naming Consistency· `isApi` spells `Api` where 46 names in the project spell it `API` · ×1
`isApi` spells `Api` where 46 names in the project spell it `API` REDACTED:84— 46 of 47 names in project github.com/ory/kratos spell the token `API` (46 of 47; unit: names in project github.com/ory/kratos containing `API`). Peers: Config.DisableAPIFlowEnforcement (driver/config/config.go:673); DefaultHydra.getAdminAPIClient (hydra/hydra.go:74); testhelpers.NewPostRequest(isAPI) (pkg/testhelpers/http.go:55); testhelpers.SelfServiceMakeLoginPostHookRequest(asAPI) (pkg/testhelpers/selfservice.go:184); testhelpers.SelfServiceMakeRegistrationPostHookRequest(asAPI) (pkg/testhelpers/selfservice.go:204). Rename to `isAPI`. [rule N6]
D21 · Naming Consistency· `TeamId` spells `Id` where 377 names in the project spell it `ID` · ×1
`TeamId` spells `Id` where 377 names in the project spell it `ID` selfservice/strategy/oidc/provider_config.go:106— 377 of 383 names in project github.com/ory/kratos spell the token `ID` (377 of 383; unit: names in project github.com/ory/kratos containing `ID`). Peers: identities.FlagExternalID (cmd/identities/get.go:22); Container.IdentityID (continuity/container.go:23); getCourierMessage.MessageID (courier/handler.go:176); Message.GetID (courier/message.go:226); MessageDispatch.MessageID (courier/message_dispatch.go:33). Rename to `TeamID`. [rule N6]
D21 · Naming Consistency· `PrivateKeyId` spells `Id` where 377 names in the project spell it `ID` · ×1
`PrivateKeyId` spells `Id` where 377 names in the project spell it `ID` selfservice/strategy/oidc/provider_config.go:111— 377 of 383 names in project github.com/ory/kratos spell the token `ID` (377 of 383; unit: names in project github.com/ory/kratos containing `ID`). Peers: identities.FlagExternalID (cmd/identities/get.go:22); Container.IdentityID (continuity/container.go:23); getCourierMessage.MessageID (courier/handler.go:176); Message.GetID (courier/message.go:226); MessageDispatch.MessageID (courier/message_dispatch.go:33). Rename to `PrivateKeyID`. [rule N6]
D21 · Naming Consistency· `redirectToGET` spells `GET` where 21 names in the project spell it `Get` · ×1
`redirectToGET` spells `GET` where 21 names in the project spell it `Get` selfservice/strategy/oidc/strategy.go:229— 21 of 22 names in project github.com/ory/kratos spell the token `Get` (21 of 22; unit: names in project github.com/ory/kratos containing `Get`). Peers: identities.NewGetCmd (cmd/identities/get.go:25); identities.NewGetIdentityCmd (cmd/identities/get.go:36); courier.AdminRouteGetMessage (courier/handler.go:25); testhelpers.NewHTTPGetJSONRequest (pkg/testhelpers/http.go:69); testhelpers.NewHTTPGetAJAXRequest (pkg/testhelpers/http.go:78). Rename to `redirectToGet`. [rule N6]
D21 · Naming Consistency· `updateLoginFlowWithTotpMethod` spells `Totp` where 31 names in the project spell it `TOTP` · ×1
`updateLoginFlowWithTotpMethod` spells `Totp` where 31 names in the project spell it `TOTP` selfservice/strategy/totp/login.go:74— 31 of 33 names in project github.com/ory/kratos spell the token `TOTP` (31 of 33; unit: names in project github.com/ory/kratos containing `TOTP`). Peers: config.ViperKeyTOTPIssuer (driver/config/config.go:188); identity.CredentialsTypeTOTP (identity/credentials.go:93); github.com/ory/kratos/identity.CredentialsTOTPConfig (identity/credentials_totp.go:7); github.com/ory/kratos/identity.AdminIdentityImportCredentialsTOTP (identity/handler.go:575); github.com/ory/kratos/identity.AdminIdentityImportCredentialsTOTPConfig (identity/handler.go:583). Rename to `updateLoginFlowWithTOTPMethod`. [rule N6]
D21 · Naming Consistency· `updateSettingsFlowWithTotpMethod` spells `Totp` where 31 names in the project spell it `TOTP` · ×1
`updateSettingsFlowWithTotpMethod` spells `Totp` where 31 names in the project spell it `TOTP` selfservice/strategy/totp/settings.go:47— 31 of 33 names in project github.com/ory/kratos spell the token `TOTP` (31 of 33; unit: names in project github.com/ory/kratos containing `TOTP`). Peers: config.ViperKeyTOTPIssuer (driver/config/config.go:188); identity.CredentialsTypeTOTP (identity/credentials.go:93); github.com/ory/kratos/identity.CredentialsTOTPConfig (identity/credentials_totp.go:7); github.com/ory/kratos/identity.AdminIdentityImportCredentialsTOTP (identity/handler.go:575); github.com/ory/kratos/identity.AdminIdentityImportCredentialsTOTPConfig (identity/handler.go:583). Rename to `updateSettingsFlowWithTOTPMethod`. [rule N6]
D21 · Naming Consistency· `AdminRouteSessionExtendId` spells `Id` where 377 names in the project spell it `ID` · ×1
`AdminRouteSessionExtendId` spells `Id` where 377 names in the project spell it `ID` session/handler.go:82— 377 of 383 names in project github.com/ory/kratos spell the token `ID` (377 of 383; unit: names in project github.com/ory/kratos containing `ID`). Peers: identities.FlagExternalID (cmd/identities/get.go:22); Container.IdentityID (continuity/container.go:23); getCourierMessage.MessageID (courier/handler.go:176); Message.GetID (courier/message.go:226); MessageDispatch.MessageID (courier/message_dispatch.go:33). Rename to `AdminRouteSessionExtendID`. [rule N6]
D21 · Naming Consistency· `RevokeSessionById` spells `Id` where 377 names in the project spell it `ID` · ×1
`RevokeSessionById` spells `Id` where 377 names in the project spell it `ID` session/persistence.go:80— 377 of 383 names in project github.com/ory/kratos spell the token `ID` (377 of 383; unit: names in project github.com/ory/kratos containing `ID`). Peers: identities.FlagExternalID (cmd/identities/get.go:22); Container.IdentityID (continuity/container.go:23); getCourierMessage.MessageID (courier/handler.go:176); Message.GetID (courier/message.go:226); MessageDispatch.MessageID (courier/message_dispatch.go:33). Rename to `RevokeSessionByID`. [rule N6]
D21 · Naming Consistency· `providerId` spells `Id` where 377 names in the project spell it `ID` · ×1
`providerId` spells `Id` where 377 names in the project spell it `ID` text/message_login.go:122— 377 of 383 names in project github.com/ory/kratos spell the token `ID` (377 of 383; unit: names in project github.com/ory/kratos containing `ID`). Peers: identities.FlagExternalID (cmd/identities/get.go:22); Container.IdentityID (continuity/container.go:23); getCourierMessage.MessageID (courier/handler.go:176); Message.GetID (courier/message.go:226); MessageDispatch.MessageID (courier/message_dispatch.go:33). Rename to `providerID`. [rule N6]
D21 · Naming Consistency· `HostedHttpBin` spells `Http` where 31 names in the project spell it `HTTP` · ×1
`HostedHttpBin` spells `Http` where 31 names in the project spell it `HTTP` x/tests.go:20— 31 of 33 names in project github.com/ory/kratos spell the token `HTTP` (31 of 33; unit: names in project github.com/ory/kratos containing `HTTP`). Peers: config.ViperKeyCourierHTTPRequestConfig (driver/config/config.go:77); config.ViperKeyClientHTTPNoPrivateIPRanges (driver/config/config.go:210); config.ViperKeyClientHTTPPrivateIPExceptionURLs (driver/config/config.go:211); Config.ClientHTTPNoPrivateIPRanges (driver/config/config.go:681); Config.ClientHTTPPrivateIPExceptionURLs (driver/config/config.go:685). Rename to `HostedHTTPBin`. [rule N6]
Scattered collaborators — 78 % of calls cross a namespace and only 59 % 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
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 18 of 322 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; 322 of the 706 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: courier/template/testhelpers/testhelpers.go, selfservice/strategy/oidc/provider_dingtalk.go, selfservice/strategy/oidc/provider_salesforce.go, selfservice/strategy/oidc/provider_facebook.go, selfservice/flow/state.go, oryx/urlx/extract.go, selfservice/flow/verification/hook.go, selfservice/strategy/oidc/provider_patreon.go (and 10 more). 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.
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`.
No dependency-update automation package.json:12— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Benchmarks don't track allocations persistence/sql/persister_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.
R7 · Dead Code· Unused module-local declaration 'criPort' · ×1
Unused module-local declaration 'criPort' test/e2e/cypress/plugins/index.js:8— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'ensureRdpPort' · ×1
Unused module-local declaration 'ensureRdpPort' test/e2e/cypress/plugins/index.js:19— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene· Test-only dependency 'yamljs' in production deps · ×1
Test-only dependency 'yamljs' in production deps package.json:14— Only test files import it (first: test/e2e/cypress/support/commands.ts:18) — move it to devDependencies.
No security response headers detected contrib/quickstart/kratos/cloud/Caddyfile:10— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `Caddyfile` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
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/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/bwmarrin/discordgo — `github.com/bwmarrin/discordgo` is required at v0.28.1 in REDACTED, but v0.29.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/bwmarrin/discordgo@v0.29.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-crypt/crypt — `github.com/go-crypt/crypt` is required at v0.2.25 in REDACTED, but v0.14.15 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-crypt/crypt@v0.14.15 && 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.4.2 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-openapi/strfmt — `github.com/go-openapi/strfmt` is required at v0.23.0 in REDACTED, but v0.27.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/strfmt@v0.27.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.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/go-sql-driver/mysql@v1.10.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-webauthn/webauthn — `github.com/go-webauthn/webauthn` is required at v0.11.2 in REDACTED, but v0.18.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-webauthn/webauthn@v0.18.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/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/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/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/jarcoal/httpmock — `github.com/jarcoal/httpmock` is required at v1.3.1 in REDACTED, but v1.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/jarcoal/httpmock@v1.4.2 && 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.
doc comments repeat the names test/e2e/playwright/actions/webhook.ts:15— 0 of 5 documented parameters and 0 of 10 summaries in `@ory/kratos-e2e-suite` only repeat the member or parameter name (e.g. "" for `key`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 8 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`, … (+3 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 01a1e6a9-3650-7f58-8ceb-05364a2285a6 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 113 · Warnings: 978 · Recommendations: 136 · Info: 90 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 23:20 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.