Public report of OnurGumus/FCQRS, published 15 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, 15 November 2026, 10:07 UTC · Survey ID cd_c7784df6506040babcbd0240101bd34b
OnurGumus/FCQRS
Measured 15 November 2026, 10:06 UTC, at code version 57ae99e
Code coverage is not measured: The suite ran but produced no coverage data.
Test reliability is not measured: No test run produced results.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 3 since the last survey
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: 26,521 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Security and Compliance, 31
Findings by how serious they are
11 critical207 serious85 minor
10 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
15 November 2026, 10:06 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
45of 45 dimensions measured by tools.
221of 303 findings point to an exact file and line, so you can open each one in the code. The other 82 concern the repository as a whole, such as missing documentation.
45dimensions across 6 lenses, read from 26,521 lines of product code in 22 projects.
OnurGumus/FCQRS falls short of our standard for production, in part because we found no access checks on the code's endpoints or handlers. It scores 49 out of 100 and is rated Weak, and all 11 of its critical findings are security problems in the build pipeline.
Security and Compliance, at 31, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 11 points. Replacing the two deprecated dependencies comes next, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 61.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 26,521 lines, about €35,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 31 to 70, the lowest score rated Strong, the score would rise from 49 to about 61.
Code composition: what the lines of code are
Business logic 7%Supporting code 17%Tests 76%
New since the last survey: 135 findings
These 135 critical or serious findings weren't in the previous survey, on 31 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 18 findings
These 18 critical or serious findings were in the previous survey, on 31 October 2026, and are gone from this one.
€12,000 to €59,000, for 195 to 617 hours of work, about 0.2 person-years for one engineer
Difficulty of the problem
Low, 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.7 at a score of 49. 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: 26,521 lines of product code
Comment lines
The estimate prices 25,445 lines. Comment lines count towards the size of 26,521 lines but aren't priced as work.
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.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 11 points · Medium effort · Access Controls
2
Resolve the 2 Deprecated finding(s) in Dependency Hygiene.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
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 €35,000 to build again, about 0.2 person-years of work. Its weakest lens is Security and Compliance, at 31 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. Of all the actions in this report, it raises the score most for the work it takes: about 11 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 63,289 lines over the last 90 days, which is about 256,672 lines a year. At that pace, the extra work comes to an estimated 32.5 to 195.1 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.
92 modules, with 94 dependencies between them. 2 loops run through 5 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 52 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.
FCQRS.Common.CommandHandler uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Common.CommandHandler, while a change to FCQRS.Common.CommandHandler can't break FCQRS.Common.
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.
FCQRS.Model.CSharp uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.Model.CSharp, while a change to FCQRS.Model.CSharp can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.Model.CSharp uses a module listed above it, which is the healthy direction.
FCQRS.Common uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.Common, while a change to FCQRS.Common can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.Common uses a module listed above it, which is the healthy direction.
FCQRS.Common uses FCQRS.Common.CommandHandler, so a change to FCQRS.Common.CommandHandler can break FCQRS.Common, while a change to FCQRS.Common can't break FCQRS.Common.CommandHandler.
Position
Below the diagonal: FCQRS.Common uses a module listed above it, which is the healthy direction.
FCQRS.Query.Internal uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.Query.Internal, while a change to FCQRS.Query.Internal can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.Query.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Query.Internal uses FCQRS.Query, so a change to FCQRS.Query can break FCQRS.Query.Internal, while a change to FCQRS.Query.Internal can't break FCQRS.Query.
Position
Below the diagonal: FCQRS.Query.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Actor.Internal uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.Actor.Internal, while a change to FCQRS.Actor.Internal can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.Actor.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Actor.Internal uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Actor.Internal, while a change to FCQRS.Actor.Internal can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Actor.Internal uses a module listed above it, which is the healthy direction.
FCQRS.AkklingHelpers.Internal uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.AkklingHelpers.Internal, while a change to FCQRS.AkklingHelpers.Internal can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.AkklingHelpers.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Common.CommandHandler.Internal uses FCQRS.Common.CommandHandler, so a change to FCQRS.Common.CommandHandler can break FCQRS.Common.CommandHandler.Internal, while a change to FCQRS.Common.CommandHandler.Internal can't break FCQRS.Common.CommandHandler.
Position
Below the diagonal: FCQRS.Common.CommandHandler.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Common.CommandHandler.Internal uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Common.CommandHandler.Internal, while a change to FCQRS.Common.CommandHandler.Internal can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Common.CommandHandler.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Common.Internal uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.Common.Internal, while a change to FCQRS.Common.Internal can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.Common.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Common.Internal uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Common.Internal, while a change to FCQRS.Common.Internal can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Common.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Common.SagaStarter uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Common.SagaStarter, while a change to FCQRS.Common.SagaStarter can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Common.SagaStarter uses a module listed above it, which is the healthy direction.
FCQRS.Common.SagaStarter.Internal uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Common.SagaStarter.Internal, while a change to FCQRS.Common.SagaStarter.Internal can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Common.SagaStarter.Internal uses a module listed above it, which is the healthy direction.
FCQRS.Projections uses FCQRS.ProjectionStorage, so a change to FCQRS.ProjectionStorage can break FCQRS.Projections, while a change to FCQRS.Projections can't break FCQRS.ProjectionStorage.
Position
Below the diagonal: FCQRS.Projections uses a module listed above it, which is the healthy direction.
FCQRS.Projections uses FCQRS.Query, so a change to FCQRS.Query can break FCQRS.Projections, while a change to FCQRS.Projections can't break FCQRS.Query.
Position
Below the diagonal: FCQRS.Projections uses a module listed above it, which is the healthy direction.
FCQRS.Projections uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Projections, while a change to FCQRS.Projections can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Projections uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Steps uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.Steps, while a change to FCQRS.Workflows.Steps can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.Steps uses a module listed above it, which is the healthy direction.
20→30 FCQRS.Workflows.Steps uses FCQRS.Workflowspart of a loop✕
Connections
3 pairs of types, where a type in FCQRS.Workflows.Steps uses a type in FCQRS.Workflows.
FCQRS.Workflows.Steps uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.Steps, while a change to FCQRS.Workflows.Steps can't break FCQRS.Workflows.
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.
FCQRS.CSharp uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.CSharp, while a change to FCQRS.CSharp can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.CSharp uses a module listed above it, which is the healthy direction.
39 pairs of types, where a type in FCQRS.CSharp uses a type in FCQRS.Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
FCQRS.CSharp uses FCQRS.Projections, so a change to FCQRS.Projections can break FCQRS.CSharp, while a change to FCQRS.CSharp can't break FCQRS.Projections.
Position
Below the diagonal: FCQRS.CSharp uses a module listed above it, which is the healthy direction.
FCQRS.Common.SagaBuilder uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Common.SagaBuilder, while a change to FCQRS.Common.SagaBuilder can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Common.SagaBuilder uses a module listed above it, which is the healthy direction.
FCQRS.Common.SagaBuilder uses FCQRS.Common.SagaStarter, so a change to FCQRS.Common.SagaStarter can break FCQRS.Common.SagaBuilder, while a change to FCQRS.Common.SagaBuilder can't break FCQRS.Common.SagaStarter.
Position
Below the diagonal: FCQRS.Common.SagaBuilder uses a module listed above it, which is the healthy direction.
FCQRS.FSharp.Fcqrs uses FCQRS.Model.Data, so a change to FCQRS.Model.Data can break FCQRS.FSharp.Fcqrs, while a change to FCQRS.FSharp.Fcqrs can't break FCQRS.Model.Data.
Position
Below the diagonal: FCQRS.FSharp.Fcqrs uses a module listed above it, which is the healthy direction.
FCQRS.FSharp.Fcqrs uses FCQRS.Query, so a change to FCQRS.Query can break FCQRS.FSharp.Fcqrs, while a change to FCQRS.FSharp.Fcqrs can't break FCQRS.Query.
Position
Below the diagonal: FCQRS.FSharp.Fcqrs uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in FCQRS.FSharp.Fcqrs uses a type in FCQRS.Common.
The types involved
FCQRS.FSharp.Fcqrs.Fcqrs → FCQRS.Common.Event`1
FCQRS.FSharp.Fcqrs.Fcqrs → FCQRS.Common.IActor
Direction
FCQRS.FSharp.Fcqrs uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.FSharp.Fcqrs, while a change to FCQRS.FSharp.Fcqrs can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.FSharp.Fcqrs uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in FCQRS.FSharp.Fcqrs uses a type in FCQRS.Actor.
The types involved
FCQRS.FSharp.Fcqrs.Fcqrs → FCQRS.Actor.Connection
FCQRS.FSharp.Fcqrs.Fcqrs → FCQRS.Actor.DBType
Direction
FCQRS.FSharp.Fcqrs uses FCQRS.Actor, so a change to FCQRS.Actor can break FCQRS.FSharp.Fcqrs, while a change to FCQRS.FSharp.Fcqrs can't break FCQRS.Actor.
Position
Below the diagonal: FCQRS.FSharp.Fcqrs uses a module listed above it, which is the healthy direction.
FCQRS.FSharp.Fcqrs uses FCQRS.FSharp, so a change to FCQRS.FSharp can break FCQRS.FSharp.Fcqrs, while a change to FCQRS.FSharp.Fcqrs can't break FCQRS.FSharp.
Position
Below the diagonal: FCQRS.FSharp.Fcqrs uses a module listed above it, which is the healthy direction.
FCQRS.FSharp.Fcqrs uses FCQRS.Projections, so a change to FCQRS.Projections can break FCQRS.FSharp.Fcqrs, while a change to FCQRS.FSharp.Fcqrs can't break FCQRS.Projections.
Position
Below the diagonal: FCQRS.FSharp.Fcqrs uses a module listed above it, which is the healthy direction.
FCQRS.FSharp.ProjectionModule uses FCQRS.FSharp, so a change to FCQRS.FSharp can break FCQRS.FSharp.ProjectionModule, while a change to FCQRS.FSharp.ProjectionModule can't break FCQRS.FSharp.
Position
Below the diagonal: FCQRS.FSharp.ProjectionModule uses a module listed above it, which is the healthy direction.
FCQRS.Saga uses FCQRS.Common.Internal, so a change to FCQRS.Common.Internal can break FCQRS.Saga, while a change to FCQRS.Saga can't break FCQRS.Common.Internal.
Position
Below the diagonal: FCQRS.Saga uses a module listed above it, which is the healthy direction.
FCQRS.Saga uses FCQRS.Common.SagaStarter, so a change to FCQRS.Common.SagaStarter can break FCQRS.Saga, while a change to FCQRS.Saga can't break FCQRS.Common.SagaStarter.
Position
Below the diagonal: FCQRS.Saga uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.CSharp uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.CSharp, while a change to FCQRS.Workflows.CSharp can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.CSharp uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.CSharp uses FCQRS.CSharp, so a change to FCQRS.CSharp can break FCQRS.Workflows.CSharp, while a change to FCQRS.Workflows.CSharp can't break FCQRS.CSharp.
Position
Below the diagonal: FCQRS.Workflows.CSharp uses a module listed above it, which is the healthy direction.
29→30 FCQRS.Workflows.CSharp uses FCQRS.Workflowspart of a loop✕
Connections
20 pairs of types, where a type in FCQRS.Workflows.CSharp uses a type in FCQRS.Workflows.
FCQRS.Workflows.CSharp uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.CSharp, while a change to FCQRS.Workflows.CSharp can't break FCQRS.Workflows.
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.
FCQRS.Workflows uses FCQRS.ProjectionStorage, so a change to FCQRS.ProjectionStorage can break FCQRS.Workflows, while a change to FCQRS.Workflows can't break FCQRS.ProjectionStorage.
Position
Below the diagonal: FCQRS.Workflows uses a module listed above it, which is the healthy direction.
FCQRS.Workflows uses FCQRS.Projections, so a change to FCQRS.Projections can break FCQRS.Workflows, while a change to FCQRS.Workflows can't break FCQRS.Projections.
Position
Below the diagonal: FCQRS.Workflows uses a module listed above it, which is the healthy direction.
FCQRS.Workflows uses FCQRS.Workflows.Steps, so a change to FCQRS.Workflows.Steps can break FCQRS.Workflows, while a change to FCQRS.Workflows can't break FCQRS.Workflows.Steps.
Position
Below the diagonal: FCQRS.Workflows uses a module listed above it, which is the healthy direction.
FCQRS.Workflows uses FCQRS.Workflows.CSharp, so a change to FCQRS.Workflows.CSharp can break FCQRS.Workflows, while a change to FCQRS.Workflows can't break FCQRS.Workflows.CSharp.
Position
Below the diagonal: FCQRS.Workflows uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.ChildSteps uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.ChildSteps, while a change to FCQRS.Workflows.ChildSteps can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.ChildSteps uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.ChildSteps uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.ChildSteps, while a change to FCQRS.Workflows.ChildSteps can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.ChildSteps uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Protocol uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.Protocol, while a change to FCQRS.Workflows.Protocol can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.Protocol uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Protocol uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.Protocol, while a change to FCQRS.Workflows.Protocol can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.Protocol uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Retry uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.Retry, while a change to FCQRS.Workflows.Retry can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.Retry uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Retry uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.Retry, while a change to FCQRS.Workflows.Retry can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.Retry uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Schedule uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.Schedule, while a change to FCQRS.Workflows.Schedule can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.Schedule uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Schedule uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.Schedule, while a change to FCQRS.Workflows.Schedule can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.Schedule uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.ScheduleIndex uses FCQRS.ProjectionStorage, so a change to FCQRS.ProjectionStorage can break FCQRS.Workflows.ScheduleIndex, while a change to FCQRS.Workflows.ScheduleIndex can't break FCQRS.ProjectionStorage.
Position
Below the diagonal: FCQRS.Workflows.ScheduleIndex uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.ScheduleIndex uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.ScheduleIndex, while a change to FCQRS.Workflows.ScheduleIndex can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.ScheduleIndex uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.ScheduleIndex uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.ScheduleIndex, while a change to FCQRS.Workflows.ScheduleIndex can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.ScheduleIndex uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Schedules uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.Schedules, while a change to FCQRS.Workflows.Schedules can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.Schedules uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Schedules uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.Schedules, while a change to FCQRS.Workflows.Schedules can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.Schedules uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.WorkflowActor uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.WorkflowActor, while a change to FCQRS.Workflows.WorkflowActor can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.WorkflowActor uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.WorkflowActor uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.WorkflowActor, while a change to FCQRS.Workflows.WorkflowActor can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.WorkflowActor uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.WorkflowCore uses FCQRS.Workflows.Steps, so a change to FCQRS.Workflows.Steps can break FCQRS.Workflows.WorkflowCore, while a change to FCQRS.Workflows.WorkflowCore can't break FCQRS.Workflows.Steps.
Position
Below the diagonal: FCQRS.Workflows.WorkflowCore uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.WorkflowCore uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.WorkflowCore, while a change to FCQRS.Workflows.WorkflowCore can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.WorkflowCore uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.WorkflowSteps uses FCQRS.FSharp, so a change to FCQRS.FSharp can break FCQRS.Workflows.WorkflowSteps, while a change to FCQRS.Workflows.WorkflowSteps can't break FCQRS.FSharp.
Position
Below the diagonal: FCQRS.Workflows.WorkflowSteps uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.WorkflowSteps uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.WorkflowSteps, while a change to FCQRS.Workflows.WorkflowSteps can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.WorkflowSteps uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Workflows uses FCQRS.Common, so a change to FCQRS.Common can break FCQRS.Workflows.Workflows, while a change to FCQRS.Workflows.Workflows can't break FCQRS.Common.
Position
Below the diagonal: FCQRS.Workflows.Workflows uses a module listed above it, which is the healthy direction.
FCQRS.Workflows.Workflows uses FCQRS.Workflows, so a change to FCQRS.Workflows can break FCQRS.Workflows.Workflows, while a change to FCQRS.Workflows.Workflows can't break FCQRS.Workflows.
Position
Below the diagonal: FCQRS.Workflows.Workflows uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 81% · Adequate · gated by D4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
12
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
Roadmap
Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them; Resolve the 2 Deprecated 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
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Adopt a versioned schema-migration mechanism (DbUp, FluentMigrator, Evolve, EF Core migrations) and create every table in a migration, so the production schema can evolve safely and reproducibly.
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 — 11
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 — 207
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 — 85
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 45 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, 221 of 303 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: this repository's test suite BUILT and its tests PASSED in this run — so neither the build nor our analyzer environment is in question — but the run produced no coverage data, and it captured no message saying why. The usual cause is that the test projects wire up no coverage collector (`--collect:"XPlat Code Coverage"` needs a `coverlet.collector` PackageReference); on a very large suite the instrumented run can also exceed its per-target budget before writing anything. Add a `coverlet.collector` PackageReference, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage is measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D15 Churn × Complexity Hotspots — 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. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/FCQRS.Workflows/Schedules.fs, src/FCQRS/Projections.fs, src/FCQRS/Common.fs, src/FCQRS/Actor.fs, src/FCQRS.Workflows/Api.fs, … that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 485 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — 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 C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/FCQRS/FCQRS.fsproj' because the file extension '.fsproj' is not associated with a language.
D17 Explicit Debt — 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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (19,763 lines, 75% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
AX6 Interface segregation — 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.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
X21 Side-effecting pattern guard — 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.
X23 Unguarded diagnostic materialisation — 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.
X27 Collection changed while being enumerated — 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WorkflowActor.behavior at 180. A further 2 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 Actor.api at 17 — 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 methods was excluded, so the exclusion is disclosed nowhere in the file itself: samples/getting-started-csharp/Document.cs (DocumentAggregate.HandleCommand at 16). 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.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with WorkflowActor.behavior (cyclomatic 180). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.8/10.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with WorkflowActor.behavior (cognitive 224). — Refactoring it lifts Cognitive Complexity from 5.8 to about 6.5/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.4 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 7 FileTooLong finding(s) in God Classes — start with Schedules.fs, Actor.fs, Common.fs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 TooManyMethods finding(s) in God Classes — start with Validation.fs, Scheduler.fs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
112 duplicated block group(s) detected. 18.9 % of the production lines (4,959 of 26,262) are in a reported copy. A further 28 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 116 of the 140 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (8 corresponding lines) · ×7scripts/check-accounts.py:28
+ 101 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with check-accounts.py (2), Transfer.cs (2), Program.cs (2). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Program.cs (3), Aether.fs, CSharpInterop.fs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Query.fs, Transfer.cs, Program.fs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with HostExtensions.fs, Validation.fs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 332 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 198 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with WorkflowActor.fs, Projections.fs, Actor.fs. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted debt markers + unmeasured dead symbols across 5114 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (75% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: 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.
91 % of calls cross a namespace and 8 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
12 finding(s): 0 critical, 11 high, 1 medium, 0 low. 11 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 34 file(s) — `samples/accounts/1-open-an-account/csharp/Account.cs` (lines 7–11), `samples/accounts/2-withdraw-money/csharp/Account.cs` (lines 7–12), `samples/accounts/3-restart-the-bank/csharp/Account.cs` (lines 6–11), `samples/accounts/4-show-a-statement/csharp/Account.cs` (lines 6–11), `samples/accounts/5-transfer-money/csharp/Account.cs` (lines 9–20), … (+29 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. In 23 of those file(s) — `samples/accounts/5-transfer-money/csharp/Transfer.cs`, `samples/accounts/6-add-a-memo/csharp/Transfer.cs`, `samples/getting-started-csharp/Publication.cs`, `samples/orders/1-place-an-order/csharp/Order.cs`, `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs`, … (+18 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 13 of those file(s) — `samples/accounts/1-open-an-account/csharp/Account.cs`, `samples/accounts/2-withdraw-money/csharp/Account.cs`, `samples/accounts/3-restart-the-bank/csharp/Account.cs`, `samples/accounts/4-show-a-statement/csharp/Account.cs`, `samples/accounts/5-transfer-money/csharp/Account.cs`, … (+8 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. 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
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
No action in Static Analysis (SAST) — all 11 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 (11 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.
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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 44 of the 54 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 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. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 53 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
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 · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
`MapPost("/accounts/{id}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/accounts/serve-over-http/csharp/Program.cs:74
`MapPost("/accounts/{id}/deposits")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/accounts/serve-over-http/csharp/Program.cs:79
`MapPost("/accounts/{id}/withdrawals")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/accounts/serve-over-http/csharp/Program.cs:83
`MapGet("/accounts/{id}/statement")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/accounts/serve-over-http/csharp/Program.cs:91
What to do
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
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.
1 ADR-shaped document(s) detected by content — `design/specs/2026-11-10-fcqrs-workflows-design.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.
Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:10
`.livedocs/examples/Examples.fsproj` 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`. — .livedocs/examples/Examples.fsproj:11
What to do
Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
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.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
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.
a CREATE TABLE statement here creates the schema at runtime, and this repository keeps no migration history — there's no upgrade path for an existing production database. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` or a migrations bundle) so schema changes are versioned and applied safely. (×3) — samples/accounts/4-show-a-statement/csharp/Statement.cs:12, samples/accounts/5-transfer-money/csharp/Statement.cs:11, samples/accounts/6-add-a-memo/csharp/Statement.cs:13
What to do
Adopt a versioned schema-migration mechanism (DbUp, FluentMigrator, Evolve, EF Core migrations) and create every table in a migration, so the production schema can evolve safely and reproducibly.
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.
`(module-level async block)` holds an async function that calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — saga_sample/Program.fs:47
What to do
F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
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. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — samples/accounts/serve-over-http/csharp/Program.cs:11
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — samples/accounts/serve-over-http/csharp/Program.cs:11
No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
`MapPost("/accounts/{id}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — samples/accounts/serve-over-http/csharp/Program.cs:74
`MapPost("/accounts/{id}/deposits")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — samples/accounts/serve-over-http/csharp/Program.cs:79
`MapPost("/accounts/{id}/withdrawals")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — samples/accounts/serve-over-http/csharp/Program.cs:83
`MapGet("/accounts/{id}/statement")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — samples/accounts/serve-over-http/csharp/Program.cs:91
What to do
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.3 `!` suppressions per 1k syntax nodes — 8 suppression(s) across the 30085 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 70 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — AX6 reached only 20% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 1 markup document under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — ~13072 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — no test run produced results
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .py, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs, .py source were not judged.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage not measured — the suite ran but produced no coverage data
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 137 value object(s); 52 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
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
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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.
X1 Async correctness — X1 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 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 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — X2 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — X21 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 — X23 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — 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
X3 Exception handling — X3 reached only 19% of this repository's production lines — fsharp (19,763 lines), python (1,385 lines), javascript (259 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Hotspot: src/FCQRS.Workflows/WorkflowActor.fs src/FCQRS.Workflows/WorkflowActor.fs:66— src/FCQRS.Workflows/WorkflowActor.fs changed 6 times in last 90 days, max cyclomatic complexity 180 in WorkflowActor.behavior at line 66. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS.Workflows/WorkflowActor.fs`: 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: src/FCQRS/Projections.fs src/FCQRS/Projections.fs:204— src/FCQRS/Projections.fs changed 13 times in last 90 days, max cyclomatic complexity 71 in Projections.run at line 204. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS/Projections.fs`: 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: src/FCQRS/Actor.fs src/FCQRS/Actor.fs:201— src/FCQRS/Actor.fs changed 12 times in last 90 days, max cyclomatic complexity 69 in Internal.runActor at line 201. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS/Actor.fs`: 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: src/FCQRS.Workflows/Schedules.fs src/FCQRS.Workflows/Schedules.fs:308— src/FCQRS.Workflows/Schedules.fs changed 17 times in last 90 days, max cyclomatic complexity 39 in Schedule.decide at line 308. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS.Workflows/Schedules.fs`: 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: src/FCQRS/Common.fs src/FCQRS/Common.fs:1391— src/FCQRS/Common.fs changed 11 times in last 90 days, max cyclomatic complexity 49 in Internal.subscribeForCommandCore at line 1391. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS/Common.fs`: 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: src/FCQRS/Saga.fs src/FCQRS/Saga.fs:721— src/FCQRS/Saga.fs changed 6 times in last 90 days, max cyclomatic complexity 79 in Saga.actorProp at line 721. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS/Saga.fs`: 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: src/FCQRS/Serialization.fs src/FCQRS/Serialization.fs:80— src/FCQRS/Serialization.fs changed 7 times in last 90 days, max cyclomatic complexity 17 in Manifests.resolve at line 80. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS/Serialization.fs`: 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: samples/getting-started-fsharp/Program.fs samples/getting-started-fsharp/Program.fs:14— samples/getting-started-fsharp/Program.fs changed 2 times in last 90 days, max cyclomatic complexity 26 in App.run at line 14. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- samples/getting-started-fsharp/Program.fs`: 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: scripts/build-docs.py scripts/build-docs.py:236— scripts/build-docs.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in build-docs.finish at line 236. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- scripts/build-docs.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/FCQRS.Workflows/Api.fs src/FCQRS.Workflows/Api.fs:73— src/FCQRS.Workflows/Api.fs changed 3 times in last 90 days, max cyclomatic complexity 16 in Workflows.register at line 73. 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 11:01:36 +01:00' --until='2026-11-15 11:01:36 +01:00' --full-history --no-merges -- src/FCQRS.Workflows/Api.fs`: 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.
FileTooLong: FCQRS.Workflows/Schedules.fs src/FCQRS.Workflows/Schedules.fs— FileTooLong — 1039 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 539 over it, 2.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FCQRS/Actor.fs src/FCQRS/Actor.fs— FileTooLong — 994 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 494 over it, 1.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FCQRS/Common.fs src/FCQRS/Common.fs— FileTooLong — 985 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 485 over it, 1.97× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FCQRS/Saga.fs src/FCQRS/Saga.fs— FileTooLong — 926 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 426 over it, 1.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FCQRS.Workflows/WorkflowActor.fs src/FCQRS.Workflows/WorkflowActor.fs— FileTooLong — 710 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 210 over it, 1.42× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FCQRS/Projections.fs src/FCQRS/Projections.fs— FileTooLong — 583 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 83 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FCQRS/CSharpInterop.fs src/FCQRS/CSharpInterop.fs— FileTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 39 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×7
Edited copy of a member (8 corresponding lines) scripts/check-accounts.py:28— scripts/check-accounts.py:28-35 | scripts/check-orders.py:37-51 — 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) scripts/check-accounts.py:60— scripts/check-accounts.py:60-68 | scripts/check-accounts.py:198-205 — 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) samples/accounts/5-transfer-money/csharp/Transfer.cs:80— samples/accounts/5-transfer-money/csharp/Transfer.cs:80-87 | samples/accounts/6-add-a-memo/csharp/Transfer.cs:81-88 — 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) samples/accounts/4-show-a-statement/csharp/Program.cs:44— samples/accounts/4-show-a-statement/csharp/Program.cs:44-54 | samples/accounts/5-transfer-money/csharp/Program.cs:52-59 — 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) samples/orders/3-read-the-clock/csharp/Program.cs:126— samples/orders/3-read-the-clock/csharp/Program.cs:126-133 | samples/orders/4-wait-for-approval/csharp/Program.cs:119-126 — 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) samples/accounts/5-transfer-money/csharp/Transfer.cs:34— samples/accounts/5-transfer-money/csharp/Transfer.cs:34-41 | samples/accounts/6-add-a-memo/csharp/Transfer.cs:35-42 — 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) samples/orders/1-place-an-order/csharp/Order.cs:29— samples/orders/1-place-an-order/csharp/Order.cs:29-37 | samples/orders/2-retry-the-warehouse/csharp/Order.cs:34-41 — 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.
Duplicated block (6 lines × 2) src/FCQRS.Model/Aether.fs:92— src/FCQRS.Model/Aether.fs:92-97 | src/FCQRS.Model/Aether.fs:102-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/FCQRS/CSharpInterop.fs:431— src/FCQRS/CSharpInterop.fs:431-436 | src/FCQRS/CSharpInterop.fs:467-472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/FCQRS/Projections.fs:639— src/FCQRS/Projections.fs:639-644 | src/FCQRS/Projections.fs:797-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) samples/accounts/4-show-a-statement/csharp/Program.cs:44— samples/accounts/4-show-a-statement/csharp/Program.cs:44-51 | samples/accounts/5-transfer-money/csharp/Program.cs:52-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/accounts/4-show-a-statement/csharp/Program.cs:44` 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) samples/accounts/4-show-a-statement/csharp/Program.cs:78— samples/accounts/4-show-a-statement/csharp/Program.cs:78-83 | samples/accounts/5-transfer-money/csharp/Program.cs:111-116 — 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 `samples/accounts/4-show-a-statement/csharp/Program.cs:78` 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) samples/accounts/5-transfer-money/csharp/Program.cs:125— samples/accounts/5-transfer-money/csharp/Program.cs:125-130 | samples/accounts/6-add-a-memo/csharp/Program.cs:149-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/accounts/5-transfer-money/csharp/Program.cs:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization samples/accounts/serve-over-http/csharp/Program.cs:74— `MapPost("/accounts/{id}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/accounts/serve-over-http/csharp/Program.cs:79— `MapPost("/accounts/{id}/deposits")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/accounts/serve-over-http/csharp/Program.cs:83— `MapPost("/accounts/{id}/withdrawals")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/accounts/serve-over-http/csharp/Program.cs:91— `MapGet("/accounts/{id}/statement")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
Duplicated block (13 lines × 2) saga_sample/Query.fs:3— saga_sample/Query.fs:3-15 | sample/Query.fs:3-15 — `saga_sample/Query.fs` and `sample/Query.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 13 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 (13 lines × 2) samples/accounts/5-transfer-money/csharp/Transfer.cs:60— samples/accounts/5-transfer-money/csharp/Transfer.cs:60-72 | samples/accounts/6-add-a-memo/csharp/Transfer.cs:61-73 — before extracting anything, compare `samples/accounts/5-transfer-money/csharp/Transfer.cs` and `samples/accounts/6-add-a-memo/csharp/Transfer.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) samples/accounts/1-open-an-account/fsharp/Program.fs:62— samples/accounts/1-open-an-account/fsharp/Program.fs:62-74 | samples/accounts/2-withdraw-money/fsharp/Program.fs:81-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/FCQRS.Workflows/CSharp.fs:37— src/FCQRS.Workflows/CSharp.fs:37-48 | src/FCQRS.Workflows/CSharp.fs:60-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/FCQRS/Common.fs:167— src/FCQRS/Common.fs:167-178 | src/FCQRS/Common.fs:203-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/FCQRS.Model/CSharpHelpers.fs:23— src/FCQRS.Model/CSharpHelpers.fs:23-34 | src/FCQRS/CSharpInterop.fs:95-106 — 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 × 3) src/FCQRS/HostExtensions.fs:346— src/FCQRS/HostExtensions.fs:346-354 | src/FCQRS/HostExtensions.fs:357-364 | src/FCQRS/HostExtensions.fs:367-373 — 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 `src/FCQRS/HostExtensions.fs:346` 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) samples/orders/4-wait-for-approval/csharp/Program.cs:43— samples/orders/4-wait-for-approval/csharp/Program.cs:43-49 | samples/orders/5-restart-during-shipping/csharp/Program.cs:46-52 | samples/orders/6-charge-the-customer/csharp/Program.cs:60-66 — before extracting anything, compare `samples/orders/4-wait-for-approval/csharp/Program.cs` and `samples/orders/5-restart-during-shipping/csharp/Program.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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 `samples/orders/4-wait-for-approval/csharp/Program.cs:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/orders/4-wait-for-approval/csharp/Program.cs:54` calls `Place` and `samples/orders/5-restart-during-shipping/csharp/Program.cs:60` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) samples/accounts/2-withdraw-money/csharp/Program.cs:60— samples/accounts/2-withdraw-money/csharp/Program.cs:60-66 | samples/accounts/3-restart-the-bank/csharp/Program.cs:47-53 | samples/accounts/4-show-a-statement/csharp/Program.cs:92-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (14 lines × 2) src/FCQRS/Serialization.fs:213— src/FCQRS/Serialization.fs:213-226 | src/FCQRS/Serialization.fs:339-352 — 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) samples/accounts/1-open-an-account/csharp/Program.cs:53— samples/accounts/1-open-an-account/csharp/Program.cs:53-66 | samples/accounts/2-withdraw-money/csharp/Program.cs:72-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) samples/orders/6-charge-the-customer/fsharp/Order.fs:45— samples/orders/6-charge-the-customer/fsharp/Order.fs:45-58 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:46-59 — before extracting anything, compare `samples/orders/6-charge-the-customer/fsharp/Order.fs` and `samples/orders/7-when-a-step-fails/fsharp/Order.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 117 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 `samples/orders/6-charge-the-customer/fsharp/Order.fs:45` 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) src/FCQRS/Actor.fs:82— src/FCQRS/Actor.fs:82-86 | src/FCQRS/Actor.fs:627-632 — 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. 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 × 2) src/FCQRS/CSharpInterop.fs:477— src/FCQRS/CSharpInterop.fs:477-481 | src/FCQRS/CSharpInterop.fs:543-547 — 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) samples/accounts/4-show-a-statement/fsharp/Program.fs:92— samples/accounts/4-show-a-statement/fsharp/Program.fs:92-96 | samples/accounts/5-transfer-money/fsharp/Program.fs:129-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) samples/accounts/5-transfer-money/csharp/Transfer.cs:46— samples/accounts/5-transfer-money/csharp/Transfer.cs:46-56 | samples/accounts/6-add-a-memo/csharp/Transfer.cs:47-57 — before extracting anything, compare `samples/accounts/5-transfer-money/csharp/Transfer.cs` and `samples/accounts/6-add-a-memo/csharp/Transfer.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) samples/accounts/5-transfer-money/fsharp/Account.fs:87— samples/accounts/5-transfer-money/fsharp/Account.fs:87-97 | samples/accounts/6-add-a-memo/fsharp/Account.fs:99-109 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Account.fs` and `samples/accounts/6-add-a-memo/fsharp/Account.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 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 (11 lines × 2) samples/accounts/5-transfer-money/fsharp/Account.fs:68— samples/accounts/5-transfer-money/fsharp/Account.fs:68-78 | samples/accounts/6-add-a-memo/fsharp/Account.fs:80-90 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Account.fs` and `samples/accounts/6-add-a-memo/fsharp/Account.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 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 (8 lines × 2) samples/accounts/5-transfer-money/csharp/Account.cs:82— samples/accounts/5-transfer-money/csharp/Account.cs:82-89 | samples/accounts/6-add-a-memo/csharp/Account.cs:85-92 — before extracting anything, compare `samples/accounts/5-transfer-money/csharp/Account.cs` and `samples/accounts/6-add-a-memo/csharp/Account.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 `samples/accounts/5-transfer-money/csharp/Account.cs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) samples/orders/4-wait-for-approval/csharp/Program.cs:42— samples/orders/4-wait-for-approval/csharp/Program.cs:42-49 | samples/orders/5-restart-during-shipping/csharp/Program.cs:45-52 — before extracting anything, compare `samples/orders/4-wait-for-approval/csharp/Program.cs` and `samples/orders/5-restart-during-shipping/csharp/Program.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/orders/4-wait-for-approval/csharp/Program.cs:54` calls `Place` and `samples/orders/5-restart-during-shipping/csharp/Program.cs:60` 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 × 2) samples/accounts/5-transfer-money/fsharp/Program.fs:47— samples/accounts/5-transfer-money/fsharp/Program.fs:47-54 | samples/accounts/6-add-a-memo/fsharp/Program.fs:60-70 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Program.fs` and `samples/accounts/6-add-a-memo/fsharp/Program.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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. 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.
P8 · Schema migrations· Schema created by a CREATE TABLE statement (no migration path) · ×3
Schema created by a CREATE TABLE statement (no migration path) samples/accounts/4-show-a-statement/csharp/Statement.cs:12— a CREATE TABLE statement here creates the schema at runtime, and this repository keeps no migration history — there's no upgrade path for an existing production database. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` or a migrations bundle) so schema changes are versioned and applied safely.
Schema created by a CREATE TABLE statement (no migration path) samples/accounts/5-transfer-money/csharp/Statement.cs:11— a CREATE TABLE statement here creates the schema at runtime, and this repository keeps no migration history — there's no upgrade path for an existing production database. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` or a migrations bundle) so schema changes are versioned and applied safely.
Schema created by a CREATE TABLE statement (no migration path) samples/accounts/6-add-a-memo/csharp/Statement.cs:13— a CREATE TABLE statement here creates the schema at runtime, and this repository keeps no migration history — there's no upgrade path for an existing production database. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` or a migrations bundle) so schema changes are versioned and applied safely.
Deprecated: System.Reactive.Linq — System.Reactive.Linq 6.1.0 — Legacy — the publisher's replacement is `System.Reactive`; migrate the reference to it.
Deprecated: SerilogTracing.Sinks.Seq — SerilogTracing.Sinks.Seq 1.0.1-dev-00264 — Legacy — the publisher's replacement is `Serilog.Sinks.Seq`; migrate the reference to it.
TooManyMethods: Validator`1 src/FCQRS.Model/Validation.fs:54— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: ObservingScheduler src/FCQRS/Scheduler.fs:60— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
Duplicated block (16 lines × 2) src/FCQRS.Model/Aether.fs:342— src/FCQRS.Model/Aether.fs:342-357 | src/FCQRS.Model/Aether.fs:369-384 — 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. 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 × 2) samples/accounts/5-transfer-money/csharp/Account.cs:56— samples/accounts/5-transfer-money/csharp/Account.cs:56-71 | samples/accounts/6-add-a-memo/csharp/Account.cs:59-74 — before extracting anything, compare `samples/accounts/5-transfer-money/csharp/Account.cs` and `samples/accounts/6-add-a-memo/csharp/Account.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 `samples/accounts/5-transfer-money/csharp/Account.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/FCQRS/Saga.fs:724— src/FCQRS/Saga.fs:724-730 | src/FCQRS/Saga.fs:1323-1329 — 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) samples/orders/3-read-the-clock/csharp/Program.cs:127— samples/orders/3-read-the-clock/csharp/Program.cs:127-133 | samples/orders/4-wait-for-approval/csharp/Program.cs:120-126 — before extracting anything, compare `samples/orders/3-read-the-clock/csharp/Program.cs` and `samples/orders/4-wait-for-approval/csharp/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 3) src/FCQRS/HostExtensions.fs:377— src/FCQRS/HostExtensions.fs:377-381 | src/FCQRS/HostExtensions.fs:385-389 | src/FCQRS/HostExtensions.fs:393-405 — 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 `src/FCQRS/HostExtensions.fs:377` 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) samples/accounts/2-withdraw-money/csharp/Program.cs:32— samples/accounts/2-withdraw-money/csharp/Program.cs:32-36 | samples/accounts/5-transfer-money/csharp/Program.cs:41-45 | samples/accounts/6-add-a-memo/csharp/Program.cs:60-64 — 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) samples/accounts/2-withdraw-money/fsharp/Account.fs:2— samples/accounts/2-withdraw-money/fsharp/Account.fs:2-46 | samples/accounts/3-restart-the-bank/fsharp/Account.fs:1-43 | samples/accounts/4-show-a-statement/fsharp/Account.fs:1-43 | samples/accounts/5-transfer-money/fsharp/Account.fs:2-97 | samples/accounts/6-add-a-memo/fsharp/Account.fs:2-109 — 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) samples/orders/10-feed-orders-from-a-stream/fsharp/Account.fs:2— samples/orders/10-feed-orders-from-a-stream/fsharp/Account.fs:2-48 | samples/orders/6-charge-the-customer/fsharp/Account.fs:2-48 | samples/orders/7-when-a-step-fails/fsharp/Account.fs:2-48 | samples/orders/8-add-a-step/fsharp/Account.fs:2-48 | samples/orders/9-guard-the-change/fsharp/Account.fs:2-48 — 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.
Duplicated block (29 lines × 2) samples/accounts/5-transfer-money/csharp/Account.cs:94— samples/accounts/5-transfer-money/csharp/Account.cs:94-122 | samples/accounts/6-add-a-memo/csharp/Account.cs:97-125 — before extracting anything, compare `samples/accounts/5-transfer-money/csharp/Account.cs` and `samples/accounts/6-add-a-memo/csharp/Account.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (29 lines × 2) samples/accounts/5-transfer-money/fsharp/Account.fs:22— samples/accounts/5-transfer-money/fsharp/Account.fs:22-50 | samples/accounts/6-add-a-memo/fsharp/Account.fs:33-61 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Account.fs` and `samples/accounts/6-add-a-memo/fsharp/Account.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 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 (28 lines × 4) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:64— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:64-91 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:57-84 | samples/orders/8-add-a-step/fsharp/Order.fs:64-91 | samples/orders/9-guard-the-change/fsharp/Order.fs:64-91 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/7-when-a-step-fails/fsharp/Order.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 176 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 `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 4) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:129— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:129-156 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:107-134 | samples/orders/8-add-a-step/fsharp/Order.fs:122-149 | samples/orders/9-guard-the-change/fsharp/Order.fs:129-156 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/7-when-a-step-fails/fsharp/Order.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 176 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 `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:129` 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 (25 lines × 2) samples/accounts/5-transfer-money/fsharp/Transfer.fs:39— samples/accounts/5-transfer-money/fsharp/Transfer.fs:39-63 | samples/accounts/6-add-a-memo/fsharp/Transfer.fs:46-70 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Transfer.fs` and `samples/accounts/6-add-a-memo/fsharp/Transfer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 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 `samples/accounts/5-transfer-money/fsharp/Transfer.fs:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25 lines × 2) samples/orders/5-restart-during-shipping/fsharp/Program.fs:45— samples/orders/5-restart-during-shipping/fsharp/Program.fs:45-69 | samples/orders/6-charge-the-customer/fsharp/Program.fs:54-78 — before extracting anything, compare `samples/orders/5-restart-during-shipping/fsharp/Program.fs` and `samples/orders/6-charge-the-customer/fsharp/Program.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 106 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 `samples/orders/5-restart-during-shipping/fsharp/Program.fs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 3) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:73— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:73-91 | samples/orders/8-add-a-step/csharp/Order.cs:73-90 | samples/orders/9-guard-the-change/csharp/Order.cs:73-91 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs` and `samples/orders/8-add-a-step/csharp/Order.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 97 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 `samples/orders/8-add-a-step/csharp/Order.cs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (18 lines × 3) samples/orders/1-place-an-order/fsharp/Program.fs:43— samples/orders/1-place-an-order/fsharp/Program.fs:43-60 | samples/orders/2-retry-the-warehouse/fsharp/Program.fs:50-67 | samples/orders/3-read-the-clock/fsharp/Program.fs:66-83 — before extracting anything, compare `samples/orders/1-place-an-order/fsharp/Program.fs` and `samples/orders/2-retry-the-warehouse/fsharp/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 (5 lines × 5) samples/accounts/2-withdraw-money/csharp/Account.cs:34— samples/accounts/2-withdraw-money/csharp/Account.cs:34-38 | samples/accounts/3-restart-the-bank/csharp/Account.cs:35-39 | samples/accounts/4-show-a-statement/csharp/Account.cs:31-35 | samples/accounts/5-transfer-money/csharp/Account.cs:56-60 | samples/accounts/6-add-a-memo/csharp/Account.cs:59-63 — before extracting anything, compare `samples/accounts/2-withdraw-money/csharp/Account.cs` and `samples/accounts/3-restart-the-bank/csharp/Account.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `samples/accounts/2-withdraw-money/csharp/Account.cs: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/accounts/3-restart-the-bank/csharp/Account.cs:29` calls `NewEvery` and `samples/accounts/2-withdraw-money/csharp/Account.cs:29` 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 × 5) samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs:30— samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs:30-34 | samples/orders/6-charge-the-customer/csharp/Program.cs:39-43 | samples/orders/7-when-a-step-fails/csharp/Program.cs:39-43 | samples/orders/8-add-a-step/csharp/Program.cs:39-43 | samples/orders/9-guard-the-change/csharp/Program.cs:39-43 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs` and `samples/orders/7-when-a-step-fails/csharp/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
Low cohesion: FcqrsBuilder (LCOM4 6) src/FCQRS/HostExtensions.fs:75— FcqrsBuilder's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Validator`1 (LCOM4 4) src/FCQRS.Model/Validation.fs:54— Validator`1'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.
WorkflowActor.behavior (cyclomatic 180) src/FCQRS.Workflows/WorkflowActor.fs:66— WorkflowActor.behavior has cyclomatic complexity 180 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Saga.actorProp (cyclomatic 79) src/FCQRS/Saga.fs:721— Saga.actorProp has cyclomatic complexity 79 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
language-tabs.csharpTypeRanges (cyclomatic 78) docs/content/language-tabs.js:109— language-tabs.csharpTypeRanges has cyclomatic complexity 78 (threshold 15). Of this number, 75 points are the body's own statements and 3 belong to 3 function items inside it that branch. 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.
Projections.run (cyclomatic 71) src/FCQRS/Projections.fs:204— Projections.run has cyclomatic complexity 71 (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.
Internal.runActor (cyclomatic 69) src/FCQRS/Actor.fs:201— Internal.runActor has cyclomatic complexity 69 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Saga.runSaga (cyclomatic 61) src/FCQRS/Saga.fs:285— Saga.runSaga has cyclomatic complexity 61 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Internal.subscribeForCommandCore (cyclomatic 49) src/FCQRS/Common.fs:1391— Internal.subscribeForCommandCore has cyclomatic complexity 49 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Schedule.decide (cyclomatic 39) src/FCQRS.Workflows/Schedules.fs:308— Schedule.decide has cyclomatic complexity 39 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Internal.actorProp (cyclomatic 29) src/FCQRS/Actor.fs:844— Internal.actorProp has cyclomatic complexity 29 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SchedulerController.createAgent (cyclomatic 25) src/FCQRS/SchedulerController.fs:37— SchedulerController.createAgent has cyclomatic complexity 25 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Query.augment (cyclomatic 23) src/FCQRS.SQLProvider/Query.fs:21— Query.augment has cyclomatic complexity 23 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Manifests.resolve (cyclomatic 17) src/FCQRS/Serialization.fs:80— Manifests.resolve has cyclomatic complexity 17 (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.
Workflows.register (cyclomatic 16) src/FCQRS.Workflows/Api.fs:73— Workflows.register has cyclomatic complexity 16 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Prerelease dependency: SerilogTracing.Sinks.Seq — SerilogTracing.Sinks.Seq resolves to 1.0.1-dev-00264, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
WorkflowActor.behavior (cognitive 224) src/FCQRS.Workflows/WorkflowActor.fs:66— WorkflowActor.behavior has cognitive complexity 224 (threshold 15). Drivers by points: match/switch 60 (104 pts), if/else 44 (76 pts), error handling 6 (19 pts), loops 7 (14 pts), boolean chains 11 (nesting depth added 96). 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.
language-tabs.csharpTypeRanges (cognitive 102) docs/content/language-tabs.js:109— language-tabs.csharpTypeRanges has cognitive complexity 102 (threshold 15). Drivers by points: if/else 32 (53 pts), boolean chains 32, loops 7 (13 pts), ternaries 2 (4 pts) (nesting depth added 29). Of this number, 99 points are the body's own statements and 3 belong to 3 function items 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.
Saga.actorProp (cognitive 101) src/FCQRS/Saga.fs:721— Saga.actorProp has cognitive complexity 101 (threshold 15). Drivers by points: match/switch 29 (62 pts), if/else 10 (21 pts), error handling 5 (11 pts), boolean chains 5, loops 2 (nesting depth added 50). 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.
Projections.run (cognitive 94) src/FCQRS/Projections.fs:204— Projections.run has cognitive complexity 94 (threshold 15). Drivers by points: if/else 24 (39 pts), match/switch 13 (22 pts), loops 9 (14 pts), error handling 11 (13 pts), boolean chains 6 (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.
Internal.runActor (cognitive 79) src/FCQRS/Actor.fs:201— Internal.runActor has cognitive complexity 79 (threshold 15). Drivers by points: match/switch 21 (38 pts), if/else 21 (30 pts), error handling 3 (5 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 29). 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.
Saga.runSaga (cognitive 78) src/FCQRS/Saga.fs:285— Saga.runSaga has cognitive complexity 78 (threshold 15). Drivers by points: match/switch 16 (39 pts), if/else 13 (26 pts), error handling 3 (8 pts), boolean chains 5 (nesting depth added 41). 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.
Internal.actorProp (cognitive 47) src/FCQRS/Actor.fs:844— Internal.actorProp has cognitive complexity 47 (threshold 15). Drivers by points: match/switch 15 (36 pts), if/else 5 (9 pts), error handling 1 (2 pts) (nesting depth added 26). 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.
Internal.subscribeForCommandCore (cognitive 41) src/FCQRS/Common.fs:1391— Internal.subscribeForCommandCore has cognitive complexity 41 (threshold 15). Drivers by points: match/switch 13 (26 pts), boolean chains 6, if/else 3 (5 pts), error handling 2 (4 pts) (nesting depth added 17). 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.
SchedulerController.createAgent (cognitive 33) src/FCQRS/SchedulerController.fs:37— SchedulerController.createAgent has cognitive complexity 33 (threshold 15). Drivers by points: match/switch 7 (18 pts), if/else 4 (14 pts), boolean chains 1 (nesting depth added 21). 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.
Manifests.resolve (cognitive 23) src/FCQRS/Serialization.fs:80— Manifests.resolve has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 2 (4 pts), match/switch 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotificationSubscription`1.Start (cognitive 22) src/FCQRS/Query.fs:219— NotificationSubscription`1.Start has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 1 (5 pts), loops 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Schedule.decide (cognitive 22) src/FCQRS.Workflows/Schedules.fs:308— Schedule.decide has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 9 (18 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 10). 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.
ReadUpcasting.upcastStored (cognitive 20) src/FCQRS/Saga.fs:216— ReadUpcasting.upcastStored has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 3 (8 pts), boolean chains 1 (nesting depth added 12). 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.
Query.augment (cognitive 19) src/FCQRS.SQLProvider/Query.fs:21— Query.augment has cognitive complexity 19 (threshold 15). Drivers by points: loops 8 (15 pts), match/switch 4 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
top-level statements (cognitive 18) samples/getting-started-csharp/Program.cs:9— top-level statements has cognitive complexity 18 (threshold 15). 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.
Projections.startTracked (cognitive 17) src/FCQRS/Projections.fs:734— Projections.startTracked has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 5 (7 pts), error handling 1 (nesting depth added 6). 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.
language-tabs.document.querySelectorAll(".cs-alt").forEach() (cognitive 16) docs/content/language-tabs.js:51— language-tabs.document.querySelectorAll(".cs-alt").forEach() has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 5, if/else 5 (nesting depth added 3). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 84, 52, 54, …). 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.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) saga_sample/Query.fs:3— saga_sample/Query.fs:3-33 | sample/Query.fs:3-32 — 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.
Duplicated block (27–29 lines × 2) saga_sample/Bootstrap.fs:45— saga_sample/Bootstrap.fs:45-71 | sample/Bootstrap.fs:52-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.
Duplicated block (26–27 lines × 2) saga_sample/Command.fs:23— saga_sample/Command.fs:23-49 | sample/Command.fs:28-53 — 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 `saga_sample/Command.fs:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note 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 (19–20 lines × 2) src/FCQRS/Actor.fs:858— src/FCQRS/Actor.fs:858-877 | src/FCQRS/Saga.fs:822-840 — 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. 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 (11–13 lines × 2) src/FCQRS.Model/Aether.fs:228— src/FCQRS.Model/Aether.fs:228-240 | src/FCQRS.Model/Aether.fs:248-258 — 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. 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 (8–12 lines × 2) src/FCQRS/Scheduler.fs:97— src/FCQRS/Scheduler.fs:97-104 | src/FCQRS/Scheduler.fs:146-157 — 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 `src/FCQRS/Scheduler.fs:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) src/FCQRS.Model/CSharpHelpers.fs:12— src/FCQRS.Model/CSharpHelpers.fs:12-20 | src/FCQRS/CSharpInterop.fs:108-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. 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–6 lines × 2) src/FCQRS/Common.fs:1088— src/FCQRS/Common.fs:1088-1093 | src/FCQRS/Common.fs:1114-1118 — 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 `src/FCQRS/Common.fs:1088` 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 (4–5 lines × 10) src/FCQRS/CSharpInterop.fs:409— src/FCQRS/CSharpInterop.fs:409-412 | src/FCQRS/CSharpInterop.fs:420-424 | src/FCQRS/CSharpInterop.fs:431-435 | src/FCQRS/CSharpInterop.fs:447-450 | src/FCQRS/CSharpInterop.fs:456-460 | src/FCQRS/CSharpInterop.fs:467-471 | src/FCQRS/CSharpInterop.fs:490-494 | src/FCQRS/CSharpInterop.fs:504-508 | src/FCQRS/CSharpInterop.fs:520-524 | src/FCQRS/CSharpInterop.fs:532-536 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) saga_sample/Environments.fs:1— saga_sample/Environments.fs:1-15 | sample/Environments.fs:1-15 — `saga_sample/Environments.fs` and `sample/Environments.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication· Near-duplicate member family (7 members, 21 shared lines) · ×1
Near-duplicate member family (7 members, 21 shared lines) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:2— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:2-156 | samples/orders/4-wait-for-approval/fsharp/Order.fs:2-99 | samples/orders/5-restart-during-shipping/fsharp/Order.fs:2-99 | samples/orders/6-charge-the-customer/fsharp/Order.fs:2-116 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:2-134 | samples/orders/8-add-a-step/fsharp/Order.fs:2-149 | samples/orders/9-guard-the-change/fsharp/Order.fs:2-156 — These 7 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 77 shared lines) · ×1
Near-duplicate member family (5 members, 77 shared lines) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:2— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:2-156 | samples/orders/6-charge-the-customer/fsharp/Order.fs:2-116 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:2-134 | samples/orders/8-add-a-step/fsharp/Order.fs:2-149 | samples/orders/9-guard-the-change/fsharp/Order.fs:2-156 — These 5 members are variants of one another: a block of 77 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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· Near-duplicate member family (5 members, 35 shared lines) · ×1
Near-duplicate member family (5 members, 35 shared lines) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:70— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:70-127 | samples/orders/6-charge-the-customer/csharp/Order.cs:44-91 | samples/orders/7-when-a-step-fails/csharp/Order.cs:62-109 | samples/orders/8-add-a-step/csharp/Order.cs:70-124 | samples/orders/9-guard-the-change/csharp/Order.cs:70-127 — These 5 members are variants of one another: a block of 35 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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.
Near-duplicate member pair (37 shared lines) samples/accounts/5-transfer-money/fsharp/Program.fs:1— samples/accounts/5-transfer-money/fsharp/Program.fs:1-139 | samples/accounts/6-add-a-memo/fsharp/Program.fs:1-156 — These two members are variants of one another: 37 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) samples/orders/1-place-an-order/fsharp/Program.fs:2— samples/orders/1-place-an-order/fsharp/Program.fs:2-98 | samples/orders/10-feed-orders-from-a-stream/fsharp/Program.fs:2-208 | samples/orders/2-retry-the-warehouse/fsharp/Program.fs:2-105 | samples/orders/3-read-the-clock/fsharp/Program.fs:2-136 | samples/orders/4-wait-for-approval/fsharp/Program.fs:2-130 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:2-133 | samples/orders/6-charge-the-customer/fsharp/Program.fs:2-173 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:2-197 | samples/orders/8-add-a-step/fsharp/Program.fs:2-197 | samples/orders/9-guard-the-change/fsharp/Program.fs:2-199 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Edited copy of a member (86 corresponding lines) · ×1
Edited copy of a member (86 corresponding lines) samples/accounts/5-transfer-money/fsharp/Transfer.fs:1— samples/accounts/5-transfer-money/fsharp/Transfer.fs:1-86 | samples/accounts/6-add-a-memo/fsharp/Transfer.fs:1-94 — These two members are one piece of code written twice and then edited apart: 86 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) · ×1
Edited copy of a member (34 corresponding lines) samples/accounts/5-transfer-money/csharp/Account.cs:56— samples/accounts/5-transfer-money/csharp/Account.cs:56-89 | samples/accounts/6-add-a-memo/csharp/Account.cs:59-92 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) samples/accounts/1-open-an-account/fsharp/Program.fs:1— samples/accounts/1-open-an-account/fsharp/Program.fs:1-74 | samples/accounts/2-withdraw-money/fsharp/Program.fs:1-93 — 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 copy of a member (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) samples/accounts/5-transfer-money/fsharp/Statement.fs:1— samples/accounts/5-transfer-money/fsharp/Statement.fs:1-55 | samples/accounts/6-add-a-memo/fsharp/Statement.fs:1-65 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) samples/orders/4-wait-for-approval/csharp/Order.cs:42— samples/orders/4-wait-for-approval/csharp/Order.cs:42-72 | samples/orders/5-restart-during-shipping/csharp/Order.cs:42-72 — 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) samples/accounts/5-transfer-money/csharp/Statement.cs:33— samples/accounts/5-transfer-money/csharp/Statement.cs:33-64 | samples/accounts/6-add-a-memo/csharp/Statement.cs:38-73 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) samples/accounts/4-show-a-statement/csharp/Program.cs:66— samples/accounts/4-show-a-statement/csharp/Program.cs:66-85 | samples/accounts/5-transfer-money/csharp/Program.cs:98-118 | samples/accounts/6-add-a-memo/csharp/Program.cs:116-137 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) samples/accounts/5-transfer-money/csharp/Program.cs:125— samples/accounts/5-transfer-money/csharp/Program.cs:125-135 | samples/accounts/6-add-a-memo/csharp/Program.cs:147-162 — 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) samples/orders/1-place-an-order/fsharp/Order.fs:2— samples/orders/1-place-an-order/fsharp/Order.fs:2-40 | samples/orders/2-retry-the-warehouse/fsharp/Order.fs:2-49 — 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 (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) scripts/check-accounts.py:18— scripts/check-accounts.py:18-24 | scripts/check-orders.py: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.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) samples/orders/4-wait-for-approval/csharp/Program.cs:41— samples/orders/4-wait-for-approval/csharp/Program.cs:41-49 | samples/orders/5-restart-during-shipping/csharp/Program.cs:44-52 | samples/orders/6-charge-the-customer/csharp/Program.cs:58-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) samples/accounts/5-transfer-money/csharp/Program.cs:75— samples/accounts/5-transfer-money/csharp/Program.cs:75-84 | samples/accounts/6-add-a-memo/csharp/Program.cs:78-86 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) samples/orders/6-charge-the-customer/csharp/Program.cs:132— samples/orders/6-charge-the-customer/csharp/Program.cs:132-137 | samples/orders/7-when-a-step-fails/csharp/Program.cs:162-167 | samples/orders/8-add-a-step/csharp/Program.cs:152-157 | samples/orders/9-guard-the-change/csharp/Program.cs:148-153 — 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.
Duplicated block (62–63 lines × 3) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:34— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:34-96 | samples/orders/8-add-a-step/fsharp/Order.fs:34-95 | samples/orders/9-guard-the-change/fsharp/Order.fs:34-96 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/8-add-a-step/fsharp/Order.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 239 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 `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs: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. 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 (63 lines × 2) samples/orders/8-add-a-step/fsharp/Program.fs:70— samples/orders/8-add-a-step/fsharp/Program.fs:70-132 | samples/orders/9-guard-the-change/fsharp/Program.fs:70-132 — before extracting anything, compare `samples/orders/8-add-a-step/fsharp/Program.fs` and `samples/orders/9-guard-the-change/fsharp/Program.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 301 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 `samples/orders/8-add-a-step/fsharp/Program.fs:70` 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 (55 lines × 2) samples/orders/1-place-an-order/fsharp/Program.fs:32— samples/orders/1-place-an-order/fsharp/Program.fs:32-86 | samples/orders/2-retry-the-warehouse/fsharp/Program.fs:39-93 — before extracting anything, compare `samples/orders/1-place-an-order/fsharp/Program.fs` and `samples/orders/2-retry-the-warehouse/fsharp/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 `samples/orders/1-place-an-order/fsharp/Program.fs:32` 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 (50 lines × 2) samples/orders/4-wait-for-approval/fsharp/Order.fs:50— samples/orders/4-wait-for-approval/fsharp/Order.fs:50-99 | samples/orders/5-restart-during-shipping/fsharp/Order.fs:50-99 — before extracting anything, compare `samples/orders/4-wait-for-approval/fsharp/Order.fs` and `samples/orders/5-restart-during-shipping/fsharp/Order.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 147 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 (48 lines × 2) samples/orders/6-charge-the-customer/fsharp/Program.fs:65— samples/orders/6-charge-the-customer/fsharp/Program.fs:65-112 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:73-120 — before extracting anything, compare `samples/orders/6-charge-the-customer/fsharp/Program.fs` and `samples/orders/7-when-a-step-fails/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 170 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 `samples/orders/6-charge-the-customer/fsharp/Program.fs:65` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (47 lines × 5) samples/orders/10-feed-orders-from-a-stream/fsharp/Account.fs:2— samples/orders/10-feed-orders-from-a-stream/fsharp/Account.fs:2-48 | samples/orders/6-charge-the-customer/fsharp/Account.fs:2-48 | samples/orders/7-when-a-step-fails/fsharp/Account.fs:2-48 | samples/orders/8-add-a-step/fsharp/Account.fs:2-48 | samples/orders/9-guard-the-change/fsharp/Account.fs:2-48 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Account.fs` and `samples/orders/6-charge-the-customer/fsharp/Account.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (43 lines × 3) samples/orders/3-read-the-clock/fsharp/Order.fs:19— samples/orders/3-read-the-clock/fsharp/Order.fs:19-61 | samples/orders/4-wait-for-approval/fsharp/Order.fs:20-62 | samples/orders/5-restart-during-shipping/fsharp/Order.fs:20-62 — before extracting anything, compare `samples/orders/3-read-the-clock/fsharp/Order.fs` and `samples/orders/4-wait-for-approval/fsharp/Order.fs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/orders/3-read-the-clock/fsharp/Order.fs:19` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (37–38 lines × 5) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:2— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:2-39 | samples/orders/6-charge-the-customer/fsharp/Order.fs:2-38 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:2-39 | samples/orders/8-add-a-step/fsharp/Order.fs:2-39 | samples/orders/9-guard-the-change/fsharp/Order.fs:2-39 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/6-charge-the-customer/fsharp/Order.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 103 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. 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 (34–36 lines × 2) samples/orders/3-read-the-clock/fsharp/Program.fs:37— samples/orders/3-read-the-clock/fsharp/Program.fs:37-70 | samples/orders/4-wait-for-approval/fsharp/Program.fs:37-72 — before extracting anything, compare `samples/orders/3-read-the-clock/fsharp/Program.fs` and `samples/orders/4-wait-for-approval/fsharp/Program.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 101 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 `samples/orders/3-read-the-clock/fsharp/Program.fs:37` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note 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 (65 lines × 3) samples/orders/7-when-a-step-fails/fsharp/Program.fs:16— samples/orders/7-when-a-step-fails/fsharp/Program.fs:16-80 | samples/orders/8-add-a-step/fsharp/Program.fs:16-80 | samples/orders/9-guard-the-change/fsharp/Program.fs:16-80 — before extracting anything, compare `samples/orders/7-when-a-step-fails/fsharp/Program.fs` and `samples/orders/8-add-a-step/fsharp/Program.fs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 238 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 `samples/orders/7-when-a-step-fails/fsharp/Program.fs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 3) samples/orders/7-when-a-step-fails/fsharp/Program.fs:115— samples/orders/7-when-a-step-fails/fsharp/Program.fs:115-147 | samples/orders/8-add-a-step/fsharp/Program.fs:127-159 | samples/orders/9-guard-the-change/fsharp/Program.fs:127-159 — before extracting anything, compare `samples/orders/7-when-a-step-fails/fsharp/Program.fs` and `samples/orders/8-add-a-step/fsharp/Program.fs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 238 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 (33 lines × 2) samples/orders/4-wait-for-approval/fsharp/Program.fs:66— samples/orders/4-wait-for-approval/fsharp/Program.fs:66-98 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:74-106 — before extracting anything, compare `samples/orders/4-wait-for-approval/fsharp/Program.fs` and `samples/orders/5-restart-during-shipping/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 130 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 (30 lines × 2) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:73— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:73-102 | samples/orders/9-guard-the-change/csharp/Order.cs:73-102 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs` and `samples/orders/9-guard-the-change/csharp/Order.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 127 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 `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–27 lines × 5) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:114— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:114-140 | samples/orders/6-charge-the-customer/fsharp/Order.fs:89-113 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:92-118 | samples/orders/8-add-a-step/fsharp/Order.fs:107-133 | samples/orders/9-guard-the-change/fsharp/Order.fs:114-140 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/6-charge-the-customer/fsharp/Order.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 103 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 `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:114` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note 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 (26 lines × 3) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:94— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:94-119 | samples/orders/8-add-a-step/csharp/Order.cs:91-116 | samples/orders/9-guard-the-change/csharp/Order.cs:94-119 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs` and `samples/orders/8-add-a-step/csharp/Order.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 97 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 `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs: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 (43–45 lines × 3) samples/accounts/2-withdraw-money/fsharp/Account.fs:2— samples/accounts/2-withdraw-money/fsharp/Account.fs:2-46 | samples/accounts/3-restart-the-bank/fsharp/Account.fs:1-43 | samples/accounts/4-show-a-statement/fsharp/Account.fs:1-43 — before extracting anything, compare `samples/accounts/2-withdraw-money/fsharp/Account.fs` and `samples/accounts/3-restart-the-bank/fsharp/Account.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (47–48 lines × 4) samples/orders/6-charge-the-customer/fsharp/Program.fs:73— samples/orders/6-charge-the-customer/fsharp/Program.fs:73-119 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:81-127 | samples/orders/8-add-a-step/fsharp/Program.fs:92-139 | samples/orders/9-guard-the-change/fsharp/Program.fs:92-139 — before extracting anything, compare `samples/orders/6-charge-the-customer/fsharp/Program.fs` and `samples/orders/7-when-a-step-fails/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 170 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 `samples/orders/6-charge-the-customer/fsharp/Program.fs:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24 lines × 2) samples/accounts/4-show-a-statement/fsharp/Statement.fs:27— samples/accounts/4-show-a-statement/fsharp/Statement.fs:27-50 | samples/accounts/5-transfer-money/fsharp/Statement.fs:24-47 — before extracting anything, compare `samples/accounts/4-show-a-statement/fsharp/Statement.fs` and `samples/accounts/5-transfer-money/fsharp/Statement.fs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/accounts/4-show-a-statement/fsharp/Statement.fs:27` 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, `samples/accounts/5-transfer-money/fsharp/Statement.fs:48` calls `TransferSent`, `TransferReceived`, `TransferRefunded` and `samples/accounts/4-show-a-statement/fsharp/Statement.fs:52` 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 (22–23 lines × 4) samples/orders/6-charge-the-customer/fsharp/Program.fs:39— samples/orders/6-charge-the-customer/fsharp/Program.fs:39-60 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:43-65 | samples/orders/8-add-a-step/fsharp/Program.fs:43-65 | samples/orders/9-guard-the-change/fsharp/Program.fs:43-65 — before extracting anything, compare `samples/orders/6-charge-the-customer/fsharp/Program.fs` and `samples/orders/7-when-a-step-fails/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 170 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 `samples/orders/6-charge-the-customer/fsharp/Program.fs:39` 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–23 lines × 2) samples/accounts/2-withdraw-money/fsharp/Program.fs:1— samples/accounts/2-withdraw-money/fsharp/Program.fs:1-22 | samples/accounts/3-restart-the-bank/fsharp/Program.fs:1-23 — 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 (23 lines × 2) samples/accounts/5-transfer-money/fsharp/Transfer.fs:64— samples/accounts/5-transfer-money/fsharp/Transfer.fs:64-86 | samples/accounts/6-add-a-memo/fsharp/Transfer.fs:72-94 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Transfer.fs` and `samples/accounts/6-add-a-memo/fsharp/Transfer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 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 `samples/accounts/5-transfer-money/fsharp/Transfer.fs:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 7) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:13— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:13-34 | samples/orders/4-wait-for-approval/fsharp/Order.fs:11-31 | samples/orders/5-restart-during-shipping/fsharp/Order.fs:11-31 | samples/orders/6-charge-the-customer/fsharp/Order.fs:13-34 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:13-34 | samples/orders/8-add-a-step/fsharp/Order.fs:13-34 | samples/orders/9-guard-the-change/fsharp/Order.fs:13-34 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/6-charge-the-customer/fsharp/Order.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 103 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 `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:13` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note 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–22 lines × 4) samples/orders/4-wait-for-approval/csharp/Order.cs:45— samples/orders/4-wait-for-approval/csharp/Order.cs:45-60 | samples/orders/5-restart-during-shipping/csharp/Order.cs:45-60 | samples/orders/6-charge-the-customer/csharp/Order.cs:47-68 | samples/orders/7-when-a-step-fails/csharp/Order.cs:65-85 — before extracting anything, compare `samples/orders/4-wait-for-approval/csharp/Order.cs` and `samples/orders/5-restart-during-shipping/csharp/Order.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/orders/4-wait-for-approval/csharp/Order.cs:45` 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 (21 lines × 2) samples/accounts/4-show-a-statement/csharp/Statement.cs:37— samples/accounts/4-show-a-statement/csharp/Statement.cs:37-57 | samples/accounts/5-transfer-money/csharp/Statement.cs:34-54 — before extracting anything, compare `samples/accounts/4-show-a-statement/csharp/Statement.cs` and `samples/accounts/5-transfer-money/csharp/Statement.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/accounts/4-show-a-statement/csharp/Statement.cs:37` 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–20 lines × 5) samples/orders/5-restart-during-shipping/csharp/Program.cs:118— samples/orders/5-restart-during-shipping/csharp/Program.cs:118-131 | samples/orders/6-charge-the-customer/csharp/Program.cs:149-162 | samples/orders/7-when-a-step-fails/csharp/Program.cs:180-199 | samples/orders/8-add-a-step/csharp/Program.cs:170-189 | samples/orders/9-guard-the-change/csharp/Program.cs:166-185 — before extracting anything, compare `samples/orders/5-restart-during-shipping/csharp/Program.cs` and `samples/orders/6-charge-the-customer/csharp/Program.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 4) samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs:116— samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs:116-134 | samples/orders/7-when-a-step-fails/csharp/Program.cs:104-122 | samples/orders/8-add-a-step/csharp/Program.cs:94-112 | samples/orders/9-guard-the-change/csharp/Program.cs:90-108 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs` and `samples/orders/7-when-a-step-fails/csharp/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) samples/accounts/1-open-an-account/fsharp/Program.fs:15— samples/accounts/1-open-an-account/fsharp/Program.fs:15-34 | samples/accounts/2-withdraw-money/fsharp/Program.fs:14-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17–19 lines × 10) samples/orders/1-place-an-order/fsharp/Program.fs:11— samples/orders/1-place-an-order/fsharp/Program.fs:11-27 | samples/orders/10-feed-orders-from-a-stream/fsharp/Program.fs:16-34 | samples/orders/2-retry-the-warehouse/fsharp/Program.fs:11-27 | samples/orders/3-read-the-clock/fsharp/Program.fs:12-28 | samples/orders/4-wait-for-approval/fsharp/Program.fs:12-28 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:12-28 | samples/orders/6-charge-the-customer/fsharp/Program.fs:14-30 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:14-31 | samples/orders/8-add-a-step/fsharp/Program.fs:14-31 | samples/orders/9-guard-the-change/fsharp/Program.fs:14-31 — before extracting anything, compare `samples/orders/1-place-an-order/fsharp/Program.fs` and `samples/orders/2-retry-the-warehouse/fsharp/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 (14–19 lines × 8) samples/orders/2-retry-the-warehouse/csharp/Program.cs:83— samples/orders/2-retry-the-warehouse/csharp/Program.cs:83-96 | samples/orders/3-read-the-clock/csharp/Program.cs:101-114 | samples/orders/4-wait-for-approval/csharp/Program.cs:94-107 | samples/orders/5-restart-during-shipping/csharp/Program.cs:92-105 | samples/orders/6-charge-the-customer/csharp/Program.cs:115-128 | samples/orders/7-when-a-step-fails/csharp/Program.cs:140-158 | samples/orders/8-add-a-step/csharp/Program.cs:130-148 | samples/orders/9-guard-the-change/csharp/Program.cs:126-144 — before extracting anything, compare `samples/orders/2-retry-the-warehouse/csharp/Program.cs` and `samples/orders/3-read-the-clock/csharp/Program.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 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 `samples/orders/2-retry-the-warehouse/csharp/Program.cs:83` 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 (19 lines × 6) samples/orders/1-place-an-order/fsharp/Program.fs:80— samples/orders/1-place-an-order/fsharp/Program.fs:80-98 | samples/orders/2-retry-the-warehouse/fsharp/Program.fs:87-105 | samples/orders/3-read-the-clock/fsharp/Program.fs:118-136 | samples/orders/4-wait-for-approval/fsharp/Program.fs:112-130 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:115-133 | samples/orders/6-charge-the-customer/fsharp/Program.fs:155-173 — before extracting anything, compare `samples/orders/1-place-an-order/fsharp/Program.fs` and `samples/orders/2-retry-the-warehouse/fsharp/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 (19 lines × 3) samples/accounts/4-show-a-statement/fsharp/Program.fs:15— samples/accounts/4-show-a-statement/fsharp/Program.fs:15-33 | samples/accounts/5-transfer-money/fsharp/Program.fs:16-34 | samples/accounts/6-add-a-memo/fsharp/Program.fs:30-48 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Program.fs` and `samples/accounts/6-add-a-memo/fsharp/Program.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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 `samples/accounts/4-show-a-statement/fsharp/Program.fs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) samples/accounts/5-transfer-money/fsharp/Transfer.fs:15— samples/accounts/5-transfer-money/fsharp/Transfer.fs:15-33 | samples/accounts/6-add-a-memo/fsharp/Transfer.fs:17-35 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Transfer.fs` and `samples/accounts/6-add-a-memo/fsharp/Transfer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 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 `samples/accounts/5-transfer-money/fsharp/Transfer.fs:15` 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 (17 lines × 6) samples/orders/1-place-an-order/csharp/Program.cs:53— samples/orders/1-place-an-order/csharp/Program.cs:53-69 | samples/orders/2-retry-the-warehouse/csharp/Program.cs:53-69 | samples/orders/3-read-the-clock/csharp/Program.cs:71-87 | samples/orders/4-wait-for-approval/csharp/Program.cs:64-80 | samples/orders/5-restart-during-shipping/csharp/Program.cs:62-78 | samples/orders/6-charge-the-customer/csharp/Program.cs:84-100 — before extracting anything, compare `samples/orders/1-place-an-order/csharp/Program.cs` and `samples/orders/2-retry-the-warehouse/csharp/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 4) samples/orders/10-feed-orders-from-a-stream/fsharp/Program.fs:188— samples/orders/10-feed-orders-from-a-stream/fsharp/Program.fs:188-205 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:177-194 | samples/orders/8-add-a-step/fsharp/Program.fs:177-194 | samples/orders/9-guard-the-change/fsharp/Program.fs:179-196 — before extracting anything, compare `samples/orders/7-when-a-step-fails/fsharp/Program.fs` and `samples/orders/8-add-a-step/fsharp/Program.fs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 238 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 (16–17 lines × 5) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:109— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:109-125 | samples/orders/6-charge-the-customer/csharp/Order.cs:74-89 | samples/orders/7-when-a-step-fails/csharp/Order.cs:91-107 | samples/orders/8-add-a-step/csharp/Order.cs:106-122 | samples/orders/9-guard-the-change/csharp/Order.cs:109-125 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs` and `samples/orders/6-charge-the-customer/csharp/Order.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 4) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:46— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:46-62 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:40-56 | samples/orders/8-add-a-step/fsharp/Order.fs:46-62 | samples/orders/9-guard-the-change/fsharp/Order.fs:46-62 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/7-when-a-step-fails/fsharp/Order.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 176 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 × 3) samples/orders/4-wait-for-approval/fsharp/Program.fs:82— samples/orders/4-wait-for-approval/fsharp/Program.fs:82-98 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:90-106 | samples/orders/6-charge-the-customer/fsharp/Program.fs:122-138 — before extracting anything, compare `samples/orders/4-wait-for-approval/fsharp/Program.fs` and `samples/orders/5-restart-during-shipping/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 130 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 `samples/orders/4-wait-for-approval/fsharp/Program.fs:82` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9–16 lines × 4) samples/orders/3-read-the-clock/fsharp/Order.fs:35— samples/orders/3-read-the-clock/fsharp/Order.fs:35-43 | samples/orders/4-wait-for-approval/fsharp/Order.fs:36-44 | samples/orders/5-restart-during-shipping/fsharp/Order.fs:36-44 | samples/orders/6-charge-the-customer/fsharp/Order.fs:39-54 — before extracting anything, compare `samples/orders/3-read-the-clock/fsharp/Order.fs` and `samples/orders/4-wait-for-approval/fsharp/Order.fs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (15 lines × 3) samples/orders/7-when-a-step-fails/csharp/Program.cs:60— samples/orders/7-when-a-step-fails/csharp/Program.cs:60-74 | samples/orders/8-add-a-step/csharp/Program.cs:60-74 | samples/orders/9-guard-the-change/csharp/Program.cs:60-74 — before extracting anything, compare `samples/orders/7-when-a-step-fails/csharp/Program.cs` and `samples/orders/8-add-a-step/csharp/Program.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15–16 lines × 3) samples/orders/3-read-the-clock/fsharp/Program.fs:36— samples/orders/3-read-the-clock/fsharp/Program.fs:36-50 | samples/orders/4-wait-for-approval/fsharp/Program.fs:36-50 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:36-51 — before extracting anything, compare `samples/orders/3-read-the-clock/fsharp/Program.fs` and `samples/orders/4-wait-for-approval/fsharp/Program.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 101 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 `samples/orders/3-read-the-clock/fsharp/Program.fs:36` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note 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) samples/orders/4-wait-for-approval/fsharp/Order.fs:62— samples/orders/4-wait-for-approval/fsharp/Order.fs:62-77 | samples/orders/5-restart-during-shipping/fsharp/Order.fs:62-77 | samples/orders/6-charge-the-customer/fsharp/Order.fs:80-95 — before extracting anything, compare `samples/orders/4-wait-for-approval/fsharp/Order.fs` and `samples/orders/5-restart-during-shipping/fsharp/Order.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 147 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 `samples/orders/6-charge-the-customer/fsharp/Order.fs:80` 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 (15 lines × 7) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:70— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:70-87 | samples/orders/4-wait-for-approval/csharp/Order.cs:42-56 | samples/orders/5-restart-during-shipping/csharp/Order.cs:42-56 | samples/orders/6-charge-the-customer/csharp/Order.cs:44-64 | samples/orders/7-when-a-step-fails/csharp/Order.cs:62-81 | samples/orders/8-add-a-step/csharp/Order.cs:70-87 | samples/orders/9-guard-the-change/csharp/Order.cs:70-87 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs` and `samples/orders/6-charge-the-customer/csharp/Order.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 6) samples/orders/4-wait-for-approval/fsharp/Program.fs:83— samples/orders/4-wait-for-approval/fsharp/Program.fs:83-97 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:91-105 | samples/orders/6-charge-the-customer/fsharp/Program.fs:123-137 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:131-145 | samples/orders/8-add-a-step/fsharp/Program.fs:143-157 | samples/orders/9-guard-the-change/fsharp/Program.fs:143-157 — before extracting anything, compare `samples/orders/4-wait-for-approval/fsharp/Program.fs` and `samples/orders/5-restart-during-shipping/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 130 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 `samples/orders/4-wait-for-approval/fsharp/Program.fs:83` 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 (10–13 lines × 2) samples/accounts/5-transfer-money/fsharp/Program.fs:63— samples/accounts/5-transfer-money/fsharp/Program.fs:63-72 | samples/accounts/6-add-a-memo/fsharp/Program.fs:79-91 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Program.fs` and `samples/accounts/6-add-a-memo/fsharp/Program.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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. 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 (12 lines × 5) samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:80— samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs:80-91 | samples/orders/6-charge-the-customer/fsharp/Order.fs:69-84 | samples/orders/7-when-a-step-fails/fsharp/Order.fs:73-87 | samples/orders/8-add-a-step/fsharp/Order.fs:80-91 | samples/orders/9-guard-the-change/fsharp/Order.fs:80-91 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/fsharp/Order.fs` and `samples/orders/6-charge-the-customer/fsharp/Order.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 103 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. 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 (12 lines × 3) samples/accounts/2-withdraw-money/csharp/Account.cs:34— samples/accounts/2-withdraw-money/csharp/Account.cs:34-45 | samples/accounts/3-restart-the-bank/csharp/Account.cs:35-46 | samples/accounts/4-show-a-statement/csharp/Account.cs:31-42 — before extracting anything, compare `samples/accounts/2-withdraw-money/csharp/Account.cs` and `samples/accounts/3-restart-the-bank/csharp/Account.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/accounts/3-restart-the-bank/csharp/Account.cs:29` calls `NewEvery` and `samples/accounts/2-withdraw-money/csharp/Account.cs:29` 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 × 8) samples/orders/2-retry-the-warehouse/fsharp/Program.fs:33— samples/orders/2-retry-the-warehouse/fsharp/Program.fs:33-43 | samples/orders/3-read-the-clock/fsharp/Program.fs:34-44 | samples/orders/4-wait-for-approval/fsharp/Program.fs:34-44 | samples/orders/5-restart-during-shipping/fsharp/Program.fs:34-44 | samples/orders/6-charge-the-customer/fsharp/Program.fs:37-47 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:41-51 | samples/orders/8-add-a-step/fsharp/Program.fs:41-51 | samples/orders/9-guard-the-change/fsharp/Program.fs:41-51 — before extracting anything, compare `samples/orders/2-retry-the-warehouse/fsharp/Program.fs` and `samples/orders/3-read-the-clock/fsharp/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 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 (11 lines × 5) samples/orders/10-feed-orders-from-a-stream/csharp/Account.cs:35— samples/orders/10-feed-orders-from-a-stream/csharp/Account.cs:35-45 | samples/orders/6-charge-the-customer/csharp/Account.cs:35-45 | samples/orders/7-when-a-step-fails/csharp/Account.cs:35-45 | samples/orders/8-add-a-step/csharp/Account.cs:35-45 | samples/orders/9-guard-the-change/csharp/Account.cs:35-45 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Account.cs` and `samples/orders/6-charge-the-customer/csharp/Account.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 10) samples/orders/1-place-an-order/csharp/Program.cs:62— samples/orders/1-place-an-order/csharp/Program.cs:62-69 | samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs:127-134 | samples/orders/2-retry-the-warehouse/csharp/Program.cs:62-69 | samples/orders/3-read-the-clock/csharp/Program.cs:80-87 | samples/orders/4-wait-for-approval/csharp/Program.cs:73-80 | samples/orders/5-restart-during-shipping/csharp/Program.cs:71-78 | samples/orders/6-charge-the-customer/csharp/Program.cs:93-100 | samples/orders/7-when-a-step-fails/csharp/Program.cs:115-122 | samples/orders/8-add-a-step/csharp/Program.cs:105-112 | samples/orders/9-guard-the-change/csharp/Program.cs:101-108 — before extracting anything, compare `samples/orders/1-place-an-order/csharp/Program.cs` and `samples/orders/2-retry-the-warehouse/csharp/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 `samples/orders/1-place-an-order/csharp/Program.cs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/orders/10-feed-orders-from-a-stream/csharp/Program.cs:136` calls `PrintJournal` and `samples/orders/1-place-an-order/csharp/Program.cs:71` 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 × 3) samples/accounts/2-withdraw-money/fsharp/Account.fs:23— samples/accounts/2-withdraw-money/fsharp/Account.fs:23-31 | samples/accounts/5-transfer-money/fsharp/Account.fs:42-50 | samples/accounts/6-add-a-memo/fsharp/Account.fs:53-61 — before extracting anything, compare `samples/accounts/5-transfer-money/fsharp/Account.fs` and `samples/accounts/6-add-a-memo/fsharp/Account.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 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 `samples/accounts/5-transfer-money/fsharp/Account.fs:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 9) samples/orders/1-place-an-order/csharp/Program.cs:83— samples/orders/1-place-an-order/csharp/Program.cs:83-90 | samples/orders/2-retry-the-warehouse/csharp/Program.cs:90-97 | samples/orders/3-read-the-clock/csharp/Program.cs:108-115 | samples/orders/4-wait-for-approval/csharp/Program.cs:101-108 | samples/orders/5-restart-during-shipping/csharp/Program.cs:99-106 | samples/orders/6-charge-the-customer/csharp/Program.cs:122-129 | samples/orders/7-when-a-step-fails/csharp/Program.cs:152-159 | samples/orders/8-add-a-step/csharp/Program.cs:142-149 | samples/orders/9-guard-the-change/csharp/Program.cs:138-145 — before extracting anything, compare `samples/orders/1-place-an-order/csharp/Program.cs` and `samples/orders/2-retry-the-warehouse/csharp/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 `samples/orders/2-retry-the-warehouse/csharp/Program.cs:90` 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 (6 lines × 5) samples/accounts/2-withdraw-money/csharp/Account.cs:39— samples/accounts/2-withdraw-money/csharp/Account.cs:39-44 | samples/accounts/3-restart-the-bank/csharp/Account.cs:40-45 | samples/accounts/4-show-a-statement/csharp/Account.cs:36-41 | samples/accounts/5-transfer-money/csharp/Account.cs:62-67 | samples/accounts/6-add-a-memo/csharp/Account.cs:65-70 — before extracting anything, compare `samples/accounts/2-withdraw-money/csharp/Account.cs` and `samples/accounts/3-restart-the-bank/csharp/Account.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `samples/accounts/5-transfer-money/csharp/Account.cs:62` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 lines × 4) samples/orders/6-charge-the-customer/fsharp/Program.fs:31— samples/orders/6-charge-the-customer/fsharp/Program.fs:31-36 | samples/orders/7-when-a-step-fails/fsharp/Program.fs:32-37 | samples/orders/8-add-a-step/fsharp/Program.fs:32-37 | samples/orders/9-guard-the-change/fsharp/Program.fs:32-37 — before extracting anything, compare `samples/orders/6-charge-the-customer/fsharp/Program.fs` and `samples/orders/7-when-a-step-fails/fsharp/Program.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 170 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 `samples/orders/6-charge-the-customer/fsharp/Program.fs: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 (6 lines × 3) samples/orders/1-place-an-order/csharp/Program.cs:32— samples/orders/1-place-an-order/csharp/Program.cs:32-37 | samples/orders/2-retry-the-warehouse/csharp/Program.cs:32-37 | samples/orders/3-read-the-clock/csharp/Program.cs:34-39 — before extracting anything, compare `samples/orders/1-place-an-order/csharp/Program.cs` and `samples/orders/2-retry-the-warehouse/csharp/Program.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 5) samples/orders/10-feed-orders-from-a-stream/csharp/Account.cs:50— samples/orders/10-feed-orders-from-a-stream/csharp/Account.cs:50-62 | samples/orders/6-charge-the-customer/csharp/Account.cs:50-62 | samples/orders/7-when-a-step-fails/csharp/Account.cs:50-62 | samples/orders/8-add-a-step/csharp/Account.cs:50-62 | samples/orders/9-guard-the-change/csharp/Account.cs:50-62 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Account.cs` and `samples/orders/6-charge-the-customer/csharp/Account.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 4) samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:53— samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:53-66 | samples/orders/7-when-a-step-fails/csharp/Order.cs:45-58 | samples/orders/8-add-a-step/csharp/Order.cs:53-66 | samples/orders/9-guard-the-change/csharp/Order.cs:53-66 — before extracting anything, compare `samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs` and `samples/orders/7-when-a-step-fails/csharp/Order.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 6) samples/orders/4-wait-for-approval/csharp/Program.cs:32— samples/orders/4-wait-for-approval/csharp/Program.cs:32-37 | samples/orders/5-restart-during-shipping/csharp/Program.cs:35-40 | samples/orders/6-charge-the-customer/csharp/Program.cs:49-54 | samples/orders/7-when-a-step-fails/csharp/Program.cs:49-54 | samples/orders/8-add-a-step/csharp/Program.cs:49-54 | samples/orders/9-guard-the-change/csharp/Program.cs:49-54 — before extracting anything, compare `samples/orders/4-wait-for-approval/csharp/Program.cs` and `samples/orders/5-restart-during-shipping/csharp/Program.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 4) samples/orders/6-charge-the-customer/csharp/Program.cs:133— samples/orders/6-charge-the-customer/csharp/Program.cs:133-137 | samples/orders/7-when-a-step-fails/csharp/Program.cs:163-167 | samples/orders/8-add-a-step/csharp/Program.cs:153-157 | samples/orders/9-guard-the-change/csharp/Program.cs:149-153 — before extracting anything, compare `samples/orders/6-charge-the-customer/csharp/Program.cs` and `samples/orders/7-when-a-step-fails/csharp/Program.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10–12 lines × 2) scripts/check-orders.py:188— scripts/check-orders.py:188-199 | scripts/check-orders.py:218-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 `scripts/check-orders.py:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) scripts/check-orders.py:191— scripts/check-orders.py:191-200 | scripts/check-orders.py:220-228 | scripts/check-orders.py:239-247 — 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 `scripts/check-orders.py:191` 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.
Sync-over-async blocking saga_sample/Program.fs:47— `(module-level async block)` holds an async function that calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 19 finding(s)
S1 · Web-Security Posture· No inbound model validation detected · ×5
No inbound model validation detected — No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
No inbound model validation detected samples/accounts/serve-over-http/csharp/Program.cs:74— `MapPost("/accounts/{id}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
No inbound model validation detected samples/accounts/serve-over-http/csharp/Program.cs:79— `MapPost("/accounts/{id}/deposits")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
No inbound model validation detected samples/accounts/serve-over-http/csharp/Program.cs:83— `MapPost("/accounts/{id}/withdrawals")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
No inbound model validation detected samples/accounts/serve-over-http/csharp/Program.cs:91— `MapGet("/accounts/{id}/statement")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
No security response headers detected — 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. (−2.0 on this card.)
No security response headers detected samples/accounts/serve-over-http/csharp/Program.cs:11— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
No app-layer HTTPS enforcement detected samples/accounts/serve-over-http/csharp/Program.cs:11— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `design/specs/2026-11-10-fcqrs-workflows-design.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
No SAST REDACTED:10— No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation .livedocs/examples/Examples.fsproj:11— `.livedocs/examples/Examples.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Duplicated predicate samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs:92— `change < 2 || await ctx.Activity("check-fraud", Retry.times(3), attempt => fraud.Check( attempt.IdempotencyKey, request.Customer, total))` appears character-identically in 2 files — samples/orders/10-feed-orders-from-a-stream/csharp/Order.cs, samples/orders/9-guard-the-change/csharp/Order.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.3 `!` suppressions per 1k syntax nodes — 8 suppression(s) across the 30085 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated: Akka — Akka 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Cluster — Akka.Cluster 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Cluster.Sharding — Akka.Cluster.Sharding 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Cluster.Tools — Akka.Cluster.Tools 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Coordination — Akka.Coordination 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Discovery — Akka.Discovery 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.DistributedData — Akka.DistributedData 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.DistributedData.LightningDB — Akka.DistributedData.LightningDB 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Persistence — Akka.Persistence 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Persistence.Query — Akka.Persistence.Query 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Persistence.Sql — Akka.Persistence.Sql 1.5.59 → 1.5.73 available (referenced by FCQRS).
Outdated: Akka.Remote — Akka.Remote 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Serialization.Hyperion — Akka.Serialization.Hyperion 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.Streams — Akka.Streams 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akka.TestKit — Akka.TestKit 1.5.59 → 1.5.74 available (referenced by FCQRS).
Outdated: Akkling — Akkling 0.17.0 → 0.18.1 available (referenced by FCQRS).
Outdated: Akkling.Cluster.Sharding — Akkling.Cluster.Sharding 0.17.0 → 0.18.1 available (referenced by FCQRS).
Outdated: Akkling.DistributedData — Akkling.DistributedData 0.17.0 → 0.18.1 available (referenced by FCQRS).
Outdated: Akkling.Persistence — Akkling.Persistence 0.17.0 → 0.18.1 available (referenced by FCQRS).
Outdated: Akkling.Streams — Akkling.Streams 0.17.0 → 0.18.1 available (referenced by FCQRS).
Outdated: Fable.Package.SDK — Fable.Package.SDK 1.3.2 → 1.4.1 available (referenced by FCQRS).
Outdated: FluentAssertions — FluentAssertions 8.8.0 → 8.11.0 available (referenced by FCQRS).
Outdated: FSharp.Core — FSharp.Core 10.0.102 → 11.0.101 available (referenced by FCQRS).
Outdated: FSharp.Interop.Dynamic — FSharp.Interop.Dynamic 5.0.1.268 → 7.0.0 available (referenced by FCQRS).
Outdated: FsToolkit.ErrorHandling — FsToolkit.ErrorHandling 5.1.0 → 5.2.0 available (referenced by FCQRS).
+ 41 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1deac-46bd-71ac-a51e-e2f06243f06f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 11 · Warnings: 207 · Recommendations: 19 · Info: 66 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 10:06 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.