Public report of tonyx/Sharpino, published 9 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). 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, 9 November 2026, 11:32 UTC · Survey ID cd_bf6baa24b98a4fff85fb1f95e508c205

tonyx/Sharpino

Measured 9 November 2026, 11:31 UTC, at code version 9dacedd

Code coverage is not measured: No coverage collector is wired up.

Test reliability is not measured: No test run produced results.

CAI score 46out of 100 At risk Up 1 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,919 lines of product code in 36 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 32

Findings by how serious they are

27 critical 550 serious 30 minor

37 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
9 November 2026, 11:31 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

41of 41 dimensions measured by tools.
591of 607 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
41dimensions across 6 lenses, read from 26,919 lines of product code in 36 projects.
Chapters

Executive summary

tonyx/Sharpino is rated At risk because critical security findings are open. Its score is held back because eight passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 46 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 32, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 12 points. Adding an automated build and test pipeline comes next, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 58.

Ten known security holes in the packages the code depends on can be used by attackers. Eight passwords or keys in the code and three in the code's history are open to anyone who can read the repository, and two settings leave the servers or containers unsafe. Updating the vulnerable packages, replacing each exposed password or key and correcting the unsafe settings would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The three pieces of product code that depend on test code need their reference to the test project removed.

The product code is 26,919 lines, about €41,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 for The 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.
Production Readiness 32 · counts for 46%Maturity 50 · counts for 25%Performance 60 · counts for 14%Code Health 64 · counts for 8%Architecture 69 · counts for 4%Security and Compliance 84 · counts for 2%

If Production Readiness rose from 32 to 70, the lowest score rated Strong, the score would rise from 46 to about 58.

Code composition: what the lines of code are
Product code 58%Tests 42%
New since the last survey: 57 findings

