Public report of tonyx/Sharpino, published 22 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 22 October 2026, 17:58 UTC · Survey ID cd_42fa7e8f37594f5381f76c51e374cf45
tonyx/Sharpino
Measured 22 October 2026, 17:51 UTC, at code version fba667e
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
CAI scoreAt riskDown 4 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,070 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 critical530 serious33 minor
35 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 17:51 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 Watchdog. It is open to any tool that
implements it, and today Watchdog 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. Watchdog works 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 ▸
40of 43 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
571of 590 findings point to an exact file and line, so you can open each one in the code. The other 19 concern the repository as a whole, such as missing documentation.
43dimensions across 6 lenses, read from 26,070 lines of product code in 36 projects.
tonyx/Sharpino scores 45 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 32 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 8 Leaked secret finding(s) in REDACTED Scanning and to add a CI workflow that builds and runs the test suite on every push/PR, and if Production Readiness rose to 70, the score would rise from 45 to about 57.
27 findings are critical: ten in Dependency Vulnerabilities, eight in REDACTED Scanning, three in Secrets (history), three in Test isolation, two in IaC & Container Security and one in Static Analysis (SAST).
Watchdog couldn't measure 34 dimensions in this code, among them Explicit Debt, IL Efficiency and Data Protection, so they are left out of the score. The product code is 26,070 lines, which would take an estimated 0.3 person-years, around €39,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares 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: 8 findings
These 8 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: Microsoft.IdentityModel.JsonWebTokens 6.10.0
Dependency Vulnerabilities · Medium CVE: System.IdentityModel.Tokens.Jwt 6.10.0
IaC & Container Security · Medium IaC: REDACTED REDACTED
IaC & Container Security · Medium IaC: REDACTED REDACTED
IaC & Container Security · Medium IaC: REDACTED Sharpino.Sample.25/docker-compose.yml
IaC & Container Security · Medium IaC: REDACTED REDACTED
Rebuild cost: about €39,000 · Estimate
Cost to rebuild
€13,000 to €65,000, for 215 to 684 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 26,070 lines of product code
How the estimate is made: Watchdog prices 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.
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 €39,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.6 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 3% to 8% on every change. The history of the code shows how much it changes: about 7,692 lines over the last 90 days, which is about 31,195 lines a year. At that pace, the extra work comes to an estimated 2.7 to 16.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 Watchdog's 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; 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 — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
256 modules, with 153 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; 216 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.
AsyncTests uses Sharpino.Sample._11.CourseManager, so a change to Sharpino.Sample._11.CourseManager can break AsyncTests, while a change to AsyncTests can't break Sharpino.Sample._11.CourseManager.
Position
Below the diagonal: AsyncTests uses a module listed above it, which is the healthy direction.
BulkLoadTests uses Sharpino.Sample._11.CourseManager, so a change to Sharpino.Sample._11.CourseManager can break BulkLoadTests, while a change to BulkLoadTests can't break Sharpino.Sample._11.CourseManager.
Position
Below the diagonal: BulkLoadTests uses a module listed above it, which is the healthy direction.
BulkLoadTests uses Sharpino.Storage, so a change to Sharpino.Storage can break BulkLoadTests, while a change to BulkLoadTests can't break Sharpino.Storage.
Position
Below the diagonal: BulkLoadTests uses a module listed above it, which is the healthy direction.
Sharpino.CommandHandler uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.CommandHandler, while a change to Sharpino.CommandHandler can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.CommandHandler uses a module listed above it, which is the healthy direction.
Sharpino.CommandHandler uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Sharpino.CommandHandler, while a change to Sharpino.CommandHandler can't break Sharpino.EventBroker.
Position
Below the diagonal: Sharpino.CommandHandler uses a module listed above it, which is the healthy direction.
Sharpino.CommandHandler uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.CommandHandler, while a change to Sharpino.CommandHandler can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.CommandHandler uses a module listed above it, which is the healthy direction.
Sharpino.PgStorage uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.PgStorage, while a change to Sharpino.PgStorage can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.PgStorage uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Categories.CategoriesCommands uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Sample.Categories.CategoriesCommands, while a change to Sharpino.Sample.Categories.CategoriesCommands can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Sample.Categories.CategoriesCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Categories.CategoriesCommands uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.Categories.CategoriesCommands, while a change to Sharpino.Sample.Categories.CategoriesCommands can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.Categories.CategoriesCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Categories.CategoriesEvents uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Sample.Categories.CategoriesEvents, while a change to Sharpino.Sample.Categories.CategoriesEvents can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Sample.Categories.CategoriesEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Categories.CategoriesEvents uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.Categories.CategoriesEvents, while a change to Sharpino.Sample.Categories.CategoriesEvents can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.Categories.CategoriesEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Saga.Api.SeatBooking uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Sharpino.Sample.Saga.Api.SeatBooking, while a change to Sharpino.Sample.Saga.Api.SeatBooking can't break Sharpino.EventBroker.
Position
Below the diagonal: Sharpino.Sample.Saga.Api.SeatBooking uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Saga.Api.SeatBooking uses Sharpino.Sample.Saga.Domain.Booking.Booking, so a change to Sharpino.Sample.Saga.Domain.Booking.Booking can break Sharpino.Sample.Saga.Api.SeatBooking, while a change to Sharpino.Sample.Saga.Api.SeatBooking can't break Sharpino.Sample.Saga.Domain.Booking.Booking.
Position
Below the diagonal: Sharpino.Sample.Saga.Api.SeatBooking uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Saga.Api.SeatBooking uses Sharpino.Sample.Saga.Domain.Seat.Row, so a change to Sharpino.Sample.Saga.Domain.Seat.Row can break Sharpino.Sample.Saga.Api.SeatBooking, while a change to Sharpino.Sample.Saga.Api.SeatBooking can't break Sharpino.Sample.Saga.Domain.Seat.Row.
Position
Below the diagonal: Sharpino.Sample.Saga.Api.SeatBooking uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Saga.Api.SeatBooking uses Sharpino.Sample.Saga.Domain.Vaucher.Voucher, so a change to Sharpino.Sample.Saga.Domain.Vaucher.Voucher can break Sharpino.Sample.Saga.Api.SeatBooking, while a change to Sharpino.Sample.Saga.Api.SeatBooking can't break Sharpino.Sample.Saga.Domain.Vaucher.Voucher.
Position
Below the diagonal: Sharpino.Sample.Saga.Api.SeatBooking uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Saga.Api.SeatBooking uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Sample.Saga.Api.SeatBooking, while a change to Sharpino.Sample.Saga.Api.SeatBooking can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Sample.Saga.Api.SeatBooking uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Tags.TagCommands uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Sample.Tags.TagCommands, while a change to Sharpino.Sample.Tags.TagCommands can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Sample.Tags.TagCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Tags.TagCommands uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.Tags.TagCommands, while a change to Sharpino.Sample.Tags.TagCommands can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.Tags.TagCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Tags.TagsEvents uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Sample.Tags.TagsEvents, while a change to Sharpino.Sample.Tags.TagsEvents can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Sample.Tags.TagsEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Tags.TagsEvents uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.Tags.TagsEvents, while a change to Sharpino.Sample.Tags.TagsEvents can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.Tags.TagsEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample.TodosContext uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.TodosContext, while a change to Sharpino.Sample.TodosContext can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.TodosContext uses a module listed above it, which is the healthy direction.
Sharpino.Sample._10 uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Sharpino.Sample._10, while a change to Sharpino.Sample._10 can't break Sharpino.EventBroker.
Position
Below the diagonal: Sharpino.Sample._10 uses a module listed above it, which is the healthy direction.
Sharpino.Sample._10 uses Sharpino.Sample._10.Models.Counter, so a change to Sharpino.Sample._10.Models.Counter can break Sharpino.Sample._10, while a change to Sharpino.Sample._10 can't break Sharpino.Sample._10.Models.Counter.
Position
Below the diagonal: Sharpino.Sample._10 uses a module listed above it, which is the healthy direction.
Sharpino.Sample._10 uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Sample._10, while a change to Sharpino.Sample._10 can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Sample._10 uses a module listed above it, which is the healthy direction.
Sharpino.Sample._14.Details.Details uses Sharpino.Cache, so a change to Sharpino.Cache can break Sharpino.Sample._14.Details.Details, while a change to Sharpino.Sample._14.Details.Details can't break Sharpino.Cache.
Position
Below the diagonal: Sharpino.Sample._14.Details.Details uses a module listed above it, which is the healthy direction.
Sharpino.Sample._15.Details uses Sharpino.Cache, so a change to Sharpino.Cache can break Sharpino.Sample._15.Details, while a change to Sharpino.Sample._15.Details can't break Sharpino.Cache.
Position
Below the diagonal: Sharpino.Sample._15.Details uses a module listed above it, which is the healthy direction.
Sharpino.Template.Models uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Template.Models, while a change to Sharpino.Template.Models can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Template.Models uses a module listed above it, which is the healthy direction.
Sharpino.Template.Models uses Sharpino.Template.Commons, so a change to Sharpino.Template.Commons can break Sharpino.Template.Models, while a change to Sharpino.Template.Models can't break Sharpino.Template.Commons.
Position
Below the diagonal: Sharpino.Template.Models uses a module listed above it, which is the healthy direction.
Tonyx.SeatsBooking.StorageStadiumBookingSystem uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Tonyx.SeatsBooking.StorageStadiumBookingSystem, while a change to Tonyx.SeatsBooking.StorageStadiumBookingSystem can't break Sharpino.EventBroker.
Position
Below the diagonal: Tonyx.SeatsBooking.StorageStadiumBookingSystem uses a module listed above it, which is the healthy direction.
Tonyx.SeatsBooking.StorageStadiumBookingSystem uses Sharpino.Storage, so a change to Sharpino.Storage can break Tonyx.SeatsBooking.StorageStadiumBookingSystem, while a change to Tonyx.SeatsBooking.StorageStadiumBookingSystem can't break Sharpino.Storage.
Position
Below the diagonal: Tonyx.SeatsBooking.StorageStadiumBookingSystem uses a module listed above it, which is the healthy direction.
Tonyx.Sharpino.Pub uses Sharpino.Core, so a change to Sharpino.Core can break Tonyx.Sharpino.Pub, while a change to Tonyx.Sharpino.Pub can't break Sharpino.Core.
Position
Below the diagonal: Tonyx.Sharpino.Pub uses a module listed above it, which is the healthy direction.
seatsLockWithSharpino.Row uses seatsLockWithSharpino.Seats, so a change to seatsLockWithSharpino.Seats can break seatsLockWithSharpino.Row, while a change to seatsLockWithSharpino.Row can't break seatsLockWithSharpino.Seats.
Position
Below the diagonal: seatsLockWithSharpino.Row uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Todos.TodoCommands uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Sample.Todos.TodoCommands, while a change to Sharpino.Sample.Todos.TodoCommands can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Sample.Todos.TodoCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Todos.TodoCommands uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.Todos.TodoCommands, while a change to Sharpino.Sample.Todos.TodoCommands can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.Todos.TodoCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Todos.TodoCommands uses Sharpino.Sample.TodosContext, so a change to Sharpino.Sample.TodosContext can break Sharpino.Sample.Todos.TodoCommands, while a change to Sharpino.Sample.Todos.TodoCommands can't break Sharpino.Sample.TodosContext.
Position
Below the diagonal: Sharpino.Sample.Todos.TodoCommands uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Todos.TodoEvents uses Sharpino.Core, so a change to Sharpino.Core can break Sharpino.Sample.Todos.TodoEvents, while a change to Sharpino.Sample.Todos.TodoEvents can't break Sharpino.Core.
Position
Below the diagonal: Sharpino.Sample.Todos.TodoEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Todos.TodoEvents uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.Todos.TodoEvents, while a change to Sharpino.Sample.Todos.TodoEvents can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.Todos.TodoEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample.Todos.TodoEvents uses Sharpino.Sample.TodosContext, so a change to Sharpino.Sample.TodosContext can break Sharpino.Sample.Todos.TodoEvents, while a change to Sharpino.Sample.Todos.TodoEvents can't break Sharpino.Sample.TodosContext.
Position
Below the diagonal: Sharpino.Sample.Todos.TodoEvents uses a module listed above it, which is the healthy direction.
Sharpino.Sample._10.Tests.Tests uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Sample._10.Tests.Tests, while a change to Sharpino.Sample._10.Tests.Tests can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Sample._10.Tests.Tests uses a module listed above it, which is the healthy direction.
Sharpino.Sample._10.Tests.Tests uses Sharpino.Sample._10, so a change to Sharpino.Sample._10 can break Sharpino.Sample._10.Tests.Tests, while a change to Sharpino.Sample._10.Tests.Tests can't break Sharpino.Sample._10.
Position
Below the diagonal: Sharpino.Sample._10.Tests.Tests uses a module listed above it, which is the healthy direction.
Sharpino.Template.Models.Details uses Sharpino.Cache, so a change to Sharpino.Cache can break Sharpino.Template.Models.Details, while a change to Sharpino.Template.Models.Details can't break Sharpino.Cache.
Position
Below the diagonal: Sharpino.Template.Models.Details uses a module listed above it, which is the healthy direction.
Sharpino.Template.Models.Details uses Sharpino.Template.Models, so a change to Sharpino.Template.Models can break Sharpino.Template.Models.Details, while a change to Sharpino.Template.Models.Details can't break Sharpino.Template.Models.
Position
Below the diagonal: Sharpino.Template.Models.Details uses a module listed above it, which is the healthy direction.
Tests uses Sharpino.Sample._11.CourseManager, so a change to Sharpino.Sample._11.CourseManager can break Tests, while a change to Tests can't break Sharpino.Sample._11.CourseManager.
Position
Below the diagonal: Tests uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Tests uses a type in Sharpino.Template.Commons.
The types involved
Tests.TodoV2 → Sharpino.Template.Commons.TodoId
Direction
Tests uses Sharpino.Template.Commons, so a change to Sharpino.Template.Commons can break Tests, while a change to Tests can't break Sharpino.Template.Commons.
Position
Below the diagonal: Tests uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Tests uses a type in Sharpino.Template.Models.
The types involved
Tests.TodoV2 → Sharpino.Template.Models.State
Direction
Tests uses Sharpino.Template.Models, so a change to Sharpino.Template.Models can break Tests, while a change to Tests can't break Sharpino.Template.Models.
Position
Below the diagonal: Tests uses a module listed above it, which is the healthy direction.
sharpino.Template.Models uses Sharpino.Core, so a change to Sharpino.Core can break sharpino.Template.Models, while a change to sharpino.Template.Models can't break Sharpino.Core.
Position
Below the diagonal: sharpino.Template.Models uses a module listed above it, which is the healthy direction.
sharpino.Template.Models uses Sharpino.Template.Commons, so a change to Sharpino.Template.Commons can break sharpino.Template.Models, while a change to sharpino.Template.Models can't break Sharpino.Template.Commons.
Position
Below the diagonal: sharpino.Template.Models uses a module listed above it, which is the healthy direction.
sharpino.Template.Models uses Sharpino.Template.Models, so a change to Sharpino.Template.Models can break sharpino.Template.Models, while a change to sharpino.Template.Models can't break Sharpino.Template.Models.
Position
Below the diagonal: sharpino.Template.Models uses a module listed above it, which is the healthy direction.
Sharpino.Sample.App uses Sharpino.Sample.Shared.Entities, so a change to Sharpino.Sample.Shared.Entities can break Sharpino.Sample.App, while a change to Sharpino.Sample.App can't break Sharpino.Sample.Shared.Entities.
Position
Below the diagonal: Sharpino.Sample.App uses a module listed above it, which is the healthy direction.
Sharpino.Sample.App uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Sample.App, while a change to Sharpino.Sample.App can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Sample.App uses a module listed above it, which is the healthy direction.
Sharpino.Sample.App uses Sharpino.Sample.Todos.TodoEvents, so a change to Sharpino.Sample.Todos.TodoEvents can break Sharpino.Sample.App, while a change to Sharpino.Sample.App can't break Sharpino.Sample.Todos.TodoEvents.
Position
Below the diagonal: Sharpino.Sample.App uses a module listed above it, which is the healthy direction.
Sharpino.Template uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Sharpino.Template, while a change to Sharpino.Template can't break Sharpino.EventBroker.
Position
Below the diagonal: Sharpino.Template uses a module listed above it, which is the healthy direction.
Sharpino.Template uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Template, while a change to Sharpino.Template can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Template uses a module listed above it, which is the healthy direction.
Sharpino.Template uses Sharpino.Template.Commons, so a change to Sharpino.Template.Commons can break Sharpino.Template, while a change to Sharpino.Template can't break Sharpino.Template.Commons.
Position
Below the diagonal: Sharpino.Template uses a module listed above it, which is the healthy direction.
Sharpino.Template uses Sharpino.Template.Models, so a change to Sharpino.Template.Models can break Sharpino.Template, while a change to Sharpino.Template can't break Sharpino.Template.Models.
Position
Below the diagonal: Sharpino.Template uses a module listed above it, which is the healthy direction.
Sharpino.Template uses sharpino.Template.Models, so a change to sharpino.Template.Models can break Sharpino.Template, while a change to Sharpino.Template can't break sharpino.Template.Models.
Position
Below the diagonal: Sharpino.Template uses a module listed above it, which is the healthy direction.
Sharpino.Template.Manager uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Sharpino.Template.Manager, while a change to Sharpino.Template.Manager can't break Sharpino.EventBroker.
Position
Below the diagonal: Sharpino.Template.Manager uses a module listed above it, which is the healthy direction.
Sharpino.Template.Manager uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Template.Manager, while a change to Sharpino.Template.Manager can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Template.Manager uses a module listed above it, which is the healthy direction.
Sharpino.Template.Manager uses Sharpino.Template.Commons, so a change to Sharpino.Template.Commons can break Sharpino.Template.Manager, while a change to Sharpino.Template.Manager can't break Sharpino.Template.Commons.
Position
Below the diagonal: Sharpino.Template.Manager uses a module listed above it, which is the healthy direction.
Sharpino.Template.Manager uses Sharpino.PgStorage, so a change to Sharpino.PgStorage can break Sharpino.Template.Manager, while a change to Sharpino.Template.Manager can't break Sharpino.PgStorage.
Position
Below the diagonal: Sharpino.Template.Manager uses a module listed above it, which is the healthy direction.
Sharpino.Template.Manager uses Sharpino.Template.Models, so a change to Sharpino.Template.Models can break Sharpino.Template.Manager, while a change to Sharpino.Template.Manager can't break Sharpino.Template.Models.
Position
Below the diagonal: Sharpino.Template.Manager uses a module listed above it, which is the healthy direction.
Sharpino.Template.Manager uses sharpino.Template.Models, so a change to sharpino.Template.Models can break Sharpino.Template.Manager, while a change to Sharpino.Template.Manager can't break sharpino.Template.Models.
Position
Below the diagonal: Sharpino.Template.Manager uses a module listed above it, which is the healthy direction.
Sharpino.Template.TodosManager uses Sharpino.EventBroker, so a change to Sharpino.EventBroker can break Sharpino.Template.TodosManager, while a change to Sharpino.Template.TodosManager can't break Sharpino.EventBroker.
Position
Below the diagonal: Sharpino.Template.TodosManager uses a module listed above it, which is the healthy direction.
Sharpino.Template.TodosManager uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.Template.TodosManager, while a change to Sharpino.Template.TodosManager can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.Template.TodosManager uses a module listed above it, which is the healthy direction.
Sharpino.Template.TodosManager uses Sharpino.Template.Commons, so a change to Sharpino.Template.Commons can break Sharpino.Template.TodosManager, while a change to Sharpino.Template.TodosManager can't break Sharpino.Template.Commons.
Position
Below the diagonal: Sharpino.Template.TodosManager uses a module listed above it, which is the healthy direction.
Sharpino.Template.TodosManager uses Sharpino.Template.Models, so a change to Sharpino.Template.Models can break Sharpino.Template.TodosManager, while a change to Sharpino.Template.TodosManager can't break Sharpino.Template.Models.
Position
Below the diagonal: Sharpino.Template.TodosManager uses a module listed above it, which is the healthy direction.
Sharpino.Template.TodosManager uses Sharpino.Template.Models.Details, so a change to Sharpino.Template.Models.Details can break Sharpino.Template.TodosManager, while a change to Sharpino.Template.TodosManager can't break Sharpino.Template.Models.Details.
Position
Below the diagonal: Sharpino.Template.TodosManager uses a module listed above it, which is the healthy direction.
Sharpino.EventSourcing.Sample.AppVersions uses Sharpino.Storage, so a change to Sharpino.Storage can break Sharpino.EventSourcing.Sample.AppVersions, while a change to Sharpino.EventSourcing.Sample.AppVersions can't break Sharpino.Storage.
Position
Below the diagonal: Sharpino.EventSourcing.Sample.AppVersions uses a module listed above it, which is the healthy direction.
Sharpino.EventSourcing.Sample.AppVersions uses Sharpino.PgStorage, so a change to Sharpino.PgStorage can break Sharpino.EventSourcing.Sample.AppVersions, while a change to Sharpino.EventSourcing.Sample.AppVersions can't break Sharpino.PgStorage.
Position
Below the diagonal: Sharpino.EventSourcing.Sample.AppVersions uses a module listed above it, which is the healthy direction.
Sharpino.EventSourcing.Sample.AppVersions uses Sharpino.Sample.App, so a change to Sharpino.Sample.App can break Sharpino.EventSourcing.Sample.AppVersions, while a change to Sharpino.EventSourcing.Sample.AppVersions can't break Sharpino.Sample.App.
Position
Below the diagonal: Sharpino.EventSourcing.Sample.AppVersions uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 65% · Adequate · gated by D4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
16
High / Critical
A02:2025 — Security Misconfiguration
14
High / Critical
A07:2025 — Authentication Failures
12
High / Critical
A05:2025 — Injection
1
High / Critical
Roadmap
Immediately resolve the eight leaked secrets in configuration files to eliminate critical security risks. Establish a CI pipeline that builds the project and runs tests on every push to prevent regressions, while integrating static analysis and secret scanning tools to enforce quality gates. Finally, update the README to accurately reflect the current codebase structure and remove outdated documentation links.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (2).
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.
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.
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.
Code Duplication: Near-duplicate member pair (130 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 — 530
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 — 33
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 35
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
Watchdog 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. 40 of 43 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 43 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 571 of 590 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog measured this, but not all of it. What it 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 1261 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.
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.
D39 IL Efficiency — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
S1 Web-Security Posture — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
Bring the 5 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 5 together lifts Cyclomatic Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
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.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 16 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 16 together lifts Cognitive Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
Do you agree with this assessment?
D3 · God Classes8.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 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).
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).
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.
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.
438 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.
+ 230 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with PgBinaryEventStore.fs (6), PgEventStore.fs (3), AzureServiceBusBackplane.fs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 15 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with CommandHandler.fs (4), PgBinaryEventStore.fs (2), StateView.fs (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 12 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CommandHandler.fs (4), StateView.fs (3), Cache.fs. — One of this dimension's main actionable groups (12 warning-level).
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.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with CourseManager.fs (2), MemoryStorage.fs. — One of this dimension's main actionable groups (3 warning-level).
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.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
5 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: Farmer · ×5
Outdated (npm): react · ×3
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
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).
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.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 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.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
Sharpino's documentation is clear and complete for its repository root README (a one-document overview with NuGet/MSVC links, What-is-event-sourcing, What-is-Sharpino, Goals, Issues, Projects, How to use it, How to contribute, Acknowledgements, News/Updates), plus detailed per-directory READMEs documenting Sharpino.Lib.Core/, Sharpino.Lib/, and the sample directories. The samples show real installation (dbmate up for local Postgres) and run commands with concrete output ('dotnet run'), which is excellent for usage. There are no missing-*/sections in the visible text, but the document outline lists several unshown sections that would appear under headings such as 'How to contribute' or 'Testing Strategy', so they exist and must not be flagged as missing. The Sharpino project's documentation is strong for its domain examples: each sample README (e.g. Stadium Seat Booking System, Pub Management System) gives an overview, a setup section with .env/dbmate commands, detailed key features, a domain model breakdown, business rules, and links to testing the application. The architecture/Docs markdown files provide design documentation that is not visible in this summary. However, there are gaps: the READMEs for Sharpino.Sample.24-28 (all work-in-progress samples) lack an overview of what the project does or its scope, and the root README is missing installation/contribution guidance. Sharpino.Sample's README is a well-structured sample project with an overview, key features, and a clear deprecation warning. It documents its own directory (Sharpino.Sample) rather than the repository as a whole, so it does not carry the root-level overview/installation/usage/contributing guidance. The accompanying architecture/Docs markdown files cover event sourcing, storage, and migration to newer patterns, which are internal design docs. The visible content is clear but clipped mid-document; the deprecation warning alone already conveys the project's purpose and direction.
Documentation: no project overviewSharpino.Sample/README.md
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 of 27 build units (MSBuild) flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability5.1 / 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.
96 % of calls cross a namespace and 2 % go through an interface, but 0 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
Scattered collaborators
What to do
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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
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).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
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.
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).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
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).
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.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 69 of the 183 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 5 Change coupling finding(s) in Change Coupling — start with CommandHandler.fs (2), Context.fs, Commands.fs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with Events.fs (3), Commands.fs. — One of this dimension's main actionable groups (4 warning-level).
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.
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. Scored 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. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
End-of-life runtime: .NET net9.0REDACTED:5
What to do
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
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.
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.
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 a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
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
Sharpino.Sample.22/Readme.md documents the environment variable `DATABASE_URL`, but no code, script or configuration file names it. 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.Sample.22/Readme.md:37
Sharpino.Sample.25/README.md documents the environment variable `DATABASE_URL`, but no code, script or configuration file names it. 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.Sample.25/README.md:14
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
P2 · Observability5.6 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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.
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.
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.
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.
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.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 16 use(s) across 29,945 production line(s) (~0.5/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
F#: on hot paths, work through Span/Memory (AsSpan/AsMemory) instead of copies, rent buffers from ArrayPool, make small records, unions and tuples [<Struct>]/struct (…) and options voption, mark lambda parameters of inline functions [<InlineIfLambda>], use valueTask for completions that are usually synchronous, and presize ResizeArray/StringBuilder.
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 the language 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/PgEventStore.fs:1785, Sharpino.Lib/PgEventStore.fs:2491, Sharpino.Lib/PgEventStore.fs:3313, …
What to do
F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
Other · 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.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not 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 — 71 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 — compose up failed (exit 18 — an image could not be pulled) — postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~17765 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.
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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
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: `--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.
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): 2 aggregate root(s) (entities that raise its domain events); 26 strongly-typed id(s); 135 value object(s); 61 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.
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.
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.
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/MemoryStorage.fs:348— Sharpino.Lib/MemoryStorage.fs:348-360 | Sharpino.Lib/MemoryStorage.fs:1022-1034 — both copies are in the same file, so extract the 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 (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:663— Sharpino.Lib/PgBinaryEventStore.fs:663-675 | Sharpino.Lib/PgEventStore.fs:823-835 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1206— Sharpino.Lib/PgBinaryEventStore.fs:1206-1218 | Sharpino.Lib/PgEventStore.fs:1180-1192 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1206` 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:2140— Sharpino.Lib/PgBinaryEventStore.fs:2140-2154 | Sharpino.Lib/PgEventStore.fs:2188-2200 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2140` 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:2397— Sharpino.Lib/PgBinaryEventStore.fs:2397-2409 | Sharpino.Lib/PgEventStore.fs:2240-2252 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2397` 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:800— Sharpino.Lib/PgEventStore.fs:800-812 | Sharpino.Lib/PgEventStore.fs:867-879 — both copies are in the same file, so extract the 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 (13 lines × 2) Sharpino.Lib/PgEventStore.fs:1277— Sharpino.Lib/PgEventStore.fs:1277-1289 | Sharpino.Lib/PgEventStore.fs:2572-2584 — both copies are in the same file, so extract the 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:1277` 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:2262— Sharpino.Lib/PgEventStore.fs:2262-2274 | Sharpino.Lib/PgEventStore.fs:2285-2297 — both copies are in the same file, so extract the 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:2262` 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.Lib/StateView.fs:453— Sharpino.Lib/StateView.fs:453-465 | Sharpino.Lib/StateView.fs:494-506 — both copies are in the same file, so extract the 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 (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.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs:8— Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs:8-20 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/Events.fs:7-19 — 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 (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1139— Sharpino.Lib/PgBinaryEventStore.fs:1139-1151 | Sharpino.Lib/PgEventStore.fs:1112-1124 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1139` 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:1127` calls `NpgsqlConnection` and `Sharpino.Lib/PgBinaryEventStore.fs:1154` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:838— Sharpino.Lib/PgBinaryEventStore.fs:838-850 | Sharpino.Lib/PgEventStore.fs:659-671 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:838` 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/Cache.fs:309— Sharpino.Lib/Cache.fs:309-317 | Sharpino.Lib/Cache.fs:529-537 — both copies are in the same file, so extract the 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:2201— Sharpino.Lib/CommandHandler.fs:2201-2209 | Sharpino.Lib/CommandHandler.fs:2429-2437 — both copies are in the same file, so extract the 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:2681— Sharpino.Lib/CommandHandler.fs:2681-2689 | Sharpino.Lib/CommandHandler.fs:2773-2781 — both copies are in the same file, so extract the 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:2905— Sharpino.Lib/CommandHandler.fs:2905-2913 | Sharpino.Lib/CommandHandler.fs:3036-3044 — both copies are in the same file, so extract the 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:2905` 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:4039— Sharpino.Lib/CommandHandler.fs:4039-4047 | Sharpino.Lib/CommandHandler.fs:5511-5519 — both copies are in the same file, so extract the 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:4039` 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:5522` calls `traverseResultM` and `Sharpino.Lib/CommandHandler.fs:4049` 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 103 separate duplicated blocks between them, totalling at least 2355 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:2452— Sharpino.Lib/PgBinaryEventStore.fs:2452-2460 | Sharpino.Lib/PgBinaryEventStore.fs:2735-2743 — both copies are in the same file, so extract the 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:2452` 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:613— Sharpino.Lib/StateView.fs:613-621 | Sharpino.Lib/StateView.fs:640-648 — both copies are in the same file, so extract the 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:671— Sharpino.Lib/StateView.fs:671-679 | Sharpino.Lib/StateView.fs:698-706 — both copies are in the same file, so extract the 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:1943— Sharpino.Lib/PgEventStore.fs:1943-1951 | Sharpino.Lib/PgEventStore.fs:2019-2028 — both copies are in the same file, so extract the 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:1943` 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/Cache.fs:637— Sharpino.Lib/Cache.fs:637-643 | Sharpino.Lib/Cache.fs:699-705 — both copies are in the same file, so extract the 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:637` 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:271— Sharpino.Lib/CommandHandler.fs:271-277 | Sharpino.Lib/CommandHandler.fs:310-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.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:883— Sharpino.Lib/CommandHandler.fs:883-889 | Sharpino.Lib/CommandHandler.fs:1090-1098 — both copies are in the same file, so extract the 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:1243— Sharpino.Lib/CommandHandler.fs:1243-1249 | Sharpino.Lib/CommandHandler.fs:1336-1342 — both copies are in the same file, so extract the 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:1243` 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:1344` calls `eventStore` and `Sharpino.Lib/CommandHandler.fs:1251` 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:1734— Sharpino.Lib/CommandHandler.fs:1734-1741 | Sharpino.Lib/CommandHandler.fs:1831-1837 — both copies are in the same file, so extract the 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:1734` 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:648— Sharpino.Lib/PgBinaryEventStore.fs:648-655 | Sharpino.Lib/PgEventStore.fs:809-815 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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/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:441— Sharpino.Lib/StateView.fs:441-447 | Sharpino.Lib/StateView.fs:551-557 — both copies are in the same file, so extract the 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.Lib/StateView.fs:453— Sharpino.Lib/StateView.fs:453-459 | Sharpino.Lib/StateView.fs:563-569 — both copies are in the same file, so extract the 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:869— Sharpino.Lib/StateView.fs:869-875 | Sharpino.Lib/StateView.fs:900-906 — both copies are in the same file, so extract the 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:869` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Lib/CommandHandler.fs:3968— Sharpino.Lib/CommandHandler.fs:3968-3981 | Sharpino.Lib/CommandHandler.fs:4475-4488 — both copies are in the same file, so extract the 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:5901— Sharpino.Lib/CommandHandler.fs:5901-5914 | Sharpino.Lib/CommandHandler.fs:5976-5989 — both copies are in the same file, so extract the 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:671— Sharpino.Lib/PgBinaryEventStore.fs:671-684 | Sharpino.Lib/PgBinaryEventStore.fs:744-757 — both copies are in the same file, so extract the 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:671` 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:831— Sharpino.Lib/PgEventStore.fs:831-844 | Sharpino.Lib/PgEventStore.fs:905-918 — both copies are in the same file, so extract the 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:831` 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.
Duplicated block (14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs:7— Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs:7-20 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Events.fs:6-19 — 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.Lib/CommandHandler.fs:1408— Sharpino.Lib/CommandHandler.fs:1408-1418 | Sharpino.Lib/CommandHandler.fs:1496-1506 — both copies are in the same file, so extract the 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:659— Sharpino.Lib/MemoryStorage.fs:659-669 | Sharpino.Lib/MemoryStorage.fs:678-688 — both copies are in the same file, so extract the 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:838— Sharpino.Lib/MemoryStorage.fs:838-848 | Sharpino.Lib/MemoryStorage.fs:856-866 — both copies are in the same file, so extract the 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:1984-1994 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:715— Sharpino.Lib/PgBinaryEventStore.fs:715-725 | Sharpino.Lib/PgEventStore.fs:876-886 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2464— Sharpino.Lib/PgBinaryEventStore.fs:2464-2474 | Sharpino.Lib/PgBinaryEventStore.fs:2510-2520 — both copies are in the same file, so extract the 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:1936— Sharpino.Lib/PgEventStore.fs:1936-1946 | Sharpino.Lib/PgEventStore.fs:2194-2204 — both copies are in the same file, so extract the 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:1936` 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/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.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:4177— Sharpino.Lib/CommandHandler.fs:4177-4187 | Sharpino.Lib/CommandHandler.fs:4326-4336 — both copies are in the same file, so extract the 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:330— Sharpino.Lib/CommandHandler.fs:330-341 | Sharpino.Lib/CommandHandler.fs:1136-1147 — both copies are in the same file, so extract the 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:5451— Sharpino.Lib/CommandHandler.fs:5451-5462 | Sharpino.Lib/CommandHandler.fs:5676-5687 — both copies are in the same file, so extract the 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 103 separate duplicated blocks between them, totalling at least 2355 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:2506— Sharpino.Lib/PgBinaryEventStore.fs:2506-2517 | Sharpino.Lib/PgEventStore.fs:2361-2372 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2127— Sharpino.Lib/PgBinaryEventStore.fs:2127-2138 | Sharpino.Lib/PgEventStore.fs:2105-2119 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2127` 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.
Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:2612— Sharpino.Lib/CommandHandler.fs:2612-2619 | Sharpino.Lib/CommandHandler.fs:2803-2810 — both copies are in the same file, so extract the 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 103 separate duplicated blocks between them, totalling at least 2355 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/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:588— Sharpino.Lib/StateView.fs:588-595 | Sharpino.Lib/StateView.fs:732-739 — both copies are in the same file, so extract the 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:798— Sharpino.Lib/StateView.fs:798-805 | Sharpino.Lib/StateView.fs:862-869 — both copies are in the same file, so extract the 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.11/Models/Course/Events.fs:21— Sharpino.Sample.11/Models/Course/Events.fs:21-28 | Sharpino.Sample.14/Models/Course/Events.fs:23-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 (8 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs:14— Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs:14-21 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Events.fs:12-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) 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.
Duplicated block (17 lines × 2) Sharpino.Lib/CommandHandler.fs:2174— Sharpino.Lib/CommandHandler.fs:2174-2190 | Sharpino.Lib/CommandHandler.fs:2214-2230 — both copies are in the same file, so extract the 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 103 separate duplicated blocks between them, totalling at least 2355 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:891— Sharpino.Lib/PgBinaryEventStore.fs:891-907 | Sharpino.Lib/PgEventStore.fs:713-729 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:891` 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.Lib/PgBinaryEventStore.fs:1263— Sharpino.Lib/PgBinaryEventStore.fs:1263-1279 | Sharpino.Lib/PgEventStore.fs:1241-1257 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1263` 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:2543— Sharpino.Lib/PgBinaryEventStore.fs:2543-2559 | Sharpino.Lib/PgEventStore.fs:2287-2303 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1131— Sharpino.Lib/PgEventStore.fs:1131-1147 | Sharpino.Lib/PgEventStore.fs:1564-1580 — both copies are in the same file, so extract the 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:1131` 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.
Duplicated block (6 lines × 2) Sharpino.Lib/Cache.fs:259— Sharpino.Lib/Cache.fs:259-264 | Sharpino.Lib/Cache.fs:553-558 — both copies are in the same file, so extract the 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:667— Sharpino.Lib/Cache.fs:667-672 | Sharpino.Lib/Cache.fs:707-712 — both copies are in the same file, so extract the 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:1678— Sharpino.Lib/CommandHandler.fs:1678-1683 | Sharpino.Lib/CommandHandler.fs:1775-1780 — both copies are in the same file, so extract the 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:1678` 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:3160— Sharpino.Lib/CommandHandler.fs:3160-3165 | Sharpino.Lib/CommandHandler.fs:3232-3237 — both copies are in the same file, so extract the 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:3160` 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:3167` calls `Obsolete` and `Sharpino.Lib/CommandHandler.fs:3239` 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:5916— Sharpino.Lib/CommandHandler.fs:5916-5921 | Sharpino.Lib/CommandHandler.fs:5991-5996 — both copies are in the same file, so extract the 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:1289— Sharpino.Lib/PgBinaryEventStore.fs:1289-1294 | Sharpino.Lib/PgBinaryEventStore.fs:2424-2429 — both copies are in the same file, so extract the 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:1289` 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/StateView.fs:887— Sharpino.Lib/StateView.fs:887-892 | Sharpino.Lib/StateView.fs:911-916 — both copies are in the same file, so extract the 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:887` 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:461-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ 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:457` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1600— Sharpino.Lib/PgBinaryEventStore.fs:1600-1618 | Sharpino.Lib/PgEventStore.fs:1577-1595 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 (19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1624— Sharpino.Lib/PgBinaryEventStore.fs:1624-1642 | Sharpino.Lib/PgEventStore.fs:1603-1624 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1624` 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:2520— Sharpino.Lib/PgBinaryEventStore.fs:2520-2538 | Sharpino.Lib/PgEventStore.fs:2375-2393 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2520` 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:3158— Sharpino.Lib/PgBinaryEventStore.fs:3158-3176 | Sharpino.Lib/PgEventStore.fs:3185-3203 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:3158` 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.16/Models/Products/Events.fs:1— Sharpino.Sample.16/Models/Products/Events.fs:1-19 | Sharpino.Sample.17/Models/Products/Events.fs:1-19 — 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 (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:1181— Sharpino.Lib/PgBinaryEventStore.fs:1181-1199 | Sharpino.Lib/PgEventStore.fs:1155-1173 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1181` 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.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 103 separate duplicated blocks between them, totalling at least 2355 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:2327— Sharpino.Lib/PgBinaryEventStore.fs:2327-2344 | Sharpino.Lib/PgEventStore.fs:2716-2733 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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: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.
Duplicated block (18 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2793— Sharpino.Lib/PgBinaryEventStore.fs:2793-2810 | Sharpino.Lib/PgEventStore.fs:2616-2633 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2793` 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:2813` calls `NpgsqlConnection` and `Sharpino.Lib/PgEventStore.fs:2636` 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.
Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:1163— Sharpino.Lib/CommandHandler.fs:1163-1172 | Sharpino.Lib/CommandHandler.fs:1583-1592 — both copies are in the same file, so extract the 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:2252— Sharpino.Lib/CommandHandler.fs:2252-2261 | Sharpino.Lib/CommandHandler.fs:2268-2277 — both copies are in the same file, so extract the 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:2252` 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:3993— Sharpino.Lib/CommandHandler.fs:3993-4002 | Sharpino.Lib/CommandHandler.fs:4500-4509 — both copies are in the same file, so extract the 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 103 separate duplicated blocks between them, totalling at least 2355 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:953— Sharpino.Lib/StateView.fs:953-962 | Sharpino.Lib/StateView.fs:977-986 — both copies are in the same file, so extract the 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:953` 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/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.
FileTooLong: Sharpino.Lib/CommandHandler.fs Sharpino.Lib/CommandHandler.fs— FileTooLong — 5107 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 86 functions. The bar is 500 significant lines; this is 4607 over it, 10.21× 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 — 2652 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2152 over it, 5.30× 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 — 2645 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2145 over it, 5.29× 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 — 1089 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 41 functions. The bar is 500 significant lines; this is 589 over it, 2.18× 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 — 1043 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 543 over it, 2.09× 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 — 790 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 290 over it, 1.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.
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-29 | Sharpino.Sample.24/Domain/User/Events.fs:2-29 | Sharpino.Sample.26/Domain/User/Events.fs:2-29 | Sharpino.Sample.27/Domain/User/Events.fs:2-29 | Sharpino.Sample.28/Domain/User/Events.fs:2-29 — 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.
Duplicated block (6 lines × 3) Sharpino.Lib/Cache.fs:237— Sharpino.Lib/Cache.fs:237-242 | Sharpino.Lib/Cache.fs:309-314 | Sharpino.Lib/Cache.fs:529-534 — 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:315` 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:53-58 — 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:897— Sharpino.Lib/CommandHandler.fs:897-902 | Sharpino.Lib/CommandHandler.fs:2699-2705 | Sharpino.Lib/CommandHandler.fs:2788-2793 — 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:2707` calls `commands` and `Sharpino.Lib/CommandHandler.fs:2796` 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:3475— Sharpino.Lib/CommandHandler.fs:3475-3480 | Sharpino.Lib/CommandHandler.fs:3702-3707 | Sharpino.Lib/CommandHandler.fs:3928-3933 — 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:1246-1251 — 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.
Sync-over-async blocking Sharpino.Lib/PgEventStore.fs:1785— `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:2491— `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:3313— `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:1794— `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:2661— `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:3283— `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.
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 82% of the time (18 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 18 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: Commands.fs ↔ Commands.fs Sharpino.Sample/Domain/Tags/Commands.fs:1— `Sharpino.Sample/Domain/Tags/Commands.fs` and `Sharpino.Sample/Domain/Todos/Commands.fs` change together 75% of the time (12 of the 16 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 12 shared commits counted here, the most recent 3 are `fb1d9b9b` adjust sample to vers. 2.5.5; `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 86 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 `6ceddf45` added new async multi stream stuff; `d36e4f4d` added new async eventstore+commands; `7c912b8a` async stateviewer tests — run `git show` on any of them.
Change coupling: AppVersions.fs ↔ Commands.fs Sharpino.Sample/AppVersions.fs:1— `Sharpino.Sample/AppVersions.fs` and `Sharpino.Sample/Domain/Todos/Commands.fs` change together 53% of the time (10 of the 19 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 10 shared commits counted here, the most recent 3 are `a7f8d64e` wip; `8ecfd6b9` refactor name uniformity (context not cluster); `d9af08cf` refactor naming — 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 50% of the time (70 of the 139 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 70 shared commits counted here, the most recent 3 are `ddd62a8c` mailboxprocessor + r/w separate connections; `1ace3260` Improve&fix lock 4 high concurrency; `d002c0cf` v. 5.0.1 (improve task comp) — run `git show` on any of them.
Duplicated block (25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1900— Sharpino.Lib/PgBinaryEventStore.fs:1900-1924 | Sharpino.Lib/PgEventStore.fs:1895-1919 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2088— Sharpino.Lib/PgBinaryEventStore.fs:2088-2112 | Sharpino.Lib/PgEventStore.fs:2066-2090 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2088` 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:2877— Sharpino.Lib/PgBinaryEventStore.fs:2877-2901 | Sharpino.Lib/PgEventStore.fs:2903-2927 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1878— Sharpino.Lib/PgBinaryEventStore.fs:1878-1898 | Sharpino.Lib/PgEventStore.fs:1873-1893 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.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.
Duplicated block (20 lines × 2) Sharpino.Lib/MemoryStorage.fs:411— Sharpino.Lib/MemoryStorage.fs:411-430 | Sharpino.Lib/MemoryStorage.fs:436-455 — both copies are in the same file, so extract the 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 103 separate duplicated blocks between them, totalling at least 2355 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:1327— Sharpino.Lib/PgBinaryEventStore.fs:1327-1346 | Sharpino.Lib/PgEventStore.fs:1304-1323 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1728— Sharpino.Lib/PgBinaryEventStore.fs:1728-1747 | Sharpino.Lib/PgBinaryEventStore.fs:1839-1858 — both copies are in the same file, so extract the 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:1728` 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.
Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:637— Sharpino.Lib/PgBinaryEventStore.fs:637-652 | Sharpino.Lib/PgBinaryEventStore.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. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:637` 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:733— Sharpino.Lib/PgBinaryEventStore.fs:733-748 | Sharpino.Lib/PgEventStore.fs:894-909 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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/PgBinaryEventStore.fs:1399— Sharpino.Lib/PgBinaryEventStore.fs:1399-1414 | Sharpino.Lib/PgEventStore.fs:1433-1448 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1399` 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:2768— Sharpino.Lib/PgBinaryEventStore.fs:2768-2783 | Sharpino.Lib/PgEventStore.fs:2591-2606 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2768` 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.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 (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/PgBinaryEventStore.fs:1295— Sharpino.Lib/PgBinaryEventStore.fs:1295-1309 | Sharpino.Lib/PgBinaryEventStore.fs:2744-2758 — both copies are in the same file, so extract the 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:2146— Sharpino.Lib/PgBinaryEventStore.fs:2146-2160 | Sharpino.Lib/PgEventStore.fs:2125-2139 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2125` 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/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/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.
Duplicated block (10 lines × 3) Sharpino.Lib/CommandHandler.fs:2345— Sharpino.Lib/CommandHandler.fs:2345-2354 | Sharpino.Lib/CommandHandler.fs:2393-2402 | Sharpino.Lib/CommandHandler.fs:2440-2449 — 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:2345` 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:2829— Sharpino.Lib/CommandHandler.fs:2829-2838 | Sharpino.Lib/CommandHandler.fs:3110-3119 | Sharpino.Lib/CommandHandler.fs:3183-3192 — 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:838— Sharpino.Lib/MemoryStorage.fs:838-847 | Sharpino.Lib/MemoryStorage.fs:856-865 | Sharpino.Lib/MemoryStorage.fs:886-895 — 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.
Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs:1962— Sharpino.Lib/CommandHandler.fs:1962-1966 | Sharpino.Lib/CommandHandler.fs:2086-2090 — both copies are in the same file, so extract the 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:2084` calls `Memoize2` and `Sharpino.Lib/CommandHandler.fs:1960` 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:1192— Sharpino.Lib/CommandHandler.fs:1192-1196 | Sharpino.Lib/CommandHandler.fs:1625-1629 — both copies are in the same file, so extract the 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:5804— Sharpino.Lib/CommandHandler.fs:5804-5808 | Sharpino.Lib/CommandHandler.fs:5862-5866 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
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.
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.
Change-coupling hub: Events.fs → AppVersions.fs, Commands.fs, Context.fs, Events.fs Sharpino.Sample/Domain/Categories/Events.fs— `Sharpino.Sample/Domain/Categories/Events.fs` changes together with 4 other files — `Sharpino.Sample/AppVersions.fs`, `Sharpino.Sample/Domain/Tags/Commands.fs`, `Sharpino.Sample/Domain/Tags/Context.fs`, `Sharpino.Sample/Domain/Tags/Events.fs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
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— `Sharpino.Sample/Domain/Todos/Events.fs` changes together with 7 other files — `Sharpino.Sample/AppVersions.fs`, `Sharpino.Sample/Domain/Categories/Commands.fs`, `Sharpino.Sample/Domain/Categories/Context.fs`, `Sharpino.Sample/Domain/Categories/Events.fs`, `Sharpino.Sample/Domain/Tags/Commands.fs`, `Sharpino.Sample/Domain/Tags/Context.fs`, `Sharpino.Sample/Domain/Tags/Events.fs` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Change-coupling hub: Commands.fs → AppVersions.fs, Commands.fs, Context.fs, Events.fs, Commands.fs Sharpino.Sample/Domain/Categories/Commands.fs— `Sharpino.Sample/Domain/Categories/Commands.fs` changes together with 5 other files — `Sharpino.Sample/AppVersions.fs`, `Sharpino.Sample/Domain/Tags/Commands.fs`, `Sharpino.Sample/Domain/Tags/Context.fs`, `Sharpino.Sample/Domain/Tags/Events.fs`, `Sharpino.Sample/Domain/Todos/Commands.fs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: Events.fs → AppVersions.fs, Context.fs, Commands.fs Sharpino.Sample/Domain/Tags/Events.fs— `Sharpino.Sample/Domain/Tags/Events.fs` changes together with 3 other files — `Sharpino.Sample/AppVersions.fs`, `Sharpino.Sample/Domain/Categories/Context.fs`, `Sharpino.Sample/Domain/Todos/Commands.fs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
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-27 | Sharpino.Sample.24/Domain/Todo/Events.fs:2-27 | Sharpino.Sample.25/Models/Todo/Events.fs:2-27 | Sharpino.Sample.26/Domain/Todo/Events.fs:2-27 | Sharpino.Sample.27/Domain/Todo/Events.fs:2-27 | Sharpino.Sample.28/Domain/Todo/Events.fs:2-27 — 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.
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:3294— Sharpino.Lib/CommandHandler.fs:3294-3306 | Sharpino.Lib/CommandHandler.fs:3524-3534 | Sharpino.Lib/CommandHandler.fs:3750-3760 — 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 × 4) Sharpino.Lib/CommandHandler.fs:2155— Sharpino.Lib/CommandHandler.fs:2155-2164 | Sharpino.Lib/CommandHandler.fs:2194-2203 | Sharpino.Lib/CommandHandler.fs:2283-2292 | Sharpino.Lib/CommandHandler.fs:2469-2478 — 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:2155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) Sharpino.Lib/MemoryStorage.fs:421— Sharpino.Lib/MemoryStorage.fs:421-430 | Sharpino.Lib/MemoryStorage.fs:446-455 | Sharpino.Lib/MemoryStorage.fs:590-599 | Sharpino.Lib/MemoryStorage.fs:614-623 — 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 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (8 lines × 4) Sharpino.Lib/CommandHandler.fs:2828— Sharpino.Lib/CommandHandler.fs:2828-2835 | Sharpino.Lib/CommandHandler.fs:3109-3116 | Sharpino.Lib/CommandHandler.fs:3182-3189 | Sharpino.Lib/CommandHandler.fs:3253-3260 — 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:4074— Sharpino.Lib/CommandHandler.fs:4074-4081 | Sharpino.Lib/CommandHandler.fs:4222-4229 | Sharpino.Lib/CommandHandler.fs:4371-4378 | Sharpino.Lib/CommandHandler.fs:5561-5568 — 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:5571` calls `fun` and `Sharpino.Lib/CommandHandler.fs:4083` 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:4083— Sharpino.Lib/CommandHandler.fs:4083-4090 | Sharpino.Lib/CommandHandler.fs:4231-4238 | Sharpino.Lib/CommandHandler.fs:4380-4387 | Sharpino.Lib/CommandHandler.fs:5573-5580 — 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:670— Sharpino.Lib/PgBinaryEventStore.fs:670-677 | Sharpino.Lib/PgBinaryEventStore.fs:743-750 | Sharpino.Lib/PgEventStore.fs:830-837 | Sharpino.Lib/PgEventStore.fs:904-911 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 × 6) Sharpino.Lib/CommandHandler.fs:159— Sharpino.Lib/CommandHandler.fs:159-163 | Sharpino.Lib/CommandHandler.fs:218-222 | Sharpino.Lib/CommandHandler.fs:2159-2163 | Sharpino.Lib/CommandHandler.fs:2198-2202 | Sharpino.Lib/CommandHandler.fs:2287-2291 | Sharpino.Lib/CommandHandler.fs:2473-2477 — 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.
Duplicated block (5 lines × 6) Sharpino.Lib/CommandHandler.fs:894— Sharpino.Lib/CommandHandler.fs:894-898 | Sharpino.Lib/CommandHandler.fs:1111-1115 | Sharpino.Lib/CommandHandler.fs:2696-2702 | Sharpino.Lib/CommandHandler.fs:4774-4779 | Sharpino.Lib/CommandHandler.fs:5067-5072 | Sharpino.Lib/CommandHandler.fs:5360-5365 — 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:2263— Sharpino.Lib/PgBinaryEventStore.fs:2263-2267 | Sharpino.Lib/PgBinaryEventStore.fs:2305-2309 | Sharpino.Lib/PgBinaryEventStore.fs:2347-2351 | Sharpino.Lib/PgEventStore.fs:2736-2740 | Sharpino.Lib/PgEventStore.fs:2821-2825 | Sharpino.Lib/PgEventStore.fs:2870-2874 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2344` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2261` 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:825— Sharpino.Lib/StateView.fs:825-829 | Sharpino.Lib/StateView.fs:861-865 | Sharpino.Lib/StateView.fs:893-897 | Sharpino.Lib/StateView.fs:917-921 | Sharpino.Lib/StateView.fs:996-1000 | Sharpino.Lib/StateView.fs:1034-1038 — 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.
TooManyMethods: PgBinaryStore Sharpino.Lib/PgBinaryEventStore.fs:35— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PgEventStore Sharpino.Lib/PgEventStore.fs:52— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MemoryStorage Sharpino.Lib/MemoryStorage.fs:27— TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1003— Sharpino.Lib/PgBinaryEventStore.fs:1003-1025 | Sharpino.Lib/PgEventStore.fs:971-993 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1003` 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:996` calls `fun` and `Sharpino.Lib/PgBinaryEventStore.fs:1027` 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:1042— Sharpino.Lib/StateView.fs:1042-1064 | Sharpino.Lib/StateView.fs:1212-1234 — both copies are in the same file, so extract the 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:1042` 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:1736— Sharpino.Lib/PgBinaryEventStore.fs:1736-1758 | Sharpino.Lib/PgEventStore.fs:1725-1750 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1736` 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/CommandHandler.fs:1470— Sharpino.Lib/CommandHandler.fs:1470-1491 | Sharpino.Lib/CommandHandler.fs:1556-1577 — both copies are in the same file, so extract the 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:1470` 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:2346— Sharpino.Lib/PgBinaryEventStore.fs:2346-2367 | Sharpino.Lib/PgEventStore.fs:2735-2756 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2346` 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 (22 lines × 2) Sharpino.Sample.16/Models/Materials/Events.fs:1— Sharpino.Sample.16/Models/Materials/Events.fs:1-22 | Sharpino.Sample.17/Models/Materials/Events.fs:1-22 — 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.
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 103 separate duplicated blocks between them, totalling at least 2355 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:2018— Sharpino.Lib/PgBinaryEventStore.fs:2018-2039 | Sharpino.Lib/PgEventStore.fs:2146-2166 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2018` 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:2055— Sharpino.Lib/PgBinaryEventStore.fs:2055-2076 | Sharpino.Lib/PgEventStore.fs:2031-2051 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2055` 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 (20 lines × 3) Sharpino.Lib/CommandHandler.fs:4710— Sharpino.Lib/CommandHandler.fs:4710-4729 | Sharpino.Lib/CommandHandler.fs:5009-5028 | Sharpino.Lib/CommandHandler.fs:5302-5321 — 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.
Duplicated block (19–20 lines × 2) Sharpino.Lib/CommandHandler.fs:2357— Sharpino.Lib/CommandHandler.fs:2357-2376 | Sharpino.Lib/CommandHandler.fs:2405-2423 — both copies are in the same file, so extract the 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:2357` 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–20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1434— Sharpino.Lib/PgBinaryEventStore.fs:1434-1453 | Sharpino.Lib/PgEventStore.fs:1468-1486 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1434` 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:1468` calls `ExecuteNonQueryAsync` and `Sharpino.Lib/PgBinaryEventStore.fs:1434` 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 (19–20 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2632— Sharpino.Lib/PgBinaryEventStore.fs:2632-2651 | Sharpino.Lib/PgEventStore.fs:2463-2481 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2632` 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:424— Sharpino.Lib/PgBinaryEventStore.fs:424-442 | Sharpino.Lib/PgEventStore.fs:1954-1971 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1929— Sharpino.Lib/PgBinaryEventStore.fs:1929-1947 | Sharpino.Lib/PgEventStore.fs:1924-1941 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1929` 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:2369— Sharpino.Lib/PgBinaryEventStore.fs:2369-2387 | Sharpino.Lib/PgEventStore.fs:2213-2230 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 × 3) Sharpino.Lib/CommandHandler.fs:670— Sharpino.Lib/CommandHandler.fs:670-684 | Sharpino.Lib/CommandHandler.fs:768-782 | Sharpino.Lib/CommandHandler.fs:906-920 — 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:670` 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:3448— Sharpino.Lib/CommandHandler.fs:3448-3462 | Sharpino.Lib/CommandHandler.fs:3678-3692 | Sharpino.Lib/CommandHandler.fs:3904-3918 — 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.
Duplicated block (12 lines × 4) Sharpino.Lib/CommandHandler.fs:1665— Sharpino.Lib/CommandHandler.fs:1665-1676 | Sharpino.Lib/CommandHandler.fs:1762-1773 | Sharpino.Lib/CommandHandler.fs:1858-1869 | Sharpino.Lib/CommandHandler.fs:5713-5724 — 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:657— Sharpino.Lib/PgBinaryEventStore.fs:657-668 | Sharpino.Lib/PgBinaryEventStore.fs:727-738 | Sharpino.Lib/PgEventStore.fs:817-828 | Sharpino.Lib/PgEventStore.fs:888-899 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.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.
Duplicated block (11 lines × 5) Sharpino.Lib/CommandHandler.fs:4537— Sharpino.Lib/CommandHandler.fs:4537-4547 | Sharpino.Lib/CommandHandler.fs:4815-4825 | Sharpino.Lib/CommandHandler.fs:5108-5118 | Sharpino.Lib/CommandHandler.fs:5401-5411 | Sharpino.Lib/CommandHandler.fs:5489-5499 — 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.
Duplicated block (9 lines × 4) Sharpino.Lib/CommandHandler.fs:4133— Sharpino.Lib/CommandHandler.fs:4133-4141 | Sharpino.Lib/CommandHandler.fs:4283-4291 | Sharpino.Lib/CommandHandler.fs:4432-4440 | Sharpino.Lib/CommandHandler.fs:5634-5642 — 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:803-811 | Sharpino.Lib/PgEventStore.fs:870-878 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (7–8 lines × 2) Sharpino.Lib/CommandHandler.fs:891— Sharpino.Lib/CommandHandler.fs:891-898 | Sharpino.Lib/CommandHandler.fs:1109-1115 — both copies are in the same file, so extract the 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:1056— Sharpino.Lib/MemoryStorage.fs:1056-1062 | Sharpino.Lib/MemoryStorage.fs:1070-1077 — both copies are in the same file, so extract the 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:964— Sharpino.Lib/PgBinaryEventStore.fs:964-970 | Sharpino.Lib/PgBinaryEventStore.fs:999-1006 — both copies are in the same file, so extract the 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.
Duplicated block (5 lines × 3) Sharpino.Lib/CommandHandler.fs:603— Sharpino.Lib/CommandHandler.fs:603-607 | Sharpino.Lib/CommandHandler.fs:686-690 | Sharpino.Lib/CommandHandler.fs:922-926 — 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:894— Sharpino.Lib/CommandHandler.fs:894-898 | Sharpino.Lib/CommandHandler.fs:1111-1115 | Sharpino.Lib/CommandHandler.fs:1119-1123 — 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.
Low cohesion: MemoryStorage (LCOM4 13) Sharpino.Lib/MemoryStorage.fs:27— MemoryStorage's methods fall into 13 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 13 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.
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.
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.
Duplicated block (40 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1093— Sharpino.Lib/PgBinaryEventStore.fs:1093-1132 | Sharpino.Lib/PgEventStore.fs:1069-1108 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1093` 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:1800— Sharpino.Lib/PgBinaryEventStore.fs:1800-1839 | Sharpino.Lib/PgEventStore.fs:1791-1830 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1800` 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 (35–36 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1762— Sharpino.Lib/PgBinaryEventStore.fs:1762-1797 | Sharpino.Lib/PgEventStore.fs:1754-1788 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1762` 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:2826— Sharpino.Lib/PgBinaryEventStore.fs:2826-2861 | Sharpino.Lib/PgEventStore.fs:2649-2683 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 (35 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1511— Sharpino.Lib/PgBinaryEventStore.fs:1511-1545 | Sharpino.Lib/PgEventStore.fs:1486-1520 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1511` 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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.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.
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.
Duplicated block (28 lines × 5) Sharpino.Sample.22/Domain/User/Events.fs:2— Sharpino.Sample.22/Domain/User/Events.fs:2-29 | Sharpino.Sample.24/Domain/User/Events.fs:2-29 | Sharpino.Sample.26/Domain/User/Events.fs:2-29 | Sharpino.Sample.27/Domain/User/Events.fs:2-29 | Sharpino.Sample.28/Domain/User/Events.fs:2-29 — 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.
Duplicated block (28 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Events.fs:1— Sharpino.Sample.16/Models/WorkOrders/Events.fs:1-28 | Sharpino.Sample.17/Models/WorkOrders/Events.fs:1-28 — 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 (28 lines × 2) Sharpino.Sample.15/Models/Course/Events.fs:1— Sharpino.Sample.15/Models/Course/Events.fs:1-28 | Sharpino.Sample.15/Models/Student/Events.fs:1-28 — 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 (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.
Duplicated block (24 lines × 2) Sharpino.Lib/CommandHandler.fs:3681— Sharpino.Lib/CommandHandler.fs:3681-3704 | Sharpino.Lib/CommandHandler.fs:3907-3930 — both copies are in the same file, so extract the 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:1568— Sharpino.Lib/PgBinaryEventStore.fs:1568-1591 | Sharpino.Lib/PgEventStore.fs:1545-1568 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1568` 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:978— Sharpino.Lib/PgBinaryEventStore.fs:978-1001 | Sharpino.Lib/PgEventStore.fs:947-969 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:978` 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:1457— Sharpino.Lib/PgBinaryEventStore.fs:1457-1480 | Sharpino.Lib/PgEventStore.fs:1329-1351 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1457` 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 × 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.
Duplicated block (21 lines × 3) Sharpino.Lib/CommandHandler.fs:1308— Sharpino.Lib/CommandHandler.fs:1308-1328 | Sharpino.Lib/CommandHandler.fs:2030-2050 | Sharpino.Lib/CommandHandler.fs:2122-2142 — 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.
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.
Duplicated block (16–19 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2199— Sharpino.Lib/PgBinaryEventStore.fs:2199-2214 | Sharpino.Lib/PgBinaryEventStore.fs:2229-2247 — both copies are in the same file, so extract the 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:2762— Sharpino.Lib/PgEventStore.fs:2762-2777 | Sharpino.Lib/PgEventStore.fs:2787-2805 — both copies are in the same file, so extract the 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 × 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.
Duplicated block (16–17 lines × 3) Sharpino.Lib/CommandHandler.fs:4551— Sharpino.Lib/CommandHandler.fs:4551-4566 | Sharpino.Lib/CommandHandler.fs:4837-4853 | Sharpino.Lib/CommandHandler.fs:5130-5146 — 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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (12–13 lines × 3) Sharpino.Lib/CommandHandler.fs:1224— Sharpino.Lib/CommandHandler.fs:1224-1236 | Sharpino.Lib/CommandHandler.fs:1923-1935 | Sharpino.Lib/CommandHandler.fs:1997-2008 — 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:600— Sharpino.Lib/StateView.fs:600-612 | Sharpino.Lib/StateView.fs:627-639 | Sharpino.Lib/StateView.fs:659-670 — 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:600` 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–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:685— Sharpino.Lib/StateView.fs:685-697 | Sharpino.Lib/StateView.fs:719-730 — both copies are in the same file, so extract the 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:685` 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 (11–12 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:2263— Sharpino.Lib/PgBinaryEventStore.fs:2263-2273 | Sharpino.Lib/PgBinaryEventStore.fs:2305-2315 | Sharpino.Lib/PgBinaryEventStore.fs:2347-2358 | Sharpino.Lib/PgEventStore.fs:2736-2747 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2344` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2261` 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.
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:2584— Sharpino.Lib/CommandHandler.fs:2584-2594 | Sharpino.Lib/CommandHandler.fs:2681-2692 — both copies are in the same file, so extract the 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 × 6) Sharpino.Lib/CommandHandler.fs:377— Sharpino.Lib/CommandHandler.fs:377-387 | Sharpino.Lib/CommandHandler.fs:403-413 | Sharpino.Lib/CommandHandler.fs:436-446 | Sharpino.Lib/CommandHandler.fs:469-479 | Sharpino.Lib/CommandHandler.fs:499-509 | Sharpino.Lib/CommandHandler.fs:543-553 — 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:377` 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.
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.
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.
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:2613-2620 — 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.
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.
Duplicated block (8 lines × 7) Sharpino.Lib/CommandHandler.fs:2159— Sharpino.Lib/CommandHandler.fs:2159-2166 | Sharpino.Lib/CommandHandler.fs:2198-2205 | Sharpino.Lib/CommandHandler.fs:2287-2294 | Sharpino.Lib/CommandHandler.fs:2331-2338 | Sharpino.Lib/CommandHandler.fs:2379-2386 | Sharpino.Lib/CommandHandler.fs:2426-2433 | Sharpino.Lib/CommandHandler.fs:2473-2480 — 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.
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.
Duplicated block (8 lines × 3) Sharpino.Lib/CommandHandler.fs:2493— Sharpino.Lib/CommandHandler.fs:2493-2500 | Sharpino.Lib/CommandHandler.fs:2630-2637 | Sharpino.Lib/CommandHandler.fs:2716-2723 — 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:3235— Sharpino.Lib/CommandHandler.fs:3235-3242 | Sharpino.Lib/CommandHandler.fs:3485-3492 | Sharpino.Lib/CommandHandler.fs:4144-4151 — 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:3235` 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 × 4) Sharpino.Lib/CommandHandler.fs:4098— Sharpino.Lib/CommandHandler.fs:4098-4104 | Sharpino.Lib/CommandHandler.fs:4246-4252 | Sharpino.Lib/CommandHandler.fs:4395-4401 | Sharpino.Lib/CommandHandler.fs:5594-5600 — 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:825— Sharpino.Lib/StateView.fs:825-831 | Sharpino.Lib/StateView.fs:861-867 | Sharpino.Lib/StateView.fs:893-899 | Sharpino.Lib/StateView.fs:917-923 — 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 × 3) Sharpino.Lib/StateView.fs:587— Sharpino.Lib/StateView.fs:587-593 | Sharpino.Lib/StateView.fs:731-737 | Sharpino.Lib/StateView.fs:757-763 — 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:798— Sharpino.Lib/StateView.fs:798-804 | Sharpino.Lib/StateView.fs:826-832 | Sharpino.Lib/StateView.fs:862-868 — 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 × 5) Sharpino.Lib/StateView.fs:441— Sharpino.Lib/StateView.fs:441-446 | Sharpino.Lib/StateView.fs:481-486 | Sharpino.Lib/StateView.fs:551-556 | Sharpino.Lib/StateView.fs:613-618 | Sharpino.Lib/StateView.fs:640-645 — 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:607— Sharpino.Lib/StateView.fs:607-612 | Sharpino.Lib/StateView.fs:634-639 | Sharpino.Lib/StateView.fs:665-670 | Sharpino.Lib/StateView.fs:692-697 | Sharpino.Lib/StateView.fs:725-730 — 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:607` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 4) Sharpino.Lib/CommandHandler.fs:267— Sharpino.Lib/CommandHandler.fs:267-272 | Sharpino.Lib/CommandHandler.fs:306-311 | Sharpino.Lib/CommandHandler.fs:326-331 | Sharpino.Lib/CommandHandler.fs:1132-1137 — 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 (6 lines × 4) Sharpino.Lib/StateView.fs:798— Sharpino.Lib/StateView.fs:798-803 | Sharpino.Lib/StateView.fs:826-831 | Sharpino.Lib/StateView.fs:862-867 | Sharpino.Lib/StateView.fs:918-923 — 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 (5 lines × 12) Sharpino.Lib/CommandHandler.fs:600— Sharpino.Lib/CommandHandler.fs:600-604 | Sharpino.Lib/CommandHandler.fs:1159-1163 | Sharpino.Lib/CommandHandler.fs:1215-1219 | Sharpino.Lib/CommandHandler.fs:1299-1303 | Sharpino.Lib/CommandHandler.fs:1405-1409 | Sharpino.Lib/CommandHandler.fs:1493-1497 | Sharpino.Lib/CommandHandler.fs:1579-1583 | Sharpino.Lib/CommandHandler.fs:1891-1895 | Sharpino.Lib/CommandHandler.fs:1914-1918 | Sharpino.Lib/CommandHandler.fs:1988-1992 | Sharpino.Lib/CommandHandler.fs:2021-2025 | Sharpino.Lib/CommandHandler.fs:2113-2117 — 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:2043-2047 | Sharpino.Lib/PgBinaryEventStore.fs:2118-2122 | Sharpino.Lib/PgBinaryEventStore.fs:2787-2791 | Sharpino.Lib/PgEventStore.fs:467-471 | Sharpino.Lib/PgEventStore.fs:515-519 | Sharpino.Lib/PgEventStore.fs:1976-1980 | Sharpino.Lib/PgEventStore.fs:2096-2100 | Sharpino.Lib/PgEventStore.fs:2170-2174 | Sharpino.Lib/PgEventStore.fs:2610-2614 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.
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:2042-2046 | Sharpino.Lib/PgBinaryEventStore.fs:2345-2349 | Sharpino.Lib/PgEventStore.fs:466-470 | Sharpino.Lib/PgEventStore.fs:1975-1979 | Sharpino.Lib/PgEventStore.fs:2169-2173 | Sharpino.Lib/PgEventStore.fs:2734-2738 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.
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.
Hotspot: Sharpino.Lib/Cache.fs Sharpino.Lib/Cache.fs:128— Sharpino.Lib/Cache.fs changed 2 times in last 90 days, max cyclomatic complexity 15 in DetailsCache.SetupL2AndBackplane at line 128. 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 13:12:16 +02:00' --until='2026-10-22 13:12:16 +02: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.
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.
AggregateCache3.SetupL2AndBackplane (cognitive 38) Sharpino.Lib/Cache.fs:451— AggregateCache3.SetupL2AndBackplane has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (31 pts), match/switch 1 (5 pts), boolean chains 2 (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.
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.
CommandHandler.runThreeNAggregateCommandsMd (cognitive 33) Sharpino.Lib/CommandHandler.fs:5465— 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.
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.
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.
AggregateCache3.Memoize (cognitive 21) Sharpino.Lib/Cache.fs:660— 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.
AggregateCache3.MemoizeAsync (cognitive 21) Sharpino.Lib/Cache.fs:698— 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.
CommandHandler.runTwoNAggregateCommandsMd (cognitive 17) Sharpino.Lib/CommandHandler.fs:4006— 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.
CommandHandler.runTwoNAggregateCommandsMdAsync2 (cognitive 17) Sharpino.Lib/CommandHandler.fs:4148— 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.
CommandHandler.runTwoNAggregateCommandsMdAsync3 (cognitive 17) Sharpino.Lib/CommandHandler.fs:4297— 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.
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
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.
Near-duplicate member pair (2304 shared lines) Sharpino.Lib/PgBinaryEventStore.fs:1— Sharpino.Lib/PgBinaryEventStore.fs:1-3336 | Sharpino.Lib/PgEventStore.fs:1-3361 — These two members are variants of one another: 2304 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (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.
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.
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.
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.
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.
Duplicated block (143–144 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3013— Sharpino.Lib/PgBinaryEventStore.fs:3013-3155 | Sharpino.Lib/PgEventStore.fs:3039-3182 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:3013` 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 (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.
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.
Duplicated block (102 lines × 3) Sharpino.Lib/CommandHandler.fs:4584— Sharpino.Lib/CommandHandler.fs:4584-4685 | Sharpino.Lib/CommandHandler.fs:4881-4982 | Sharpino.Lib/CommandHandler.fs:5174-5275 — 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:4584` 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:4983` calls `crossAggregatesConstraint` and `Sharpino.Lib/CommandHandler.fs:4686` 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 (96 lines × 4) Sharpino.Lib/CommandHandler.fs:953— Sharpino.Lib/CommandHandler.fs:953-1048 | Sharpino.Lib/CommandHandler.fs:3333-3428 | Sharpino.Lib/CommandHandler.fs:3561-3656 | Sharpino.Lib/CommandHandler.fs:3787-3882 — 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 (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.
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.
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.
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.
Duplicated block (67 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3178— Sharpino.Lib/PgBinaryEventStore.fs:3178-3244 | Sharpino.Lib/PgEventStore.fs:3205-3271 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:3178` 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 (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.
Duplicated block (61–62 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:3270— Sharpino.Lib/PgBinaryEventStore.fs:3270-3331 | Sharpino.Lib/PgEventStore.fs:3301-3361 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:3270` 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 (59 lines × 3) Sharpino.Lib/CommandHandler.fs:4049— Sharpino.Lib/CommandHandler.fs:4049-4107 | Sharpino.Lib/CommandHandler.fs:4197-4255 | Sharpino.Lib/CommandHandler.fs:4346-4404 — 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 (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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (51–52 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1039— Sharpino.Lib/PgBinaryEventStore.fs:1039-1090 | Sharpino.Lib/PgEventStore.fs:1016-1066 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 (49–50 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2564— Sharpino.Lib/PgBinaryEventStore.fs:2564-2612 | Sharpino.Lib/PgEventStore.fs:2395-2444 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2613` calls `LogError` and `Sharpino.Lib/PgEventStore.fs:2447` 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 (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.
Duplicated block (41–43 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1221— Sharpino.Lib/PgBinaryEventStore.fs:1221-1261 | Sharpino.Lib/PgEventStore.fs:1195-1237 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1195` 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 (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.
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.
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.
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.
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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.
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.
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.
Duplicated block (37–38 lines × 3) Sharpino.Lib/CommandHandler.fs:2917— Sharpino.Lib/CommandHandler.fs:2917-2954 | Sharpino.Lib/CommandHandler.fs:2988-3025 | Sharpino.Lib/CommandHandler.fs:3048-3084 — 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 (34–38 lines × 3) Sharpino.Lib/CommandHandler.fs:4756— Sharpino.Lib/CommandHandler.fs:4756-4793 | Sharpino.Lib/CommandHandler.fs:5053-5086 | Sharpino.Lib/CommandHandler.fs:5346-5379 — 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:4756` 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 (38 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2904— Sharpino.Lib/PgBinaryEventStore.fs:2904-2941 | Sharpino.Lib/PgEventStore.fs:2930-2967 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 (36 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2975— Sharpino.Lib/PgBinaryEventStore.fs:2975-3010 | Sharpino.Lib/PgEventStore.fs:3001-3036 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2975` 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 (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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (30–32 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:764— Sharpino.Lib/PgBinaryEventStore.fs:764-795 | Sharpino.Lib/PgBinaryEventStore.fs:855-885 | Sharpino.Lib/PgEventStore.fs:585-614 | Sharpino.Lib/PgEventStore.fs:676-707 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:764` 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 (31–32 lines × 3) Sharpino.Lib/CommandHandler.fs:1343— Sharpino.Lib/CommandHandler.fs:1343-1374 | Sharpino.Lib/CommandHandler.fs:1685-1715 | Sharpino.Lib/CommandHandler.fs:1782-1812 — 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 (32 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1481— Sharpino.Lib/PgBinaryEventStore.fs:1481-1512 | Sharpino.Lib/PgEventStore.fs:1352-1383 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1481` 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 (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.
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.
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 (28–30 lines × 4) Sharpino.Lib/CommandHandler.fs:1423— Sharpino.Lib/CommandHandler.fs:1423-1451 | Sharpino.Lib/CommandHandler.fs:1513-1541 | Sharpino.Lib/CommandHandler.fs:2646-2673 | Sharpino.Lib/CommandHandler.fs:2735-2764 — 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 (24–30 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:1695— Sharpino.Lib/PgBinaryEventStore.fs:1695-1724 | Sharpino.Lib/PgBinaryEventStore.fs:2962-2985 | Sharpino.Lib/PgEventStore.fs:1679-1708 | Sharpino.Lib/PgEventStore.fs:2988-3011 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1695` 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 (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.
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 103 separate duplicated blocks between them, totalling at least 2355 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.
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.
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.
Duplicated block (25–27 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:811— Sharpino.Lib/PgBinaryEventStore.fs:811-836 | Sharpino.Lib/PgBinaryEventStore.fs:912-936 | Sharpino.Lib/PgEventStore.fs:630-656 | Sharpino.Lib/PgEventStore.fs:734-759 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:811` 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 (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.
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.
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.
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.
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 103 separate duplicated blocks between them, totalling at least 2355 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 × 5) Sharpino.Sample.22/Domain/Todo/Events.fs:2— Sharpino.Sample.22/Domain/Todo/Events.fs:2-26 | Sharpino.Sample.24/Domain/Todo/Events.fs:2-26 | Sharpino.Sample.26/Domain/Todo/Events.fs:2-26 | Sharpino.Sample.27/Domain/Todo/Events.fs:2-26 | Sharpino.Sample.28/Domain/Todo/Events.fs:2-26 — 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 (24–25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1934— Sharpino.Lib/PgBinaryEventStore.fs:1934-1958 | Sharpino.Lib/PgBinaryEventStore.fs:1993-2016 — both copies are in the same file, so extract the 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–25 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2695— Sharpino.Lib/PgBinaryEventStore.fs:2695-2719 | Sharpino.Lib/PgEventStore.fs:2523-2542 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2695` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–24 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:2669— Sharpino.Lib/PgBinaryEventStore.fs:2669-2692 | Sharpino.Lib/PgBinaryEventStore.fs:3291-3309 | Sharpino.Lib/PgEventStore.fs:2498-2520 | Sharpino.Lib/PgEventStore.fs:3321-3339 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20–23 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2174— Sharpino.Lib/PgBinaryEventStore.fs:2174-2193 | Sharpino.Lib/PgEventStore.fs:2693-2715 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (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.
Duplicated block (20–22 lines × 3) Sharpino.Lib/StateView.fs:1003— Sharpino.Lib/StateView.fs:1003-1022 | Sharpino.Lib/StateView.fs:1084-1105 | Sharpino.Lib/StateView.fs:1153-1174 — 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:1003` 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–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 103 separate duplicated blocks between them, totalling at least 2355 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–21 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1154— Sharpino.Lib/PgBinaryEventStore.fs:1154-1173 | Sharpino.Lib/PgBinaryEventStore.fs:1583-1603 — both copies are in the same file, so extract the 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:1154` 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–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.
Duplicated block (13–20 lines × 8) Sharpino.Lib/PgBinaryEventStore.fs:348— Sharpino.Lib/PgBinaryEventStore.fs:348-363 | Sharpino.Lib/PgBinaryEventStore.fs:1699-1717 | Sharpino.Lib/PgBinaryEventStore.fs:1809-1828 | Sharpino.Lib/PgBinaryEventStore.fs:2966-2978 | Sharpino.Lib/PgEventStore.fs:361-376 | Sharpino.Lib/PgEventStore.fs:1683-1701 | Sharpino.Lib/PgEventStore.fs:1800-1819 | Sharpino.Lib/PgEventStore.fs:2992-3004 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (18–19 lines × 3) Sharpino.Lib/CommandHandler.fs:2318— Sharpino.Lib/CommandHandler.fs:2318-2336 | Sharpino.Lib/CommandHandler.fs:2366-2384 | Sharpino.Lib/CommandHandler.fs:2414-2431 — 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:2318` 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 × 3) Sharpino.Lib/CommandHandler.fs:4685— Sharpino.Lib/CommandHandler.fs:4685-4703 | Sharpino.Lib/CommandHandler.fs:4985-5003 | Sharpino.Lib/CommandHandler.fs:5278-5296 — 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:4983` calls `crossAggregatesConstraint` and `Sharpino.Lib/CommandHandler.fs:4683` 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 × 6) Sharpino.Lib/PgBinaryEventStore.fs:1733— Sharpino.Lib/PgBinaryEventStore.fs:1733-1750 | Sharpino.Lib/PgBinaryEventStore.fs:1844-1861 | Sharpino.Lib/PgBinaryEventStore.fs:2696-2713 | Sharpino.Lib/PgBinaryEventStore.fs:2846-2863 | Sharpino.Lib/PgEventStore.fs:2525-2542 | Sharpino.Lib/PgEventStore.fs:2668-2685 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1733` 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–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.
Duplicated block (16–17 lines × 7) Sharpino.Lib/CommandHandler.fs:949— Sharpino.Lib/CommandHandler.fs:949-964 | Sharpino.Lib/CommandHandler.fs:3328-3344 | Sharpino.Lib/CommandHandler.fs:3556-3572 | Sharpino.Lib/CommandHandler.fs:3782-3798 | Sharpino.Lib/CommandHandler.fs:4587-4603 | Sharpino.Lib/CommandHandler.fs:4884-4900 | Sharpino.Lib/CommandHandler.fs:5177-5193 — 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.
Duplicated block (15–17 lines × 3) Sharpino.Lib/CommandHandler.fs:2360— Sharpino.Lib/CommandHandler.fs:2360-2375 | Sharpino.Lib/CommandHandler.fs:2408-2422 | Sharpino.Lib/CommandHandler.fs:2452-2468 — 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:2360` 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 (16–17 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2487— Sharpino.Lib/PgBinaryEventStore.fs:2487-2503 | Sharpino.Lib/PgEventStore.fs:2343-2358 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2487` 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–16 lines × 6) Sharpino.Lib/PgBinaryEventStore.fs:1610— Sharpino.Lib/PgBinaryEventStore.fs:1610-1622 | Sharpino.Lib/PgBinaryEventStore.fs:1720-1733 | Sharpino.Lib/PgBinaryEventStore.fs:1831-1844 | Sharpino.Lib/PgEventStore.fs:1587-1601 | Sharpino.Lib/PgEventStore.fs:1704-1719 | Sharpino.Lib/PgEventStore.fs:1822-1837 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1587` 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 × 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.
Duplicated block (4–16 lines × 4) Sharpino.Lib/CommandHandler.fs:5810— Sharpino.Lib/CommandHandler.fs:5810-5825 | Sharpino.Lib/CommandHandler.fs:5868-5883 | Sharpino.Lib/CommandHandler.fs:5894-5897 | Sharpino.Lib/CommandHandler.fs:5969-5972 — 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 (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.
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.
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.
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.
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.
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.
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.
Duplicated block (13–14 lines × 4) Sharpino.Lib/CommandHandler.fs:3518— Sharpino.Lib/CommandHandler.fs:3518-3530 | Sharpino.Lib/CommandHandler.fs:3744-3756 | Sharpino.Lib/CommandHandler.fs:4831-4844 | Sharpino.Lib/CommandHandler.fs:5124-5137 — 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 (14 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:1164— Sharpino.Lib/PgBinaryEventStore.fs:1164-1177 | Sharpino.Lib/PgBinaryEventStore.fs:1594-1607 | Sharpino.Lib/PgEventStore.fs:1138-1151 | Sharpino.Lib/PgEventStore.fs:1571-1584 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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–14 lines × 3) Sharpino.Lib/CommandHandler.fs:1941— Sharpino.Lib/CommandHandler.fs:1941-1952 | Sharpino.Lib/CommandHandler.fs:3123-3136 | Sharpino.Lib/CommandHandler.fs:3196-3208 — 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:1941` 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–14 lines × 3) Sharpino.Lib/CommandHandler.fs:4732— Sharpino.Lib/CommandHandler.fs:4732-4745 | Sharpino.Lib/CommandHandler.fs:5031-5043 | Sharpino.Lib/CommandHandler.fs:5324-5336 — 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–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.
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.
Duplicated block (11–13 lines × 4) Sharpino.Lib/CommandHandler.fs:1067— Sharpino.Lib/CommandHandler.fs:1067-1079 | Sharpino.Lib/CommandHandler.fs:3437-3447 | Sharpino.Lib/CommandHandler.fs:3667-3677 | Sharpino.Lib/CommandHandler.fs:3893-3903 — 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/CommandHandler.fs:4064— Sharpino.Lib/CommandHandler.fs:4064-4075 | Sharpino.Lib/CommandHandler.fs:4212-4223 | Sharpino.Lib/CommandHandler.fs:4361-4372 | Sharpino.Lib/CommandHandler.fs:5546-5558 — 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 (13 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:2254— Sharpino.Lib/PgBinaryEventStore.fs:2254-2266 | Sharpino.Lib/PgBinaryEventStore.fs:2296-2308 | Sharpino.Lib/PgEventStore.fs:2812-2824 | Sharpino.Lib/PgEventStore.fs:2861-2873 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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–13 lines × 3) Sharpino.Lib/MemoryStorage.fs:418— Sharpino.Lib/MemoryStorage.fs:418-430 | Sharpino.Lib/MemoryStorage.fs:443-455 | Sharpino.Lib/MemoryStorage.fs:589-599 — 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–13 lines × 2) Sharpino.Lib/Cache.fs:129— Sharpino.Lib/Cache.fs:129-141 | Sharpino.Lib/Cache.fs:452-456 — both copies are in the same file, so extract the 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 (11–13 lines × 2) Sharpino.Lib/CommandHandler.fs:2597— Sharpino.Lib/CommandHandler.fs:2597-2609 | Sharpino.Lib/CommandHandler.fs:2703-2713 — both copies are in the same file, so extract the 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:2597` 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 × 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.
Duplicated block (12 lines × 6) Sharpino.Lib/CommandHandler.fs:1216— Sharpino.Lib/CommandHandler.fs:1216-1227 | Sharpino.Lib/CommandHandler.fs:1300-1311 | Sharpino.Lib/CommandHandler.fs:1915-1926 | Sharpino.Lib/CommandHandler.fs:1989-2000 | Sharpino.Lib/CommandHandler.fs:2022-2033 | Sharpino.Lib/CommandHandler.fs:2114-2125 — 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.
Duplicated block (11–12 lines × 5) Sharpino.Lib/StateView.fs:1010— Sharpino.Lib/StateView.fs:1010-1020 | Sharpino.Lib/StateView.fs:1050-1061 | Sharpino.Lib/StateView.fs:1092-1102 | Sharpino.Lib/StateView.fs:1161-1171 | Sharpino.Lib/StateView.fs:1220-1231 — 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 (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.
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.
Duplicated block (10–12 lines × 2) Sharpino.Lib/CommandHandler.fs:3483— Sharpino.Lib/CommandHandler.fs:3483-3492 | Sharpino.Lib/CommandHandler.fs:4140-4151 — both copies are in the same file, so extract the 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:3483` 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 (1–12 lines × 5) Sharpino.Lib/CommandHandler.fs:1084— Sharpino.Lib/CommandHandler.fs:1084-1084 | Sharpino.Lib/CommandHandler.fs:4121-4121 | Sharpino.Lib/CommandHandler.fs:4273-4284 | Sharpino.Lib/CommandHandler.fs:4422-4433 | Sharpino.Lib/CommandHandler.fs:5619-5619 — 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.
Duplicated block (8–12 lines × 2) Sharpino.Lib/StateView.fs:933— Sharpino.Lib/StateView.fs:933-944 | Sharpino.Lib/StateView.fs:957-964 — both copies are in the same file, so extract the 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:933` 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 (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.
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.
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.
Duplicated block (8–11 lines × 4) Sharpino.Lib/CommandHandler.fs:3710— Sharpino.Lib/CommandHandler.fs:3710-3718 | Sharpino.Lib/CommandHandler.fs:3936-3943 | Sharpino.Lib/CommandHandler.fs:4291-4300 | Sharpino.Lib/CommandHandler.fs:4440-4450 — 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:3710` 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–11 lines × 4) Sharpino.Lib/CommandHandler.fs:4128— Sharpino.Lib/CommandHandler.fs:4128-4137 | Sharpino.Lib/CommandHandler.fs:4277-4287 | Sharpino.Lib/CommandHandler.fs:4426-4436 | Sharpino.Lib/CommandHandler.fs:5625-5633 — 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 (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.
Duplicated block (10–11 lines × 3) Sharpino.Lib/PgBinaryEventStore.fs:1479— Sharpino.Lib/PgBinaryEventStore.fs:1479-1489 | Sharpino.Lib/PgEventStore.fs:1350-1360 | Sharpino.Lib/PgEventStore.fs:1454-1463 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 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.
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 (9–10 lines × 4) Sharpino.Lib/CommandHandler.fs:4089— Sharpino.Lib/CommandHandler.fs:4089-4098 | Sharpino.Lib/CommandHandler.fs:4237-4246 | Sharpino.Lib/CommandHandler.fs:4386-4395 | Sharpino.Lib/CommandHandler.fs:5583-5591 — 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:5594` calls `fun` and `Sharpino.Lib/CommandHandler.fs:4100` 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–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:2788-2795 — 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:2785` 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–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.
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:989-995 | Sharpino.Lib/PgBinaryEventStore.fs:2033-2040 | Sharpino.Lib/PgBinaryEventStore.fs:2108-2114 | Sharpino.Lib/PgBinaryEventStore.fs:2499-2505 | Sharpino.Lib/PgBinaryEventStore.fs:2779-2785 | Sharpino.Lib/PgEventStore.fs:137-145 | Sharpino.Lib/PgEventStore.fs:457-463 | Sharpino.Lib/PgEventStore.fs:957-963 | Sharpino.Lib/PgEventStore.fs:1967-1973 | Sharpino.Lib/PgEventStore.fs:2086-2092 | Sharpino.Lib/PgEventStore.fs:2161-2167 | Sharpino.Lib/PgEventStore.fs:2354-2360 | Sharpino.Lib/PgEventStore.fs:2602-2608 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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.
Duplicated block (9 lines × 11) Sharpino.Lib/CommandHandler.fs:1155— Sharpino.Lib/CommandHandler.fs:1155-1163 | Sharpino.Lib/CommandHandler.fs:1211-1219 | Sharpino.Lib/CommandHandler.fs:1295-1303 | Sharpino.Lib/CommandHandler.fs:1401-1409 | Sharpino.Lib/CommandHandler.fs:1489-1497 | Sharpino.Lib/CommandHandler.fs:1575-1583 | Sharpino.Lib/CommandHandler.fs:1887-1895 | Sharpino.Lib/CommandHandler.fs:1910-1918 | Sharpino.Lib/CommandHandler.fs:1984-1992 | Sharpino.Lib/CommandHandler.fs:2017-2025 | Sharpino.Lib/CommandHandler.fs:2109-2117 — 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.
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.
Duplicated block (9 lines × 8) Sharpino.Lib/CommandHandler.fs:3282— Sharpino.Lib/CommandHandler.fs:3282-3290 | Sharpino.Lib/CommandHandler.fs:3504-3512 | Sharpino.Lib/CommandHandler.fs:3730-3738 | Sharpino.Lib/CommandHandler.fs:3955-3963 | Sharpino.Lib/CommandHandler.fs:4021-4029 | Sharpino.Lib/CommandHandler.fs:4163-4171 | Sharpino.Lib/CommandHandler.fs:4312-4320 | Sharpino.Lib/CommandHandler.fs:4462-4470 — 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.
Duplicated block (9 lines × 7) Sharpino.Lib/CommandHandler.fs:4535— Sharpino.Lib/CommandHandler.fs:4535-4543 | Sharpino.Lib/CommandHandler.fs:4813-4821 | Sharpino.Lib/CommandHandler.fs:5106-5114 | Sharpino.Lib/CommandHandler.fs:5399-5407 | Sharpino.Lib/CommandHandler.fs:5449-5457 | Sharpino.Lib/CommandHandler.fs:5487-5495 | Sharpino.Lib/CommandHandler.fs:5674-5682 — 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.
Duplicated block (9 lines × 5) Sharpino.Lib/CommandHandler.fs:1664— Sharpino.Lib/CommandHandler.fs:1664-1672 | Sharpino.Lib/CommandHandler.fs:1761-1769 | Sharpino.Lib/CommandHandler.fs:1857-1865 | Sharpino.Lib/CommandHandler.fs:5712-5720 | Sharpino.Lib/CommandHandler.fs:5788-5796 — 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 (8–9 lines × 2) Sharpino.Lib/CommandHandler.fs:850— Sharpino.Lib/CommandHandler.fs:850-858 | Sharpino.Lib/CommandHandler.fs:1051-1058 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 26) Sharpino.Lib/CommandHandler.fs:1648— Sharpino.Lib/CommandHandler.fs:1648-1655 | Sharpino.Lib/CommandHandler.fs:1745-1752 | Sharpino.Lib/CommandHandler.fs:1841-1848 | Sharpino.Lib/CommandHandler.fs:2820-2827 | Sharpino.Lib/CommandHandler.fs:3101-3108 | Sharpino.Lib/CommandHandler.fs:3174-3181 | Sharpino.Lib/CommandHandler.fs:3245-3252 | Sharpino.Lib/CommandHandler.fs:3273-3280 | Sharpino.Lib/CommandHandler.fs:3495-3502 | Sharpino.Lib/CommandHandler.fs:3721-3728 | Sharpino.Lib/CommandHandler.fs:3946-3953 | Sharpino.Lib/CommandHandler.fs:3984-3991 | Sharpino.Lib/CommandHandler.fs:4012-4019 | Sharpino.Lib/CommandHandler.fs:4154-4161 | Sharpino.Lib/CommandHandler.fs:4303-4310 | Sharpino.Lib/CommandHandler.fs:4453-4460 | Sharpino.Lib/CommandHandler.fs:4491-4498 | Sharpino.Lib/CommandHandler.fs:4519-4526 | Sharpino.Lib/CommandHandler.fs:4797-4804 | Sharpino.Lib/CommandHandler.fs:5090-5097 | Sharpino.Lib/CommandHandler.fs:5383-5390 | Sharpino.Lib/CommandHandler.fs:5433-5440 | Sharpino.Lib/CommandHandler.fs:5471-5478 | Sharpino.Lib/CommandHandler.fs:5658-5665 | Sharpino.Lib/CommandHandler.fs:5696-5703 | Sharpino.Lib/CommandHandler.fs:5772-5779 — 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.
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:987-994 | Sharpino.Lib/PgBinaryEventStore.fs:2106-2113 | Sharpino.Lib/PgBinaryEventStore.fs:2254-2261 | Sharpino.Lib/PgBinaryEventStore.fs:2296-2303 | Sharpino.Lib/PgBinaryEventStore.fs:2336-2343 | Sharpino.Lib/PgBinaryEventStore.fs:2497-2504 | Sharpino.Lib/PgBinaryEventStore.fs:2777-2784 | Sharpino.Lib/PgEventStore.fs:135-144 | Sharpino.Lib/PgEventStore.fs:455-462 | Sharpino.Lib/PgEventStore.fs:955-962 | Sharpino.Lib/PgEventStore.fs:1965-1972 | Sharpino.Lib/PgEventStore.fs:2084-2091 | Sharpino.Lib/PgEventStore.fs:2352-2359 | Sharpino.Lib/PgEventStore.fs:2600-2607 | Sharpino.Lib/PgEventStore.fs:2725-2732 | Sharpino.Lib/PgEventStore.fs:2812-2819 | Sharpino.Lib/PgEventStore.fs:2861-2868 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2262` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 13) Sharpino.Lib/CommandHandler.fs:3284— Sharpino.Lib/CommandHandler.fs:3284-3291 | Sharpino.Lib/CommandHandler.fs:3506-3513 | Sharpino.Lib/CommandHandler.fs:3732-3739 | Sharpino.Lib/CommandHandler.fs:3957-3964 | Sharpino.Lib/CommandHandler.fs:4023-4030 | Sharpino.Lib/CommandHandler.fs:4165-4172 | Sharpino.Lib/CommandHandler.fs:4314-4321 | Sharpino.Lib/CommandHandler.fs:4464-4471 | Sharpino.Lib/CommandHandler.fs:4540-4546 | Sharpino.Lib/CommandHandler.fs:4818-4824 | Sharpino.Lib/CommandHandler.fs:5111-5117 | Sharpino.Lib/CommandHandler.fs:5404-5410 | Sharpino.Lib/CommandHandler.fs:5492-5498 — 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.
Duplicated block (8 lines × 12) Sharpino.Lib/CommandHandler.fs:1656— Sharpino.Lib/CommandHandler.fs:1656-1663 | Sharpino.Lib/CommandHandler.fs:1753-1760 | Sharpino.Lib/CommandHandler.fs:1849-1856 | Sharpino.Lib/CommandHandler.fs:4527-4534 | Sharpino.Lib/CommandHandler.fs:4805-4812 | Sharpino.Lib/CommandHandler.fs:5098-5105 | Sharpino.Lib/CommandHandler.fs:5391-5398 | Sharpino.Lib/CommandHandler.fs:5441-5448 | Sharpino.Lib/CommandHandler.fs:5479-5486 | Sharpino.Lib/CommandHandler.fs:5666-5673 | Sharpino.Lib/CommandHandler.fs:5704-5711 | Sharpino.Lib/CommandHandler.fs:5780-5787 — 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 (8 lines × 10) Sharpino.Lib/CommandHandler.fs:3281— Sharpino.Lib/CommandHandler.fs:3281-3288 | Sharpino.Lib/CommandHandler.fs:3503-3510 | Sharpino.Lib/CommandHandler.fs:3729-3736 | Sharpino.Lib/CommandHandler.fs:3954-3961 | Sharpino.Lib/CommandHandler.fs:3992-3999 | Sharpino.Lib/CommandHandler.fs:4020-4027 | Sharpino.Lib/CommandHandler.fs:4162-4169 | Sharpino.Lib/CommandHandler.fs:4311-4318 | Sharpino.Lib/CommandHandler.fs:4461-4468 | Sharpino.Lib/CommandHandler.fs:4499-4506 — 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.
Duplicated block (8 lines × 8) Sharpino.Lib/PgBinaryEventStore.fs:816— Sharpino.Lib/PgBinaryEventStore.fs:816-826 | Sharpino.Lib/PgBinaryEventStore.fs:916-926 | Sharpino.Lib/PgBinaryEventStore.fs:2678-2689 | Sharpino.Lib/PgBinaryEventStore.fs:3300-3307 | Sharpino.Lib/PgEventStore.fs:635-645 | Sharpino.Lib/PgEventStore.fs:738-748 | Sharpino.Lib/PgEventStore.fs:2507-2518 | Sharpino.Lib/PgEventStore.fs:3330-3337 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 × 6) Sharpino.Sample.22/Domain/Todo/Events.fs:20— Sharpino.Sample.22/Domain/Todo/Events.fs:20-27 | Sharpino.Sample.24/Domain/Todo/Events.fs:20-27 | Sharpino.Sample.25/Models/Todo/Events.fs:20-27 | Sharpino.Sample.26/Domain/Todo/Events.fs:20-27 | Sharpino.Sample.27/Domain/Todo/Events.fs:20-27 | Sharpino.Sample.28/Domain/Todo/Events.fs:20-27 — 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 (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.
Duplicated block (7 lines × 20) Sharpino.Lib/PgBinaryEventStore.fs:353— Sharpino.Lib/PgBinaryEventStore.fs:353-359 | Sharpino.Lib/PgBinaryEventStore.fs:662-669 | Sharpino.Lib/PgBinaryEventStore.fs:732-739 | Sharpino.Lib/PgBinaryEventStore.fs:815-825 | Sharpino.Lib/PgBinaryEventStore.fs:915-925 | Sharpino.Lib/PgBinaryEventStore.fs:1701-1714 | Sharpino.Lib/PgBinaryEventStore.fs:1815-1825 | Sharpino.Lib/PgBinaryEventStore.fs:2678-2688 | Sharpino.Lib/PgBinaryEventStore.fs:2968-2975 | Sharpino.Lib/PgBinaryEventStore.fs:3300-3306 | Sharpino.Lib/PgEventStore.fs:366-372 | Sharpino.Lib/PgEventStore.fs:634-644 | Sharpino.Lib/PgEventStore.fs:737-747 | Sharpino.Lib/PgEventStore.fs:822-829 | Sharpino.Lib/PgEventStore.fs:893-900 | Sharpino.Lib/PgEventStore.fs:1685-1698 | Sharpino.Lib/PgEventStore.fs:1806-1816 | Sharpino.Lib/PgEventStore.fs:2507-2516 | Sharpino.Lib/PgEventStore.fs:2994-3001 | Sharpino.Lib/PgEventStore.fs:3330-3336 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:740` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:670` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 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:988-994 | Sharpino.Lib/PgBinaryEventStore.fs:2032-2039 | Sharpino.Lib/PgBinaryEventStore.fs:2107-2113 | Sharpino.Lib/PgBinaryEventStore.fs:2337-2343 | Sharpino.Lib/PgBinaryEventStore.fs:2498-2504 | Sharpino.Lib/PgBinaryEventStore.fs:2778-2784 | Sharpino.Lib/PgEventStore.fs:136-144 | Sharpino.Lib/PgEventStore.fs:456-462 | Sharpino.Lib/PgEventStore.fs:956-962 | Sharpino.Lib/PgEventStore.fs:1966-1972 | Sharpino.Lib/PgEventStore.fs:2085-2091 | Sharpino.Lib/PgEventStore.fs:2160-2166 | Sharpino.Lib/PgEventStore.fs:2353-2359 | Sharpino.Lib/PgEventStore.fs:2601-2607 | Sharpino.Lib/PgEventStore.fs:2726-2732 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2787` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 5) Sharpino.Lib/CommandHandler.fs:2492— Sharpino.Lib/CommandHandler.fs:2492-2498 | Sharpino.Lib/CommandHandler.fs:2611-2617 | Sharpino.Lib/CommandHandler.fs:2629-2635 | Sharpino.Lib/CommandHandler.fs:2715-2721 | Sharpino.Lib/CommandHandler.fs:2802-2808 — 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 (5–7 lines × 5) Sharpino.Lib/PgBinaryEventStore.fs:2263— Sharpino.Lib/PgBinaryEventStore.fs:2263-2267 | Sharpino.Lib/PgBinaryEventStore.fs:2305-2309 | Sharpino.Lib/PgBinaryEventStore.fs:2347-2351 | Sharpino.Lib/PgEventStore.fs:2736-2740 | Sharpino.Lib/PgEventStore.fs:2821-2827 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:2344` calls `AddWithValue` and `Sharpino.Lib/PgBinaryEventStore.fs:2261` 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–7 lines × 4) Sharpino.Lib/CommandHandler.fs:3995— Sharpino.Lib/CommandHandler.fs:3995-4001 | Sharpino.Lib/CommandHandler.fs:4502-4508 | Sharpino.Lib/CommandHandler.fs:5454-5459 | Sharpino.Lib/CommandHandler.fs:5679-5684 — 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 (6–7 lines × 2) Sharpino.Lib/CommandHandler.fs:98— Sharpino.Lib/CommandHandler.fs:98-104 | Sharpino.Sample.9/Commons.fs:54-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (4–7 lines × 3) Sharpino.Lib/CommandHandler.fs:743— Sharpino.Lib/CommandHandler.fs:743-746 | Sharpino.Lib/CommandHandler.fs:3141-3147 | Sharpino.Lib/CommandHandler.fs:3213-3219 — 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:743` 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 (2–7 lines × 9) Sharpino.Lib/CommandHandler.fs:1459— Sharpino.Lib/CommandHandler.fs:1459-1460 | Sharpino.Lib/CommandHandler.fs:1548-1549 | Sharpino.Lib/CommandHandler.fs:2573-2574 | Sharpino.Lib/CommandHandler.fs:2677-2678 | Sharpino.Lib/CommandHandler.fs:2769-2770 | Sharpino.Lib/CommandHandler.fs:4112-4115 | Sharpino.Lib/CommandHandler.fs:4261-4267 | Sharpino.Lib/CommandHandler.fs:4410-4416 | Sharpino.Lib/CommandHandler.fs:5614-5615 — 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.
Duplicated block (3–7 lines × 4) Sharpino.Lib/StateView.fs:857— Sharpino.Lib/StateView.fs:857-860 | Sharpino.Lib/StateView.fs:967-969 | Sharpino.Lib/StateView.fs:1027-1033 | Sharpino.Lib/StateView.fs:1196-1202 — 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:1027` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 7) Sharpino.Lib/CommandHandler.fs:4136— Sharpino.Lib/CommandHandler.fs:4136-4141 | Sharpino.Lib/CommandHandler.fs:4286-4291 | Sharpino.Lib/CommandHandler.fs:4435-4440 | Sharpino.Lib/CommandHandler.fs:4776-4781 | Sharpino.Lib/CommandHandler.fs:5069-5074 | Sharpino.Lib/CommandHandler.fs:5362-5367 | Sharpino.Lib/CommandHandler.fs:5637-5642 — 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.
Duplicated block (6 lines × 6) Sharpino.Lib/CommandHandler.fs:601— Sharpino.Lib/CommandHandler.fs:601-606 | Sharpino.Lib/CommandHandler.fs:1160-1165 | Sharpino.Lib/CommandHandler.fs:1406-1411 | Sharpino.Lib/CommandHandler.fs:1494-1499 | Sharpino.Lib/CommandHandler.fs:1580-1585 | Sharpino.Lib/CommandHandler.fs:1892-1897 — 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.
Duplicated block (5–6 lines × 4) Sharpino.Lib/StateView.fs:970— Sharpino.Lib/StateView.fs:970-974 | Sharpino.Lib/StateView.fs:1076-1081 | Sharpino.Lib/StateView.fs:1145-1150 | Sharpino.Lib/StateView.fs:1203-1208 — 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 (5 lines × 43) Sharpino.Lib/CommandHandler.fs:592— Sharpino.Lib/CommandHandler.fs:592-596 | Sharpino.Lib/CommandHandler.fs:1154-1158 | Sharpino.Lib/CommandHandler.fs:1210-1214 | Sharpino.Lib/CommandHandler.fs:1294-1298 | Sharpino.Lib/CommandHandler.fs:1400-1404 | Sharpino.Lib/CommandHandler.fs:1488-1492 | Sharpino.Lib/CommandHandler.fs:1574-1578 | Sharpino.Lib/CommandHandler.fs:1643-1647 | Sharpino.Lib/CommandHandler.fs:1740-1744 | Sharpino.Lib/CommandHandler.fs:1836-1840 | Sharpino.Lib/CommandHandler.fs:1886-1890 | Sharpino.Lib/CommandHandler.fs:1909-1913 | Sharpino.Lib/CommandHandler.fs:1983-1987 | Sharpino.Lib/CommandHandler.fs:2016-2020 | Sharpino.Lib/CommandHandler.fs:2108-2112 | Sharpino.Lib/CommandHandler.fs:2487-2491 | Sharpino.Lib/CommandHandler.fs:2606-2610 | Sharpino.Lib/CommandHandler.fs:2624-2628 | Sharpino.Lib/CommandHandler.fs:2710-2714 | Sharpino.Lib/CommandHandler.fs:2797-2801 | Sharpino.Lib/CommandHandler.fs:2815-2819 | Sharpino.Lib/CommandHandler.fs:3096-3100 | Sharpino.Lib/CommandHandler.fs:3169-3173 | Sharpino.Lib/CommandHandler.fs:3240-3244 | Sharpino.Lib/CommandHandler.fs:3268-3272 | Sharpino.Lib/CommandHandler.fs:3490-3494 | Sharpino.Lib/CommandHandler.fs:3716-3720 | Sharpino.Lib/CommandHandler.fs:3941-3945 | Sharpino.Lib/CommandHandler.fs:3979-3983 | Sharpino.Lib/CommandHandler.fs:4007-4011 | Sharpino.Lib/CommandHandler.fs:4149-4153 | Sharpino.Lib/CommandHandler.fs:4298-4302 | Sharpino.Lib/CommandHandler.fs:4448-4452 | Sharpino.Lib/CommandHandler.fs:4486-4490 | Sharpino.Lib/CommandHandler.fs:4514-4518 | Sharpino.Lib/CommandHandler.fs:4792-4796 | Sharpino.Lib/CommandHandler.fs:5085-5089 | Sharpino.Lib/CommandHandler.fs:5378-5382 | Sharpino.Lib/CommandHandler.fs:5428-5432 | Sharpino.Lib/CommandHandler.fs:5466-5470 | Sharpino.Lib/CommandHandler.fs:5653-5657 | Sharpino.Lib/CommandHandler.fs:5691-5695 | Sharpino.Lib/CommandHandler.fs:5767-5771 — 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:592` 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:1737` calls `command` and `Sharpino.Lib/CommandHandler.fs:5764` 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 × 32) Sharpino.Lib/CommandHandler.fs:1218— Sharpino.Lib/CommandHandler.fs:1218-1222 | Sharpino.Lib/CommandHandler.fs:1302-1306 | Sharpino.Lib/CommandHandler.fs:1651-1655 | Sharpino.Lib/CommandHandler.fs:1748-1752 | Sharpino.Lib/CommandHandler.fs:1844-1848 | Sharpino.Lib/CommandHandler.fs:1917-1921 | Sharpino.Lib/CommandHandler.fs:1991-1995 | Sharpino.Lib/CommandHandler.fs:2024-2028 | Sharpino.Lib/CommandHandler.fs:2116-2120 | Sharpino.Lib/CommandHandler.fs:2823-2827 | Sharpino.Lib/CommandHandler.fs:3104-3108 | Sharpino.Lib/CommandHandler.fs:3177-3181 | Sharpino.Lib/CommandHandler.fs:3248-3252 | Sharpino.Lib/CommandHandler.fs:3276-3280 | Sharpino.Lib/CommandHandler.fs:3498-3502 | Sharpino.Lib/CommandHandler.fs:3724-3728 | Sharpino.Lib/CommandHandler.fs:3949-3953 | Sharpino.Lib/CommandHandler.fs:3987-3991 | Sharpino.Lib/CommandHandler.fs:4015-4019 | Sharpino.Lib/CommandHandler.fs:4157-4161 | Sharpino.Lib/CommandHandler.fs:4306-4310 | Sharpino.Lib/CommandHandler.fs:4456-4460 | Sharpino.Lib/CommandHandler.fs:4494-4498 | Sharpino.Lib/CommandHandler.fs:4522-4526 | Sharpino.Lib/CommandHandler.fs:4800-4804 | Sharpino.Lib/CommandHandler.fs:5093-5097 | Sharpino.Lib/CommandHandler.fs:5386-5390 | Sharpino.Lib/CommandHandler.fs:5436-5440 | Sharpino.Lib/CommandHandler.fs:5474-5478 | Sharpino.Lib/CommandHandler.fs:5661-5665 | Sharpino.Lib/CommandHandler.fs:5699-5703 | Sharpino.Lib/CommandHandler.fs:5775-5779 — 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.
Duplicated block (5 lines × 15) Sharpino.Lib/CommandHandler.fs:1310— Sharpino.Lib/CommandHandler.fs:1310-1314 | Sharpino.Lib/CommandHandler.fs:1659-1663 | Sharpino.Lib/CommandHandler.fs:1756-1760 | Sharpino.Lib/CommandHandler.fs:1852-1856 | Sharpino.Lib/CommandHandler.fs:2032-2036 | Sharpino.Lib/CommandHandler.fs:2124-2128 | Sharpino.Lib/CommandHandler.fs:4530-4534 | Sharpino.Lib/CommandHandler.fs:4808-4812 | Sharpino.Lib/CommandHandler.fs:5101-5105 | Sharpino.Lib/CommandHandler.fs:5394-5398 | Sharpino.Lib/CommandHandler.fs:5444-5448 | Sharpino.Lib/CommandHandler.fs:5482-5486 | Sharpino.Lib/CommandHandler.fs:5669-5673 | Sharpino.Lib/CommandHandler.fs:5707-5711 | Sharpino.Lib/CommandHandler.fs:5783-5787 — 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.
Duplicated block (1–5 lines × 4) Sharpino.Lib/CommandHandler.fs:1392— Sharpino.Lib/CommandHandler.fs:1392-1396 | Sharpino.Lib/CommandHandler.fs:1732-1737 | Sharpino.Lib/CommandHandler.fs:1829-1834 | Sharpino.Lib/CommandHandler.fs:2101-2101 — 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:1392` 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:2101` calls `events3` and `Sharpino.Lib/CommandHandler.fs:1737` 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 (4–5 lines × 3) Sharpino.Lib/CommandHandler.fs:84— Sharpino.Lib/CommandHandler.fs:84-88 | Sharpino.Lib/CommandHandler.fs:132-136 | Sharpino.Lib/CommandHandler.fs:185-188 — 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.
Duplicated block (1–5 lines × 6) Sharpino.Lib/CommandHandler.fs:1287— Sharpino.Lib/CommandHandler.fs:1287-1291 | Sharpino.Lib/CommandHandler.fs:1391-1391 | Sharpino.Lib/CommandHandler.fs:1731-1731 | Sharpino.Lib/CommandHandler.fs:1828-1828 | Sharpino.Lib/CommandHandler.fs:1976-1980 | Sharpino.Lib/CommandHandler.fs:2100-2100 — 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:1287` 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:1386` calls `newState3` and `Sharpino.Lib/CommandHandler.fs:1282` 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 (2–5 lines × 4) Sharpino.Lib/CommandHandler.fs:1377— Sharpino.Lib/CommandHandler.fs:1377-1378 | Sharpino.Lib/CommandHandler.fs:1717-1721 | Sharpino.Lib/CommandHandler.fs:1814-1818 | Sharpino.Lib/CommandHandler.fs:2084-2085 — 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:1380` calls `Memoize2` and `Sharpino.Lib/CommandHandler.fs:1724` 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 (3–5 lines × 3) Sharpino.Lib/MemoryStorage.fs:946— Sharpino.Lib/MemoryStorage.fs:946-950 | Sharpino.Lib/MemoryStorage.fs:968-972 | Sharpino.Lib/MemoryStorage.fs:1001-1003 — 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:972` calls `collect` and `Sharpino.Lib/MemoryStorage.fs:1003` 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 (34 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1644— Sharpino.Lib/PgBinaryEventStore.fs:1644-1677 | Sharpino.Lib/PgEventStore.fs:1626-1659 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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 × 8) Sharpino.Lib/PgBinaryEventStore.fs:1735— Sharpino.Lib/PgBinaryEventStore.fs:1735-1750 | Sharpino.Lib/PgBinaryEventStore.fs:1846-1861 | Sharpino.Lib/PgBinaryEventStore.fs:2698-2713 | Sharpino.Lib/PgBinaryEventStore.fs:2848-2863 | Sharpino.Lib/PgEventStore.fs:1721-1742 | Sharpino.Lib/PgEventStore.fs:1839-1860 | Sharpino.Lib/PgEventStore.fs:2527-2542 | Sharpino.Lib/PgEventStore.fs:2670-2685 — before extracting anything, compare `Sharpino.Lib/PgBinaryEventStore.fs` and `Sharpino.Lib/PgEventStore.fs` as WHOLE FILES: this scan already matched 103 separate duplicated blocks between them, totalling at least 2355 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:1735` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 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.
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.
End-of-life runtime: .NET net9.0 REDACTED:5— REDACTED declares .NET net9.0 as this project's target framework, and .NET 9 STS, support ended 2026-05-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-05-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Coverage not measured — no coverage collector is wired up — 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.
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.
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.
README/code drift Sharpino.Sample.22/Readme.md:37— Sharpino.Sample.22/Readme.md documents the environment variable `DATABASE_URL`, but no code, script or configuration file names it. 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.Sample.25/README.md:14— Sharpino.Sample.25/README.md documents the environment variable `DATABASE_URL`, but no code, script or configuration file names it. 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.
Documentation: no project overview Sharpino.Sample/README.md— The README begins with a deprecation notice ('This example demonstrates an older approach that is being deprecated') but does not state what the sample itself does or its project scope beyond the single-line 'Todo application built with Sharpino'. State what the sample Todo app does (managing todos, categories, tags) and why it is a sample rather than production code.
Scattered collaborators — 96 % of calls cross a namespace and only 0 % 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
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.
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'.
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.
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.
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.)
Duplicated predicate Sharpino.Lib/PgBinaryEventStore.fs:1230— `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.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a164bc-f8ee-723e-92ac-1c694d8b717b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 27 · Warnings: 530 · Recommendations: 25 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 17:51 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.