These 57 critical or serious findings weren't in the previous survey, on 22 October 2026.

  • Cyclomatic Complexity · AggregateCache3.SetupL2AndBackplane (cyclomatic 19) Sharpino.Lib/Cache.fs
  • Cyclomatic Complexity · Sanitizer.sanitizeAggregateStreamWithInitialState (cyclomatic 18) Sharpino.Lib/Sanitizer.fs
  • Cognitive Complexity · Sanitizer.sanitizeAggregateStreamWithInitialState (cognitive 34) Sharpino.Lib/Sanitizer.fs
  • Code Duplication · Near-duplicate member pair (2341 shared lines) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) Sharpino.Sample.22/Domain/Todo/Events.fs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) Sharpino.Sample.22/Domain/User/Events.fs
  • Code Duplication · Duplicated block (44–46 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (31 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Events.fs
  • Code Duplication · Duplicated block (23–24 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (19–22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (20–21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (18 lines × 2) Sharpino.Lib/Cache.fs
  • Code Duplication · Duplicated block (17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs
  • Code Duplication · Duplicated block (16 lines × 2) Sharpino.Lib/Sanitizer.fs
  • Code Duplication · Duplicated block (16 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs
  • Code Duplication · Duplicated block (15 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (15 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs
  • Code Duplication · Duplicated block (12–14 lines × 2) Sharpino.Lib/MemoryStorage.fs
  • Code Duplication · Duplicated block (13–14 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (13 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (12–13 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (11–12 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (4–12 lines × 3) Sharpino.Lib/Sanitizer.fs
  • Code Duplication · Duplicated block (11 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (10–11 lines × 2) Sharpino.Lib/PgEventStore.fs
  • Code Duplication · Duplicated block (11 lines × 2) Sharpino.Sample.11/Models/Student/Events.fs
  • Code Duplication · Duplicated block (11 lines × 2) Sharpino.Sample.12/Models/Student/Events.fs
  • Code Duplication · Duplicated block (10 lines × 6) Sharpino.Sample.22/Domain/Todo/Events.fs
  • Code Duplication · Duplicated block (10 lines × 5) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (10 lines × 2) Sharpino.Sample.11/Models/Course/Events.fs
  • Code Duplication · Duplicated block (10 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs
  • Code Duplication · Duplicated block (9 lines × 3) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (9 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (9 lines × 2) Sharpino.Lib/StateView.fs
  • Code Duplication · Duplicated block (8 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (8 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (7 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (6 lines × 5) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (6 lines × 2) Sharpino.Lib/Sanitizer.fs
  • Code Duplication · Duplicated block (6 lines × 2) Sharpino.Lib/Sanitizer.fs
  • Code Duplication · Duplicated block (5 lines × 7) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (5 lines × 5) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (5 lines × 3) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (5 lines × 3) Sharpino.Lib/StateView.fs
  • Code Duplication · Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (30 lines × 2) Sharpino.Sample.15/Models/Course/Events.fs
  • Code Duplication · Duplicated block (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (11 lines × 2) Sharpino.Lib/PgEventStore.fs
  • Code Duplication · Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs
  • Cohesion (LCOM4) · Low cohesion: PgBinaryStore (LCOM4 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Cohesion (LCOM4) · Low cohesion: PgEventStore (LCOM4 4) Sharpino.Lib/PgEventStore.fs

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: 37 findings

These 37 critical or serious findings were in the previous survey, on 22 October 2026, and are gone from this one.

  • Code Duplication · Near-duplicate member pair (2304 shared lines) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) Sharpino.Sample.22/Domain/Todo/Events.fs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) Sharpino.Sample.22/Domain/User/Events.fs
  • Code Duplication · Duplicated block (41–43 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (28 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Events.fs
  • Code Duplication · Duplicated block (25–27 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (19–24 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (23–24 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (19–20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs
  • Code Duplication · Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs
  • Code Duplication · Duplicated block (13 lines × 2) Sharpino.Lib/StateView.fs
  • Code Duplication · Duplicated block (13 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs
  • Code Duplication · Duplicated block (10 lines × 4) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (8 lines × 8) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (8 lines × 6) Sharpino.Sample.22/Domain/Todo/Events.fs
  • Code Duplication · Duplicated block (8 lines × 2) Sharpino.Sample.11/Models/Course/Events.fs
  • Code Duplication · Duplicated block (8 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs
  • Code Duplication · Duplicated block (7 lines × 2) Sharpino.Lib/StateView.fs
  • Code Duplication · Duplicated block (6 lines × 4) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (5 lines × 6) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (4–5 lines × 3) Sharpino.Lib/CommandHandler.fs
  • Code Duplication · Duplicated block (28 lines × 2) Sharpino.Sample.15/Models/Course/Events.fs
  • Code Duplication · Duplicated block (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Duplication · Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs
  • Code Coverage · Coverage not measured — no coverage collector is wired up
  • Change Coupling · Change-coupling hub: Events.fs → AppVersions.fs, Commands.fs, Context.fs, Events.fs Sharpino.Sample/Domain/Categories/Events.fs
  • Change Coupling · Change-coupling hub: Events.fs → AppVersions.fs, Commands.fs, Context.fs, Events.fs, Commands.fs, Context.fs, Events.fs Sharpino.Sample/Domain/Todos/Events.fs
  • Change Coupling · Change-coupling hub: Commands.fs → AppVersions.fs, Commands.fs, Context.fs, Events.fs, Commands.fs Sharpino.Sample/Domain/Categories/Commands.fs
  • Change Coupling · Change coupling: Commands.fs ↔ Commands.fs Sharpino.Sample/Domain/Tags/Commands.fs
  • Change Coupling · Change-coupling hub: Events.fs → AppVersions.fs, Context.fs, Commands.fs Sharpino.Sample/Domain/Tags/Events.fs
  • Change Coupling · Change coupling: AppVersions.fs ↔ Commands.fs Sharpino.Sample/AppVersions.fs
  • Platform End-of-Life · End-of-life runtime: .NET net9.0 REDACTED
Rebuild cost: about €41,000 · Estimate
Cost to rebuild€14,000 to €69,000, for 228 to 722 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemStandard, 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 46. 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.
SizeMedium: 26,919 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2).
Raises the score by about 12 points · Low effort · REDACTED Scanning
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 7 points · Medium effort · CI/CD gates
3
Run 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) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Raises the score by about 7 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €41,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 32 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for low effort, because it clears the 8 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 16,738 lines over the last 90 days, which is about 67,882 lines a year. At that pace, the extra work comes to an estimated 6.7 to 40.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.

arch App App Sharpino.Lib.Core Core

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.

230 modules, with 143 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 190 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.
uses →1 Sharpino.Cache2 Sharpino.Core3 Sharpino.EventBroker4 Sharpino.Sample.Saga.Domain.Booking.Booking5 Sharpino.Sample.Saga.Domain.Seat.Row6 Sharpino.Sample.Saga.Domain.Vaucher.Voucher7 Sharpino.Sample.Shared.Entities8 Sharpino.Sample._10.Models.Counter9 Sharpino.Sample._11.CourseManager10 Sharpino.Storage11 Sharpino.Template.Commons12 seatsLockWithSharpino.Seats13 AsyncTests14 BulkLoadTests15 Sharpino.CommandHandler16 Sharpino.PgStorage17 Sharpino.Sample.Categories.CategoriesCommands18 Sharpino.Sample.Categories.CategoriesEvents19 Sharpino.Sample.Saga.Api.SeatBooking20 Sharpino.Sample.Tags.TagCommands21 Sharpino.Sample.Tags.TagsEvents22 Sharpino.Sample.TodosContext23 Sharpino.Sample._1024 Sharpino.Sample._14.Details.Details25 Sharpino.Sample._15.Details26 Sharpino.Template.Models27 Tonyx.SeatsBooking.StorageStadiumBookingSystem28 Tonyx.Sharpino.Pub29 seatsLockWithSharpino.Row30 Sharpino.Sample.Todos.TodoCommands31 Sharpino.Sample.Todos.TodoEvents32 Sharpino.Sample._10.Tests.Tests33 Sharpino.Template.Models.Details34 Tests35 sharpino.Template.Models36 Sharpino.Sample.App37 Sharpino.Template38 Sharpino.Template.Manager39 Sharpino.Template.TodosManager40 Sharpino.EventSourcing.Sample.AppVersions
1 Sharpino.Cache
2 Sharpino.Core
3 Sharpino.EventBroker
4 Sharpino.Sample.Saga.Domain.Booking.Booking
5 Sharpino.Sample.Saga.Domain.Seat.Row
6 Sharpino.Sample.Saga.Domain.Vaucher.Voucher
7 Sharpino.Sample.Shared.Entities
8 Sharpino.Sample._10.Models.Counter
9 Sharpino.Sample._11.CourseManager
10 Sharpino.Storage
11 Sharpino.Template.Commons
12 seatsLockWithSharpino.Seats
13 AsyncTests11
14 BulkLoadTests11
15 Sharpino.CommandHandler212
16 Sharpino.PgStorage2
17 Sharpino.Sample.Categories.CategoriesCommands11
18 Sharpino.Sample.Categories.CategoriesEvents11
19 Sharpino.Sample.Saga.Api.SeatBooking11112
20 Sharpino.Sample.Tags.TagCommands11
21 Sharpino.Sample.Tags.TagsEvents11
22 Sharpino.Sample.TodosContext1
23 Sharpino.Sample._10111
24 Sharpino.Sample._14.Details.Details2
25 Sharpino.Sample._15.Details2
26 Sharpino.Template.Models79
27 Tonyx.SeatsBooking.StorageStadiumBookingSystem11
28 Tonyx.Sharpino.Pub5
29 seatsLockWithSharpino.Row2
30 Sharpino.Sample.Todos.TodoCommands232
31 Sharpino.Sample.Todos.TodoEvents232
32 Sharpino.Sample._10.Tests.Tests11
33 Sharpino.Template.Models.Details48
34 Tests1111
35 sharpino.Template.Models3111
36 Sharpino.Sample.App652
37 Sharpino.Template22541
38 Sharpino.Template.Manager114121
39 Sharpino.Template.TodosManager11221
40 Sharpino.EventSourcing.Sample.AppVersions112
Uses a module listed above itPart of a loopThe module itself
1 Sharpino.Cache2 Sharpino.Core3 Sharpino.EventBroker4 Sharpino.Sample.Saga.Domain.Booking.Booking5 Sharpino.Sample.Saga.Domain.Seat.Row6 Sharpino.Sample.Saga.Domain.Vaucher.Voucher7 Sharpino.Sample.Shared.Entities8 Sharpino.Sample._10.Models.Counter9 Sharpino.Sample._11.CourseManager10 Sharpino.Storage11 Sharpino.Template.Commons12 seatsLockWithSharpino.Seats13 AsyncTests14 BulkLoadTests15 Sharpino.CommandHandler16 Sharpino.PgStorage17 Sharpino.Sample.Categories.CategoriesCommands18 Sharpino.Sample.Categories.CategoriesEvents19 Sharpino.Sample.Saga.Api.SeatBooking20 Sharpino.Sample.Tags.TagCommands21 Sharpino.Sample.Tags.TagsEvents22 Sharpino.Sample.TodosContext23 Sharpino.Sample._1024 Sharpino.Sample._14.Details.Details25 Sharpino.Sample._15.Details26 Sharpino.Template.Models27 Tonyx.SeatsBooking.StorageStadiumBookingSystem28 Tonyx.Sharpino.Pub29 seatsLockWithSharpino.Row30 Sharpino.Sample.Todos.TodoCommands31 Sharpino.Sample.Todos.TodoEvents32 Sharpino.Sample._10.Tests.Tests33 Sharpino.Template.Models.Details34 Tests35 sharpino.Template.Models36 Sharpino.Sample.App37 Sharpino.Template38 Sharpino.Template.Manager39 Sharpino.Template.TodosManager40 Sharpino.EventSourcing.Sample.AppVersionsSharpino.Cache1Sharpino.Core2Sharpino.EventBroker3Sharpino.Sample.Saga.Domain.Booking.Booking4Sharpino.Sample.Saga.Domain.Seat.Row5Sharpino.Sample.Saga.Domain.Vaucher.Voucher6Sharpino.Sample.Shared.Entities7Sharpino.Sample._10.Models.Counter8Sharpino.Sample._11.CourseManager9Sharpino.Storage10Sharpino.Template.Commons11seatsLockWithSharpino.Seats12AsyncTests13BulkLoadTests14Sharpino.CommandHandler15Sharpino.PgStorage16Sharpino.Sample.Categories.CategoriesCommands17Sharpino.Sample.Categories.CategoriesEvents18Sharpino.Sample.Saga.Api.SeatBooking19Sharpino.Sample.Tags.TagCommands20Sharpino.Sample.Tags.TagsEvents21Sharpino.Sample.TodosContext22Sharpino.Sample._1023Sharpino.Sample._14.Details.Details24Sharpino.Sample._15.Details25Sharpino.Template.Models26Tonyx.SeatsBooking.StorageStadiumBookingSystem27Tonyx.Sharpino.Pub28seatsLockWithSharpino.Row29Sharpino.Sample.Todos.TodoCommands30Sharpino.Sample.Todos.TodoEvents31Sharpino.Sample._10.Tests.Tests32Sharpino.Template.Models.Details33Tests34sharpino.Template.Models35Sharpino.Sample.App36Sharpino.Template37Sharpino.Template.Manager38Sharpino.Template.TodosManager39Sharpino.EventSourcing.Sample.AppVersions401111212211111111211111111227911522322321148111131116522254111412111221112+190 more modules (most-connected shown)

At a glance — Code Health · 64% · Checked 4 of 12 · gated by D4 ·

At a glance — Architecture · 69% · Adequate · gated by AX8 ·

At a glance — Maturity · 50% · Adequate · gated by M4 ·

At a glance — Readiness · 32% · Weak · gated by D13, P1, P3 ·

At a glance — Security · 84% · Checked 4 of 10 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures16High / Critical
A02:2025 — Security Misconfiguration14High / Critical
A07:2025 — Authentication Failures12High / Critical
A05:2025 — Injection1High / Critical

Roadmap

Top priorities: Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2); Add a CI workflow that builds and runs the test suite on every push/PR; Run 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) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2).+12.3 ptsLowREDACTED Scanning
Add a CI workflow that builds and runs the test suite on every push/PR.+6.7 ptsMediumCI/CD gates
Run 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) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+6.7 ptsMediumSecurity & performance tooling
Reconcile the README with reality: Sharpino.Lib.Core/README.md links to `Sharpino.Lib.Core/Core.fs`, but `Sharpino.Lib.Core/Sharpino.Lib.Core/Core.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/CommandHandler.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/CommandHandler.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/PgEventStore.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/PgEventStore.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/MemoryStorage.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/MemoryStorage.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/Cache.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/Cache.fs` does not exist.+3.8 ptsMediumDocumentation accuracy
Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene.+1.6 ptsLowDependency Hygiene
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+2.6 ptsMediumArchitecture documentation
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.+2.0 ptsMediumAsync & latency hygiene
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+1.9 ptsMediumRelease Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 108 files carrying findings, judged against the Production bar: 5% slop · 60% mixed · 35% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.6SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.1SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
Sharpino.Lib/CommandHandler.fs4.8MixedCognitive Complexity: CommandHandler.runThreeNAggregateCommandsMd (cognitive 33)
Sharpino.Lib/PgBinaryEventStore.fs5.5MixedGod Classes: FileTooLong: Sharpino.Lib/PgBinaryEventStore.fs
Sharpino.Lib/PgEventStore.fs5.5MixedGod Classes: FileTooLong: Sharpino.Lib/PgEventStore.fs
Sharpino.Lib/MemoryStorage.fs5.5MixedGod Classes: TooManyMethods: MemoryStorage
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED6.9MixedIaC & Container Security: Medium IaC: REDACTED
Sharpino.Lib/Cache.fs7.0MixedCyclomatic Complexity: AggregateCache3.SetupL2AndBackplane (cyclomatic 19)
Sharpino.Lib/StateView.fs7.0MixedCognitive Complexity: StateView.getLastAggregateSnapshot (cognitive 16)
Sharpino.Sample.11/CourseManager.fs7.0MixedCode Duplication: Duplicated block (18 lines × 2)
Sharpino.Sample.11/Test2.fs7.0MixedCode Duplication: Duplicated block (17 lines × 2)
Sharpino.Sample.22/Program.fs7.0MixedCyclomatic Complexity: Main.main (cyclomatic 57)
Sharpino.Sample.11/Models/Student/Consumer.fs7.0MixedCode Duplication: Near-duplicate member family (3 members, 43 shared lines)
Sharpino.Lib/Sanitizer.fs7.1MixedCyclomatic Complexity: Sanitizer.sanitizeAggregateStreamWithInitialState (cyclomatic 18)
Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs7.1MixedCode Duplication: Near-duplicate member pair (130 shared lines)
Sharpino.Lib/AzureServiceBusBackplane.fs7.1MixedCode Duplication: Near-duplicate member pair (40 shared lines)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 27

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 — 550

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 — 30

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 37

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 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 41 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D19D26D27D28D29D30D31D34D35D43D44AX10AX3AX4AX8GD1M1M2M3M4P1P2P3P4P6P8PF3X20X23X27X28

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
  1. 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, 591 of 607 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1c014-10f8-7bf4-8692-6e17ea309a9c.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be 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.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • 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 Sharpino.Lib/Cache.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 1268 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.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — 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 deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. User interface: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5435: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5435/ Call log: - navigating to "http://127.0.0.1:5435/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:6380: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:6380/ Call log: - navigating to "http://127.0.0.1:6380/", waiting until "load" .
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X26 Unsynchronised callback handoff — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X30 Support guard that admits what it rejects — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X32 Type resolved by simple name across every loaded assembly — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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".
  • 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.

Dimensions

D1 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Prevented

7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Main.main at 60.

Main.main (cyclomatic 60) · ×4Sharpino.Sample.24/Program.fs:20
Main.main (cyclomatic 57)Sharpino.Sample.22/Program.fs:14
AggregateCache3.SetupL2AndBackplane (cyclomatic 19)Sharpino.Lib/Cache.fs:462
Sanitizer.sanitizeAggregateStreamWithInitialState (cyclomatic 18)Sharpino.Lib/Sanitizer.fs:32

What to do

  1. Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Main.main (cyclomatic 60), Main.main (cyclomatic 60), Main.main (cyclomatic 60). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.6 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Prevented

17 method(s) exceeded the cognitive complexity threshold of 15; the worst was Main.main at 105.

Main.main (cognitive 105) · ×4Sharpino.Sample.24/Program.fs:20
Main.main (cognitive 101)Sharpino.Sample.22/Program.fs:14
AggregateCache3.SetupL2AndBackplane (cognitive 53)Sharpino.Lib/Cache.fs:462
add_opt_lock2.process_migrations (cognitive 36)scratch/add_opt_lock2.py:4
Sanitizer.sanitizeAggregateStreamWithInitialState (cognitive 34)Sharpino.Lib/Sanitizer.fs:32

+ 9 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with Main.main (cognitive 105), Main.main (cognitive 105), Main.main (cognitive 105). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 17 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes9.0 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Prevented

9 god class(es) detected.

FileTooLong: Sharpino.Lib/CommandHandler.fs · ×6Sharpino.Lib/CommandHandler.fs
TooManyMethods: PgBinaryStore · ×3Sharpino.Lib/PgBinaryEventStore.fs:35

What to do

  1. Resolve the 6 FileTooLong finding(s) in God Classes — start with CommandHandler.fs, PgBinaryEventStore.fs, PgEventStore.fs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 3 TooManyMethods finding(s) in God Classes — start with PgBinaryEventStore.fs, PgEventStore.fs, MemoryStorage.fs. — One of this dimension's main actionable groups (3 warning-level).
  3. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication2.0 / 10Critical✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Verified

461 duplicated block group(s) detected. A further 21 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (9 lines × 2) · ×18Sharpino.Lib/Cache.fs:312
Duplicated block (11 lines × 2) · ×14Sharpino.Lib/CommandHandler.fs:1444
Duplicated block (13 lines × 2) · ×12Sharpino.Lib/AzureServiceBusBackplane.fs:116
Duplicated block (7 lines × 2) · ×11Sharpino.Lib/Cache.fs:674
Duplicated block (14 lines × 2) · ×10Sharpino.Lib/CommandHandler.fs:4045

+ 230 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 18 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with CommandHandler.fs (5), PgBinaryEventStore.fs (3), StateView.fs (3). — One of this dimension's main actionable groups (18 warning-level).
  2. Resolve the 14 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with PgBinaryEventStore.fs (3), CommandHandler.fs (2), MemoryStorage.fs (2). — One of this dimension's main actionable groups (14 warning-level).
  3. Resolve the 12 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with PgBinaryEventStore.fs (4), PgEventStore.fs (2), AzureServiceBusBackplane.fs. — One of this dimension's main actionable groups (12 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

36 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.1 / 10Stronggated by 5 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Verified

5 of 66 classes have LCOM4 above 3.

Low cohesion: MemoryStorage (LCOM4 14) · ×5Sharpino.Lib/MemoryStorage.fs:27

What to do

  1. Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with CourseManager.fs (2), MemoryStorage.fs, PgBinaryEventStore.fs. — One of this dimension's main actionable groups (5 warning-level).
  2. Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene9.7 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

3 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 4 outdated of 5 package(s) across 1 lockfile(s).

Outdated (npm): js-tokens
Outdated (npm): react · ×3
Outdated: FSharp.Core · ×3

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

5 secret(s) detected.

REDACTED

What to do

  1. Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
  2. Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 386 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 57 direct `PackageReference`(s), and 192 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: Sharpino.Lib/Cache.fs (3×19=57)

Hotspot: Sharpino.Lib/Cache.fsSharpino.Lib/Cache.fs:462

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with Cache.fs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 33 document(s) read across 2 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 27 build units (MSBuild) flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability5.4 / 10Adequate✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 5.4 / 10 · rule-coverage 100% · ceiling Documented

96 % of calls cross a namespace and 3 % go through an interface, but 7 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

Scattered collaborators

What to do

  1. Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)8.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities2.1 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.1 / 10 · rule-coverage 100% · ceiling Documented

16 finding(s): 1 critical, 9 high, 5 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security8.1 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.1 / 10 · rule-coverage 100% · ceiling Documented

14 finding(s): 0 critical, 2 high, 12 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 70 of the 184 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.7 / 10Stronggated by 4 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: Categories.fs↔Tags.fs 88%; Context.fs↔Context.fs 77%; Categories.fs↔Todos.fs 76%

Change coupling: Context.fs ↔ Context.fs · ×3Sharpino.Sample/Domain/Categories/Context.fs:1
Change coupling clique: Categories.fs, Tags.fs, Todos.fsSharpino.Sample/Domain/Categories/Categories.fs

What to do

  1. Resolve the 3 Change coupling finding(s) in Change Coupling — start with CommandHandler.fs (2), Context.fs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with Categories.fs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 36 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX8 · Test isolation2.5 / 10Weak✓ 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.

  • `Sharpino.Sample.2` (production) references the test project `Sharpino.Lib`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Sharpino.Sample.2/Sharpino.Sample.2.fsproj:25
  • `Sharpino.Sample.6` (production) references the test project `Sharpino.Lib`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Sharpino.Sample.6/Sharpino.Sample.6.fsproj:27
  • `Sharpino.Sample.FormerlySaga` (production) references the test project `Sharpino.Lib`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Sharpino.Sample.FormerlySaga/Sharpino.Sample.FormerlySaga.fsproj:35

What to do

  • Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's F#: bindings whose whole body still raises a "not implemented" error (NotImplementedException, failwith "not implemented"), and placeholder text (lorem ipsum, changeme/replace_me…) left in string literals of 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.

M1 · Documentation (README)9.3 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

  • Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

What to do

  • Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy0.0 / 10Critical✓ Tool-verified

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.

  • Sharpino.Lib.Core/README.md links to `Sharpino.Lib.Core/Core.fs`, but `Sharpino.Lib.Core/Sharpino.Lib.Core/Core.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib.Core/README.md:70
  • Sharpino.Lib.Core/README.md links to `Sharpino.Lib/CommandHandler.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/CommandHandler.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib.Core/README.md:74
  • Sharpino.Lib.Core/README.md links to `Sharpino.Lib/PgEventStore.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/PgEventStore.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib.Core/README.md:75
  • Sharpino.Lib.Core/README.md links to `Sharpino.Lib/MemoryStorage.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/MemoryStorage.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib.Core/README.md:75
  • Sharpino.Lib.Core/README.md links to `Sharpino.Lib/Cache.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/Cache.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib.Core/README.md:77
  • Sharpino.Lib.Core/README.md links to `CONTRIBUTING.md`, but `Sharpino.Lib.Core/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib.Core/README.md:105
  • Sharpino.Lib/README.md links to `Sharpino.Lib.Core/Core.fs`, but `Sharpino.Lib/Sharpino.Lib.Core/Core.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib/README.md:45
  • Sharpino.Lib/README.md links to `Sharpino.Lib/CommandHandler.fs`, but `Sharpino.Lib/Sharpino.Lib/CommandHandler.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib/README.md:49
  • Sharpino.Lib/README.md links to `Sharpino.Lib/PgEventStore.fs`, but `Sharpino.Lib/Sharpino.Lib/PgEventStore.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib/README.md:50
  • Sharpino.Lib/README.md links to `Sharpino.Lib/MemoryStorage.fs`, but `Sharpino.Lib/Sharpino.Lib/MemoryStorage.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib/README.md:50
  • Sharpino.Lib/README.md links to `Sharpino.Lib/Cache.fs`, but `Sharpino.Lib/Sharpino.Lib/Cache.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib/README.md:52
  • Sharpino.Lib/README.md links to `CONTRIBUTING.md`, but `Sharpino.Lib/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sharpino.Lib/README.md:80

What to do

  • Reconcile the README with reality: Sharpino.Lib.Core/README.md links to `Sharpino.Lib.Core/Core.fs`, but `Sharpino.Lib.Core/Sharpino.Lib.Core/Core.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/CommandHandler.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/CommandHandler.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/PgEventStore.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/PgEventStore.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/MemoryStorage.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/MemoryStorage.fs` does not exist; Sharpino.Lib.Core/README.md links to `Sharpino.Lib/Cache.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/Cache.fs` does not exist.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability5.6 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 8/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `Sharpino.Sample.22`, `Sharpino.Sample.24`, `Sharpino.Sample.26`, `Sharpino.Sample.27` and 2 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Consider OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) and a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
  • `Sharpino.Lib.Core/Sharpino.Lib.Core.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`. — Sharpino.Lib.Core/Sharpino.Lib.Core.fsproj:28

What to do

  • Run 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) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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.

  • `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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. (×6) — Sharpino.Lib/PgBinaryEventStore.fs:1856, Sharpino.Lib/PgBinaryEventStore.fs:2737, Sharpino.Lib/PgBinaryEventStore.fs:3361, …

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.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for … in` loop leaves the mutable .NET collection it is walking alone — F#'s own lists, arrays, maps and sets cannot be changed by a loop body, but a `ResizeArray`, `Dictionary`, `Queue` or other BCL collection walked by `for x in c do` is walked through its enumerator, so a body that adds to or removes from `c` makes the next `MoveNext` throw `InvalidOperationException` and the remaining items are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

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.

LensScoreRatingImpact
Code Health64%Checked 4 of 12Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture69%Adequate — gated by AX8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity50%Adequate — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness32%Weak — gated by D13, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security84%Checked 4 of 10Strongest area.
Performance60%AdequateAcceptable, with room to improve.
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 — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC7 A11y enforcement — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5435: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5435/ Call log: - navigating to "http://127.0.0.1:5435/", waiting until "load" rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:6380: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:6380/ Call log: - navigating to "http://127.0.0.1:6380/", waiting until "load" . This repository also has a user interface (2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D10 Test Quality — ~19111 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
  • D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, Python not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • 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.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — no coverage collector is wired up
  • D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • DM1 Domain Modelling — applicable but not scored (5 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 aggregate root(s) (entities that raise its domain events); 26 strongly-typed id(s); 130 value object(s); 73 domain event(s); a Domain/Aggregates/ValueObjects layer; a top-level Sharpino.Sample/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (26 event handler(s))
  • ED5 Idempotency — Not assessed, and this one is on us: 676 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 27 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX8 · Test isolation · Production project references a test project · ×3
  • Production project references a test project: Sharpino.Sample.2 → Sharpino.Lib Sharpino.Sample.2/Sharpino.Sample.2.fsproj:25 — `Sharpino.Sample.2` (production) references the test project `Sharpino.Lib`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: Sharpino.Sample.6 → Sharpino.Lib Sharpino.Sample.6/Sharpino.Sample.6.fsproj:27 — `Sharpino.Sample.6` (production) references the test project `Sharpino.Lib`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: Sharpino.Sample.FormerlySaga → Sharpino.Lib Sharpino.Sample.FormerlySaga/Sharpino.Sample.FormerlySaga.fsproj:35 — `Sharpino.Sample.FormerlySaga` (production) references the test project `Sharpino.Lib`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
D28 · Secrets (history) · High secret · ×2
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×2
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
Serious — 550 finding(s)
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×18
  • Duplicated block (9 lines × 2) Sharpino.Lib/Cache.fs:312 — Sharpino.Lib/Cache.fs:312-320 | Sharpino.Lib/Cache.fs:566-574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:2237 — Sharpino.Lib/CommandHandler.fs:2237-2245 | Sharpino.Lib/CommandHandler.fs:2506-2514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:2758 — Sharpino.Lib/CommandHandler.fs:2758-2766 | Sharpino.Lib/CommandHandler.fs:2850-2858 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:2982 — Sharpino.Lib/CommandHandler.fs:2982-2990 | Sharpino.Lib/CommandHandler.fs:3113-3121 — 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 `Sharpino.Lib/CommandHandler.fs:2982` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:4116 — Sharpino.Lib/CommandHandler.fs:4116-4124 | Sharpino.Lib/CommandHandler.fs:5588-5596 — 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 `Sharpino.Lib/CommandHandler.fs:4116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:5599` calls `traverseResultM` and `Sharpino.Lib/CommandHandler.fs:4126` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) Sharpino.Lib/MemoryStorage.fs:83 — Sharpino.Lib/MemoryStorage.fs:83-91 | Sharpino.Lib/MemoryStorage.fs:147-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:22 — Sharpino.Lib/PgBinaryEventStore.fs:22-30 | Sharpino.Lib/PgEventStore.fs:23-31 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:939 — Sharpino.Lib/PgBinaryEventStore.fs:939-947 | Sharpino.Lib/PgEventStore.fs:721-729 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:939` 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, `Sharpino.Lib/PgEventStore.fs:720` calls `NewGuid` and `Sharpino.Lib/PgBinaryEventStore.fs:937` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2514 — Sharpino.Lib/PgBinaryEventStore.fs:2514-2522 | Sharpino.Lib/PgBinaryEventStore.fs:2813-2821 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:2514` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sharpino.Lib/RabbitMq.fs:196 — Sharpino.Lib/RabbitMq.fs:196-204 | Sharpino.Lib/RabbitMq.fs:255-263 — 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 `Sharpino.Lib/RabbitMq.fs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sharpino.Lib/StateView.fs:455 — Sharpino.Lib/StateView.fs:455-463 | Sharpino.Lib/StateView.fs:495-503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `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 (9 lines × 2) Sharpino.Lib/StateView.fs:609 — Sharpino.Lib/StateView.fs:609-617 | Sharpino.Lib/StateView.fs:636-644 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Sharpino.Lib/StateView.fs:667 — Sharpino.Lib/StateView.fs:667-675 | Sharpino.Lib/StateView.fs:694-702 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Sharpino.Sample.11/Models/Course/Course.fs:62 — Sharpino.Sample.11/Models/Course/Course.fs:62-70 | Sharpino.Sample.14/Models/Course/Course.fs:69-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) Sharpino.Sample.11/Models/Student/Commands.fs:13 — Sharpino.Sample.11/Models/Student/Commands.fs:13-21 | Sharpino.Sample.14/Models/Student/Commands.fs:16-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) Sharpino.Sample.12/Models/Course/Commands.fs:17 — Sharpino.Sample.12/Models/Course/Commands.fs:17-25 | Sharpino.Sample.9/models/Course/Commands.fs:15-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 (9 lines × 2) Sharpino.Lib/PgEventStore.fs:2008 — Sharpino.Lib/PgEventStore.fs:2008-2016 | Sharpino.Lib/PgEventStore.fs:2084-2093 — 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 `Sharpino.Lib/PgEventStore.fs:2008` 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 lines × 2) Sharpino.Lib/CommandHandler.fs:281 — Sharpino.Lib/CommandHandler.fs:281-289 | Sharpino.Lib/CommandHandler.fs:316-324 — 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 `Sharpino.Lib/CommandHandler.fs:281` 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×14
  • Duplicated block (11 lines × 2) Sharpino.Lib/CommandHandler.fs:1444 — Sharpino.Lib/CommandHandler.fs:1444-1454 | Sharpino.Lib/CommandHandler.fs:1532-1542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Sharpino.Lib/MemoryStorage.fs:732 — Sharpino.Lib/MemoryStorage.fs:732-742 | Sharpino.Lib/MemoryStorage.fs:751-761 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Sharpino.Lib/MemoryStorage.fs:911 — Sharpino.Lib/MemoryStorage.fs:911-921 | Sharpino.Lib/MemoryStorage.fs:929-939 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:455 — Sharpino.Lib/PgBinaryEventStore.fs:455-466 | Sharpino.Lib/PgEventStore.fs:2049-2059 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:753 — Sharpino.Lib/PgBinaryEventStore.fs:753-763 | Sharpino.Lib/PgEventStore.fs:920-930 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2526 — Sharpino.Lib/PgBinaryEventStore.fs:2526-2536 | Sharpino.Lib/PgBinaryEventStore.fs:2572-2582 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Sharpino.Lib/PgEventStore.fs:2001 — Sharpino.Lib/PgEventStore.fs:2001-2011 | Sharpino.Lib/PgEventStore.fs:2259-2269 — 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 `Sharpino.Lib/PgEventStore.fs:2001` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Sharpino.Sample.11/Models/Student/Events.fs:23 — Sharpino.Sample.11/Models/Student/Events.fs:23-33 | Sharpino.Sample.14/Models/Student/Events.fs:22-32 — 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) Sharpino.Sample.11/Test2.fs:244 — Sharpino.Sample.11/Test2.fs:244-254 | Sharpino.Sample.11/Test2.fs:459-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Sharpino.Sample.12/Models/Student/Events.fs:13 — Sharpino.Sample.12/Models/Student/Events.fs:13-23 | Sharpino.Sample.9/models/Student/Event.fs:7-17 — 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) Sharpino.Sample.3/Rows/Consumer.fs:25 — Sharpino.Sample.3/Rows/Consumer.fs:25-35 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:20-30 — 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) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:3 — Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:3-13 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:3-13 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.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 6 separate duplicated blocks between them, totalling at least 95 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (11 lines × 2) Sharpino.Lib/CommandHandler.fs:4254 — Sharpino.Lib/CommandHandler.fs:4254-4264 | Sharpino.Lib/CommandHandler.fs:4403-4413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Sharpino.Lib/PgEventStore.fs:807 — Sharpino.Lib/PgEventStore.fs:807-817 | Sharpino.Lib/PgEventStore.fs:898-908 — 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 `Sharpino.Lib/PgEventStore.fs:807` 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.
D31 · IaC & Container Security · Medium IaC · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×12
  • Duplicated block (13 lines × 2) Sharpino.Lib/AzureServiceBusBackplane.fs:116 — Sharpino.Lib/AzureServiceBusBackplane.fs:116-128 | Sharpino.Lib/PgNotifyBackplane.fs:102-114 — before extracting anything, compare `Sharpino.Lib/AzureServiceBusBackplane.fs` and `Sharpino.Lib/PgNotifyBackplane.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/AzureServiceBusBackplane.fs:116` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) Sharpino.Lib/CommandHandler.fs:2354 — Sharpino.Lib/CommandHandler.fs:2354-2366 | Sharpino.Lib/CommandHandler.fs:2536-2548 — 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 `Sharpino.Lib/CommandHandler.fs:2354` 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 (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1265 — Sharpino.Lib/PgBinaryEventStore.fs:1265-1277 | Sharpino.Lib/PgEventStore.fs:1242-1254 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2202 — Sharpino.Lib/PgBinaryEventStore.fs:2202-2216 | Sharpino.Lib/PgEventStore.fs:2253-2265 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2459 — Sharpino.Lib/PgBinaryEventStore.fs:2459-2471 | Sharpino.Lib/PgEventStore.fs:2305-2317 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2459` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs:1342 — Sharpino.Lib/PgEventStore.fs:1342-1354 | Sharpino.Lib/PgEventStore.fs:2653-2665 — 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 `Sharpino.Lib/PgEventStore.fs:1342` 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 (13 lines × 2) Sharpino.Lib/PgEventStore.fs:2327 — Sharpino.Lib/PgEventStore.fs:2327-2339 | Sharpino.Lib/PgEventStore.fs:2350-2362 — 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 `Sharpino.Lib/PgEventStore.fs:2327` 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 (13 lines × 2) Sharpino.Sample.11/Models/Course/Consumer.fs:3 — Sharpino.Sample.11/Models/Course/Consumer.fs:3-15 | Sharpino.Sample.14/Models/Course/Consumer.fs:3-15 — before extracting anything, compare `Sharpino.Sample.11/Models/Course/Consumer.fs` and `Sharpino.Sample.14/Models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 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 (13 lines × 2) Sharpino.Sample.11/Models/Course/Course.fs:42 — Sharpino.Sample.11/Models/Course/Course.fs:42-54 | Sharpino.Sample.14/Models/Course/Course.fs:41-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 `Sharpino.Sample.11/Models/Course/Course.fs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Sharpino.Sample.16/MaterialManager.fs:106 — Sharpino.Sample.16/MaterialManager.fs:106-118 | Sharpino.Sample.17/MaterialManager.fs:121-133 — `Sharpino.Sample.16/MaterialManager.fs` and `Sharpino.Sample.17/MaterialManager.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 4 separate duplicated blocks between them, totalling at least 107 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) Sharpino.Sample.25/TodoManager.fs:88 — Sharpino.Sample.25/TodoManager.fs:88-100 | Sharpino.Sample.25/TodoManager.fs:112-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.25/TodoManager.fs:88` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:882 — Sharpino.Lib/PgBinaryEventStore.fs:882-894 | Sharpino.Lib/PgEventStore.fs:662-674 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:882` 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×11
  • Duplicated block (7 lines × 2) Sharpino.Lib/Cache.fs:674 — Sharpino.Lib/Cache.fs:674-680 | Sharpino.Lib/Cache.fs:736-742 — 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 `Sharpino.Lib/Cache.fs:674` 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) Sharpino.Lib/CommandHandler.fs:919 — Sharpino.Lib/CommandHandler.fs:919-925 | Sharpino.Lib/CommandHandler.fs:1126-1134 — 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 (7 lines × 2) Sharpino.Lib/CommandHandler.fs:1279 — Sharpino.Lib/CommandHandler.fs:1279-1285 | Sharpino.Lib/CommandHandler.fs:1372-1378 — 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 `Sharpino.Lib/CommandHandler.fs:1279` 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, `Sharpino.Lib/CommandHandler.fs:1380` calls `eventStore` and `Sharpino.Lib/CommandHandler.fs:1287` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:1770 — Sharpino.Lib/CommandHandler.fs:1770-1777 | Sharpino.Lib/CommandHandler.fs:1867-1873 — 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 `Sharpino.Lib/CommandHandler.fs:1770` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:668 — Sharpino.Lib/PgBinaryEventStore.fs:668-675 | Sharpino.Lib/PgEventStore.fs:835-841 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3478 — Sharpino.Lib/PgBinaryEventStore.fs:3478-3484 | Sharpino.Lib/PgEventStore.fs:3506-3512 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:3478` 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) Sharpino.Lib/RabbitMq.fs:215 — Sharpino.Lib/RabbitMq.fs:215-221 | Sharpino.Lib/RabbitMq.fs:277-283 — 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 `Sharpino.Lib/RabbitMq.fs:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Sharpino.Lib/StateView.fs:440 — Sharpino.Lib/StateView.fs:440-446 | Sharpino.Lib/StateView.fs:548-554 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Sharpino.Sample.11/Models/Course/Consumer.fs:98 — Sharpino.Sample.11/Models/Course/Consumer.fs:98-104 | Sharpino.Sample.14/Models/Course/Consumer.fs:98-104 — before extracting anything, compare `Sharpino.Sample.11/Models/Course/Consumer.fs` and `Sharpino.Sample.14/Models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/GoodsContainer.fs:33 — Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/GoodsContainer.fs:33-39 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/GoodsContainer.fs:32-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) Sharpino.Lib/StateView.fs:865 — Sharpino.Lib/StateView.fs:865-871 | Sharpino.Lib/StateView.fs:896-902 — 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 `Sharpino.Lib/StateView.fs:865` 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×10
  • Duplicated block (14 lines × 2) Sharpino.Lib/CommandHandler.fs:4045 — Sharpino.Lib/CommandHandler.fs:4045-4058 | Sharpino.Lib/CommandHandler.fs:4552-4565 — 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) Sharpino.Lib/CommandHandler.fs:5978 — Sharpino.Lib/CommandHandler.fs:5978-5991 | Sharpino.Lib/CommandHandler.fs:6053-6066 — 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) Sharpino.Lib/PgBinaryEventStore.fs:146 — Sharpino.Lib/PgBinaryEventStore.fs:146-159 | Sharpino.Lib/PgBinaryEventStore.fs:393-406 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:694 — Sharpino.Lib/PgBinaryEventStore.fs:694-707 | Sharpino.Lib/PgBinaryEventStore.fs:785-798 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:694` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:860 — Sharpino.Lib/PgEventStore.fs:860-873 | Sharpino.Lib/PgEventStore.fs:952-965 — 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 `Sharpino.Lib/PgEventStore.fs:860` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Sharpino.Sample.10/Models/Account/Consumer.fs:1 — Sharpino.Sample.10/Models/Account/Consumer.fs:1-14 | Sharpino.Sample.10/Models/Counter/Consumer.fs:1-14 — `Sharpino.Sample.10/Models/Account/Consumer.fs` and `Sharpino.Sample.10/Models/Counter/Consumer.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 3 separate duplicated blocks between them, totalling at least 40 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 (14 lines × 2) Sharpino.Sample.11/Models/Course/Commands.fs:1 — Sharpino.Sample.11/Models/Course/Commands.fs:1-14 | Sharpino.Sample.12/Models/Course/Commands.fs:1-14 — 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 (14 lines × 2) Sharpino.Sample.11/Test2.fs:371 — Sharpino.Sample.11/Test2.fs:371-384 | Sharpino.Sample.11/Test2.fs:441-454 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.11/Test2.fs:455` calls `Stop` and `Sharpino.Sample.11/Test2.fs:385` 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 (14 lines × 2) Sharpino.Sample.16/Models/Products/Commands.fs:1 — Sharpino.Sample.16/Models/Products/Commands.fs:1-14 | Sharpino.Sample.17/Models/Products/Commands.fs:1-14 — before extracting anything, compare `Sharpino.Sample.16/Models/Products/Commands.fs` and `Sharpino.Sample.17/Models/Products/Commands.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 (14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:1 — Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:1-14 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:1-14 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×10
  • Duplicated block (12 lines × 2) Sharpino.Lib/CommandHandler.fs:366 — Sharpino.Lib/CommandHandler.fs:366-377 | Sharpino.Lib/CommandHandler.fs:1172-1183 — 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) Sharpino.Lib/CommandHandler.fs:5528 — Sharpino.Lib/CommandHandler.fs:5528-5539 | Sharpino.Lib/CommandHandler.fs:5753-5764 — 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) Sharpino.Lib/PgBinaryEventStore.fs:592 — Sharpino.Lib/PgBinaryEventStore.fs:592-603 | Sharpino.Lib/PgEventStore.fs:556-567 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2568 — Sharpino.Lib/PgBinaryEventStore.fs:2568-2579 | Sharpino.Lib/PgEventStore.fs:2426-2437 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Sharpino.Sample.11/Test2.fs:112 — Sharpino.Sample.11/Test2.fs:112-123 | Sharpino.Sample.11/Test2.fs:331-342 — 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) Sharpino.Sample.11/Test2.fs:269 — Sharpino.Sample.11/Test2.fs:269-280 | Sharpino.Sample.11/Test2.fs:483-494 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Sample.11/Test2.fs:267` calls `Clear` and `Sharpino.Sample.11/Test2.fs:480` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) Sharpino.Sample.9/models/Course/Consumer.fs:43 — Sharpino.Sample.9/models/Course/Consumer.fs:43-54 | Sharpino.Sample.9/models/Teacher/Consumer.fs:43-54 — `Sharpino.Sample.9/models/Course/Consumer.fs` and `Sharpino.Sample.9/models/Teacher/Consumer.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 5 separate duplicated blocks between them, totalling at least 64 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (12 lines × 2) Sharpino.Sample/App.fs:113 — Sharpino.Sample/App.fs:113-124 | Sharpino.Sample/App.fs:303-314 — 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) Sharpino.Lib/PgBinaryEventStore.fs:2189 — Sharpino.Lib/PgBinaryEventStore.fs:2189-2200 | Sharpino.Lib/PgEventStore.fs:2170-2184 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2189` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) Sharpino.Sample.11/Test2.fs:161 — Sharpino.Sample.11/Test2.fs:161-172 | Sharpino.Sample.11/Test2.fs:380-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×10
  • Duplicated block (6 lines × 2) Sharpino.Lib/Cache.fs:259 — Sharpino.Lib/Cache.fs:259-264 | Sharpino.Lib/Cache.fs:590-595 — 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) Sharpino.Lib/Cache.fs:704 — Sharpino.Lib/Cache.fs:704-709 | Sharpino.Lib/Cache.fs:744-749 — 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) Sharpino.Lib/CommandHandler.fs:1714 — Sharpino.Lib/CommandHandler.fs:1714-1719 | Sharpino.Lib/CommandHandler.fs:1811-1816 — 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 `Sharpino.Lib/CommandHandler.fs:1714` 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) Sharpino.Lib/CommandHandler.fs:3237 — Sharpino.Lib/CommandHandler.fs:3237-3242 | Sharpino.Lib/CommandHandler.fs:3309-3314 — 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 `Sharpino.Lib/CommandHandler.fs:3237` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:3244` calls `Obsolete` and `Sharpino.Lib/CommandHandler.fs:3316` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) Sharpino.Lib/CommandHandler.fs:5993 — Sharpino.Lib/CommandHandler.fs:5993-5998 | Sharpino.Lib/CommandHandler.fs:6068-6073 — 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) Sharpino.Lib/PgBinaryEventStore.fs:1351 — Sharpino.Lib/PgBinaryEventStore.fs:1351-1356 | Sharpino.Lib/PgBinaryEventStore.fs:2486-2491 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:1351` 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) Sharpino.Lib/Sanitizer.fs:37 — Sharpino.Lib/Sanitizer.fs:37-42 | Sharpino.Lib/Sanitizer.fs:133-138 — 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) Sharpino.Lib/Sanitizer.fs:154 — Sharpino.Lib/Sanitizer.fs:154-159 | Sharpino.Lib/Sanitizer.fs:215-220 — 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) Sharpino.Lib/StateView.fs:883 — Sharpino.Lib/StateView.fs:883-888 | Sharpino.Lib/StateView.fs:907-912 — 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 `Sharpino.Lib/StateView.fs:883` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Sharpino.Lib/Cache.fs:148 — Sharpino.Lib/Cache.fs:148-153 | Sharpino.Lib/Cache.fs:472-477 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/Cache.fs:142` calls `SetupBackplane`, `activateBackplane` and `Sharpino.Lib/Cache.fs:468` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×9
  • Duplicated block (17 lines × 2) Sharpino.Lib/CommandHandler.fs:2210 — Sharpino.Lib/CommandHandler.fs:2210-2226 | Sharpino.Lib/CommandHandler.fs:2250-2266 — 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 (17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:573 — Sharpino.Lib/PgBinaryEventStore.fs:573-589 | Sharpino.Lib/PgEventStore.fs:537-553 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:573` 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 × 2) Sharpino.Lib/PgBinaryEventStore.fs:1325 — Sharpino.Lib/PgBinaryEventStore.fs:1325-1341 | Sharpino.Lib/PgEventStore.fs:1306-1322 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1325` 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 (17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2605 — Sharpino.Lib/PgBinaryEventStore.fs:2605-2621 | Sharpino.Lib/PgEventStore.fs:2352-2368 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3459 — Sharpino.Lib/PgBinaryEventStore.fs:3459-3475 | Sharpino.Lib/PgEventStore.fs:3487-3503 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) Sharpino.Lib/PgEventStore.fs:1183 — Sharpino.Lib/PgEventStore.fs:1183-1199 | Sharpino.Lib/PgEventStore.fs:1629-1645 — 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 `Sharpino.Lib/PgEventStore.fs:1183` 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 (17 lines × 2) Sharpino.Sample.11/Test2.fs:80 — Sharpino.Sample.11/Test2.fs:80-96 | Sharpino.Sample.11/Test2.fs:223-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.11/Test2.fs:240` calls `Stop` and `Sharpino.Sample.11/Test2.fs:97` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (17 lines × 2) Sharpino.Sample.11/Test2.fs:186 — Sharpino.Sample.11/Test2.fs:186-202 | Sharpino.Sample.11/Test2.fs:261-277 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.11/Test2.fs:280` calls `Stop` and `Sharpino.Sample.11/Test2.fs:204` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (17 lines × 2) Sharpino.Sample.11/Test2.fs:404 — Sharpino.Sample.11/Test2.fs:404-420 | Sharpino.Sample.11/Test2.fs:475-491 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.11/Test2.fs:494` calls `Stop` and `Sharpino.Sample.11/Test2.fs:422` 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×9
  • Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:1199 — Sharpino.Lib/CommandHandler.fs:1199-1208 | Sharpino.Lib/CommandHandler.fs:1619-1628 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:2288 — Sharpino.Lib/CommandHandler.fs:2288-2297 | Sharpino.Lib/CommandHandler.fs:2304-2313 — 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 `Sharpino.Lib/CommandHandler.fs:2288` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:4070 — Sharpino.Lib/CommandHandler.fs:4070-4079 | Sharpino.Lib/CommandHandler.fs:4577-4586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:604 — Sharpino.Lib/PgBinaryEventStore.fs:604-613 | Sharpino.Lib/PgEventStore.fs:568-577 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) Sharpino.Lib/StateView.fs:949 — Sharpino.Lib/StateView.fs:949-958 | Sharpino.Lib/StateView.fs:973-982 — 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 `Sharpino.Lib/StateView.fs:949` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Sharpino.Sample.11/Models/Course/Events.fs:21 — Sharpino.Sample.11/Models/Course/Events.fs:21-30 | Sharpino.Sample.14/Models/Course/Events.fs:23-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs:14 — Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs:14-23 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Events.fs:12-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) Sharpino.Sample/App.fs:92 — Sharpino.Sample/App.fs:92-101 | Sharpino.Sample/App.fs:109-118 — 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 `Sharpino.Sample/App.fs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Sharpino.Lib/MemoryStorage.fs:248 — Sharpino.Lib/MemoryStorage.fs:248-257 | Sharpino.Lib/MemoryStorage.fs:271-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×9
  • Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:2689 — Sharpino.Lib/CommandHandler.fs:2689-2696 | Sharpino.Lib/CommandHandler.fs:2880-2887 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:468 — Sharpino.Lib/PgBinaryEventStore.fs:468-477 | Sharpino.Lib/PgEventStore.fs:482-489 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:468` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1226 — Sharpino.Lib/PgBinaryEventStore.fs:1226-1233 | Sharpino.Lib/PgEventStore.fs:1203-1210 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) Sharpino.Lib/StateView.fs:88 — Sharpino.Lib/StateView.fs:88-95 | Sharpino.Lib/StateView.fs:107-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Sharpino.Lib/StateView.fs:584 — Sharpino.Lib/StateView.fs:584-591 | Sharpino.Lib/StateView.fs:728-735 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Sharpino.Lib/StateView.fs:794 — Sharpino.Lib/StateView.fs:794-801 | Sharpino.Lib/StateView.fs:858-865 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:64 — Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:64-71 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:63-70 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.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 6 separate duplicated blocks between them, totalling at least 95 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 (8 lines × 2) Sharpino.Lib/AzureServiceBusBackplane.fs:75 — Sharpino.Lib/AzureServiceBusBackplane.fs:75-82 | Sharpino.Lib/PgNotifyBackplane.fs:86-93 — before extracting anything, compare `Sharpino.Lib/AzureServiceBusBackplane.fs` and `Sharpino.Lib/PgNotifyBackplane.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/AzureServiceBusBackplane.fs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Sharpino.Sample/App.fs:271 — Sharpino.Sample/App.fs:271-278 | Sharpino.Sample/App.fs:296-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×8
  • Duplicated block (18 lines × 2) Sharpino.Lib/Cache.fs:506 — Sharpino.Lib/Cache.fs:506-523 | Sharpino.Lib/Cache.fs:526-543 — 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 (18 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:532 — Sharpino.Lib/PgBinaryEventStore.fs:532-549 | Sharpino.Lib/PgEventStore.fs:496-513 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:532` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2389 — Sharpino.Lib/PgBinaryEventStore.fs:2389-2406 | Sharpino.Lib/PgEventStore.fs:2797-2814 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2389` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2871 — Sharpino.Lib/PgBinaryEventStore.fs:2871-2888 | Sharpino.Lib/PgEventStore.fs:2697-2714 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2871` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2891` calls `NpgsqlConnection` and `Sharpino.Lib/PgEventStore.fs:2717` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 2) Sharpino.Lib/StateView.fs:325 — Sharpino.Lib/StateView.fs:325-342 | Sharpino.Lib/StateView.fs:383-400 — 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 `Sharpino.Lib/StateView.fs:325` 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 (18 lines × 2) Sharpino.Sample.11/CourseManager.fs:75 — Sharpino.Sample.11/CourseManager.fs:75-92 | Sharpino.Sample.14/CourseManager.fs:199-216 — `Sharpino.Sample.11/CourseManager.fs` and `Sharpino.Sample.14/CourseManager.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 18 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.11/CourseManager.fs:75` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Sharpino.Sample.16/MaterialManager.fs:1 — Sharpino.Sample.16/MaterialManager.fs:1-18 | Sharpino.Sample.25/TodoManager.fs:1-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (18 lines × 2) Sharpino.Sample.9/models/Course/Consumer.fs:68 — Sharpino.Sample.9/models/Course/Consumer.fs:68-85 | Sharpino.Sample.9/models/Item/Consumer.fs:76-93 — `Sharpino.Sample.9/models/Course/Consumer.fs` and `Sharpino.Sample.9/models/Item/Consumer.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 7 separate duplicated blocks between them, totalling at least 96 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 · Duplicated block (15 lines × 2) · ×8
  • Duplicated block (15 lines × 2) Sharpino.Lib/MemoryStorage.fs:197 — Sharpino.Lib/MemoryStorage.fs:197-211 | Sharpino.Lib/MemoryStorage.fs:283-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) Sharpino.Lib/MemoryStorage.fs:363 — Sharpino.Lib/MemoryStorage.fs:363-377 | Sharpino.Lib/MemoryStorage.fs:1100-1114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1357 — Sharpino.Lib/PgBinaryEventStore.fs:1357-1371 | Sharpino.Lib/PgBinaryEventStore.fs:2822-2836 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2208 — Sharpino.Lib/PgBinaryEventStore.fs:2208-2222 | Sharpino.Lib/PgEventStore.fs:2190-2204 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2190` 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 × 2) Sharpino.Lib/PgBinaryEventStore.fs:3421 — Sharpino.Lib/PgBinaryEventStore.fs:3421-3435 | Sharpino.Lib/PgEventStore.fs:3449-3463 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Sharpino.Lib/StateView.fs:237 — Sharpino.Lib/StateView.fs:237-251 | Sharpino.Lib/StateView.fs:271-285 — 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 `Sharpino.Lib/StateView.fs:237` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs:8 — Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs:8-22 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/Events.fs:7-21 — 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 (15 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:1 — Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:1-15 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:1-15 — 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×7
  • Duplicated block (21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:872 — Sharpino.Lib/PgBinaryEventStore.fs:872-892 | Sharpino.Lib/PgBinaryEventStore.fs:972-992 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:872` 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 (21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1940 — Sharpino.Lib/PgBinaryEventStore.fs:1940-1960 | Sharpino.Lib/PgEventStore.fs:1938-1958 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (21 lines × 2) Sharpino.Sample.12/Models/Course/Course.fs:42 — Sharpino.Sample.12/Models/Course/Course.fs:42-62 | Sharpino.Sample.9/models/Course/Course.fs:49-69 — 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 `Sharpino.Sample.12/Models/Course/Course.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 (21 lines × 2) Sharpino.Sample.16/Models/Materials/Commands.fs:1 — Sharpino.Sample.16/Models/Materials/Commands.fs:1-21 | Sharpino.Sample.17/Models/Materials/Commands.fs:1-21 — before extracting anything, compare `Sharpino.Sample.16/Models/Materials/Commands.fs` and `Sharpino.Sample.17/Models/Materials/Commands.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 (21 lines × 2) Sharpino.Sample.16/Models/Products/Events.fs:1 — Sharpino.Sample.16/Models/Products/Events.fs:1-21 | Sharpino.Sample.17/Models/Products/Events.fs:1-21 — before extracting anything, compare `Sharpino.Sample.16/Models/Products/Events.fs` and `Sharpino.Sample.17/Models/Products/Events.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 (21 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:47 — Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:47-67 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:49-69 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Sharpino.Sample.9/CourseManager.fs:3 — Sharpino.Sample.9/CourseManager.fs:3-23 | Sharpino.Sample.9/CourseManagerAsync.fs:4-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×7
  • Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1461 — Sharpino.Lib/PgBinaryEventStore.fs:1461-1476 | Sharpino.Lib/PgEventStore.fs:1498-1513 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1461` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2846 — Sharpino.Lib/PgBinaryEventStore.fs:2846-2861 | Sharpino.Lib/PgEventStore.fs:2672-2687 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2846` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3441 — Sharpino.Lib/PgBinaryEventStore.fs:3441-3456 | Sharpino.Lib/PgEventStore.fs:3469-3484 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:608 — Sharpino.Lib/PgEventStore.fs:608-623 | Sharpino.Lib/PgEventStore.fs:703-718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) Sharpino.Lib/Sanitizer.fs:52 — Sharpino.Lib/Sanitizer.fs:52-67 | Sharpino.Lib/Sanitizer.fs:166-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) Sharpino.Sample.12/Models/Student/Student.fs:11 — Sharpino.Sample.12/Models/Student/Student.fs:11-26 | Sharpino.Sample.9/models/Student/Student.fs:8-23 — before extracting anything, compare `Sharpino.Sample.12/Models/Student/Student.fs` and `Sharpino.Sample.9/models/Student/Student.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 `Sharpino.Sample.12/Models/Student/Student.fs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs:7 — Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs:7-22 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Events.fs:6-21 — 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.
D3 · God Classes · FileTooLong · ×6
  • FileTooLong: Sharpino.Lib/CommandHandler.fs Sharpino.Lib/CommandHandler.fs — FileTooLong — 5173 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 88 functions. The bar is 500 significant lines; this is 4673 over it, 10.35× 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: Sharpino.Lib/PgBinaryEventStore.fs Sharpino.Lib/PgBinaryEventStore.fs — FileTooLong — 2791 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2291 over it, 5.58× 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: Sharpino.Lib/PgEventStore.fs Sharpino.Lib/PgEventStore.fs — FileTooLong — 2787 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2287 over it, 5.57× 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: Sharpino.Lib/MemoryStorage.fs Sharpino.Lib/MemoryStorage.fs — FileTooLong — 1170 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 670 over it, 2.34× 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: Sharpino.Lib/StateView.fs Sharpino.Lib/StateView.fs — FileTooLong — 1085 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 41 functions. The bar is 500 significant lines; this is 585 over it, 2.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: Sharpino.Lib/Cache.fs Sharpino.Lib/Cache.fs — FileTooLong — 819 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 319 over it, 1.64× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×6
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Sharpino.Sample.22/Commons.fs:1 — Sharpino.Sample.22/Commons.fs:1-20 | Sharpino.Sample.24/Commons.fs:1-20 | Sharpino.Sample.26/Commons.fs:1-20 | Sharpino.Sample.27/Commons.fs:1-20 | Sharpino.Sample.28/Commons.fs:1-20 — 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) Sharpino.Sample.22/Details.fs:2 — Sharpino.Sample.22/Details.fs:2-49 | Sharpino.Sample.24/Details.fs:2-95 | Sharpino.Sample.26/Details.fs:2-95 | Sharpino.Sample.27/Details.fs:2-95 | Sharpino.Sample.28/Details.fs:2-95 — 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) Sharpino.Sample.22/Domain/User/Commands.fs:2 — Sharpino.Sample.22/Domain/User/Commands.fs:2-28 | Sharpino.Sample.24/Domain/User/Commands.fs:2-28 | Sharpino.Sample.26/Domain/User/Commands.fs:2-28 | Sharpino.Sample.27/Domain/User/Commands.fs:2-28 | Sharpino.Sample.28/Domain/User/Commands.fs:2-28 — 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) Sharpino.Sample.22/Domain/User/Events.fs:2 — Sharpino.Sample.22/Domain/User/Events.fs:2-31 | Sharpino.Sample.24/Domain/User/Events.fs:2-31 | Sharpino.Sample.26/Domain/User/Events.fs:2-31 | Sharpino.Sample.27/Domain/User/Events.fs:2-31 | Sharpino.Sample.28/Domain/User/Events.fs:2-31 — 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) Sharpino.Sample.22/Domain/User/User.fs:2 — Sharpino.Sample.22/Domain/User/User.fs:2-61 | Sharpino.Sample.24/Domain/User/User.fs:2-61 | Sharpino.Sample.26/Domain/User/User.fs:2-61 | Sharpino.Sample.27/Domain/User/User.fs:2-61 | Sharpino.Sample.28/Domain/User/User.fs:2-61 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Sharpino.Sample.6/Dishes/Consumer.fs:1 — Sharpino.Sample.6/Dishes/Consumer.fs:1-77 | Sharpino.Sample.6/Ingredients/Consumer.fs:1-79 | Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:1-76 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:1-71 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:1-73 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×6
  • Duplicated block (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:830 — Sharpino.Lib/PgBinaryEventStore.fs:830-848 | Sharpino.Lib/PgBinaryEventStore.fs:922-940 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:829` calls `NewGuid` and `Sharpino.Lib/PgBinaryEventStore.fs:919` 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 (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1686 — Sharpino.Lib/PgBinaryEventStore.fs:1686-1704 | Sharpino.Lib/PgEventStore.fs:1668-1689 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1686` 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 (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2582 — Sharpino.Lib/PgBinaryEventStore.fs:2582-2600 | Sharpino.Lib/PgEventStore.fs:2440-2458 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2582` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3236 — Sharpino.Lib/PgBinaryEventStore.fs:3236-3254 | Sharpino.Lib/PgEventStore.fs:3266-3284 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:3236` 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) Sharpino.Sample.8/Domain/Site/Consumer.fs:52 — Sharpino.Sample.8/Domain/Site/Consumer.fs:52-70 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:63-81 — `Sharpino.Sample.8/Domain/Site/Consumer.fs` and `Sharpino.Sample.8/Domain/Truck/Consumer.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 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.8/Domain/Site/Consumer.fs:52` 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) Sharpino.Lib/PgBinaryEventStore.fs:1235 — Sharpino.Lib/PgBinaryEventStore.fs:1235-1253 | Sharpino.Lib/PgEventStore.fs:1212-1230 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1235` 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×6
  • Duplicated block (6 lines × 3) Sharpino.Lib/Cache.fs:237 — Sharpino.Lib/Cache.fs:237-242 | Sharpino.Lib/Cache.fs:312-317 | Sharpino.Lib/Cache.fs:566-571 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/Cache.fs:244` calls `DetailsCacheKey`, `Trigger` and `Sharpino.Lib/Cache.fs:318` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) Sharpino.Lib/CommandHandler.fs:97 — Sharpino.Lib/CommandHandler.fs:97-102 | Sharpino.Lib/CommandHandler.fs:114-119 | Sharpino.Sample.9/Commons.fs:55-60 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (6 lines × 3) Sharpino.Lib/CommandHandler.fs:933 — Sharpino.Lib/CommandHandler.fs:933-938 | Sharpino.Lib/CommandHandler.fs:2776-2782 | Sharpino.Lib/CommandHandler.fs:2865-2870 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:2784` calls `commands` and `Sharpino.Lib/CommandHandler.fs:2873` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) Sharpino.Lib/CommandHandler.fs:3552 — Sharpino.Lib/CommandHandler.fs:3552-3557 | Sharpino.Lib/CommandHandler.fs:3779-3784 | Sharpino.Lib/CommandHandler.fs:4005-4010 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Sharpino.Lib/StateView.fs:313 — Sharpino.Lib/StateView.fs:313-318 | Sharpino.Lib/StateView.fs:371-376 | Sharpino.Lib/StateView.fs:1242-1247 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Sharpino.Lib/StateView.fs:312 — Sharpino.Lib/StateView.fs:312-317 | Sharpino.Lib/StateView.fs:343-348 | Sharpino.Lib/StateView.fs:370-375 — 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 `Sharpino.Lib/StateView.fs:312` 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×6
  • Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs:264 — Sharpino.Lib/CommandHandler.fs:264-268 | Sharpino.Lib/Sanitizer.fs:148-152 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs:1998 — Sharpino.Lib/CommandHandler.fs:1998-2002 | Sharpino.Lib/CommandHandler.fs:2122-2126 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/CommandHandler.fs:2120` calls `Memoize2` and `Sharpino.Lib/CommandHandler.fs:1996` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) Sharpino.Lib/StateView.fs:163 — Sharpino.Lib/StateView.fs:163-167 | Sharpino.Lib/StateView.fs:204-208 — 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) Sharpino.Lib/AzureServiceBusBackplane.fs:44 — Sharpino.Lib/AzureServiceBusBackplane.fs:44-48 | Sharpino.Lib/PgNotifyBackplane.fs:34-38 — before extracting anything, compare `Sharpino.Lib/AzureServiceBusBackplane.fs` and `Sharpino.Lib/PgNotifyBackplane.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs:1228 — Sharpino.Lib/CommandHandler.fs:1228-1232 | Sharpino.Lib/CommandHandler.fs:1661-1665 — 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) Sharpino.Lib/CommandHandler.fs:5881 — Sharpino.Lib/CommandHandler.fs:5881-5885 | Sharpino.Lib/CommandHandler.fs:5939-5943 — 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×6
  • Sync-over-async blocking Sharpino.Lib/PgBinaryEventStore.fs:1856 — `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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.
  • Sync-over-async blocking Sharpino.Lib/PgBinaryEventStore.fs:2737 — `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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.
  • Sync-over-async blocking Sharpino.Lib/PgBinaryEventStore.fs:3361 — `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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.
  • Sync-over-async blocking Sharpino.Lib/PgEventStore.fs:1850 — `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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.
  • Sync-over-async blocking Sharpino.Lib/PgEventStore.fs:2570 — `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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.
  • Sync-over-async blocking Sharpino.Lib/PgEventStore.fs:3394 — `transaction` holds an async function that calls .GetAwaiter().GetResult() — 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×5
  • Duplicated block (25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1962 — Sharpino.Lib/PgBinaryEventStore.fs:1962-1986 | Sharpino.Lib/PgEventStore.fs:1960-1984 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2150 — Sharpino.Lib/PgBinaryEventStore.fs:2150-2174 | Sharpino.Lib/PgEventStore.fs:2131-2155 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2150` 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 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2955 — Sharpino.Lib/PgBinaryEventStore.fs:2955-2979 | Sharpino.Lib/PgEventStore.fs:2984-3008 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (25 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Commands.fs:1 — Sharpino.Sample.16/Models/WorkOrders/Commands.fs:1-25 | Sharpino.Sample.17/Models/WorkOrders/Commands.fs:1-25 — before extracting anything, compare `Sharpino.Sample.16/Models/WorkOrders/Commands.fs` and `Sharpino.Sample.17/Models/WorkOrders/Commands.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 (25 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:34 — Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:34-58 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:29-53 — `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.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 5 separate duplicated blocks between them, totalling at least 151 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.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. 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×5
  • Duplicated block (20 lines × 2) Sharpino.Lib/MemoryStorage.fs:470 — Sharpino.Lib/MemoryStorage.fs:470-489 | Sharpino.Lib/MemoryStorage.fs:495-514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:133 — Sharpino.Lib/PgBinaryEventStore.fs:133-152 | Sharpino.Lib/PgEventStore.fs:148-167 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:133` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1389 — Sharpino.Lib/PgBinaryEventStore.fs:1389-1408 | Sharpino.Lib/PgEventStore.fs:1369-1388 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1790 — Sharpino.Lib/PgBinaryEventStore.fs:1790-1809 | Sharpino.Lib/PgBinaryEventStore.fs:1901-1920 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:1790` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (20 lines × 2) Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs:156 — Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs:156-175 | Sharpino.Sample.17/Models/WorkOrders/WorkOrder.fs:156-175 — before extracting anything, compare `Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs` and `Sharpino.Sample.17/Models/WorkOrders/WorkOrder.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 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×5
  • Duplicated block (10 lines × 3) Sharpino.Lib/CommandHandler.fs:2422 — Sharpino.Lib/CommandHandler.fs:2422-2431 | Sharpino.Lib/CommandHandler.fs:2470-2479 | Sharpino.Lib/CommandHandler.fs:2517-2526 — 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 `Sharpino.Lib/CommandHandler.fs:2422` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Sharpino.Lib/CommandHandler.fs:2906 — Sharpino.Lib/CommandHandler.fs:2906-2915 | Sharpino.Lib/CommandHandler.fs:3187-3196 | Sharpino.Lib/CommandHandler.fs:3260-3269 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) Sharpino.Lib/MemoryStorage.fs:911 — Sharpino.Lib/MemoryStorage.fs:911-920 | Sharpino.Lib/MemoryStorage.fs:929-938 | Sharpino.Lib/MemoryStorage.fs:959-968 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) Sharpino.Sample.11/Test2.fs:80 — Sharpino.Sample.11/Test2.fs:80-89 | Sharpino.Sample.11/Test2.fs:151-160 | Sharpino.Sample.11/Test2.fs:223-232 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) Sharpino.Sample.11/Test2.fs:299 — Sharpino.Sample.11/Test2.fs:299-308 | Sharpino.Sample.11/Test2.fs:370-379 | Sharpino.Sample.11/Test2.fs:440-449 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×5
  • Duplicated block (8 lines × 4) Sharpino.Lib/CommandHandler.fs:2905 — Sharpino.Lib/CommandHandler.fs:2905-2912 | Sharpino.Lib/CommandHandler.fs:3186-3193 | Sharpino.Lib/CommandHandler.fs:3259-3266 | Sharpino.Lib/CommandHandler.fs:3330-3337 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 4) Sharpino.Lib/CommandHandler.fs:4151 — Sharpino.Lib/CommandHandler.fs:4151-4158 | Sharpino.Lib/CommandHandler.fs:4299-4306 | Sharpino.Lib/CommandHandler.fs:4448-4455 | Sharpino.Lib/CommandHandler.fs:5638-5645 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:5648` calls `fun` and `Sharpino.Lib/CommandHandler.fs:4160` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 4) Sharpino.Lib/CommandHandler.fs:4160 — Sharpino.Lib/CommandHandler.fs:4160-4167 | Sharpino.Lib/CommandHandler.fs:4308-4315 | Sharpino.Lib/CommandHandler.fs:4457-4464 | Sharpino.Lib/CommandHandler.fs:5650-5657 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:693 — Sharpino.Lib/PgBinaryEventStore.fs:693-700 | Sharpino.Lib/PgBinaryEventStore.fs:784-791 | Sharpino.Lib/PgEventStore.fs:859-866 | Sharpino.Lib/PgEventStore.fs:951-958 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:960 — Sharpino.Lib/PgBinaryEventStore.fs:960-970 | Sharpino.Lib/PgBinaryEventStore.fs:3378-3385 | Sharpino.Lib/PgEventStore.fs:744-754 | Sharpino.Lib/PgEventStore.fs:3411-3418 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×5
  • Duplicated block (5 lines × 3) Sharpino.Lib/CommandHandler.fs:84 — Sharpino.Lib/CommandHandler.fs:84-88 | Sharpino.Lib/CommandHandler.fs:132-136 | Sharpino.Lib/Sanitizer.fs:150-154 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (5 lines × 3) Sharpino.Lib/CommandHandler.fs:639 — Sharpino.Lib/CommandHandler.fs:639-643 | Sharpino.Lib/CommandHandler.fs:722-726 | Sharpino.Lib/CommandHandler.fs:958-962 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Sharpino.Lib/CommandHandler.fs:930 — Sharpino.Lib/CommandHandler.fs:930-934 | Sharpino.Lib/CommandHandler.fs:1147-1151 | Sharpino.Lib/CommandHandler.fs:1155-1159 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Sharpino.Lib/StateView.fs:452 — Sharpino.Lib/StateView.fs:452-456 | Sharpino.Lib/StateView.fs:492-496 | Sharpino.Lib/StateView.fs:560-564 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Sharpino.Sample.16/MaterialManager.fs:104 — Sharpino.Sample.16/MaterialManager.fs:104-108 | Sharpino.Sample.16/MaterialManager.fs:143-147 | Sharpino.Sample.17/MaterialManager.fs:119-123 — `Sharpino.Sample.16/MaterialManager.fs` and `Sharpino.Sample.17/MaterialManager.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 4 separate duplicated blocks between them, totalling at least 107 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×5
  • Low cohesion: MemoryStorage (LCOM4 14) Sharpino.Lib/MemoryStorage.fs:27 — MemoryStorage's methods fall into 14 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 14 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: PgBinaryStore (LCOM4 4) Sharpino.Lib/PgBinaryEventStore.fs:35 — PgBinaryStore's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: PgEventStore (LCOM4 4) Sharpino.Lib/PgEventStore.fs:52 — PgEventStore's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CourseManager (LCOM4 4) Sharpino.Sample.11/CourseManager.fs:22 — CourseManager's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CourseManager (LCOM4 4) Sharpino.Sample.14/CourseManager.fs:26 — CourseManager'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.
D1 · Cyclomatic Complexity · Main.main (cyclomatic 60) · ×4
  • Main.main (cyclomatic 60) Sharpino.Sample.24/Program.fs:20 — Main.main has cyclomatic complexity 60 (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.
  • Main.main (cyclomatic 60) Sharpino.Sample.26/Program.fs:20 — Main.main has cyclomatic complexity 60 (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.
  • Main.main (cyclomatic 60) Sharpino.Sample.27/Program.fs:20 — Main.main has cyclomatic complexity 60 (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.
  • Main.main (cyclomatic 60) Sharpino.Sample.28/Program.fs:20 — Main.main has cyclomatic complexity 60 (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.
D2 · Cognitive Complexity · Main.main (cognitive 105) · ×4
  • Main.main (cognitive 105) Sharpino.Sample.24/Program.fs:20 — Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 17 (57 pts), if/else 20 (42 pts), boolean chains 6 (nesting depth added 62). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • Main.main (cognitive 105) Sharpino.Sample.26/Program.fs:20 — Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 17 (57 pts), if/else 20 (42 pts), boolean chains 6 (nesting depth added 62). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • Main.main (cognitive 105) Sharpino.Sample.27/Program.fs:20 — Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 17 (57 pts), if/else 20 (42 pts), boolean chains 6 (nesting depth added 62). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • Main.main (cognitive 105) Sharpino.Sample.28/Program.fs:20 — Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 17 (57 pts), if/else 20 (42 pts), boolean chains 6 (nesting depth added 62). 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Sharpino.Sample.17/MaterialManager.fs:1 — Sharpino.Sample.17/MaterialManager.fs:1-157 | Sharpino.Sample.22/Program.fs:1-249 | Sharpino.Sample.24/Program.fs:1-275 | Sharpino.Sample.26/Program.fs:1-275 | Sharpino.Sample.27/Program.fs:1-273 | Sharpino.Sample.28/Program.fs:1-273 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Sharpino.Sample.22/Domain/Todo/Commands.fs:2 — Sharpino.Sample.22/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.24/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.25/Models/Todo/Commands.fs:2-30 | Sharpino.Sample.26/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.27/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.28/Domain/Todo/Commands.fs:2-29 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Sharpino.Sample.22/Domain/Todo/Events.fs:2 — Sharpino.Sample.22/Domain/Todo/Events.fs:2-29 | Sharpino.Sample.24/Domain/Todo/Events.fs:2-29 | Sharpino.Sample.25/Models/Todo/Events.fs:2-29 | Sharpino.Sample.26/Domain/Todo/Events.fs:2-29 | Sharpino.Sample.27/Domain/Todo/Events.fs:2-29 | Sharpino.Sample.28/Domain/Todo/Events.fs:2-29 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Sharpino.Sample.22/Domain/Todo/Todo.fs:1 — Sharpino.Sample.22/Domain/Todo/Todo.fs:1-64 | Sharpino.Sample.24/Domain/Todo/Todo.fs:1-64 | Sharpino.Sample.25/Models/Todo/Todo.fs:1-72 | Sharpino.Sample.26/Domain/Todo/Todo.fs:1-64 | Sharpino.Sample.27/Domain/Todo/Todo.fs:1-64 | Sharpino.Sample.28/Domain/Todo/Todo.fs:1-64 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×4
  • Duplicated block (23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:956 — Sharpino.Lib/PgBinaryEventStore.fs:956-978 | Sharpino.Lib/PgEventStore.fs:740-762 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgEventStore.fs:738` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:955` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1047 — Sharpino.Lib/PgBinaryEventStore.fs:1047-1069 | Sharpino.Lib/PgEventStore.fs:1018-1040 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1047` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgEventStore.fs:1043` calls `fun` and `Sharpino.Lib/PgBinaryEventStore.fs:1071` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) Sharpino.Lib/StateView.fs:1038 — Sharpino.Lib/StateView.fs:1038-1060 | Sharpino.Lib/StateView.fs:1208-1230 — 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 `Sharpino.Lib/StateView.fs:1038` 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 (23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1798 — Sharpino.Lib/PgBinaryEventStore.fs:1798-1820 | Sharpino.Lib/PgEventStore.fs:1790-1815 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1798` 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×4
  • Duplicated block (22 lines × 2) Sharpino.Lib/CommandHandler.fs:1506 — Sharpino.Lib/CommandHandler.fs:1506-1527 | Sharpino.Lib/CommandHandler.fs:1592-1613 — 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 `Sharpino.Lib/CommandHandler.fs:1506` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:843 — Sharpino.Lib/PgBinaryEventStore.fs:843-864 | Sharpino.Lib/PgEventStore.fs:621-642 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1659 — Sharpino.Lib/PgBinaryEventStore.fs:1659-1680 | Sharpino.Lib/PgEventStore.fs:1639-1660 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2408 — Sharpino.Lib/PgBinaryEventStore.fs:2408-2429 | Sharpino.Lib/PgEventStore.fs:2816-2837 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2408` 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.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×4
  • Duplicated block (21–22 lines × 2) Sharpino.Lib/CommandHandler.fs:2434 — Sharpino.Lib/CommandHandler.fs:2434-2455 | Sharpino.Lib/CommandHandler.fs:2482-2502 — 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 `Sharpino.Lib/CommandHandler.fs:2434` 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 (21–22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:378 — Sharpino.Lib/PgBinaryEventStore.fs:378-399 | Sharpino.Lib/PgEventStore.fs:391-411 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:378` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21–22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2080 — Sharpino.Lib/PgBinaryEventStore.fs:2080-2101 | Sharpino.Lib/PgEventStore.fs:2211-2231 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2080` 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 × 2) Sharpino.Lib/PgBinaryEventStore.fs:2117 — Sharpino.Lib/PgBinaryEventStore.fs:2117-2138 | Sharpino.Lib/PgEventStore.fs:2096-2116 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2117` 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×4
  • Duplicated block (12 lines × 4) Sharpino.Lib/CommandHandler.fs:1701 — Sharpino.Lib/CommandHandler.fs:1701-1712 | Sharpino.Lib/CommandHandler.fs:1798-1809 | Sharpino.Lib/CommandHandler.fs:1894-1905 | Sharpino.Lib/CommandHandler.fs:5790-5801 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (12 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:677 — Sharpino.Lib/PgBinaryEventStore.fs:677-688 | Sharpino.Lib/PgBinaryEventStore.fs:765-776 | Sharpino.Lib/PgEventStore.fs:843-854 | Sharpino.Lib/PgEventStore.fs:932-943 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:1213 — Sharpino.Lib/PgBinaryEventStore.fs:1213-1224 | Sharpino.Lib/PgBinaryEventStore.fs:1656-1667 | Sharpino.Lib/PgEventStore.fs:1190-1201 | Sharpino.Lib/PgEventStore.fs:1636-1647 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:1225` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:1668` 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 (12 lines × 4) Sharpino.Sample.24/DetailsRefactor.fs:2 — Sharpino.Sample.24/DetailsRefactor.fs:2-13 | Sharpino.Sample.26/DetailsRefactor.fs:2-13 | Sharpino.Sample.27/DetailsRefactor.fs:2-13 | Sharpino.Sample.28/DetailsRefactor.fs:2-13 — `Sharpino.Sample.24/DetailsRefactor.fs` and `Sharpino.Sample.26/DetailsRefactor.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 2 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×4
  • Duplicated block (11 lines × 3) Sharpino.Lib.Core/Utils.fs:58 — Sharpino.Lib.Core/Utils.fs:58-68 | Sharpino.Lib.Core/Utils.fs:73-83 | Sharpino.Lib.Core/Utils.fs:87-97 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 3) Sharpino.Sample.11/Models/Student/Consumer.fs:26 — Sharpino.Sample.11/Models/Student/Consumer.fs:26-37 | Sharpino.Sample.14/Models/Student/Consumer.fs:26-37 | Sharpino.Sample.9/models/Student/Consumer.fs:21-31 — before extracting anything, compare `Sharpino.Sample.11/Models/Student/Consumer.fs` and `Sharpino.Sample.14/Models/Student/Consumer.fs` as WHOLE FILES: this scan already matched 6 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 (11 lines × 3) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:263 — Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:263-273 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:300-310 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:379-389 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 3) Sharpino.Lib/CommandHandler.fs:3371 — Sharpino.Lib/CommandHandler.fs:3371-3383 | Sharpino.Lib/CommandHandler.fs:3601-3611 | Sharpino.Lib/CommandHandler.fs:3827-3837 — 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.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: PgBinaryStore Sharpino.Lib/PgBinaryEventStore.fs:35 — TooManyMethods — 90 methods. The bar is 30 methods; this is 60 over it, 3.00× 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: PgEventStore Sharpino.Lib/PgEventStore.fs:52 — TooManyMethods — 90 methods. The bar is 30 methods; this is 60 over it, 3.00× 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: MemoryStorage Sharpino.Lib/MemoryStorage.fs:27 — TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× 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.
D35 · Change Coupling · Change coupling · ×3
  • Change coupling: Context.fs ↔ Context.fs Sharpino.Sample/Domain/Categories/Context.fs:1 — `Sharpino.Sample/Domain/Categories/Context.fs` and `Sharpino.Sample/Domain/Tags/Context.fs` change together 77% of the time (17 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `c95b9d86` refactor samples; `a7f8d64e` wip; `d9af08cf` refactor naming — run `git show` on any of them.
  • Change coupling: CommandHandler.fs ↔ MemoryStorage.fs Sharpino.Lib/CommandHandler.fs:1 — `Sharpino.Lib/CommandHandler.fs` and `Sharpino.Lib/MemoryStorage.fs` change together 59% of the time (51 of the 87 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 51 shared commits counted here, the most recent 3 are `45470694` sanytize events on event store; `6ceddf45` added new async multi stream stuff; `d36e4f4d` added new async eventstore+commands — run `git show` on any of them.
  • Change coupling: CommandHandler.fs ↔ PgEventStore.fs Sharpino.Lib/CommandHandler.fs:1 — `Sharpino.Lib/CommandHandler.fs` and `Sharpino.Lib/PgEventStore.fs` change together 51% of the time (71 of the 140 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 71 shared commits counted here, the most recent 3 are `45470694` sanytize events on event store; `ddd62a8c` mailboxprocessor + r/w separate connections; `1ace3260` Improve&fix lock 4 high concurrency — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×3
  • Duplicated block (31 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:336 — Sharpino.Lib/PgBinaryEventStore.fs:336-366 | Sharpino.Lib/PgEventStore.fs:349-379 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (31 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Events.fs:1 — Sharpino.Sample.16/Models/WorkOrders/Events.fs:1-31 | Sharpino.Sample.17/Models/WorkOrders/Events.fs:1-31 — before extracting anything, compare `Sharpino.Sample.16/Models/WorkOrders/Events.fs` and `Sharpino.Sample.17/Models/WorkOrders/Events.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 (31 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:73 — Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:73-103 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:72-102 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.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 6 separate duplicated blocks between them, totalling at least 95 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:73` 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×3
  • Duplicated block (24 lines × 2) Sharpino.Lib/CommandHandler.fs:3758 — Sharpino.Lib/CommandHandler.fs:3758-3781 | Sharpino.Lib/CommandHandler.fs:3984-4007 — 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 (24 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1630 — Sharpino.Lib/PgBinaryEventStore.fs:1630-1653 | Sharpino.Lib/PgEventStore.fs:1610-1633 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1630` 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 (24 lines × 2) Sharpino.Sample.16/Models/Materials/Events.fs:1 — Sharpino.Sample.16/Models/Materials/Events.fs:1-24 | Sharpino.Sample.17/Models/Materials/Events.fs:1-24 — before extracting anything, compare `Sharpino.Sample.16/Models/Materials/Events.fs` and `Sharpino.Sample.17/Models/Materials/Events.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.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×3
  • Duplicated block (20 lines × 3) Sharpino.Lib/CommandHandler.fs:4787 — Sharpino.Lib/CommandHandler.fs:4787-4806 | Sharpino.Lib/CommandHandler.fs:5086-5105 | Sharpino.Lib/CommandHandler.fs:5379-5398 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (20 lines × 3) Sharpino.Sample.11/Models/Course/Consumer.fs:21 — Sharpino.Sample.11/Models/Course/Consumer.fs:21-40 | Sharpino.Sample.14/Models/Course/Consumer.fs:21-40 | Sharpino.Sample.9/models/Course/Consumer.fs:21-40 — before extracting anything, compare `Sharpino.Sample.11/Models/Course/Consumer.fs` and `Sharpino.Sample.14/Models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 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 (20 lines × 3) Sharpino.Sample.16/MaterialManager.fs:84 — Sharpino.Sample.16/MaterialManager.fs:84-103 | Sharpino.Sample.16/MaterialManager.fs:123-142 | Sharpino.Sample.17/MaterialManager.fs:99-118 — `Sharpino.Sample.16/MaterialManager.fs` and `Sharpino.Sample.17/MaterialManager.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 4 separate duplicated blocks between them, totalling at least 107 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 · Duplicated block (18–19 lines × 2) · ×3
  • Duplicated block (18–19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:424 — Sharpino.Lib/PgBinaryEventStore.fs:424-442 | Sharpino.Lib/PgEventStore.fs:2019-2036 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:424` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1991 — Sharpino.Lib/PgBinaryEventStore.fs:1991-2009 | Sharpino.Lib/PgEventStore.fs:1989-2006 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1991` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (18–19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2431 — Sharpino.Lib/PgBinaryEventStore.fs:2431-2449 | Sharpino.Lib/PgEventStore.fs:2278-2295 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×3
  • Duplicated block (15 lines × 3) Sharpino.Lib/CommandHandler.fs:706 — Sharpino.Lib/CommandHandler.fs:706-720 | Sharpino.Lib/CommandHandler.fs:804-818 | Sharpino.Lib/CommandHandler.fs:942-956 — 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 `Sharpino.Lib/CommandHandler.fs:706` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) Sharpino.Lib/CommandHandler.fs:3525 — Sharpino.Lib/CommandHandler.fs:3525-3539 | Sharpino.Lib/CommandHandler.fs:3755-3769 | Sharpino.Lib/CommandHandler.fs:3981-3995 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 3) Sharpino.Sample.11/Models/Student/Consumer.fs:3 — Sharpino.Sample.11/Models/Student/Consumer.fs:3-17 | Sharpino.Sample.11/Models/Student2/Consumer.fs:3-17 | Sharpino.Sample.14/Models/Student/Consumer.fs:3-17 — `Sharpino.Sample.11/Models/Student/Consumer.fs` and `Sharpino.Sample.11/Models/Student2/Consumer.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 5 separate duplicated blocks between them, totalling at least 78 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 · Duplicated block (11–12 lines × 4) · ×3
  • Duplicated block (11–12 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:870 — Sharpino.Lib/PgBinaryEventStore.fs:870-880 | Sharpino.Lib/PgBinaryEventStore.fs:970-980 | Sharpino.Lib/PgEventStore.fs:648-659 | Sharpino.Lib/PgEventStore.fs:754-765 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:648` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:868` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:969` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11–12 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:2325 — Sharpino.Lib/PgBinaryEventStore.fs:2325-2335 | Sharpino.Lib/PgBinaryEventStore.fs:2367-2377 | Sharpino.Lib/PgBinaryEventStore.fs:2409-2420 | Sharpino.Lib/PgEventStore.fs:2817-2828 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2406` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2323` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11–12 lines × 4) Sharpino.Sample.6/Dishes/Consumer.fs:66 — Sharpino.Sample.6/Dishes/Consumer.fs:66-77 | Sharpino.Sample.6/Ingredients/Consumer.fs:69-79 | Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:65-76 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:60-71 — before extracting anything, compare `Sharpino.Sample.6/Dishes/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:62` calls `ResetFallbackAggregateStateRetriever` and `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:58` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×3
  • Duplicated block (11 lines × 5) Sharpino.Lib/CommandHandler.fs:4614 — Sharpino.Lib/CommandHandler.fs:4614-4624 | Sharpino.Lib/CommandHandler.fs:4892-4902 | Sharpino.Lib/CommandHandler.fs:5185-5195 | Sharpino.Lib/CommandHandler.fs:5478-5488 | Sharpino.Lib/CommandHandler.fs:5566-5576 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 5) Sharpino.Sample.10/Models/Account/Consumer.fs:20 — Sharpino.Sample.10/Models/Account/Consumer.fs:20-32 | Sharpino.Sample.10/Models/Counter/Consumer.fs:20-32 | Sharpino.Sample.6/Dishes/Consumer.fs:18-28 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:20-30 | Sharpino.Sample.8/Domain/Site/Consumer.fs:20-30 — `Sharpino.Sample.10/Models/Account/Consumer.fs` and `Sharpino.Sample.10/Models/Counter/Consumer.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 3 separate duplicated blocks between them, totalling at least 40 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (11 lines × 5) Sharpino.Sample.11/Models/Course/Consumer.fs:21 — Sharpino.Sample.11/Models/Course/Consumer.fs:21-31 | Sharpino.Sample.11/Models/Student/Consumer.fs:26-37 | Sharpino.Sample.11/Models/Student2/Consumer.fs:23-34 | Sharpino.Sample.14/Models/Course/Consumer.fs:21-31 | Sharpino.Sample.14/Models/Student/Consumer.fs:26-37 — before extracting anything, compare `Sharpino.Sample.11/Models/Course/Consumer.fs` and `Sharpino.Sample.14/Models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×3
  • Duplicated block (10–11 lines × 2) Sharpino.Lib/PgEventStore.fs:829 — Sharpino.Lib/PgEventStore.fs:829-838 | Sharpino.Lib/PgEventStore.fs:913-923 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10–11 lines × 2) Sharpino.Sample.11/Models/Student/Student.fs:56 — Sharpino.Sample.11/Models/Student/Student.fs:56-65 | Sharpino.Sample.14/Models/Student/Student.fs:71-81 — before extracting anything, compare `Sharpino.Sample.11/Models/Student/Student.fs` and `Sharpino.Sample.14/Models/Student/Student.fs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10–11 lines × 2) Sharpino.Sample.11/Test2.fs:87 — Sharpino.Sample.11/Test2.fs:87-97 | Sharpino.Sample.11/Test2.fs:307-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×3
  • Duplicated block (10 lines × 4) Sharpino.Lib/MemoryStorage.fs:480 — Sharpino.Lib/MemoryStorage.fs:480-489 | Sharpino.Lib/MemoryStorage.fs:505-514 | Sharpino.Lib/MemoryStorage.fs:663-672 | Sharpino.Lib/MemoryStorage.fs:687-696 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (10 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:179 — Sharpino.Lib/PgBinaryEventStore.fs:179-188 | Sharpino.Lib/PgBinaryEventStore.fs:281-292 | Sharpino.Lib/PgEventStore.fs:194-203 | Sharpino.Lib/PgEventStore.fs:297-308 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Sharpino.Sample.11/Test2.fs:169 — Sharpino.Sample.11/Test2.fs:169-178 | Sharpino.Sample.11/Test2.fs:206-215 | Sharpino.Sample.11/Test2.fs:388-397 | Sharpino.Sample.11/Test2.fs:424-433 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×3
  • Duplicated block (9 lines × 4) Sharpino.Lib/CommandHandler.fs:4210 — Sharpino.Lib/CommandHandler.fs:4210-4218 | Sharpino.Lib/CommandHandler.fs:4360-4368 | Sharpino.Lib/CommandHandler.fs:4509-4517 | Sharpino.Lib/CommandHandler.fs:5711-5719 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:180 — Sharpino.Lib/PgBinaryEventStore.fs:180-190 | Sharpino.Lib/PgEventStore.fs:195-205 | Sharpino.Lib/PgEventStore.fs:829-837 | Sharpino.Lib/PgEventStore.fs:914-922 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 4) Sharpino.Lib/StateView.fs:139 — Sharpino.Lib/StateView.fs:139-147 | Sharpino.Lib/StateView.fs:182-190 | Sharpino.Lib/StateView.fs:220-228 | Sharpino.Lib/StateView.fs:254-262 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:139` 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) Sharpino.Lib/CommandHandler.fs:2405 — Sharpino.Lib/CommandHandler.fs:2405-2413 | Sharpino.Lib/CommandHandler.fs:2453-2461 | Sharpino.Lib/CommandHandler.fs:2500-2508 — 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 `Sharpino.Lib/CommandHandler.fs:2405` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Sharpino.Sample.12/Models/Student/Commands.fs:14 — Sharpino.Sample.12/Models/Student/Commands.fs:14-22 | Sharpino.Sample.9/models/Student/Commands.fs:15-23 | Sharpino.Sample.9/models/Teacher/Commands.fs:17-25 — before extracting anything, compare `Sharpino.Sample.12/Models/Student/Commands.fs` and `Sharpino.Sample.9/models/Student/Commands.fs` as WHOLE FILES: 85% 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 (9 lines × 3) Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:41 — Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:41-49 | Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:42-50 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:42-50 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.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 6 separate duplicated blocks between them, totalling at least 95 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 · Duplicated block (7–8 lines × 2) · ×3
  • Duplicated block (7–8 lines × 2) Sharpino.Lib/CommandHandler.fs:927 — Sharpino.Lib/CommandHandler.fs:927-934 | Sharpino.Lib/CommandHandler.fs:1145-1151 — 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–8 lines × 2) Sharpino.Lib/MemoryStorage.fs:1136 — Sharpino.Lib/MemoryStorage.fs:1136-1142 | Sharpino.Lib/MemoryStorage.fs:1150-1157 — 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–8 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1008 — Sharpino.Lib/PgBinaryEventStore.fs:1008-1014 | Sharpino.Lib/PgBinaryEventStore.fs:1043-1050 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×3
  • Duplicated block (7 lines × 3) Sharpino.Lib/CommandHandler.fs:270 — Sharpino.Lib/CommandHandler.fs:270-276 | Sharpino.Lib/CommandHandler.fs:307-313 | Sharpino.Lib/CommandHandler.fs:346-352 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (7 lines × 3) Sharpino.Lib/StateView.fs:583 — Sharpino.Lib/StateView.fs:583-589 | Sharpino.Lib/StateView.fs:727-733 | Sharpino.Lib/StateView.fs:753-759 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (7 lines × 3) Sharpino.Lib/StateView.fs:794 — Sharpino.Lib/StateView.fs:794-800 | Sharpino.Lib/StateView.fs:822-828 | Sharpino.Lib/StateView.fs:858-864 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×3
  • Duplicated block (6 lines × 5) Sharpino.Lib/CommandHandler.fs:266 — Sharpino.Lib/CommandHandler.fs:266-271 | Sharpino.Lib/CommandHandler.fs:303-308 | Sharpino.Lib/CommandHandler.fs:342-347 | Sharpino.Lib/CommandHandler.fs:362-367 | Sharpino.Lib/CommandHandler.fs:1168-1173 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 5) Sharpino.Lib/StateView.fs:440 — Sharpino.Lib/StateView.fs:440-445 | Sharpino.Lib/StateView.fs:479-484 | Sharpino.Lib/StateView.fs:548-553 | Sharpino.Lib/StateView.fs:609-614 | Sharpino.Lib/StateView.fs:636-641 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 5) Sharpino.Lib/StateView.fs:603 — Sharpino.Lib/StateView.fs:603-608 | Sharpino.Lib/StateView.fs:630-635 | Sharpino.Lib/StateView.fs:661-666 | Sharpino.Lib/StateView.fs:688-693 | Sharpino.Lib/StateView.fs:721-726 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:603` 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.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×3
  • Duplicated block (5 lines × 6) Sharpino.Lib/CommandHandler.fs:930 — Sharpino.Lib/CommandHandler.fs:930-934 | Sharpino.Lib/CommandHandler.fs:1147-1151 | Sharpino.Lib/CommandHandler.fs:2773-2779 | Sharpino.Lib/CommandHandler.fs:4851-4856 | Sharpino.Lib/CommandHandler.fs:5144-5149 | Sharpino.Lib/CommandHandler.fs:5437-5442 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 × 6) Sharpino.Lib/PgBinaryEventStore.fs:2325 — Sharpino.Lib/PgBinaryEventStore.fs:2325-2329 | Sharpino.Lib/PgBinaryEventStore.fs:2367-2371 | Sharpino.Lib/PgBinaryEventStore.fs:2409-2413 | Sharpino.Lib/PgEventStore.fs:2817-2821 | Sharpino.Lib/PgEventStore.fs:2902-2906 | Sharpino.Lib/PgEventStore.fs:2951-2955 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2406` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2323` 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 × 6) Sharpino.Lib/StateView.fs:821 — Sharpino.Lib/StateView.fs:821-825 | Sharpino.Lib/StateView.fs:857-861 | Sharpino.Lib/StateView.fs:889-893 | Sharpino.Lib/StateView.fs:913-917 | Sharpino.Lib/StateView.fs:992-996 | Sharpino.Lib/StateView.fs:1030-1034 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Sharpino.Lib/Commons.fs:1 — Sharpino.Lib/Commons.fs:1-36 | Sharpino.Sample.2/Commons.fs:2-38 | Sharpino.Sample.6/Commons.fs:1-37 | Sharpino.Sample/Commons.fs:1-37 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Sharpino.Sample.11/Models/Student/Student.fs:1 — Sharpino.Sample.11/Models/Student/Student.fs:1-65 | Sharpino.Sample.12/Models/Student/Student.fs:1-65 | Sharpino.Sample.14/Models/Student/Student.fs:1-81 | Sharpino.Sample.9/models/Student/Student.fs:1-59 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (60 lines × 5) · ×2
  • Duplicated block (60 lines × 5) Sharpino.Sample.22/Domain/Todo/Todo.fs:1 — Sharpino.Sample.22/Domain/Todo/Todo.fs:1-60 | Sharpino.Sample.24/Domain/Todo/Todo.fs:1-60 | Sharpino.Sample.26/Domain/Todo/Todo.fs:1-60 | Sharpino.Sample.27/Domain/Todo/Todo.fs:1-60 | Sharpino.Sample.28/Domain/Todo/Todo.fs:1-60 — before extracting anything, compare `Sharpino.Sample.22/Domain/Todo/Todo.fs` and `Sharpino.Sample.24/Domain/Todo/Todo.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 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 (60 lines × 5) Sharpino.Sample.22/Domain/User/User.fs:2 — Sharpino.Sample.22/Domain/User/User.fs:2-61 | Sharpino.Sample.24/Domain/User/User.fs:2-61 | Sharpino.Sample.26/Domain/User/User.fs:2-61 | Sharpino.Sample.27/Domain/User/User.fs:2-61 | Sharpino.Sample.28/Domain/User/User.fs:2-61 — before extracting anything, compare `Sharpino.Sample.22/Domain/User/User.fs` and `Sharpino.Sample.24/Domain/User/User.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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×2
  • Duplicated block (40 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1137 — Sharpino.Lib/PgBinaryEventStore.fs:1137-1176 | Sharpino.Lib/PgEventStore.fs:1116-1155 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1137` 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 (40 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1862 — Sharpino.Lib/PgBinaryEventStore.fs:1862-1901 | Sharpino.Lib/PgEventStore.fs:1856-1895 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1862` 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.
D4 · Code Duplication · Duplicated block (35–36 lines × 2) · ×2
  • Duplicated block (35–36 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1824 — Sharpino.Lib/PgBinaryEventStore.fs:1824-1859 | Sharpino.Lib/PgEventStore.fs:1819-1853 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1824` 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 (35–36 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2904 — Sharpino.Lib/PgBinaryEventStore.fs:2904-2939 | Sharpino.Lib/PgEventStore.fs:2730-2764 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×2
  • Duplicated block (35 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1573 — Sharpino.Lib/PgBinaryEventStore.fs:1573-1607 | Sharpino.Lib/PgEventStore.fs:1551-1585 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1573` 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 (35 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:121 — Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:121-155 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:123-157 — `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.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 5 separate duplicated blocks between them, totalling at least 151 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:121` 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.
D4 · Code Duplication · Duplicated block (30 lines × 5) · ×2
  • Duplicated block (30 lines × 5) Sharpino.Sample.22/Details.fs:2 — Sharpino.Sample.22/Details.fs:2-31 | Sharpino.Sample.24/Details.fs:2-31 | Sharpino.Sample.26/Details.fs:2-31 | Sharpino.Sample.27/Details.fs:2-31 | Sharpino.Sample.28/Details.fs:2-31 — `Sharpino.Sample.22/Details.fs` and `Sharpino.Sample.24/Details.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 2 separate duplicated blocks between them, totalling at least 50 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 (30 lines × 5) Sharpino.Sample.22/Domain/User/Events.fs:2 — Sharpino.Sample.22/Domain/User/Events.fs:2-31 | Sharpino.Sample.24/Domain/User/Events.fs:2-31 | Sharpino.Sample.26/Domain/User/Events.fs:2-31 | Sharpino.Sample.27/Domain/User/Events.fs:2-31 | Sharpino.Sample.28/Domain/User/Events.fs:2-31 — before extracting anything, compare `Sharpino.Sample.22/Domain/User/Events.fs` and `Sharpino.Sample.24/Domain/User/Events.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.
D4 · Code Duplication · Duplicated block (27 lines × 5) · ×2
  • Duplicated block (27 lines × 5) Sharpino.Sample.22/Domain/Todo/Events.fs:2 — Sharpino.Sample.22/Domain/Todo/Events.fs:2-28 | Sharpino.Sample.24/Domain/Todo/Events.fs:2-28 | Sharpino.Sample.26/Domain/Todo/Events.fs:2-28 | Sharpino.Sample.27/Domain/Todo/Events.fs:2-28 | Sharpino.Sample.28/Domain/Todo/Events.fs:2-28 — before extracting anything, compare `Sharpino.Sample.22/Domain/Todo/Events.fs` and `Sharpino.Sample.24/Domain/Todo/Events.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 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 (27 lines × 5) Sharpino.Sample.22/Domain/User/Commands.fs:2 — Sharpino.Sample.22/Domain/User/Commands.fs:2-28 | Sharpino.Sample.24/Domain/User/Commands.fs:2-28 | Sharpino.Sample.26/Domain/User/Commands.fs:2-28 | Sharpino.Sample.27/Domain/User/Commands.fs:2-28 | Sharpino.Sample.28/Domain/User/Commands.fs:2-28 — before extracting anything, compare `Sharpino.Sample.22/Domain/User/Commands.fs` and `Sharpino.Sample.24/Domain/User/Commands.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.
D4 · Code Duplication · Duplicated block (25–27 lines × 2) · ×2
  • Duplicated block (25–27 lines × 2) Sharpino.Lib/RabbitMq.fs:68 — Sharpino.Lib/RabbitMq.fs:68-94 | Sharpino.Lib/RabbitMq.fs:95-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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–27 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:18 — Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:18-44 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:20-44 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs` 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 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.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×2
  • Duplicated block (23–24 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1022 — Sharpino.Lib/PgBinaryEventStore.fs:1022-1045 | Sharpino.Lib/PgEventStore.fs:994-1016 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1022` 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 (23–24 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1519 — Sharpino.Lib/PgBinaryEventStore.fs:1519-1542 | Sharpino.Lib/PgEventStore.fs:1394-1416 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1519` 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.
D4 · Code Duplication · Duplicated block (23 lines × 4) · ×2
  • Duplicated block (23 lines × 4) Sharpino.Lib/Commons.fs:14 — Sharpino.Lib/Commons.fs:14-36 | Sharpino.Sample.2/Commons.fs:13-35 | Sharpino.Sample.6/Commons.fs:12-34 | Sharpino.Sample/Commons.fs:12-34 — `Sharpino.Lib/Commons.fs` and `Sharpino.Sample.2/Commons.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 23 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 (23 lines × 4) Sharpino.Sample.24/DetailsRefactor.fs:39 — Sharpino.Sample.24/DetailsRefactor.fs:39-61 | Sharpino.Sample.26/DetailsRefactor.fs:39-61 | Sharpino.Sample.27/DetailsRefactor.fs:39-61 | Sharpino.Sample.28/DetailsRefactor.fs:39-61 — `Sharpino.Sample.24/DetailsRefactor.fs` and `Sharpino.Sample.26/DetailsRefactor.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 2 separate duplicated blocks between them, totalling at least 35 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×2
  • Duplicated block (21 lines × 3) Sharpino.Lib/CommandHandler.fs:1344 — Sharpino.Lib/CommandHandler.fs:1344-1364 | Sharpino.Lib/CommandHandler.fs:2066-2086 | Sharpino.Lib/CommandHandler.fs:2158-2178 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 3) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:150 — Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:150-170 | Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:203-223 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:152-172 — `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.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 5 separate duplicated blocks between them, totalling at least 151 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 · Duplicated block (20–21 lines × 2) · ×2
  • Duplicated block (20–21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1203 — Sharpino.Lib/PgBinaryEventStore.fs:1203-1222 | Sharpino.Lib/PgBinaryEventStore.fs:1645-1665 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:1203` 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 (20–21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2707 — Sharpino.Lib/PgBinaryEventStore.fs:2707-2727 | Sharpino.Lib/PgEventStore.fs:2541-2560 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2707` 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.
D4 · Code Duplication · Duplicated block (20 lines × 5) · ×2
  • Duplicated block (20 lines × 5) Sharpino.Sample.22/Commons.fs:1 — Sharpino.Sample.22/Commons.fs:1-20 | Sharpino.Sample.24/Commons.fs:1-20 | Sharpino.Sample.26/Commons.fs:1-20 | Sharpino.Sample.27/Commons.fs:1-20 | Sharpino.Sample.28/Commons.fs:1-20 — `Sharpino.Sample.22/Commons.fs` and `Sharpino.Sample.24/Commons.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 20 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 (20 lines × 5) Sharpino.Sample.22/Details.fs:30 — Sharpino.Sample.22/Details.fs:30-49 | Sharpino.Sample.24/Details.fs:53-72 | Sharpino.Sample.26/Details.fs:53-72 | Sharpino.Sample.27/Details.fs:53-72 | Sharpino.Sample.28/Details.fs:53-72 — `Sharpino.Sample.22/Details.fs` and `Sharpino.Sample.24/Details.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 2 separate duplicated blocks between them, totalling at least 50 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 · Duplicated block (16–19 lines × 2) · ×2
  • Duplicated block (16–19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2261 — Sharpino.Lib/PgBinaryEventStore.fs:2261-2276 | Sharpino.Lib/PgBinaryEventStore.fs:2291-2309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16–19 lines × 2) Sharpino.Lib/PgEventStore.fs:2843 — Sharpino.Lib/PgEventStore.fs:2843-2858 | Sharpino.Lib/PgEventStore.fs:2868-2886 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×2
  • Duplicated block (18 lines × 3) Sharpino.Sample.11/Models/Student/Student.fs:38 — Sharpino.Sample.11/Models/Student/Student.fs:38-55 | Sharpino.Sample.12/Models/Student/Student.fs:42-59 | Sharpino.Sample.9/models/Student/Student.fs:35-52 — before extracting anything, compare `Sharpino.Sample.12/Models/Student/Student.fs` and `Sharpino.Sample.9/models/Student/Student.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 (18 lines × 3) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:243 — Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:243-260 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:280-297 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:359-376 — 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×2
  • Duplicated block (16–17 lines × 3) Sharpino.Lib/CommandHandler.fs:4628 — Sharpino.Lib/CommandHandler.fs:4628-4643 | Sharpino.Lib/CommandHandler.fs:4914-4930 | Sharpino.Lib/CommandHandler.fs:5207-5223 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16–17 lines × 3) Sharpino.Sample.11/Models/Student/Consumer.fs:60 — Sharpino.Sample.11/Models/Student/Consumer.fs:60-75 | Sharpino.Sample.11/Models/Student2/Consumer.fs:57-73 | Sharpino.Sample.14/Models/Student/Consumer.fs:60-75 — `Sharpino.Sample.11/Models/Student/Consumer.fs` and `Sharpino.Sample.11/Models/Student2/Consumer.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 5 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.11/Models/Student/Consumer.fs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×2
  • Duplicated block (14–16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:248 — Sharpino.Lib/PgBinaryEventStore.fs:248-263 | Sharpino.Lib/PgEventStore.fs:266-279 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:248` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgEventStore.fs:266` calls `CommitAsync`, `ConfigureAwait` and `Sharpino.Lib/PgBinaryEventStore.fs:248` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14–16 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:21 — Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:21-34 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:22-37 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×2
  • Duplicated block (12–13 lines × 4) Sharpino.Lib/CommandHandler.fs:4141 — Sharpino.Lib/CommandHandler.fs:4141-4152 | Sharpino.Lib/CommandHandler.fs:4289-4300 | Sharpino.Lib/CommandHandler.fs:4438-4449 | Sharpino.Lib/CommandHandler.fs:5623-5635 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (12–13 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:858 — Sharpino.Lib/PgBinaryEventStore.fs:858-869 | Sharpino.Lib/PgBinaryEventStore.fs:2754-2766 | Sharpino.Lib/PgEventStore.fs:636-647 | Sharpino.Lib/PgEventStore.fs:2586-2597 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2
  • Duplicated block (13 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:853 — Sharpino.Lib/PgBinaryEventStore.fs:853-866 | Sharpino.Lib/PgBinaryEventStore.fs:956-968 | Sharpino.Lib/PgEventStore.fs:631-644 | Sharpino.Lib/PgEventStore.fs:740-752 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:853` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:868` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:970` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:2316 — Sharpino.Lib/PgBinaryEventStore.fs:2316-2328 | Sharpino.Lib/PgBinaryEventStore.fs:2358-2370 | Sharpino.Lib/PgEventStore.fs:2893-2905 | Sharpino.Lib/PgEventStore.fs:2942-2954 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×2
  • Duplicated block (12–13 lines × 3) Sharpino.Lib/CommandHandler.fs:1260 — Sharpino.Lib/CommandHandler.fs:1260-1272 | Sharpino.Lib/CommandHandler.fs:1959-1971 | Sharpino.Lib/CommandHandler.fs:2033-2044 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (12–13 lines × 3) Sharpino.Lib/StateView.fs:596 — Sharpino.Lib/StateView.fs:596-608 | Sharpino.Lib/StateView.fs:623-635 | Sharpino.Lib/StateView.fs:655-666 — 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 `Sharpino.Lib/StateView.fs:596` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) Sharpino.Lib/CommandHandler.fs:153 — Sharpino.Lib/CommandHandler.fs:153-164 | Sharpino.Lib/CommandHandler.fs:212-224 — 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 `Sharpino.Lib/CommandHandler.fs:153` 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 (12–13 lines × 2) Sharpino.Lib/StateView.fs:681 — Sharpino.Lib/StateView.fs:681-693 | Sharpino.Lib/StateView.fs:715-726 — 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 `Sharpino.Lib/StateView.fs:681` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) Sharpino.Lib.Core/Utils.fs:60 — Sharpino.Lib.Core/Utils.fs:60-71 | Sharpino.Lib.Core/Utils.fs:75-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib.Core/Utils.fs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) Sharpino.Lib/CommandHandler.fs:2661 — Sharpino.Lib/CommandHandler.fs:2661-2671 | Sharpino.Lib/CommandHandler.fs:2758-2769 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×2
  • Duplicated block (11 lines × 6) Sharpino.Lib/CommandHandler.fs:413 — Sharpino.Lib/CommandHandler.fs:413-423 | Sharpino.Lib/CommandHandler.fs:439-449 | Sharpino.Lib/CommandHandler.fs:472-482 | Sharpino.Lib/CommandHandler.fs:505-515 | Sharpino.Lib/CommandHandler.fs:535-545 | Sharpino.Lib/CommandHandler.fs:579-589 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:413` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 6) Sharpino.Sample.22/Domain/Todo/Todo.fs:54 — Sharpino.Sample.22/Domain/Todo/Todo.fs:54-64 | Sharpino.Sample.24/Domain/Todo/Todo.fs:54-64 | Sharpino.Sample.25/Models/Todo/Todo.fs:62-72 | Sharpino.Sample.26/Domain/Todo/Todo.fs:54-64 | Sharpino.Sample.27/Domain/Todo/Todo.fs:54-64 | Sharpino.Sample.28/Domain/Todo/Todo.fs:54-64 — before extracting anything, compare `Sharpino.Sample.22/Domain/Todo/Todo.fs` and `Sharpino.Sample.24/Domain/Todo/Todo.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 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:2748 — Sharpino.Lib/PgBinaryEventStore.fs:2748-2763 | Sharpino.Lib/PgBinaryEventStore.fs:3373-3383 | Sharpino.Lib/PgEventStore.fs:2580-2594 | Sharpino.Lib/PgEventStore.fs:3406-3416 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2748` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2765` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:3385` 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 × 4) Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:38 — Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:38-48 | Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:56-66 | Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:74-84 | Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:92-102 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–11 lines × 4) · ×2
  • Duplicated block (10–11 lines × 4) Sharpino.Sample.11/Test2.fs:193 — Sharpino.Sample.11/Test2.fs:193-203 | Sharpino.Sample.11/Test2.fs:268-278 | Sharpino.Sample.11/Test2.fs:412-421 | Sharpino.Sample.11/Test2.fs:483-492 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.11/Test2.fs:280` calls `Stop` and `Sharpino.Sample.11/Test2.fs:204` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10–11 lines × 4) Sharpino.Sample.6/Dishes/Consumer.fs:64 — Sharpino.Sample.6/Dishes/Consumer.fs:64-74 | Sharpino.Sample.6/Ingredients/Consumer.fs:67-77 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:58-68 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:60-69 — before extracting anything, compare `Sharpino.Sample.6/Dishes/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×2
  • Duplicated block (10 lines × 6) Sharpino.Sample.22/Domain/Todo/Commands.fs:14 — Sharpino.Sample.22/Domain/Todo/Commands.fs:14-23 | Sharpino.Sample.24/Domain/Todo/Commands.fs:14-23 | Sharpino.Sample.25/Models/Todo/Commands.fs:14-23 | Sharpino.Sample.26/Domain/Todo/Commands.fs:14-23 | Sharpino.Sample.27/Domain/Todo/Commands.fs:14-23 | Sharpino.Sample.28/Domain/Todo/Commands.fs:14-23 — before extracting anything, compare `Sharpino.Sample.22/Domain/Todo/Commands.fs` and `Sharpino.Sample.24/Domain/Todo/Commands.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 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 (10 lines × 6) Sharpino.Sample.22/Domain/Todo/Events.fs:20 — Sharpino.Sample.22/Domain/Todo/Events.fs:20-29 | Sharpino.Sample.24/Domain/Todo/Events.fs:20-29 | Sharpino.Sample.25/Models/Todo/Events.fs:20-29 | Sharpino.Sample.26/Domain/Todo/Events.fs:20-29 | Sharpino.Sample.27/Domain/Todo/Events.fs:20-29 | Sharpino.Sample.28/Domain/Todo/Events.fs:20-29 — before extracting anything, compare `Sharpino.Sample.22/Domain/Todo/Events.fs` and `Sharpino.Sample.24/Domain/Todo/Events.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 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×2
  • Duplicated block (8–9 lines × 3) Sharpino.Lib/AzureServiceBusBackplane.fs:54 — Sharpino.Lib/AzureServiceBusBackplane.fs:54-61 | Sharpino.Lib/MqttBackplane.fs:34-42 | Sharpino.Lib/PgNotifyBackplane.fs:42-49 — before extracting anything, compare `Sharpino.Lib/AzureServiceBusBackplane.fs` and `Sharpino.Lib/PgNotifyBackplane.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8–9 lines × 3) Sharpino.Lib/PgEventStore.fs:470 — Sharpino.Lib/PgEventStore.fs:470-478 | Sharpino.Lib/PgEventStore.fs:518-525 | Sharpino.Lib/PgEventStore.fs:2694-2701 — 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 `Sharpino.Lib/PgEventStore.fs:470` 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) Sharpino.Lib/CommandHandler.fs:2570 — Sharpino.Lib/CommandHandler.fs:2570-2577 | Sharpino.Lib/CommandHandler.fs:2707-2714 | Sharpino.Lib/CommandHandler.fs:2793-2800 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 3) Sharpino.Lib/CommandHandler.fs:3312 — Sharpino.Lib/CommandHandler.fs:3312-3319 | Sharpino.Lib/CommandHandler.fs:3562-3569 | Sharpino.Lib/CommandHandler.fs:4221-4228 — 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 `Sharpino.Lib/CommandHandler.fs:3312` 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.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) Sharpino.Lib/CommandHandler.fs:4175 — Sharpino.Lib/CommandHandler.fs:4175-4181 | Sharpino.Lib/CommandHandler.fs:4323-4329 | Sharpino.Lib/CommandHandler.fs:4472-4478 | Sharpino.Lib/CommandHandler.fs:5671-5677 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (7 lines × 4) Sharpino.Lib/StateView.fs:821 — Sharpino.Lib/StateView.fs:821-827 | Sharpino.Lib/StateView.fs:857-863 | Sharpino.Lib/StateView.fs:889-895 | Sharpino.Lib/StateView.fs:913-919 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (5 lines × 12) · ×2
  • Duplicated block (5 lines × 12) Sharpino.Lib/CommandHandler.fs:636 — Sharpino.Lib/CommandHandler.fs:636-640 | Sharpino.Lib/CommandHandler.fs:1195-1199 | Sharpino.Lib/CommandHandler.fs:1251-1255 | Sharpino.Lib/CommandHandler.fs:1335-1339 | Sharpino.Lib/CommandHandler.fs:1441-1445 | Sharpino.Lib/CommandHandler.fs:1529-1533 | Sharpino.Lib/CommandHandler.fs:1615-1619 | Sharpino.Lib/CommandHandler.fs:1927-1931 | Sharpino.Lib/CommandHandler.fs:1950-1954 | Sharpino.Lib/CommandHandler.fs:2024-2028 | Sharpino.Lib/CommandHandler.fs:2057-2061 | Sharpino.Lib/CommandHandler.fs:2149-2153 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 12) Sharpino.Lib/PgBinaryEventStore.fs:447 — Sharpino.Lib/PgBinaryEventStore.fs:447-451 | Sharpino.Lib/PgBinaryEventStore.fs:511-516 | Sharpino.Lib/PgBinaryEventStore.fs:551-555 | Sharpino.Lib/PgBinaryEventStore.fs:2105-2109 | Sharpino.Lib/PgBinaryEventStore.fs:2180-2184 | Sharpino.Lib/PgBinaryEventStore.fs:2865-2869 | Sharpino.Lib/PgEventStore.fs:467-471 | Sharpino.Lib/PgEventStore.fs:515-519 | Sharpino.Lib/PgEventStore.fs:2041-2045 | Sharpino.Lib/PgEventStore.fs:2161-2165 | Sharpino.Lib/PgEventStore.fs:2235-2239 | Sharpino.Lib/PgEventStore.fs:2691-2695 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:508` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:444` 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.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×2
  • Duplicated block (5 lines × 8) Sharpino.Lib/PgBinaryEventStore.fs:446 — Sharpino.Lib/PgBinaryEventStore.fs:446-450 | Sharpino.Lib/PgBinaryEventStore.fs:510-515 | Sharpino.Lib/PgBinaryEventStore.fs:2104-2108 | Sharpino.Lib/PgBinaryEventStore.fs:2407-2411 | Sharpino.Lib/PgEventStore.fs:466-470 | Sharpino.Lib/PgEventStore.fs:2040-2044 | Sharpino.Lib/PgEventStore.fs:2234-2238 | Sharpino.Lib/PgEventStore.fs:2815-2819 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:508` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:444` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 8) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:180 — Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:180-184 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:205-209 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:227-231 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:258-262 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:295-299 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:327-331 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:374-378 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:407-411 — all 8 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.
D1 · Cyclomatic Complexity · Main.main (cyclomatic 57) · ×1
  • Main.main (cyclomatic 57) Sharpino.Sample.22/Program.fs:14 — Main.main has cyclomatic complexity 57 (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.
D1 · Cyclomatic Complexity · AggregateCache3.SetupL2AndBackplane (cyclomatic 19) · ×1
  • AggregateCache3.SetupL2AndBackplane (cyclomatic 19) Sharpino.Lib/Cache.fs:462 — AggregateCache3.SetupL2AndBackplane has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Sanitizer.sanitizeAggregateStreamWithInitialState (cyclomatic 18) · ×1
  • Sanitizer.sanitizeAggregateStreamWithInitialState (cyclomatic 18) Sharpino.Lib/Sanitizer.fs:32 — Sanitizer.sanitizeAggregateStreamWithInitialState has cyclomatic complexity 18 (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.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: Sharpino.Lib/Cache.fs Sharpino.Lib/Cache.fs:462 — Sharpino.Lib/Cache.fs changed 3 times in last 90 days, max cyclomatic complexity 19 in AggregateCache3.SetupL2AndBackplane at line 462. 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-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 19:40:21 +01:00' --until='2026-11-08 19:40:21 +01:00' --full-history --no-merges -- Sharpino.Lib/Cache.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.
D2 · Cognitive Complexity · Main.main (cognitive 101) · ×1
  • Main.main (cognitive 101) Sharpino.Sample.22/Program.fs:14 — Main.main has cognitive complexity 101 (threshold 15). Drivers by points: match/switch 16 (56 pts), if/else 18 (39 pts), boolean chains 6 (nesting depth added 61). 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.
D2 · Cognitive Complexity · AggregateCache3.SetupL2AndBackplane (cognitive 53) · ×1
  • AggregateCache3.SetupL2AndBackplane (cognitive 53) Sharpino.Lib/Cache.fs:462 — AggregateCache3.SetupL2AndBackplane has cognitive complexity 53 (threshold 15). Drivers by points: if/else 15 (42 pts), match/switch 2 (10 pts), boolean chains 1 (nesting depth added 35). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · add_opt_lock2.process_migrations (cognitive 36) · ×1
  • add_opt_lock2.process_migrations (cognitive 36) scratch/add_opt_lock2.py:4 — add_opt_lock2.process_migrations has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 5 (13 pts), boolean chains 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Sanitizer.sanitizeAggregateStreamWithInitialState (cognitive 34) · ×1
  • Sanitizer.sanitizeAggregateStreamWithInitialState (cognitive 34) Sharpino.Lib/Sanitizer.fs:32 — Sanitizer.sanitizeAggregateStreamWithInitialState has cognitive complexity 34 (threshold 15). Drivers by points: match/switch 7 (21 pts), if/else 2 (7 pts), loops 2 (6 pts) (nesting depth added 23). 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.
D2 · Cognitive Complexity · CommandHandler.runThreeNAggregateCommandsMd (cognitive 33) · ×1
  • CommandHandler.runThreeNAggregateCommandsMd (cognitive 33) Sharpino.Lib/CommandHandler.fs:5542 — CommandHandler.runThreeNAggregateCommandsMd has cognitive complexity 33 (threshold 15). Drivers by points: loops 3 (12 pts), match/switch 3 (12 pts), if/else 6 (9 pts) (nesting depth added 21). 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.
D2 · Cognitive Complexity · DetailsCache.SetupL2AndBackplane (cognitive 32) · ×1
  • DetailsCache.SetupL2AndBackplane (cognitive 32) Sharpino.Lib/Cache.fs:128 — DetailsCache.SetupL2AndBackplane has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 3 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · DetailsCache.RefreshAsync (cognitive 27) · ×1
  • DetailsCache.RefreshAsync (cognitive 27) Sharpino.Lib/Cache.fs:195 — DetailsCache.RefreshAsync has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 3 (9 pts), error handling 2 (7 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AggregateCache3.Memoize (cognitive 21) · ×1
  • AggregateCache3.Memoize (cognitive 21) Sharpino.Lib/Cache.fs:697 — AggregateCache3.Memoize has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 4 (6 pts), error handling 1 (3 pts) (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. This shape REPEATS in the file: one other method here (AggregateCache3.MemoizeAsync) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · AggregateCache3.MemoizeAsync (cognitive 21) · ×1
  • AggregateCache3.MemoizeAsync (cognitive 21) Sharpino.Lib/Cache.fs:735 — AggregateCache3.MemoizeAsync has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 4 (6 pts), error handling 1 (3 pts) (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. This shape REPEATS in the file: one other method here (AggregateCache3.Memoize) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · CommandHandler.runTwoNAggregateCommandsMd (cognitive 17) · ×1
  • CommandHandler.runTwoNAggregateCommandsMd (cognitive 17) Sharpino.Lib/CommandHandler.fs:4083 — CommandHandler.runTwoNAggregateCommandsMd has cognitive complexity 17 (threshold 15). Drivers by points: loops 2 (6 pts), match/switch 2 (6 pts), if/else 4 (5 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. This shape REPEATS in the file: 2 other methods here (CommandHandler.runTwoNAggregateCommandsMdAsync2, CommandHandler.runTwoNAggregateCommandsMdAsync3) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · CommandHandler.runTwoNAggregateCommandsMdAsync2 (cognitive 17) · ×1
  • CommandHandler.runTwoNAggregateCommandsMdAsync2 (cognitive 17) Sharpino.Lib/CommandHandler.fs:4225 — CommandHandler.runTwoNAggregateCommandsMdAsync2 has cognitive complexity 17 (threshold 15). Drivers by points: loops 2 (6 pts), match/switch 2 (6 pts), if/else 4 (5 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. This shape REPEATS in the file: 2 other methods here (CommandHandler.runTwoNAggregateCommandsMd, CommandHandler.runTwoNAggregateCommandsMdAsync3) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · CommandHandler.runTwoNAggregateCommandsMdAsync3 (cognitive 17) · ×1
  • CommandHandler.runTwoNAggregateCommandsMdAsync3 (cognitive 17) Sharpino.Lib/CommandHandler.fs:4374 — CommandHandler.runTwoNAggregateCommandsMdAsync3 has cognitive complexity 17 (threshold 15). Drivers by points: loops 2 (6 pts), match/switch 2 (6 pts), if/else 4 (5 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. This shape REPEATS in the file: 2 other methods here (CommandHandler.runTwoNAggregateCommandsMd, CommandHandler.runTwoNAggregateCommandsMdAsync2) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · StateView.getLastAggregateSnapshot (cognitive 16) · ×1
  • StateView.getLastAggregateSnapshot (cognitive 16) Sharpino.Lib/StateView.fs:138 — StateView.getLastAggregateSnapshot has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 4 (8 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: Categories.fs, Tags.fs, Todos.fs Sharpino.Sample/Domain/Categories/Categories.fs — 3 files — `Sharpino.Sample/Domain/Categories/Categories.fs`, `Sharpino.Sample/Domain/Tags/Tags.fs`, `Sharpino.Sample/Domain/Todos/Todos.fs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication · Near-duplicate member family (5 members, 57 shared lines) · ×1
  • Near-duplicate member family (5 members, 57 shared lines) Sharpino.Sample.22/TodoManager.fs:1 — Sharpino.Sample.22/TodoManager.fs:1-159 | Sharpino.Sample.24/TodoManager.fs:1-297 | Sharpino.Sample.26/TodoManager.fs:1-297 | Sharpino.Sample.27/TodoManager.fs:1-297 | Sharpino.Sample.28/TodoManager.fs:1-297 — These 5 members are variants of one another: a block of 57 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 (4 members, 35 shared lines) · ×1
  • Near-duplicate member family (4 members, 35 shared lines) Sharpino.Sample.24/DetailsRefactor.fs:2 — Sharpino.Sample.24/DetailsRefactor.fs:2-61 | Sharpino.Sample.26/DetailsRefactor.fs:2-61 | Sharpino.Sample.27/DetailsRefactor.fs:2-61 | Sharpino.Sample.28/DetailsRefactor.fs:2-61 — These 4 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 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 43 shared lines) · ×1
  • Near-duplicate member family (3 members, 43 shared lines) Sharpino.Sample.11/Models/Student/Consumer.fs:1 — Sharpino.Sample.11/Models/Student/Consumer.fs:1-98 | Sharpino.Sample.11/Models/Student2/Consumer.fs:2-96 | Sharpino.Sample.14/Models/Student/Consumer.fs:1-98 — These 3 members are variants of one another: a block of 43 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 3 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 3 times.
D4 · Code Duplication · Near-duplicate member pair (2341 shared lines) · ×1
  • Near-duplicate member pair (2341 shared lines) Sharpino.Lib/PgBinaryEventStore.fs:1 — Sharpino.Lib/PgBinaryEventStore.fs:1-3497 | Sharpino.Lib/PgEventStore.fs:1-3525 — These two members are variants of one another: 2341 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 · Near-duplicate member pair (130 shared lines) · ×1
  • Near-duplicate member pair (130 shared lines) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:1 — Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:1-227 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:1-200 — These two members are variants of one another: 130 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 · Near-duplicate member pair (71 shared lines) · ×1
  • Near-duplicate member pair (71 shared lines) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:1 — Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:1-109 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:1-108 — These two members are variants of one another: 71 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 · Near-duplicate member pair (40 shared lines) · ×1
  • Near-duplicate member pair (40 shared lines) Sharpino.Lib/AzureServiceBusBackplane.fs:1 — Sharpino.Lib/AzureServiceBusBackplane.fs:1-164 | Sharpino.Lib/PgNotifyBackplane.fs:1-148 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/GoodsContainer.fs:1 — Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/GoodsContainer.fs:1-42 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/GoodsContainer.fs:1-41 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (9 members, 50+ identical tokens) Sharpino.Sample.10/Models/Account/Consumer.fs:1 — Sharpino.Sample.10/Models/Account/Consumer.fs:1-61 | Sharpino.Sample.10/Models/Counter/Consumer.fs:1-61 | Sharpino.Sample.9/models/Balance/Consumer.fs:1-86 | Sharpino.Sample.9/models/Course/Consumer.fs:1-102 | Sharpino.Sample.9/models/Item/Consumer.fs:1-103 | Sharpino.Sample.9/models/Reservation/Consumer.fs:1-95 | Sharpino.Sample.9/models/Student/Consumer.fs:1-93 | Sharpino.Sample.9/models/Teacher/Consumer.fs:1-92 | Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:2-76 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication · Duplicated block (175 lines × 5) · ×1
  • Duplicated block (175 lines × 5) Sharpino.Sample.22/Program.fs:75 — Sharpino.Sample.22/Program.fs:75-249 | Sharpino.Sample.24/Program.fs:101-275 | Sharpino.Sample.26/Program.fs:101-275 | Sharpino.Sample.27/Program.fs:99-273 | Sharpino.Sample.28/Program.fs:99-273 — `Sharpino.Sample.22/Program.fs` and `Sharpino.Sample.24/Program.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 6 separate duplicated blocks between them, totalling at least 275 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 · Duplicated block (151 lines × 2) · ×1
  • Duplicated block (151 lines × 2) Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs:1 — Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs:1-151 | Sharpino.Sample.17/Models/WorkOrders/WorkOrder.fs:1-151 — before extracting anything, compare `Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs` and `Sharpino.Sample.17/Models/WorkOrders/WorkOrder.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 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.
D4 · Code Duplication · Duplicated block (143–144 lines × 2) · ×1
  • Duplicated block (143–144 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3091 — Sharpino.Lib/PgBinaryEventStore.fs:3091-3233 | Sharpino.Lib/PgEventStore.fs:3120-3263 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:3091` 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.
D4 · Code Duplication · Duplicated block (135 lines × 4) · ×1
  • Duplicated block (135 lines × 4) Sharpino.Sample.24/TodoManager.fs:159 — Sharpino.Sample.24/TodoManager.fs:159-293 | Sharpino.Sample.26/TodoManager.fs:159-293 | Sharpino.Sample.27/TodoManager.fs:159-293 | Sharpino.Sample.28/TodoManager.fs:159-293 — `Sharpino.Sample.24/TodoManager.fs` and `Sharpino.Sample.26/TodoManager.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 6 separate duplicated blocks between them, totalling at least 338 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.24/TodoManager.fs:159` 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.
D4 · Code Duplication · Duplicated block (105 lines × 4) · ×1
  • Duplicated block (105 lines × 4) Sharpino.Sample.24/TodoManager.fs:40 — Sharpino.Sample.24/TodoManager.fs:40-144 | Sharpino.Sample.26/TodoManager.fs:40-144 | Sharpino.Sample.27/TodoManager.fs:40-144 | Sharpino.Sample.28/TodoManager.fs:40-144 — `Sharpino.Sample.24/TodoManager.fs` and `Sharpino.Sample.26/TodoManager.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 6 separate duplicated blocks between them, totalling at least 338 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 · Duplicated block (102 lines × 3) · ×1
  • Duplicated block (102 lines × 3) Sharpino.Lib/CommandHandler.fs:4661 — Sharpino.Lib/CommandHandler.fs:4661-4762 | Sharpino.Lib/CommandHandler.fs:4958-5059 | Sharpino.Lib/CommandHandler.fs:5251-5352 — 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 `Sharpino.Lib/CommandHandler.fs:4661` 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, `Sharpino.Lib/CommandHandler.fs:5060` calls `crossAggregatesConstraint` and `Sharpino.Lib/CommandHandler.fs:4763` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (96 lines × 4) · ×1
  • Duplicated block (96 lines × 4) Sharpino.Lib/CommandHandler.fs:989 — Sharpino.Lib/CommandHandler.fs:989-1084 | Sharpino.Lib/CommandHandler.fs:3410-3505 | Sharpino.Lib/CommandHandler.fs:3638-3733 | Sharpino.Lib/CommandHandler.fs:3864-3959 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (78 lines × 2) · ×1
  • Duplicated block (78 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Commands.fs:10 — Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Commands.fs:10-87 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Commands.fs:8-85 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Commands.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Commands.fs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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.
D4 · Code Duplication · Duplicated block (75 lines × 2) · ×1
  • Duplicated block (75 lines × 2) Sharpino.Sample.11/Models/Student/Consumer.fs:24 — Sharpino.Sample.11/Models/Student/Consumer.fs:24-98 | Sharpino.Sample.14/Models/Student/Consumer.fs:24-98 — before extracting anything, compare `Sharpino.Sample.11/Models/Student/Consumer.fs` and `Sharpino.Sample.14/Models/Student/Consumer.fs` as WHOLE FILES: this scan already matched 6 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.
D4 · Code Duplication · Duplicated block (70 lines × 2) · ×1
  • Duplicated block (70 lines × 2) Sharpino.Sample.16/Commons.fs:1 — Sharpino.Sample.16/Commons.fs:1-70 | Sharpino.Sample.17/Commons.fs:1-70 — `Sharpino.Sample.16/Commons.fs` and `Sharpino.Sample.17/Commons.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 70 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 · Duplicated block (69 lines × 2) · ×1
  • Duplicated block (69 lines × 2) Sharpino.Sample.16/MaterialManager.fs:26 — Sharpino.Sample.16/MaterialManager.fs:26-94 | Sharpino.Sample.17/MaterialManager.fs:41-109 — `Sharpino.Sample.16/MaterialManager.fs` and `Sharpino.Sample.17/MaterialManager.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 4 separate duplicated blocks between them, totalling at least 107 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.16/MaterialManager.fs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Sample.16/MaterialManager.fs:23` calls `MemoryStorage` and `Sharpino.Sample.17/MaterialManager.fs:38` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (67 lines × 2) · ×1
  • Duplicated block (67 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3256 — Sharpino.Lib/PgBinaryEventStore.fs:3256-3322 | Sharpino.Lib/PgEventStore.fs:3286-3352 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:3256` 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.
D4 · Code Duplication · Duplicated block (65 lines × 2) · ×1
  • Duplicated block (65 lines × 2) Sharpino.Sample.11/Models/Course/Consumer.fs:33 — Sharpino.Sample.11/Models/Course/Consumer.fs:33-97 | Sharpino.Sample.14/Models/Course/Consumer.fs:33-97 — before extracting anything, compare `Sharpino.Sample.11/Models/Course/Consumer.fs` and `Sharpino.Sample.14/Models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 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.
D4 · Code Duplication · Duplicated block (61–62 lines × 2) · ×1
  • Duplicated block (61–62 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3348 — Sharpino.Lib/PgBinaryEventStore.fs:3348-3409 | Sharpino.Lib/PgEventStore.fs:3382-3442 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:3348` 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.
D4 · Code Duplication · Duplicated block (59 lines × 3) · ×1
  • Duplicated block (59 lines × 3) Sharpino.Lib/CommandHandler.fs:4126 — Sharpino.Lib/CommandHandler.fs:4126-4184 | Sharpino.Lib/CommandHandler.fs:4274-4332 | Sharpino.Lib/CommandHandler.fs:4423-4481 — 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.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Commands.fs:15 — Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Commands.fs:15-69 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Commands.fs:15-69 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Commands.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Commands.fs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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.
D4 · Code Duplication · Duplicated block (53 lines × 2) · ×1
  • Duplicated block (53 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:75 — Sharpino.Lib/PgBinaryEventStore.fs:75-127 | Sharpino.Lib/PgEventStore.fs:90-142 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (51–52 lines × 2) · ×1
  • Duplicated block (51–52 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1083 — Sharpino.Lib/PgBinaryEventStore.fs:1083-1134 | Sharpino.Lib/PgEventStore.fs:1063-1113 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (49–50 lines × 2) · ×1
  • Duplicated block (49–50 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2626 — Sharpino.Lib/PgBinaryEventStore.fs:2626-2674 | Sharpino.Lib/PgEventStore.fs:2460-2509 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2675` calls `LogError` and `Sharpino.Lib/PgEventStore.fs:2512` 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.
D4 · Code Duplication · Duplicated block (44–46 lines × 2) · ×1
  • Duplicated block (44–46 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1280 — Sharpino.Lib/PgBinaryEventStore.fs:1280-1323 | Sharpino.Lib/PgEventStore.fs:1257-1302 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1257` 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.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) Sharpino.Sample.16/Models/Materials/Material.fs:1 — Sharpino.Sample.16/Models/Materials/Material.fs:1-46 | Sharpino.Sample.17/Models/Materials/Material.fs:1-46 — before extracting anything, compare `Sharpino.Sample.16/Models/Materials/Material.fs` and `Sharpino.Sample.17/Models/Materials/Material.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.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:156 — Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:156-198 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:158-200 — `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.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 5 separate duplicated blocks between them, totalling at least 151 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:156` 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.
D4 · Code Duplication · Duplicated block (41–42 lines × 2) · ×1
  • Duplicated block (41–42 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Good.fs:6 — Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Good.fs:6-47 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Good.fs:6-46 — 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.
D4 · Code Duplication · Duplicated block (37–42 lines × 2) · ×1
  • Duplicated block (37–42 lines × 2) Sharpino.Sample/AppVersions.fs:100 — Sharpino.Sample/AppVersions.fs:100-136 | Sharpino.Sample/AppVersions.fs:146-187 — 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 `Sharpino.Sample/AppVersions.fs:100` 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.
D4 · Code Duplication · Duplicated block (41 lines × 4) · ×1
  • Duplicated block (41 lines × 4) Sharpino.Sample.24/Details.fs:24 — Sharpino.Sample.24/Details.fs:24-64 | Sharpino.Sample.26/Details.fs:24-64 | Sharpino.Sample.27/Details.fs:24-64 | Sharpino.Sample.28/Details.fs:24-64 — `Sharpino.Sample.24/Details.fs` and `Sharpino.Sample.26/Details.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 4 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.24/Details.fs:24` 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.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) Sharpino.Sample.11/Models/Student/Student.fs:11 — Sharpino.Sample.11/Models/Student/Student.fs:11-51 | Sharpino.Sample.14/Models/Student/Student.fs:11-51 — before extracting anything, compare `Sharpino.Sample.11/Models/Student/Student.fs` and `Sharpino.Sample.14/Models/Student/Student.fs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `Sharpino.Sample.11/Models/Student/Student.fs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (39–40 lines × 2) · ×1
  • Duplicated block (39–40 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:208 — Sharpino.Lib/PgBinaryEventStore.fs:208-247 | Sharpino.Lib/PgEventStore.fs:223-261 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgEventStore.fs:261` calls `ExecuteNonQueryAsync`, `ConfigureAwait` and `Sharpino.Lib/PgBinaryEventStore.fs:247` does not — after which the two agree again for 5 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.
D4 · Code Duplication · Duplicated block (38–39 lines × 2) · ×1
  • Duplicated block (38–39 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Commands.fs:10 — Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Commands.fs:10-48 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/Commands.fs:9-46 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Commands.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/Commands.fs` 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 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. 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.
D4 · Code Duplication · Duplicated block (3–38 lines × 5) · ×1
  • Duplicated block (3–38 lines × 5) Sharpino.Sample.22/TodoManager.fs:24 — Sharpino.Sample.22/TodoManager.fs:24-26 | Sharpino.Sample.24/TodoManager.fs:1-38 | Sharpino.Sample.26/TodoManager.fs:1-38 | Sharpino.Sample.27/TodoManager.fs:1-38 | Sharpino.Sample.28/TodoManager.fs:1-38 — `Sharpino.Sample.22/TodoManager.fs` and `Sharpino.Sample.24/TodoManager.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 4 separate duplicated blocks between them, totalling at least 98 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 · Duplicated block (37–38 lines × 3) · ×1
  • Duplicated block (37–38 lines × 3) Sharpino.Lib/CommandHandler.fs:2994 — Sharpino.Lib/CommandHandler.fs:2994-3031 | Sharpino.Lib/CommandHandler.fs:3065-3102 | Sharpino.Lib/CommandHandler.fs:3125-3161 — 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.
D4 · Code Duplication · Duplicated block (34–38 lines × 3) · ×1
  • Duplicated block (34–38 lines × 3) Sharpino.Lib/CommandHandler.fs:4833 — Sharpino.Lib/CommandHandler.fs:4833-4870 | Sharpino.Lib/CommandHandler.fs:5130-5163 | Sharpino.Lib/CommandHandler.fs:5423-5456 — 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 `Sharpino.Lib/CommandHandler.fs:4833` 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.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2982 — Sharpino.Lib/PgBinaryEventStore.fs:2982-3019 | Sharpino.Lib/PgEventStore.fs:3011-3048 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3053 — Sharpino.Lib/PgBinaryEventStore.fs:3053-3088 | Sharpino.Lib/PgEventStore.fs:3082-3117 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:3053` 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.
D4 · Code Duplication · Duplicated block (34 lines × 5) · ×1
  • Duplicated block (34 lines × 5) Sharpino.Sample.22/TodoManager.fs:73 — Sharpino.Sample.22/TodoManager.fs:73-106 | Sharpino.Sample.24/TodoManager.fs:134-167 | Sharpino.Sample.26/TodoManager.fs:134-167 | Sharpino.Sample.27/TodoManager.fs:134-167 | Sharpino.Sample.28/TodoManager.fs:134-167 — `Sharpino.Sample.22/TodoManager.fs` and `Sharpino.Sample.24/TodoManager.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 4 separate duplicated blocks between them, totalling at least 98 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.22/TodoManager.fs:73` 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.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:158 — Sharpino.Lib/PgBinaryEventStore.fs:158-190 | Sharpino.Lib/PgEventStore.fs:173-205 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:158` 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.
D4 · Code Duplication · Duplicated block (27–33 lines × 2) · ×1
  • Duplicated block (27–33 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:479 — Sharpino.Lib/PgBinaryEventStore.fs:479-505 | Sharpino.Lib/PgEventStore.fs:429-461 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:479` 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.
D4 · Code Duplication · Duplicated block (31–32 lines × 3) · ×1
  • Duplicated block (31–32 lines × 3) Sharpino.Lib/CommandHandler.fs:1379 — Sharpino.Lib/CommandHandler.fs:1379-1410 | Sharpino.Lib/CommandHandler.fs:1721-1751 | Sharpino.Lib/CommandHandler.fs:1818-1848 — 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.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1543 — Sharpino.Lib/PgBinaryEventStore.fs:1543-1574 | Sharpino.Lib/PgEventStore.fs:1417-1448 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1543` 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.
D4 · Code Duplication · Duplicated block (31 lines × 4) · ×1
  • Duplicated block (31 lines × 4) Sharpino.Sample.24/Details.fs:65 — Sharpino.Sample.24/Details.fs:65-95 | Sharpino.Sample.26/Details.fs:65-95 | Sharpino.Sample.27/Details.fs:65-95 | Sharpino.Sample.28/Details.fs:65-95 — `Sharpino.Sample.24/Details.fs` and `Sharpino.Sample.26/Details.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 4 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.24/Details.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.
D4 · Code Duplication · Duplicated block (30–31 lines × 2) · ×1
  • Duplicated block (30–31 lines × 2) Sharpino.Sample.12/Models/Student/Student.fs:30 — Sharpino.Sample.12/Models/Student/Student.fs:30-59 | Sharpino.Sample.9/models/Student/Student.fs:22-52 — before extracting anything, compare `Sharpino.Sample.12/Models/Student/Student.fs` and `Sharpino.Sample.9/models/Student/Student.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 `Sharpino.Sample.12/Models/Student/Student.fs:30` 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.
D4 · Code Duplication · Duplicated block (28–30 lines × 4) · ×1
  • Duplicated block (28–30 lines × 4) Sharpino.Lib/CommandHandler.fs:1459 — Sharpino.Lib/CommandHandler.fs:1459-1487 | Sharpino.Lib/CommandHandler.fs:1549-1577 | Sharpino.Lib/CommandHandler.fs:2723-2750 | Sharpino.Lib/CommandHandler.fs:2812-2841 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (24–30 lines × 4) · ×1
  • Duplicated block (24–30 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:1757 — Sharpino.Lib/PgBinaryEventStore.fs:1757-1786 | Sharpino.Lib/PgBinaryEventStore.fs:3040-3063 | Sharpino.Lib/PgEventStore.fs:1744-1773 | Sharpino.Lib/PgEventStore.fs:3069-3092 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1757` 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) Sharpino.Sample.16/Models/Products/Product.fs:1 — Sharpino.Sample.16/Models/Products/Product.fs:1-29 | Sharpino.Sample.17/Models/Products/Product.fs:1-29 — before extracting anything, compare `Sharpino.Sample.16/Models/Products/Product.fs` and `Sharpino.Sample.17/Models/Products/Product.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.
D4 · Code Duplication · Duplicated block (28 lines × 5) · ×1
  • Duplicated block (28 lines × 5) Sharpino.Sample.22/Domain/Todo/Commands.fs:2 — Sharpino.Sample.22/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.24/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.26/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.27/Domain/Todo/Commands.fs:2-29 | Sharpino.Sample.28/Domain/Todo/Commands.fs:2-29 — before extracting anything, compare `Sharpino.Sample.22/Domain/Todo/Commands.fs` and `Sharpino.Sample.24/Domain/Todo/Commands.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 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.
D4 · Code Duplication · Duplicated block (26–28 lines × 2) · ×1
  • Duplicated block (26–28 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:267 — Sharpino.Lib/PgBinaryEventStore.fs:267-294 | Sharpino.Lib/PgEventStore.fs:283-308 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:267` 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 5) · ×1
  • Duplicated block (26–27 lines × 5) Sharpino.Sample.22/Program.fs:4 — Sharpino.Sample.22/Program.fs:4-29 | Sharpino.Sample.24/Program.fs:9-35 | Sharpino.Sample.26/Program.fs:9-35 | Sharpino.Sample.27/Program.fs:9-35 | Sharpino.Sample.28/Program.fs:9-35 — `Sharpino.Sample.22/Program.fs` and `Sharpino.Sample.24/Program.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 6 separate duplicated blocks between them, totalling at least 275 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 · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) Sharpino.Sample.22/Program.fs:33 — Sharpino.Sample.22/Program.fs:33-59 | Sharpino.Sample.24/Program.fs:42-68 | Sharpino.Sample.26/Program.fs:42-68 — `Sharpino.Sample.22/Program.fs` and `Sharpino.Sample.24/Program.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 6 separate duplicated blocks between them, totalling at least 275 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 · Duplicated block (4–27 lines × 4) · ×1
  • Duplicated block (4–27 lines × 4) Sharpino.Sample.24/Program.fs:37 — Sharpino.Sample.24/Program.fs:37-40 | Sharpino.Sample.26/Program.fs:37-40 | Sharpino.Sample.27/Program.fs:40-66 | Sharpino.Sample.28/Program.fs:40-66 — `Sharpino.Sample.24/Program.fs` and `Sharpino.Sample.26/Program.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 7 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Sample.27/Program.fs:40` calls `TodoManager` and `Sharpino.Sample.24/Program.fs:37` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:24 — Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:24-50 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Cart.fs:22-48 — 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:71 — Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:71-96 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:78-104 — `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.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 5 separate duplicated blocks between them, totalling at least 151 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:310 — Sharpino.Lib/PgBinaryEventStore.fs:310-333 | Sharpino.Lib/PgEventStore.fs:321-346 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21–25 lines × 4) · ×1
  • Duplicated block (21–25 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:805 — Sharpino.Lib/PgBinaryEventStore.fs:805-826 | Sharpino.Lib/PgBinaryEventStore.fs:899-922 | Sharpino.Lib/PgEventStore.fs:585-605 | Sharpino.Lib/PgEventStore.fs:679-703 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:805` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:829` calls `NewGuid` and `Sharpino.Lib/PgBinaryEventStore.fs:922` 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.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1996 — Sharpino.Lib/PgBinaryEventStore.fs:1996-2020 | Sharpino.Lib/PgBinaryEventStore.fs:2055-2078 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (20–25 lines × 2) · ×1
  • Duplicated block (20–25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2773 — Sharpino.Lib/PgBinaryEventStore.fs:2773-2797 | Sharpino.Lib/PgEventStore.fs:2604-2623 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2773` 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.
D4 · Code Duplication · Duplicated block (20–23 lines × 2) · ×1
  • Duplicated block (20–23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2236 — Sharpino.Lib/PgBinaryEventStore.fs:2236-2255 | Sharpino.Lib/PgEventStore.fs:2774-2796 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (19–22 lines × 5) · ×1
  • Duplicated block (19–22 lines × 5) Sharpino.Sample.22/Program.fs:49 — Sharpino.Sample.22/Program.fs:49-67 | Sharpino.Sample.24/Program.fs:58-79 | Sharpino.Sample.26/Program.fs:58-79 | Sharpino.Sample.27/Program.fs:56-77 | Sharpino.Sample.28/Program.fs:56-77 — `Sharpino.Sample.22/Program.fs` and `Sharpino.Sample.24/Program.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 6 separate duplicated blocks between them, totalling at least 275 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20–22 lines × 3) · ×1
  • Duplicated block (20–22 lines × 3) Sharpino.Lib/StateView.fs:999 — Sharpino.Lib/StateView.fs:999-1018 | Sharpino.Lib/StateView.fs:1080-1101 | Sharpino.Lib/StateView.fs:1149-1170 — 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 `Sharpino.Lib/StateView.fs:999` 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.
D4 · Code Duplication · Duplicated block (19–22 lines × 2) · ×1
  • Duplicated block (19–22 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2742 — Sharpino.Lib/PgBinaryEventStore.fs:2742-2763 | Sharpino.Lib/PgEventStore.fs:2576-2594 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19–21 lines × 4) · ×1
  • Duplicated block (19–21 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:197 — Sharpino.Lib/PgBinaryEventStore.fs:197-217 | Sharpino.Lib/PgBinaryEventStore.fs:301-319 | Sharpino.Lib/PgEventStore.fs:212-232 | Sharpino.Lib/PgEventStore.fs:312-330 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19–21 lines × 2) · ×1
  • Duplicated block (19–21 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:42 — Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:42-62 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:42-60 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.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 6 separate duplicated blocks between them, totalling at least 95 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:60` calls `GetString` and `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:62` does not — after which the two agree again for 5 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.
D4 · Code Duplication · Duplicated block (13–20 lines × 8) · ×1
  • Duplicated block (13–20 lines × 8) Sharpino.Lib/PgBinaryEventStore.fs:348 — Sharpino.Lib/PgBinaryEventStore.fs:348-363 | Sharpino.Lib/PgBinaryEventStore.fs:1761-1779 | Sharpino.Lib/PgBinaryEventStore.fs:1871-1890 | Sharpino.Lib/PgBinaryEventStore.fs:3044-3056 | Sharpino.Lib/PgEventStore.fs:361-376 | Sharpino.Lib/PgEventStore.fs:1748-1766 | Sharpino.Lib/PgEventStore.fs:1865-1884 | Sharpino.Lib/PgEventStore.fs:3073-3085 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:348` 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1496 — Sharpino.Lib/PgBinaryEventStore.fs:1496-1515 | Sharpino.Lib/PgEventStore.fs:1533-1551 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1496` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgEventStore.fs:1533` calls `ExecuteNonQueryAsync` and `Sharpino.Lib/PgBinaryEventStore.fs:1496` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) Sharpino.Lib/CommandHandler.fs:4762 — Sharpino.Lib/CommandHandler.fs:4762-4780 | Sharpino.Lib/CommandHandler.fs:5062-5080 | Sharpino.Lib/CommandHandler.fs:5355-5373 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/CommandHandler.fs:5060` calls `crossAggregatesConstraint` and `Sharpino.Lib/CommandHandler.fs:4760` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 6) · ×1
  • Duplicated block (18 lines × 6) Sharpino.Lib/PgBinaryEventStore.fs:1795 — Sharpino.Lib/PgBinaryEventStore.fs:1795-1812 | Sharpino.Lib/PgBinaryEventStore.fs:1906-1923 | Sharpino.Lib/PgBinaryEventStore.fs:2774-2791 | Sharpino.Lib/PgBinaryEventStore.fs:2924-2941 | Sharpino.Lib/PgEventStore.fs:2606-2623 | Sharpino.Lib/PgEventStore.fs:2749-2766 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1795` 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) Sharpino.Sample.11/Models/Student/Consumer.fs:1 — Sharpino.Sample.11/Models/Student/Consumer.fs:1-18 | Sharpino.Sample.11/Models/Student2/Consumer.fs:2-18 — `Sharpino.Sample.11/Models/Student/Consumer.fs` and `Sharpino.Sample.11/Models/Student2/Consumer.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 5 separate duplicated blocks between them, totalling at least 78 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 · Duplicated block (16–17 lines × 7) · ×1
  • Duplicated block (16–17 lines × 7) Sharpino.Lib/CommandHandler.fs:985 — Sharpino.Lib/CommandHandler.fs:985-1000 | Sharpino.Lib/CommandHandler.fs:3405-3421 | Sharpino.Lib/CommandHandler.fs:3633-3649 | Sharpino.Lib/CommandHandler.fs:3859-3875 | Sharpino.Lib/CommandHandler.fs:4664-4680 | Sharpino.Lib/CommandHandler.fs:4961-4977 | Sharpino.Lib/CommandHandler.fs:5254-5270 — all 7 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.
D4 · Code Duplication · Duplicated block (15–17 lines × 3) · ×1
  • Duplicated block (15–17 lines × 3) Sharpino.Lib/CommandHandler.fs:2437 — Sharpino.Lib/CommandHandler.fs:2437-2452 | Sharpino.Lib/CommandHandler.fs:2485-2499 | Sharpino.Lib/CommandHandler.fs:2529-2545 — 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 `Sharpino.Lib/CommandHandler.fs:2437` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2549 — Sharpino.Lib/PgBinaryEventStore.fs:2549-2565 | Sharpino.Lib/PgEventStore.fs:2408-2423 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2549` 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.
D4 · Code Duplication · Duplicated block (13–16 lines × 6) · ×1
  • Duplicated block (13–16 lines × 6) Sharpino.Lib/PgBinaryEventStore.fs:1672 — Sharpino.Lib/PgBinaryEventStore.fs:1672-1684 | Sharpino.Lib/PgBinaryEventStore.fs:1782-1795 | Sharpino.Lib/PgBinaryEventStore.fs:1893-1906 | Sharpino.Lib/PgEventStore.fs:1652-1666 | Sharpino.Lib/PgEventStore.fs:1769-1784 | Sharpino.Lib/PgEventStore.fs:1887-1902 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1652` 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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) Sharpino.Sample.8/Domain/Site/Consumer.fs:44 — Sharpino.Sample.8/Domain/Site/Consumer.fs:44-59 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:55-70 | Sharpino.Sample.9/models/Course/Consumer.fs:60-75 | Sharpino.Sample.9/models/Item/Consumer.fs:68-83 — `Sharpino.Sample.8/Domain/Site/Consumer.fs` and `Sharpino.Sample.8/Domain/Truck/Consumer.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 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.9/models/Course/Consumer.fs:77` calls `ResetAllStates`, `Clear` and `Sharpino.Sample.8/Domain/Site/Consumer.fs:61` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–16 lines × 4) · ×1
  • Duplicated block (4–16 lines × 4) Sharpino.Lib/CommandHandler.fs:5887 — Sharpino.Lib/CommandHandler.fs:5887-5902 | Sharpino.Lib/CommandHandler.fs:5945-5960 | Sharpino.Lib/CommandHandler.fs:5971-5974 | Sharpino.Lib/CommandHandler.fs:6046-6049 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) Sharpino.Sample.12/Models/Student/Commands.fs:6 — Sharpino.Sample.12/Models/Student/Commands.fs:6-20 | Sharpino.Sample.9/models/Student/Commands.fs:6-21 — before extracting anything, compare `Sharpino.Sample.12/Models/Student/Commands.fs` and `Sharpino.Sample.9/models/Student/Commands.fs` as WHOLE FILES: 85% 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 6) · ×1
  • Duplicated block (14–15 lines × 6) Sharpino.Sample.9/models/Balance/Consumer.fs:1 — Sharpino.Sample.9/models/Balance/Consumer.fs:1-14 | Sharpino.Sample.9/models/Course/Consumer.fs:1-15 | Sharpino.Sample.9/models/Item/Consumer.fs:1-15 | Sharpino.Sample.9/models/Reservation/Consumer.fs:1-15 | Sharpino.Sample.9/models/Student/Consumer.fs:1-15 | Sharpino.Sample.9/models/Teacher/Consumer.fs:1-15 — `Sharpino.Sample.9/models/Balance/Consumer.fs` and `Sharpino.Sample.9/models/Course/Consumer.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 5 separate duplicated blocks between them, totalling at least 62 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 · Duplicated block (14–15 lines × 4) · ×1
  • Duplicated block (14–15 lines × 4) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:169 — Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:169-182 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:194-207 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:315-329 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:396-409 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:169` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) Sharpino.Sample.11/Definitions.fs:6 — Sharpino.Sample.11/Definitions.fs:6-19 | Sharpino.Sample.14/Definitions.fs:9-23 | Sharpino.Sample.15/Commons.fs:6-20 — 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 · Duplicated block (13–15 lines × 3) · ×1
  • Duplicated block (13–15 lines × 3) Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:60 — Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:60-72 | Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:91-105 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:90-104 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.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 6 separate duplicated blocks between them, totalling at least 95 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:91` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) Sharpino.Lib/AzureServiceBusBackplane.fs:51 — Sharpino.Lib/AzureServiceBusBackplane.fs:51-65 | Sharpino.Lib/PgNotifyBackplane.fs:40-53 — before extracting anything, compare `Sharpino.Lib/AzureServiceBusBackplane.fs` and `Sharpino.Lib/PgNotifyBackplane.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13–14 lines × 5) · ×1
  • Duplicated block (13–14 lines × 5) Sharpino.Sample.22/TodoManager.fs:65 — Sharpino.Sample.22/TodoManager.fs:65-78 | Sharpino.Sample.24/TodoManager.fs:116-128 | Sharpino.Sample.26/TodoManager.fs:116-128 | Sharpino.Sample.27/TodoManager.fs:116-128 | Sharpino.Sample.28/TodoManager.fs:116-128 — `Sharpino.Sample.22/TodoManager.fs` and `Sharpino.Sample.24/TodoManager.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 4 separate duplicated blocks between them, totalling at least 98 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.22/TodoManager.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.
D4 · Code Duplication · Duplicated block (13–14 lines × 4) · ×1
  • Duplicated block (13–14 lines × 4) Sharpino.Lib/CommandHandler.fs:3595 — Sharpino.Lib/CommandHandler.fs:3595-3607 | Sharpino.Lib/CommandHandler.fs:3821-3833 | Sharpino.Lib/CommandHandler.fs:4908-4921 | Sharpino.Lib/CommandHandler.fs:5201-5214 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (12–14 lines × 3) · ×1
  • Duplicated block (12–14 lines × 3) Sharpino.Lib/CommandHandler.fs:1977 — Sharpino.Lib/CommandHandler.fs:1977-1988 | Sharpino.Lib/CommandHandler.fs:3200-3213 | Sharpino.Lib/CommandHandler.fs:3273-3285 — 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 `Sharpino.Lib/CommandHandler.fs:1977` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1
  • Duplicated block (13–14 lines × 3) Sharpino.Lib/CommandHandler.fs:4809 — Sharpino.Lib/CommandHandler.fs:4809-4822 | Sharpino.Lib/CommandHandler.fs:5108-5120 | Sharpino.Lib/CommandHandler.fs:5401-5413 — 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) Sharpino.Lib/MemoryStorage.fs:405 — Sharpino.Lib/MemoryStorage.fs:405-418 | Sharpino.Lib/PgEventStore.fs:888-899 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/MemoryStorage.fs:405` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:660 — Sharpino.Lib/PgBinaryEventStore.fs:660-672 | Sharpino.Lib/PgBinaryEventStore.fs:743-756 — 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 `Sharpino.Lib/PgBinaryEventStore.fs:743` 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.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:7 — Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:7-20 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Cart.fs:8-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
D4 · Code Duplication · Duplicated block (13 lines × 6) · ×1
  • Duplicated block (13 lines × 6) Sharpino.Sample.17/MaterialManager.fs:23 — Sharpino.Sample.17/MaterialManager.fs:23-35 | Sharpino.Sample.22/Program.fs:15-27 | Sharpino.Sample.24/Program.fs:21-33 | Sharpino.Sample.26/Program.fs:21-33 | Sharpino.Sample.27/Program.fs:21-33 | Sharpino.Sample.28/Program.fs:21-33 — `Sharpino.Sample.22/Program.fs` and `Sharpino.Sample.24/Program.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 6 separate duplicated blocks between them, totalling at least 275 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 · Duplicated block (11–13 lines × 4) · ×1
  • Duplicated block (11–13 lines × 4) Sharpino.Lib/CommandHandler.fs:1103 — Sharpino.Lib/CommandHandler.fs:1103-1115 | Sharpino.Lib/CommandHandler.fs:3514-3524 | Sharpino.Lib/CommandHandler.fs:3744-3754 | Sharpino.Lib/CommandHandler.fs:3970-3980 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (11–13 lines × 3) · ×1
  • Duplicated block (11–13 lines × 3) Sharpino.Lib/MemoryStorage.fs:477 — Sharpino.Lib/MemoryStorage.fs:477-489 | Sharpino.Lib/MemoryStorage.fs:502-514 | Sharpino.Lib/MemoryStorage.fs:662-672 — 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.
D4 · Code Duplication · Duplicated block (5–13 lines × 2) · ×1
  • Duplicated block (5–13 lines × 2) Sharpino.Lib/Cache.fs:129 — Sharpino.Lib/Cache.fs:129-141 | Sharpino.Lib/Cache.fs:463-467 — 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) Sharpino.Lib/CommandHandler.fs:2674 — Sharpino.Lib/CommandHandler.fs:2674-2686 | Sharpino.Lib/CommandHandler.fs:2780-2790 — 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 `Sharpino.Lib/CommandHandler.fs:2674` 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.
D4 · Code Duplication · Duplicated block (12 lines × 9) · ×1
  • Duplicated block (12 lines × 9) Sharpino.Sample.10/Models/Account/Consumer.fs:3 — Sharpino.Sample.10/Models/Account/Consumer.fs:3-14 | Sharpino.Sample.10/Models/Counter/Consumer.fs:3-14 | Sharpino.Sample.9/models/Balance/Consumer.fs:3-14 | Sharpino.Sample.9/models/Course/Consumer.fs:3-15 | Sharpino.Sample.9/models/Item/Consumer.fs:3-15 | Sharpino.Sample.9/models/Reservation/Consumer.fs:3-15 | Sharpino.Sample.9/models/Student/Consumer.fs:3-15 | Sharpino.Sample.9/models/Teacher/Consumer.fs:3-15 | Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:4-15 — `Sharpino.Sample.10/Models/Account/Consumer.fs` and `Sharpino.Sample.10/Models/Counter/Consumer.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 3 separate duplicated blocks between them, totalling at least 40 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 · Duplicated block (12 lines × 6) · ×1
  • Duplicated block (12 lines × 6) Sharpino.Lib/CommandHandler.fs:1252 — Sharpino.Lib/CommandHandler.fs:1252-1263 | Sharpino.Lib/CommandHandler.fs:1336-1347 | Sharpino.Lib/CommandHandler.fs:1951-1962 | Sharpino.Lib/CommandHandler.fs:2025-2036 | Sharpino.Lib/CommandHandler.fs:2058-2069 | Sharpino.Lib/CommandHandler.fs:2150-2161 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (11–12 lines × 5) · ×1
  • Duplicated block (11–12 lines × 5) Sharpino.Lib/StateView.fs:1006 — Sharpino.Lib/StateView.fs:1006-1016 | Sharpino.Lib/StateView.fs:1046-1057 | Sharpino.Lib/StateView.fs:1088-1098 | Sharpino.Lib/StateView.fs:1157-1167 | Sharpino.Lib/StateView.fs:1216-1227 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×1
  • Duplicated block (12 lines × 5) Sharpino.Sample.22/TodoManager.fs:148 — Sharpino.Sample.22/TodoManager.fs:148-159 | Sharpino.Sample.24/TodoManager.fs:286-297 | Sharpino.Sample.26/TodoManager.fs:286-297 | Sharpino.Sample.27/TodoManager.fs:286-297 | Sharpino.Sample.28/TodoManager.fs:286-297 — `Sharpino.Sample.22/TodoManager.fs` and `Sharpino.Sample.24/TodoManager.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 4 separate duplicated blocks between them, totalling at least 98 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.22/TodoManager.fs:148` 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) Sharpino.Sample.11/Models/Course/Consumer.fs:74 — Sharpino.Sample.11/Models/Course/Consumer.fs:74-85 | Sharpino.Sample.14/Models/Course/Consumer.fs:74-85 | Sharpino.Sample.9/models/Course/Consumer.fs:59-70 — before extracting anything, compare `Sharpino.Sample.11/Models/Course/Consumer.fs` and `Sharpino.Sample.14/Models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 129 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) Sharpino.Lib/CommandHandler.fs:3560 — Sharpino.Lib/CommandHandler.fs:3560-3569 | Sharpino.Lib/CommandHandler.fs:4217-4228 — 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 `Sharpino.Lib/CommandHandler.fs:3560` 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.
D4 · Code Duplication · Duplicated block (1–12 lines × 5) · ×1
  • Duplicated block (1–12 lines × 5) Sharpino.Lib/CommandHandler.fs:1120 — Sharpino.Lib/CommandHandler.fs:1120-1120 | Sharpino.Lib/CommandHandler.fs:4198-4198 | Sharpino.Lib/CommandHandler.fs:4350-4361 | Sharpino.Lib/CommandHandler.fs:4499-4510 | Sharpino.Lib/CommandHandler.fs:5696-5696 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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.
D4 · Code Duplication · Duplicated block (4–12 lines × 3) · ×1
  • Duplicated block (4–12 lines × 3) Sharpino.Lib/Sanitizer.fs:32 — Sharpino.Lib/Sanitizer.fs:32-35 | Sharpino.Lib/Sanitizer.fs:120-131 | Sharpino.Lib/Sanitizer.fs:202-213 — 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 `Sharpino.Lib/Sanitizer.fs:120` 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.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • Duplicated block (8–12 lines × 2) Sharpino.Lib/StateView.fs:929 — Sharpino.Lib/StateView.fs:929-940 | Sharpino.Lib/StateView.fs:953-960 — 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 `Sharpino.Lib/StateView.fs:929` 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.
D4 · Code Duplication · Duplicated block (11 lines × 10) · ×1
  • Duplicated block (11 lines × 10) Sharpino.Sample.6/Suppliers/Consumer.fs:22 — Sharpino.Sample.6/Suppliers/Consumer.fs:22-33 | Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:20-32 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:22-32 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:21-33 | Sharpino.Sample.9/models/Balance/Consumer.fs:20-30 | Sharpino.Sample.9/models/Course/Consumer.fs:21-31 | Sharpino.Sample.9/models/Item/Consumer.fs:21-33 | Sharpino.Sample.9/models/Reservation/Consumer.fs:21-31 | Sharpino.Sample.9/models/Student/Consumer.fs:21-31 | Sharpino.Sample.9/models/Teacher/Consumer.fs:21-31 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs` 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 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.
D4 · Code Duplication · Duplicated block (11 lines × 9) · ×1
  • Duplicated block (11 lines × 9) Sharpino.Sample.22/Program.fs:71 — Sharpino.Sample.22/Program.fs:71-81 | Sharpino.Sample.24/Program.fs:81-91 | Sharpino.Sample.24/Program.fs:97-107 | Sharpino.Sample.26/Program.fs:81-91 | Sharpino.Sample.26/Program.fs:97-107 | Sharpino.Sample.27/Program.fs:79-89 | Sharpino.Sample.27/Program.fs:95-105 | Sharpino.Sample.28/Program.fs:79-89 | Sharpino.Sample.28/Program.fs:95-105 — `Sharpino.Sample.22/Program.fs` and `Sharpino.Sample.24/Program.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 6 separate duplicated blocks between them, totalling at least 275 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 · Duplicated block (10–11 lines × 7) · ×1
  • Duplicated block (10–11 lines × 7) Sharpino.Sample.8/Domain/Truck/Consumer.fs:43 — Sharpino.Sample.8/Domain/Truck/Consumer.fs:43-52 | Sharpino.Sample.9/models/Balance/Consumer.fs:44-54 | Sharpino.Sample.9/models/Course/Consumer.fs:47-57 | Sharpino.Sample.9/models/Item/Consumer.fs:50-60 | Sharpino.Sample.9/models/Reservation/Consumer.fs:51-61 | Sharpino.Sample.9/models/Student/Consumer.fs:47-57 | Sharpino.Sample.9/models/Teacher/Consumer.fs:47-57 — before extracting anything, compare `Sharpino.Sample.8/Domain/Truck/Consumer.fs` and `Sharpino.Sample.9/models/Course/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (8–11 lines × 4) · ×1
  • Duplicated block (8–11 lines × 4) Sharpino.Lib/CommandHandler.fs:3787 — Sharpino.Lib/CommandHandler.fs:3787-3795 | Sharpino.Lib/CommandHandler.fs:4013-4020 | Sharpino.Lib/CommandHandler.fs:4368-4377 | Sharpino.Lib/CommandHandler.fs:4517-4527 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:3787` 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 4) · ×1
  • Duplicated block (9–11 lines × 4) Sharpino.Lib/CommandHandler.fs:4205 — Sharpino.Lib/CommandHandler.fs:4205-4214 | Sharpino.Lib/CommandHandler.fs:4354-4364 | Sharpino.Lib/CommandHandler.fs:4503-4513 | Sharpino.Lib/CommandHandler.fs:5702-5710 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×1
  • Duplicated block (10–11 lines × 3) Sharpino.Lib/PgBinaryEventStore.fs:1541 — Sharpino.Lib/PgBinaryEventStore.fs:1541-1551 | Sharpino.Lib/PgEventStore.fs:1415-1425 | Sharpino.Lib/PgEventStore.fs:1519-1528 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10 lines × 9) · ×1
  • Duplicated block (10 lines × 9) Sharpino.Sample.3/Rows/Consumer.fs:73 — Sharpino.Sample.3/Rows/Consumer.fs:73-82 | Sharpino.Sample.8/Domain/Site/Consumer.fs:50-59 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:42-51 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:61-70 | Sharpino.Sample.9/models/Balance/Consumer.fs:43-52 | Sharpino.Sample.9/models/Course/Consumer.fs:66-75 | Sharpino.Sample.9/models/Item/Consumer.fs:49-58 | Sharpino.Sample.9/models/Item/Consumer.fs:74-83 | Sharpino.Sample.9/models/Reservation/Consumer.fs:50-59 — `Sharpino.Sample.8/Domain/Site/Consumer.fs` and `Sharpino.Sample.8/Domain/Truck/Consumer.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 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.9/models/Course/Consumer.fs:77` calls `ResetAllStates`, `Clear` and `Sharpino.Sample.8/Domain/Site/Consumer.fs:61` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×1
  • Duplicated block (10 lines × 5) Sharpino.Lib/CommandHandler.fs:2191 — Sharpino.Lib/CommandHandler.fs:2191-2200 | Sharpino.Lib/CommandHandler.fs:2230-2239 | Sharpino.Lib/CommandHandler.fs:2319-2328 | Sharpino.Lib/CommandHandler.fs:2364-2373 | Sharpino.Lib/CommandHandler.fs:2546-2555 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2191` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) Sharpino.Lib/CommandHandler.fs:4166 — Sharpino.Lib/CommandHandler.fs:4166-4175 | Sharpino.Lib/CommandHandler.fs:4314-4323 | Sharpino.Lib/CommandHandler.fs:4463-4472 | Sharpino.Lib/CommandHandler.fs:5660-5668 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:5671` calls `fun` and `Sharpino.Lib/CommandHandler.fs:4177` 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 4) · ×1
  • Duplicated block (8–10 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:448 — Sharpino.Lib/PgBinaryEventStore.fs:448-457 | Sharpino.Lib/PgBinaryEventStore.fs:513-520 | Sharpino.Lib/PgBinaryEventStore.fs:552-559 | Sharpino.Lib/PgBinaryEventStore.fs:2866-2873 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:445` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2863` 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.
D4 · Code Duplication · Duplicated block (6–10 lines × 2) · ×1
  • Duplicated block (6–10 lines × 2) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:184 — Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:184-193 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:209-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. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:184` 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 16) · ×1
  • Duplicated block (7–9 lines × 16) Sharpino.Lib/PgBinaryEventStore.fs:122 — Sharpino.Lib/PgBinaryEventStore.fs:122-130 | Sharpino.Lib/PgBinaryEventStore.fs:438-444 | Sharpino.Lib/PgBinaryEventStore.fs:501-507 | Sharpino.Lib/PgBinaryEventStore.fs:1033-1039 | Sharpino.Lib/PgBinaryEventStore.fs:2095-2102 | Sharpino.Lib/PgBinaryEventStore.fs:2170-2176 | Sharpino.Lib/PgBinaryEventStore.fs:2561-2567 | Sharpino.Lib/PgBinaryEventStore.fs:2857-2863 | Sharpino.Lib/PgEventStore.fs:137-145 | Sharpino.Lib/PgEventStore.fs:457-463 | Sharpino.Lib/PgEventStore.fs:1004-1010 | Sharpino.Lib/PgEventStore.fs:2032-2038 | Sharpino.Lib/PgEventStore.fs:2151-2157 | Sharpino.Lib/PgEventStore.fs:2226-2232 | Sharpino.Lib/PgEventStore.fs:2419-2425 | Sharpino.Lib/PgEventStore.fs:2683-2689 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:510` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:447` 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.
D4 · Code Duplication · Duplicated block (9 lines × 11) · ×1
  • Duplicated block (9 lines × 11) Sharpino.Lib/CommandHandler.fs:1191 — Sharpino.Lib/CommandHandler.fs:1191-1199 | Sharpino.Lib/CommandHandler.fs:1247-1255 | Sharpino.Lib/CommandHandler.fs:1331-1339 | Sharpino.Lib/CommandHandler.fs:1437-1445 | Sharpino.Lib/CommandHandler.fs:1525-1533 | Sharpino.Lib/CommandHandler.fs:1611-1619 | Sharpino.Lib/CommandHandler.fs:1923-1931 | Sharpino.Lib/CommandHandler.fs:1946-1954 | Sharpino.Lib/CommandHandler.fs:2020-2028 | Sharpino.Lib/CommandHandler.fs:2053-2061 | Sharpino.Lib/CommandHandler.fs:2145-2153 — all 11 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.
D4 · Code Duplication · Duplicated block (9 lines × 10) · ×1
  • Duplicated block (9 lines × 10) Sharpino.Sample.11/Test2.fs:76 — Sharpino.Sample.11/Test2.fs:76-84 | Sharpino.Sample.11/Test2.fs:147-155 | Sharpino.Sample.11/Test2.fs:182-190 | Sharpino.Sample.11/Test2.fs:219-227 | Sharpino.Sample.11/Test2.fs:257-265 | Sharpino.Sample.11/Test2.fs:296-304 | Sharpino.Sample.11/Test2.fs:367-375 | Sharpino.Sample.11/Test2.fs:401-409 | Sharpino.Sample.11/Test2.fs:437-445 | Sharpino.Sample.11/Test2.fs:472-480 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Sample.11/Test2.fs:86` calls `Clear` and `Sharpino.Sample.11/Test2.fs:306` 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.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) Sharpino.Lib/CommandHandler.fs:3359 — Sharpino.Lib/CommandHandler.fs:3359-3367 | Sharpino.Lib/CommandHandler.fs:3581-3589 | Sharpino.Lib/CommandHandler.fs:3807-3815 | Sharpino.Lib/CommandHandler.fs:4032-4040 | Sharpino.Lib/CommandHandler.fs:4098-4106 | Sharpino.Lib/CommandHandler.fs:4240-4248 | Sharpino.Lib/CommandHandler.fs:4389-4397 | Sharpino.Lib/CommandHandler.fs:4539-4547 — all 8 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.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×1
  • Duplicated block (9 lines × 7) Sharpino.Lib/CommandHandler.fs:4612 — Sharpino.Lib/CommandHandler.fs:4612-4620 | Sharpino.Lib/CommandHandler.fs:4890-4898 | Sharpino.Lib/CommandHandler.fs:5183-5191 | Sharpino.Lib/CommandHandler.fs:5476-5484 | Sharpino.Lib/CommandHandler.fs:5526-5534 | Sharpino.Lib/CommandHandler.fs:5564-5572 | Sharpino.Lib/CommandHandler.fs:5751-5759 — all 7 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.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) Sharpino.Lib/CommandHandler.fs:1700 — Sharpino.Lib/CommandHandler.fs:1700-1708 | Sharpino.Lib/CommandHandler.fs:1797-1805 | Sharpino.Lib/CommandHandler.fs:1893-1901 | Sharpino.Lib/CommandHandler.fs:5789-5797 | Sharpino.Lib/CommandHandler.fs:5865-5873 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) Sharpino.Lib/CommandHandler.fs:886 — Sharpino.Lib/CommandHandler.fs:886-894 | Sharpino.Lib/CommandHandler.fs:1087-1094 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 26) · ×1
  • Duplicated block (8 lines × 26) Sharpino.Lib/CommandHandler.fs:1684 — Sharpino.Lib/CommandHandler.fs:1684-1691 | Sharpino.Lib/CommandHandler.fs:1781-1788 | Sharpino.Lib/CommandHandler.fs:1877-1884 | Sharpino.Lib/CommandHandler.fs:2897-2904 | Sharpino.Lib/CommandHandler.fs:3178-3185 | Sharpino.Lib/CommandHandler.fs:3251-3258 | Sharpino.Lib/CommandHandler.fs:3322-3329 | Sharpino.Lib/CommandHandler.fs:3350-3357 | Sharpino.Lib/CommandHandler.fs:3572-3579 | Sharpino.Lib/CommandHandler.fs:3798-3805 | Sharpino.Lib/CommandHandler.fs:4023-4030 | Sharpino.Lib/CommandHandler.fs:4061-4068 | Sharpino.Lib/CommandHandler.fs:4089-4096 | Sharpino.Lib/CommandHandler.fs:4231-4238 | Sharpino.Lib/CommandHandler.fs:4380-4387 | Sharpino.Lib/CommandHandler.fs:4530-4537 | Sharpino.Lib/CommandHandler.fs:4568-4575 | Sharpino.Lib/CommandHandler.fs:4596-4603 | Sharpino.Lib/CommandHandler.fs:4874-4881 | Sharpino.Lib/CommandHandler.fs:5167-5174 | Sharpino.Lib/CommandHandler.fs:5460-5467 | Sharpino.Lib/CommandHandler.fs:5510-5517 | Sharpino.Lib/CommandHandler.fs:5548-5555 | Sharpino.Lib/CommandHandler.fs:5735-5742 | Sharpino.Lib/CommandHandler.fs:5773-5780 | Sharpino.Lib/CommandHandler.fs:5849-5856 — all 26 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.
D4 · Code Duplication · Duplicated block (8 lines × 20) · ×1
  • Duplicated block (8 lines × 20) Sharpino.Lib/PgBinaryEventStore.fs:120 — Sharpino.Lib/PgBinaryEventStore.fs:120-129 | Sharpino.Lib/PgBinaryEventStore.fs:436-443 | Sharpino.Lib/PgBinaryEventStore.fs:499-506 | Sharpino.Lib/PgBinaryEventStore.fs:1031-1038 | Sharpino.Lib/PgBinaryEventStore.fs:2168-2175 | Sharpino.Lib/PgBinaryEventStore.fs:2316-2323 | Sharpino.Lib/PgBinaryEventStore.fs:2358-2365 | Sharpino.Lib/PgBinaryEventStore.fs:2398-2405 | Sharpino.Lib/PgBinaryEventStore.fs:2559-2566 | Sharpino.Lib/PgBinaryEventStore.fs:2855-2862 | Sharpino.Lib/PgEventStore.fs:135-144 | Sharpino.Lib/PgEventStore.fs:455-462 | Sharpino.Lib/PgEventStore.fs:1002-1009 | Sharpino.Lib/PgEventStore.fs:2030-2037 | Sharpino.Lib/PgEventStore.fs:2149-2156 | Sharpino.Lib/PgEventStore.fs:2417-2424 | Sharpino.Lib/PgEventStore.fs:2681-2688 | Sharpino.Lib/PgEventStore.fs:2806-2813 | Sharpino.Lib/PgEventStore.fs:2893-2900 | Sharpino.Lib/PgEventStore.fs:2942-2949 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:445` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2324` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 13) · ×1
  • Duplicated block (7–8 lines × 13) Sharpino.Lib/CommandHandler.fs:3361 — Sharpino.Lib/CommandHandler.fs:3361-3368 | Sharpino.Lib/CommandHandler.fs:3583-3590 | Sharpino.Lib/CommandHandler.fs:3809-3816 | Sharpino.Lib/CommandHandler.fs:4034-4041 | Sharpino.Lib/CommandHandler.fs:4100-4107 | Sharpino.Lib/CommandHandler.fs:4242-4249 | Sharpino.Lib/CommandHandler.fs:4391-4398 | Sharpino.Lib/CommandHandler.fs:4541-4548 | Sharpino.Lib/CommandHandler.fs:4617-4623 | Sharpino.Lib/CommandHandler.fs:4895-4901 | Sharpino.Lib/CommandHandler.fs:5188-5194 | Sharpino.Lib/CommandHandler.fs:5481-5487 | Sharpino.Lib/CommandHandler.fs:5569-5575 — all 13 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.
D4 · Code Duplication · Duplicated block (8 lines × 12) · ×1
  • Duplicated block (8 lines × 12) Sharpino.Lib/CommandHandler.fs:1692 — Sharpino.Lib/CommandHandler.fs:1692-1699 | Sharpino.Lib/CommandHandler.fs:1789-1796 | Sharpino.Lib/CommandHandler.fs:1885-1892 | Sharpino.Lib/CommandHandler.fs:4604-4611 | Sharpino.Lib/CommandHandler.fs:4882-4889 | Sharpino.Lib/CommandHandler.fs:5175-5182 | Sharpino.Lib/CommandHandler.fs:5468-5475 | Sharpino.Lib/CommandHandler.fs:5518-5525 | Sharpino.Lib/CommandHandler.fs:5556-5563 | Sharpino.Lib/CommandHandler.fs:5743-5750 | Sharpino.Lib/CommandHandler.fs:5781-5788 | Sharpino.Lib/CommandHandler.fs:5857-5864 — all 12 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.
D4 · Code Duplication · Duplicated block (8 lines × 10) · ×1
  • Duplicated block (8 lines × 10) Sharpino.Lib/CommandHandler.fs:3358 — Sharpino.Lib/CommandHandler.fs:3358-3365 | Sharpino.Lib/CommandHandler.fs:3580-3587 | Sharpino.Lib/CommandHandler.fs:3806-3813 | Sharpino.Lib/CommandHandler.fs:4031-4038 | Sharpino.Lib/CommandHandler.fs:4069-4076 | Sharpino.Lib/CommandHandler.fs:4097-4104 | Sharpino.Lib/CommandHandler.fs:4239-4246 | Sharpino.Lib/CommandHandler.fs:4388-4395 | Sharpino.Lib/CommandHandler.fs:4538-4545 | Sharpino.Lib/CommandHandler.fs:4576-4583 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 8) · ×1
  • Duplicated block (8 lines × 8) Sharpino.Lib/CommandHandler.fs:2195 — Sharpino.Lib/CommandHandler.fs:2195-2202 | Sharpino.Lib/CommandHandler.fs:2234-2241 | Sharpino.Lib/CommandHandler.fs:2323-2330 | Sharpino.Lib/CommandHandler.fs:2368-2375 | Sharpino.Lib/CommandHandler.fs:2408-2415 | Sharpino.Lib/CommandHandler.fs:2456-2463 | Sharpino.Lib/CommandHandler.fs:2503-2510 | Sharpino.Lib/CommandHandler.fs:2550-2557 — all 8 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.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×1
  • Duplicated block (8 lines × 7) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:178 — Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:178-185 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:203-210 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:256-263 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:293-300 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:325-332 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:372-379 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:405-412 — all 7 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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) Sharpino.Lib/StateView.fs:55 — Sharpino.Lib/StateView.fs:55-62 | Sharpino.Lib/StateView.fs:139-146 | Sharpino.Lib/StateView.fs:182-189 | Sharpino.Lib/StateView.fs:220-227 | Sharpino.Lib/StateView.fs:254-261 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:55` 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.
D4 · Code Duplication · Duplicated block (7 lines × 20) · ×1
  • Duplicated block (7 lines × 20) Sharpino.Lib/PgBinaryEventStore.fs:353 — Sharpino.Lib/PgBinaryEventStore.fs:353-359 | Sharpino.Lib/PgBinaryEventStore.fs:682-689 | Sharpino.Lib/PgBinaryEventStore.fs:770-777 | Sharpino.Lib/PgBinaryEventStore.fs:857-867 | Sharpino.Lib/PgBinaryEventStore.fs:959-969 | Sharpino.Lib/PgBinaryEventStore.fs:1763-1776 | Sharpino.Lib/PgBinaryEventStore.fs:1877-1887 | Sharpino.Lib/PgBinaryEventStore.fs:2754-2764 | Sharpino.Lib/PgBinaryEventStore.fs:3046-3053 | Sharpino.Lib/PgBinaryEventStore.fs:3378-3384 | Sharpino.Lib/PgEventStore.fs:366-372 | Sharpino.Lib/PgEventStore.fs:635-645 | Sharpino.Lib/PgEventStore.fs:743-753 | Sharpino.Lib/PgEventStore.fs:848-855 | Sharpino.Lib/PgEventStore.fs:937-944 | Sharpino.Lib/PgEventStore.fs:1750-1763 | Sharpino.Lib/PgEventStore.fs:1871-1881 | Sharpino.Lib/PgEventStore.fs:2586-2595 | Sharpino.Lib/PgEventStore.fs:3075-3082 | Sharpino.Lib/PgEventStore.fs:3411-3417 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2765` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:360` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 18) · ×1
  • Duplicated block (7 lines × 18) Sharpino.Lib/PgBinaryEventStore.fs:121 — Sharpino.Lib/PgBinaryEventStore.fs:121-129 | Sharpino.Lib/PgBinaryEventStore.fs:437-443 | Sharpino.Lib/PgBinaryEventStore.fs:500-506 | Sharpino.Lib/PgBinaryEventStore.fs:1032-1038 | Sharpino.Lib/PgBinaryEventStore.fs:2094-2101 | Sharpino.Lib/PgBinaryEventStore.fs:2169-2175 | Sharpino.Lib/PgBinaryEventStore.fs:2399-2405 | Sharpino.Lib/PgBinaryEventStore.fs:2560-2566 | Sharpino.Lib/PgBinaryEventStore.fs:2856-2862 | Sharpino.Lib/PgEventStore.fs:136-144 | Sharpino.Lib/PgEventStore.fs:456-462 | Sharpino.Lib/PgEventStore.fs:1003-1009 | Sharpino.Lib/PgEventStore.fs:2031-2037 | Sharpino.Lib/PgEventStore.fs:2150-2156 | Sharpino.Lib/PgEventStore.fs:2225-2231 | Sharpino.Lib/PgEventStore.fs:2418-2424 | Sharpino.Lib/PgEventStore.fs:2682-2688 | Sharpino.Lib/PgEventStore.fs:2807-2813 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:446` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2865` 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) Sharpino.Lib/CommandHandler.fs:2569 — Sharpino.Lib/CommandHandler.fs:2569-2575 | Sharpino.Lib/CommandHandler.fs:2688-2694 | Sharpino.Lib/CommandHandler.fs:2706-2712 | Sharpino.Lib/CommandHandler.fs:2792-2798 | Sharpino.Lib/CommandHandler.fs:2879-2885 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (5–7 lines × 5) · ×1
  • Duplicated block (5–7 lines × 5) Sharpino.Lib/PgBinaryEventStore.fs:2325 — Sharpino.Lib/PgBinaryEventStore.fs:2325-2329 | Sharpino.Lib/PgBinaryEventStore.fs:2367-2371 | Sharpino.Lib/PgBinaryEventStore.fs:2409-2413 | Sharpino.Lib/PgEventStore.fs:2817-2821 | Sharpino.Lib/PgEventStore.fs:2902-2908 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/PgBinaryEventStore.fs:2406` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2323` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 4) · ×1
  • Duplicated block (6–7 lines × 4) Sharpino.Lib/CommandHandler.fs:4072 — Sharpino.Lib/CommandHandler.fs:4072-4078 | Sharpino.Lib/CommandHandler.fs:4579-4585 | Sharpino.Lib/CommandHandler.fs:5531-5536 | Sharpino.Lib/CommandHandler.fs:5756-5761 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) Sharpino.Lib/CommandHandler.fs:98 — Sharpino.Lib/CommandHandler.fs:98-104 | Sharpino.Sample.9/Commons.fs:56-61 — 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.
D4 · Code Duplication · Duplicated block (4–7 lines × 3) · ×1
  • Duplicated block (4–7 lines × 3) Sharpino.Lib/CommandHandler.fs:779 — Sharpino.Lib/CommandHandler.fs:779-782 | Sharpino.Lib/CommandHandler.fs:3218-3224 | Sharpino.Lib/CommandHandler.fs:3290-3296 — 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 `Sharpino.Lib/CommandHandler.fs:779` 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.
D4 · Code Duplication · Duplicated block (2–7 lines × 9) · ×1
  • Duplicated block (2–7 lines × 9) Sharpino.Lib/CommandHandler.fs:1495 — Sharpino.Lib/CommandHandler.fs:1495-1496 | Sharpino.Lib/CommandHandler.fs:1584-1585 | Sharpino.Lib/CommandHandler.fs:2650-2651 | Sharpino.Lib/CommandHandler.fs:2754-2755 | Sharpino.Lib/CommandHandler.fs:2846-2847 | Sharpino.Lib/CommandHandler.fs:4189-4192 | Sharpino.Lib/CommandHandler.fs:4338-4344 | Sharpino.Lib/CommandHandler.fs:4487-4493 | Sharpino.Lib/CommandHandler.fs:5691-5692 — all 9 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.
D4 · Code Duplication · Duplicated block (3–7 lines × 4) · ×1
  • Duplicated block (3–7 lines × 4) Sharpino.Lib/StateView.fs:853 — Sharpino.Lib/StateView.fs:853-856 | Sharpino.Lib/StateView.fs:963-965 | Sharpino.Lib/StateView.fs:1023-1029 | Sharpino.Lib/StateView.fs:1192-1198 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:1023` 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.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×1
  • Duplicated block (6 lines × 7) Sharpino.Lib/CommandHandler.fs:4213 — Sharpino.Lib/CommandHandler.fs:4213-4218 | Sharpino.Lib/CommandHandler.fs:4363-4368 | Sharpino.Lib/CommandHandler.fs:4512-4517 | Sharpino.Lib/CommandHandler.fs:4853-4858 | Sharpino.Lib/CommandHandler.fs:5146-5151 | Sharpino.Lib/CommandHandler.fs:5439-5444 | Sharpino.Lib/CommandHandler.fs:5714-5719 — all 7 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.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) Sharpino.Lib/CommandHandler.fs:637 — Sharpino.Lib/CommandHandler.fs:637-642 | Sharpino.Lib/CommandHandler.fs:1196-1201 | Sharpino.Lib/CommandHandler.fs:1442-1447 | Sharpino.Lib/CommandHandler.fs:1530-1535 | Sharpino.Lib/CommandHandler.fs:1616-1621 | Sharpino.Lib/CommandHandler.fs:1928-1933 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) Sharpino.Lib/StateView.fs:794 — Sharpino.Lib/StateView.fs:794-799 | Sharpino.Lib/StateView.fs:822-827 | Sharpino.Lib/StateView.fs:858-863 | Sharpino.Lib/StateView.fs:914-919 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (5–6 lines × 4) · ×1
  • Duplicated block (5–6 lines × 4) Sharpino.Lib/StateView.fs:966 — Sharpino.Lib/StateView.fs:966-970 | Sharpino.Lib/StateView.fs:1072-1077 | Sharpino.Lib/StateView.fs:1141-1146 | Sharpino.Lib/StateView.fs:1199-1204 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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.
D4 · Code Duplication · Duplicated block (5 lines × 43) · ×1
  • Duplicated block (5 lines × 43) Sharpino.Lib/CommandHandler.fs:628 — Sharpino.Lib/CommandHandler.fs:628-632 | Sharpino.Lib/CommandHandler.fs:1190-1194 | Sharpino.Lib/CommandHandler.fs:1246-1250 | Sharpino.Lib/CommandHandler.fs:1330-1334 | Sharpino.Lib/CommandHandler.fs:1436-1440 | Sharpino.Lib/CommandHandler.fs:1524-1528 | Sharpino.Lib/CommandHandler.fs:1610-1614 | Sharpino.Lib/CommandHandler.fs:1679-1683 | Sharpino.Lib/CommandHandler.fs:1776-1780 | Sharpino.Lib/CommandHandler.fs:1872-1876 | Sharpino.Lib/CommandHandler.fs:1922-1926 | Sharpino.Lib/CommandHandler.fs:1945-1949 | Sharpino.Lib/CommandHandler.fs:2019-2023 | Sharpino.Lib/CommandHandler.fs:2052-2056 | Sharpino.Lib/CommandHandler.fs:2144-2148 | Sharpino.Lib/CommandHandler.fs:2564-2568 | Sharpino.Lib/CommandHandler.fs:2683-2687 | Sharpino.Lib/CommandHandler.fs:2701-2705 | Sharpino.Lib/CommandHandler.fs:2787-2791 | Sharpino.Lib/CommandHandler.fs:2874-2878 | Sharpino.Lib/CommandHandler.fs:2892-2896 | Sharpino.Lib/CommandHandler.fs:3173-3177 | Sharpino.Lib/CommandHandler.fs:3246-3250 | Sharpino.Lib/CommandHandler.fs:3317-3321 | Sharpino.Lib/CommandHandler.fs:3345-3349 | Sharpino.Lib/CommandHandler.fs:3567-3571 | Sharpino.Lib/CommandHandler.fs:3793-3797 | Sharpino.Lib/CommandHandler.fs:4018-4022 | Sharpino.Lib/CommandHandler.fs:4056-4060 | Sharpino.Lib/CommandHandler.fs:4084-4088 | Sharpino.Lib/CommandHandler.fs:4226-4230 | Sharpino.Lib/CommandHandler.fs:4375-4379 | Sharpino.Lib/CommandHandler.fs:4525-4529 | Sharpino.Lib/CommandHandler.fs:4563-4567 | Sharpino.Lib/CommandHandler.fs:4591-4595 | Sharpino.Lib/CommandHandler.fs:4869-4873 | Sharpino.Lib/CommandHandler.fs:5162-5166 | Sharpino.Lib/CommandHandler.fs:5455-5459 | Sharpino.Lib/CommandHandler.fs:5505-5509 | Sharpino.Lib/CommandHandler.fs:5543-5547 | Sharpino.Lib/CommandHandler.fs:5730-5734 | Sharpino.Lib/CommandHandler.fs:5768-5772 | Sharpino.Lib/CommandHandler.fs:5844-5848 — all 43 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 `Sharpino.Lib/CommandHandler.fs:628` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/CommandHandler.fs:1773` calls `command` and `Sharpino.Lib/CommandHandler.fs:5841` 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.
D4 · Code Duplication · Duplicated block (5 lines × 32) · ×1
  • Duplicated block (5 lines × 32) Sharpino.Lib/CommandHandler.fs:1254 — Sharpino.Lib/CommandHandler.fs:1254-1258 | Sharpino.Lib/CommandHandler.fs:1338-1342 | Sharpino.Lib/CommandHandler.fs:1687-1691 | Sharpino.Lib/CommandHandler.fs:1784-1788 | Sharpino.Lib/CommandHandler.fs:1880-1884 | Sharpino.Lib/CommandHandler.fs:1953-1957 | Sharpino.Lib/CommandHandler.fs:2027-2031 | Sharpino.Lib/CommandHandler.fs:2060-2064 | Sharpino.Lib/CommandHandler.fs:2152-2156 | Sharpino.Lib/CommandHandler.fs:2900-2904 | Sharpino.Lib/CommandHandler.fs:3181-3185 | Sharpino.Lib/CommandHandler.fs:3254-3258 | Sharpino.Lib/CommandHandler.fs:3325-3329 | Sharpino.Lib/CommandHandler.fs:3353-3357 | Sharpino.Lib/CommandHandler.fs:3575-3579 | Sharpino.Lib/CommandHandler.fs:3801-3805 | Sharpino.Lib/CommandHandler.fs:4026-4030 | Sharpino.Lib/CommandHandler.fs:4064-4068 | Sharpino.Lib/CommandHandler.fs:4092-4096 | Sharpino.Lib/CommandHandler.fs:4234-4238 | Sharpino.Lib/CommandHandler.fs:4383-4387 | Sharpino.Lib/CommandHandler.fs:4533-4537 | Sharpino.Lib/CommandHandler.fs:4571-4575 | Sharpino.Lib/CommandHandler.fs:4599-4603 | Sharpino.Lib/CommandHandler.fs:4877-4881 | Sharpino.Lib/CommandHandler.fs:5170-5174 | Sharpino.Lib/CommandHandler.fs:5463-5467 | Sharpino.Lib/CommandHandler.fs:5513-5517 | Sharpino.Lib/CommandHandler.fs:5551-5555 | Sharpino.Lib/CommandHandler.fs:5738-5742 | Sharpino.Lib/CommandHandler.fs:5776-5780 | Sharpino.Lib/CommandHandler.fs:5852-5856 — all 32 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.
D4 · Code Duplication · Duplicated block (5 lines × 15) · ×1
  • Duplicated block (5 lines × 15) Sharpino.Lib/CommandHandler.fs:1346 — Sharpino.Lib/CommandHandler.fs:1346-1350 | Sharpino.Lib/CommandHandler.fs:1695-1699 | Sharpino.Lib/CommandHandler.fs:1792-1796 | Sharpino.Lib/CommandHandler.fs:1888-1892 | Sharpino.Lib/CommandHandler.fs:2068-2072 | Sharpino.Lib/CommandHandler.fs:2160-2164 | Sharpino.Lib/CommandHandler.fs:4607-4611 | Sharpino.Lib/CommandHandler.fs:4885-4889 | Sharpino.Lib/CommandHandler.fs:5178-5182 | Sharpino.Lib/CommandHandler.fs:5471-5475 | Sharpino.Lib/CommandHandler.fs:5521-5525 | Sharpino.Lib/CommandHandler.fs:5559-5563 | Sharpino.Lib/CommandHandler.fs:5746-5750 | Sharpino.Lib/CommandHandler.fs:5784-5788 | Sharpino.Lib/CommandHandler.fs:5860-5864 — all 15 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.
D4 · Code Duplication · Duplicated block (5 lines × 7) · ×1
  • Duplicated block (5 lines × 7) Sharpino.Lib/CommandHandler.fs:159 — Sharpino.Lib/CommandHandler.fs:159-163 | Sharpino.Lib/CommandHandler.fs:218-222 | Sharpino.Lib/CommandHandler.fs:2195-2199 | Sharpino.Lib/CommandHandler.fs:2234-2238 | Sharpino.Lib/CommandHandler.fs:2323-2327 | Sharpino.Lib/CommandHandler.fs:2368-2372 | Sharpino.Lib/CommandHandler.fs:2550-2554 — all 7 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.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) Sharpino.Lib/CommandHandler.fs:187 — Sharpino.Lib/CommandHandler.fs:187-191 | Sharpino.Lib/Sanitizer.fs:37-41 | Sharpino.Lib/Sanitizer.fs:133-137 | Sharpino.Lib/Sanitizer.fs:154-158 | Sharpino.Lib/Sanitizer.fs:215-219 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (1–5 lines × 4) · ×1
  • Duplicated block (1–5 lines × 4) Sharpino.Lib/CommandHandler.fs:1428 — Sharpino.Lib/CommandHandler.fs:1428-1432 | Sharpino.Lib/CommandHandler.fs:1768-1773 | Sharpino.Lib/CommandHandler.fs:1865-1870 | Sharpino.Lib/CommandHandler.fs:2137-2137 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1428` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:2137` calls `events3` and `Sharpino.Lib/CommandHandler.fs:1773` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (1–5 lines × 6) · ×1
  • Duplicated block (1–5 lines × 6) Sharpino.Lib/CommandHandler.fs:1323 — Sharpino.Lib/CommandHandler.fs:1323-1327 | Sharpino.Lib/CommandHandler.fs:1427-1427 | Sharpino.Lib/CommandHandler.fs:1767-1767 | Sharpino.Lib/CommandHandler.fs:1864-1864 | Sharpino.Lib/CommandHandler.fs:2012-2016 | Sharpino.Lib/CommandHandler.fs:2136-2136 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1323` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sharpino.Lib/CommandHandler.fs:1422` calls `newState3` and `Sharpino.Lib/CommandHandler.fs:1318` 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.
D4 · Code Duplication · Duplicated block (2–5 lines × 4) · ×1
  • Duplicated block (2–5 lines × 4) Sharpino.Lib/CommandHandler.fs:1413 — Sharpino.Lib/CommandHandler.fs:1413-1414 | Sharpino.Lib/CommandHandler.fs:1753-1757 | Sharpino.Lib/CommandHandler.fs:1850-1854 | Sharpino.Lib/CommandHandler.fs:2120-2121 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/CommandHandler.fs:1416` calls `Memoize2` and `Sharpino.Lib/CommandHandler.fs:1760` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–5 lines × 3) · ×1
  • Duplicated block (3–5 lines × 3) Sharpino.Lib/MemoryStorage.fs:1019 — Sharpino.Lib/MemoryStorage.fs:1019-1023 | Sharpino.Lib/MemoryStorage.fs:1041-1045 | Sharpino.Lib/MemoryStorage.fs:1074-1076 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sharpino.Lib/MemoryStorage.fs:1045` calls `collect` and `Sharpino.Lib/MemoryStorage.fs:1076` 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.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) Sharpino.Sample.15/Models/Course/Events.fs:1 — Sharpino.Sample.15/Models/Course/Events.fs:1-30 | Sharpino.Sample.15/Models/Student/Events.fs:1-30 — 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1706 — Sharpino.Lib/PgBinaryEventStore.fs:1706-1739 | Sharpino.Lib/PgEventStore.fs:1691-1724 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 8) · ×1
  • Duplicated block (16 lines × 8) Sharpino.Lib/PgBinaryEventStore.fs:1797 — Sharpino.Lib/PgBinaryEventStore.fs:1797-1812 | Sharpino.Lib/PgBinaryEventStore.fs:1908-1923 | Sharpino.Lib/PgBinaryEventStore.fs:2776-2791 | Sharpino.Lib/PgBinaryEventStore.fs:2926-2941 | Sharpino.Lib/PgEventStore.fs:1786-1807 | Sharpino.Lib/PgEventStore.fs:1904-1925 | Sharpino.Lib/PgEventStore.fs:2608-2623 | Sharpino.Lib/PgEventStore.fs:2751-2766 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 110 separate duplicated blocks between them, totalling at least 2436 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1797` 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.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) Sharpino.Sample.11/Models/Student/Consumer.fs:60 — Sharpino.Sample.11/Models/Student/Consumer.fs:60-74 | Sharpino.Sample.11/Models/Student2/Consumer.fs:57-72 | Sharpino.Sample.14/Models/Student/Consumer.fs:60-74 | Sharpino.Sample.6/Dishes/Consumer.fs:44-58 — `Sharpino.Sample.11/Models/Student/Consumer.fs` and `Sharpino.Sample.11/Models/Student2/Consumer.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 5 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.11/Models/Student/Consumer.fs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) Sharpino.Sample.9/models/Reservation/Consumer.fs:80 — Sharpino.Sample.9/models/Reservation/Consumer.fs:80-92 | Sharpino.Sample.9/models/Student/Consumer.fs:81-93 | Sharpino.Sample.9/models/Teacher/Consumer.fs:80-92 — `Sharpino.Sample.9/models/Reservation/Consumer.fs` and `Sharpino.Sample.9/models/Student/Consumer.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 5 separate duplicated blocks between them, totalling at least 65 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.9/models/Reservation/Consumer.fs:80` 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.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
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 — 24 finding(s)
M4 · Documentation accuracy · README/code drift · ×12
  • README/code drift Sharpino.Lib.Core/README.md:70 — Sharpino.Lib.Core/README.md links to `Sharpino.Lib.Core/Core.fs`, but `Sharpino.Lib.Core/Sharpino.Lib.Core/Core.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib.Core/README.md:74 — Sharpino.Lib.Core/README.md links to `Sharpino.Lib/CommandHandler.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/CommandHandler.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib.Core/README.md:75 — Sharpino.Lib.Core/README.md links to `Sharpino.Lib/PgEventStore.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/PgEventStore.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib.Core/README.md:75 — Sharpino.Lib.Core/README.md links to `Sharpino.Lib/MemoryStorage.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/MemoryStorage.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib.Core/README.md:77 — Sharpino.Lib.Core/README.md links to `Sharpino.Lib/Cache.fs`, but `Sharpino.Lib.Core/Sharpino.Lib/Cache.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib.Core/README.md:105 — Sharpino.Lib.Core/README.md links to `CONTRIBUTING.md`, but `Sharpino.Lib.Core/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib/README.md:45 — Sharpino.Lib/README.md links to `Sharpino.Lib.Core/Core.fs`, but `Sharpino.Lib/Sharpino.Lib.Core/Core.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib/README.md:49 — Sharpino.Lib/README.md links to `Sharpino.Lib/CommandHandler.fs`, but `Sharpino.Lib/Sharpino.Lib/CommandHandler.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib/README.md:50 — Sharpino.Lib/README.md links to `Sharpino.Lib/PgEventStore.fs`, but `Sharpino.Lib/Sharpino.Lib/PgEventStore.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib/README.md:50 — Sharpino.Lib/README.md links to `Sharpino.Lib/MemoryStorage.fs`, but `Sharpino.Lib/Sharpino.Lib/MemoryStorage.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib/README.md:52 — Sharpino.Lib/README.md links to `Sharpino.Lib/Cache.fs`, but `Sharpino.Lib/Sharpino.Lib/Cache.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Sharpino.Lib/README.md:80 — Sharpino.Lib/README.md links to `CONTRIBUTING.md`, but `Sharpino.Lib/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate Sharpino.Lib/PgBinaryEventStore.fs:690 — `correlationId.IsSome || causationId.IsSome` appears character-identically in 2 files — Sharpino.Lib/PgBinaryEventStore.fs, Sharpino.Lib/PgEventStore.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Sharpino.Lib/PgBinaryEventStore.fs:1289 — `lastEventId.IsNone && eventId <> 0 || (lastEventId.IsSome && lastEventId.Value <> eventId)` appears character-identically in 2 files — Sharpino.Lib/PgBinaryEventStore.fs, Sharpino.Lib/PgEventStore.fs. 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.
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): js-tokens — js-tokens 4.0.0 → 10.0.0 available.
D27 · Navigability · Scattered collaborators · ×1
  • Scattered collaborators — 96 % of calls cross a namespace and only 7 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M3 · Folder & project structure · No src/ separation · ×1
  • No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 8/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `Sharpino.Sample.22`, `Sharpino.Sample.24`, `Sharpino.Sample.26`, `Sharpino.Sample.27` and 2 more.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — 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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation Sharpino.Lib.Core/Sharpino.Lib.Core.fsproj:28 — `Sharpino.Lib.Core/Sharpino.Lib.Core.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`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Minor — 6 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×3
  • Outdated (npm): react — react 18.2.0 → 19.3.1 available.
  • Outdated (npm): react-dom — react-dom 18.2.0 → 19.3.1 available.
  • Outdated (npm): scheduler — scheduler 0.23.0 → 0.28.0 available.
D12 · Dependency Hygiene · Outdated · ×3
  • Outdated: FSharp.Core — FSharp.Core 10.1.400 → 10.1.403 available (referenced by Sharpino.Lib).
  • Outdated: DotNetEnv — DotNetEnv 3.1.1 → 3.2.0 available (referenced by Sharpino.Lib.Test).
  • Outdated: Expecto — Expecto 11.1.0 → 11.1.1 available (referenced by Sharpino.Sample.26.Test).

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4d3c34fbbf1b489eaa3d9f1e9b656ccf/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4d3c34fbbf1b489eaa3d9f1e9b656ccf/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .1artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Sharpino.sln package --vulnerable --include-transitive --format json16artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .14artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a1c014-10f8-7bf4-8692-6e17ea309a9c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md