Public report of jet/dotnet-templates, 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:13 UTC · Survey ID cd_37fa29948d4943039da2fba276b2e3e4
jet/dotnet-templates
Measured 22 October 2026, 17:09 UTC, at code version 9a44cd9
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 7 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 small codebase: 11,476 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Maturity, 36
Findings by how serious they are
11 critical199 serious147 minor
2 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:09 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.
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 ▸
70of 76 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
321of 357 findings point to an exact file and line, so you can open each one in the code. The other 36 concern the repository as a whole, such as missing documentation.
76dimensions across 7 lenses, read from 11,476 lines of product code in 2 projects.
jet/dotnet-templates scores 52 out of 100 and is rated Adequate, while six of its seven lenses score higher still: Domain Modelling at 87 and Production Readiness at 85, both rated Exemplary, Architecture at 81, Code Health at 62 and Security and Compliance at 60, all rated Adequate, and Performance at 70, rated Strong. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.
The score is lower than those six because the weakest lens counts most, and here that is Maturity, which scores 36 and is rated Adequate. Its Knowledge Freshness dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 91 Orphaned file finding(s) in Knowledge Freshness and to reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists; README.md names the project `Equinox.EventStore`, but no project, folder or namespace of that name exists; README.md links to `propulsion-archiver/README.md`, but `propulsion-archiver/README.md` does not exist; README.md links to `propulsion-pruner/README.md`, but `propulsion-pruner/README.md` does not exist, and if Maturity rose to 70, the score would rise from 52 to about 65.
11 findings are critical: seven in Domain ↔ infrastructure boundary, three in Dependency Vulnerabilities and one in Secret Scanning.
The product code is 11,476 lines, which would take an estimated 0.1 person-years, around €16,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: 1 finding
This critical or serious finding was in the previous survey, on 8 October 2026, and is gone from this one.
Coupling · Off the main sequence: Domain
Rebuild cost: about €16,000 · Estimate
Cost to rebuild
€5,200 to €26,000, for 86 to 273 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem
High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 52. 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
Small: 11,476 lines of product code
Comment lines
The estimate prices 11,399 lines. Comment lines count towards the size of 11,476 lines but aren't priced as work.
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.
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 91 Orphaned file finding(s) in Knowledge Freshness — start with Infrastructure.fs (15), Program.fs (13), Store.fs (4).
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists; README.md names the project `Equinox.EventStore`, but no project, folder or namespace of that name exists; README.md links to `propulsion-archiver/README.md`, but `propulsion-archiver/README.md` does not exist; README.md links to `propulsion-pruner/README.md`, but `propulsion-pruner/README.md` does not exist.
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.
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 €16,000 to build again, about 0.1 person-years of work. Its weakest lens is Maturity, at 36 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 91 Orphaned file finding(s) in Knowledge Freshness. Of all the actions in this report, it raises the score most for the work it takes: about 14 points for medium effort, because it clears the 91 Knowledge Freshness findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
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.
460 modules, with 347 dependencies between them. 10 loops run through 21 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 420 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.
ConsumerTemplate.TodoSummary uses ConsumerTemplate.TodoSummary.Events, so a change to ConsumerTemplate.TodoSummary.Events can break ConsumerTemplate.TodoSummary, while a change to ConsumerTemplate.TodoSummary can't break ConsumerTemplate.TodoSummary.Events.
Position
Below the diagonal: ConsumerTemplate.TodoSummary uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Domain.GroupCheckout uses a type in (global).
The types involved
Domain.GroupCheckout.GroupCheckout → CategoryId`1
Direction
Domain.GroupCheckout uses (global), so a change to (global) can break Domain.GroupCheckout, while a change to Domain.GroupCheckout can't break (global).
Position
Below the diagonal: Domain.GroupCheckout uses a module listed above it, which is the healthy direction.
Domain.GuestStay.Factory uses Domain.Store, so a change to Domain.Store can break Domain.GuestStay.Factory, while a change to Domain.GuestStay.Factory can't break Domain.Store.
Position
Below the diagonal: Domain.GuestStay.Factory uses a module listed above it, which is the healthy direction.
FeedSourceTemplate.Domain.TicketsIngester uses FeedSourceTemplate.Domain.Store, so a change to FeedSourceTemplate.Domain.Store can break FeedSourceTemplate.Domain.TicketsIngester, while a change to FeedSourceTemplate.Domain.TicketsIngester can't break FeedSourceTemplate.Domain.Store.
Position
Below the diagonal: FeedSourceTemplate.Domain.TicketsIngester uses a module listed above it, which is the healthy direction.
FeedSourceTemplate.Domain.TicketsIngester uses FeedSourceTemplate.Domain.TicketsEpoch.Events, so a change to FeedSourceTemplate.Domain.TicketsEpoch.Events can break FeedSourceTemplate.Domain.TicketsIngester, while a change to FeedSourceTemplate.Domain.TicketsIngester can't break FeedSourceTemplate.Domain.TicketsEpoch.Events.
Position
Below the diagonal: FeedSourceTemplate.Domain.TicketsIngester uses a module listed above it, which is the healthy direction.
FeedSourceTemplate.Domain.TicketsIngester uses FeedSourceTemplate.Domain.TicketsSeries, so a change to FeedSourceTemplate.Domain.TicketsSeries can break FeedSourceTemplate.Domain.TicketsIngester, while a change to FeedSourceTemplate.Domain.TicketsIngester can't break FeedSourceTemplate.Domain.TicketsSeries.
Position
Below the diagonal: FeedSourceTemplate.Domain.TicketsIngester uses a module listed above it, which is the healthy direction.
Reactor.Integration uses Domain.Store, so a change to Domain.Store can break Reactor.Integration, while a change to Reactor.Integration can't break Domain.Store.
Position
Below the diagonal: Reactor.Integration uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs uses ReactorTemplate.Args.Cosmos, so a change to ReactorTemplate.Args.Cosmos can break ReactorTemplate.SourceArgs, while a change to ReactorTemplate.SourceArgs can't break ReactorTemplate.Args.Cosmos.
Position
Below the diagonal: ReactorTemplate.SourceArgs uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs uses ReactorTemplate.Args.Dynamo, so a change to ReactorTemplate.Args.Dynamo can break ReactorTemplate.SourceArgs, while a change to ReactorTemplate.SourceArgs can't break ReactorTemplate.Args.Dynamo.
Position
Below the diagonal: ReactorTemplate.SourceArgs uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.SourceArgs uses Args, so a change to Args can break Shipping.Watchdog.SourceArgs, while a change to Shipping.Watchdog.SourceArgs can't break Args.
Position
Below the diagonal: Shipping.Watchdog.SourceArgs uses a module listed above it, which is the healthy direction.
ConsumerTemplate.TodoSummary.Factory uses ConsumerTemplate.TodoSummary.Events, so a change to ConsumerTemplate.TodoSummary.Events can break ConsumerTemplate.TodoSummary.Factory, while a change to ConsumerTemplate.TodoSummary.Factory can't break ConsumerTemplate.TodoSummary.Events.
Position
Below the diagonal: ConsumerTemplate.TodoSummary.Factory uses a module listed above it, which is the healthy direction.
ConsumerTemplate.TodoSummary.Factory uses ConsumerTemplate.TodoSummary, so a change to ConsumerTemplate.TodoSummary can break ConsumerTemplate.TodoSummary.Factory, while a change to ConsumerTemplate.TodoSummary.Factory can't break ConsumerTemplate.TodoSummary.
Position
Below the diagonal: ConsumerTemplate.TodoSummary.Factory uses a module listed above it, which is the healthy direction.
Domain.GroupCheckout.Factory uses Domain.GroupCheckout.Fold, so a change to Domain.GroupCheckout.Fold can break Domain.GroupCheckout.Factory, while a change to Domain.GroupCheckout.Factory can't break Domain.GroupCheckout.Fold.
Position
Below the diagonal: Domain.GroupCheckout.Factory uses a module listed above it, which is the healthy direction.
Domain.GroupCheckout.Factory uses Domain.Store, so a change to Domain.Store can break Domain.GroupCheckout.Factory, while a change to Domain.GroupCheckout.Factory can't break Domain.Store.
Position
Below the diagonal: Domain.GroupCheckout.Factory uses a module listed above it, which is the healthy direction.
Domain.GroupCheckout.Factory uses Domain.GroupCheckout, so a change to Domain.GroupCheckout can break Domain.GroupCheckout.Factory, while a change to Domain.GroupCheckout.Factory can't break Domain.GroupCheckout.
Position
Below the diagonal: Domain.GroupCheckout.Factory uses a module listed above it, which is the healthy direction.
FeedSourceTemplate.Controllers uses FeedSourceTemplate.Domain.TicketsSeries, so a change to FeedSourceTemplate.Domain.TicketsSeries can break FeedSourceTemplate.Controllers, while a change to FeedSourceTemplate.Controllers can't break FeedSourceTemplate.Domain.TicketsSeries.
Position
Below the diagonal: FeedSourceTemplate.Controllers uses a module listed above it, which is the healthy direction.
FeedSourceTemplate.Controllers uses FeedSourceTemplate.Domain.TicketsIngester, so a change to FeedSourceTemplate.Domain.TicketsIngester can break FeedSourceTemplate.Controllers, while a change to FeedSourceTemplate.Controllers can't break FeedSourceTemplate.Domain.TicketsIngester.
Position
Below the diagonal: FeedSourceTemplate.Controllers uses a module listed above it, which is the healthy direction.
Reactor.Integration.ReactorIntegrationTests uses Domain.Store, so a change to Domain.Store can break Reactor.Integration.ReactorIntegrationTests, while a change to Reactor.Integration.ReactorIntegrationTests can't break Domain.Store.
Position
Below the diagonal: Reactor.Integration.ReactorIntegrationTests uses a module listed above it, which is the healthy direction.
Reactor.Integration.ReactorIntegrationTests uses Reactor.Integration, so a change to Reactor.Integration can break Reactor.Integration.ReactorIntegrationTests, while a change to Reactor.Integration.ReactorIntegrationTests can't break Reactor.Integration.
Position
Below the diagonal: Reactor.Integration.ReactorIntegrationTests uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Cosmos uses ReactorTemplate.Args.Cosmos, so a change to ReactorTemplate.Args.Cosmos can break ReactorTemplate.SourceArgs.Cosmos, while a change to ReactorTemplate.SourceArgs.Cosmos can't break ReactorTemplate.Args.Cosmos.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Cosmos uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Cosmos uses ReactorTemplate.Args.Dynamo, so a change to ReactorTemplate.Args.Dynamo can break ReactorTemplate.SourceArgs.Cosmos, while a change to ReactorTemplate.SourceArgs.Cosmos can't break ReactorTemplate.Args.Dynamo.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Cosmos uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Cosmos uses ReactorTemplate.Store, so a change to ReactorTemplate.Store can break ReactorTemplate.SourceArgs.Cosmos, while a change to ReactorTemplate.SourceArgs.Cosmos can't break ReactorTemplate.Store.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Cosmos uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Cosmos uses ReactorTemplate.SourceArgs, so a change to ReactorTemplate.SourceArgs can break ReactorTemplate.SourceArgs.Cosmos, while a change to ReactorTemplate.SourceArgs.Cosmos can't break ReactorTemplate.SourceArgs.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Cosmos uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Dynamo uses ReactorTemplate.Args.Cosmos, so a change to ReactorTemplate.Args.Cosmos can break ReactorTemplate.SourceArgs.Dynamo, while a change to ReactorTemplate.SourceArgs.Dynamo can't break ReactorTemplate.Args.Cosmos.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Dynamo uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Dynamo uses ReactorTemplate.Args.Dynamo, so a change to ReactorTemplate.Args.Dynamo can break ReactorTemplate.SourceArgs.Dynamo, while a change to ReactorTemplate.SourceArgs.Dynamo can't break ReactorTemplate.Args.Dynamo.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Dynamo uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Dynamo uses ReactorTemplate.Store, so a change to ReactorTemplate.Store can break ReactorTemplate.SourceArgs.Dynamo, while a change to ReactorTemplate.SourceArgs.Dynamo can't break ReactorTemplate.Store.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Dynamo uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Dynamo uses ReactorTemplate.SourceArgs, so a change to ReactorTemplate.SourceArgs can break ReactorTemplate.SourceArgs.Dynamo, while a change to ReactorTemplate.SourceArgs.Dynamo can't break ReactorTemplate.SourceArgs.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Dynamo uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Esdb uses ReactorTemplate.Args.Cosmos, so a change to ReactorTemplate.Args.Cosmos can break ReactorTemplate.SourceArgs.Esdb, while a change to ReactorTemplate.SourceArgs.Esdb can't break ReactorTemplate.Args.Cosmos.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Esdb uses ReactorTemplate.Args.Dynamo, so a change to ReactorTemplate.Args.Dynamo can break ReactorTemplate.SourceArgs.Esdb, while a change to ReactorTemplate.SourceArgs.Esdb can't break ReactorTemplate.Args.Dynamo.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Esdb uses ReactorTemplate.Store, so a change to ReactorTemplate.Store can break ReactorTemplate.SourceArgs.Esdb, while a change to ReactorTemplate.SourceArgs.Esdb can't break ReactorTemplate.Store.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Esdb uses ReactorTemplate.SourceArgs, so a change to ReactorTemplate.SourceArgs can break ReactorTemplate.SourceArgs.Esdb, while a change to ReactorTemplate.SourceArgs.Esdb can't break ReactorTemplate.SourceArgs.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Sss uses ReactorTemplate.Args.Cosmos, so a change to ReactorTemplate.Args.Cosmos can break ReactorTemplate.SourceArgs.Sss, while a change to ReactorTemplate.SourceArgs.Sss can't break ReactorTemplate.Args.Cosmos.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Sss uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Sss uses ReactorTemplate.Args.Dynamo, so a change to ReactorTemplate.Args.Dynamo can break ReactorTemplate.SourceArgs.Sss, while a change to ReactorTemplate.SourceArgs.Sss can't break ReactorTemplate.Args.Dynamo.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Sss uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Sss uses ReactorTemplate.Store, so a change to ReactorTemplate.Store can break ReactorTemplate.SourceArgs.Sss, while a change to ReactorTemplate.SourceArgs.Sss can't break ReactorTemplate.Store.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Sss uses a module listed above it, which is the healthy direction.
ReactorTemplate.SourceArgs.Sss uses ReactorTemplate.SourceArgs, so a change to ReactorTemplate.SourceArgs can break ReactorTemplate.SourceArgs.Sss, while a change to ReactorTemplate.SourceArgs.Sss can't break ReactorTemplate.SourceArgs.
Position
Below the diagonal: ReactorTemplate.SourceArgs.Sss uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Integration uses Shipping.Domain.FinalizationProcess, so a change to Shipping.Domain.FinalizationProcess can break Shipping.Watchdog.Integration, while a change to Shipping.Watchdog.Integration can't break Shipping.Domain.FinalizationProcess.
Position
Below the diagonal: Shipping.Watchdog.Integration uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Integration uses Store, so a change to Store can break Shipping.Watchdog.Integration, while a change to Shipping.Watchdog.Integration can't break Store.
Position
Below the diagonal: Shipping.Watchdog.Integration uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Integration uses Shipping.Watchdog.SourceArgs, so a change to Shipping.Watchdog.SourceArgs can break Shipping.Watchdog.Integration, while a change to Shipping.Watchdog.Integration can't break Shipping.Watchdog.SourceArgs.
Position
Below the diagonal: Shipping.Watchdog.Integration uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.SourceArgs.Esdb uses Args, so a change to Args can break Shipping.Watchdog.SourceArgs.Esdb, while a change to Shipping.Watchdog.SourceArgs.Esdb can't break Args.
Position
Below the diagonal: Shipping.Watchdog.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.SourceArgs.Esdb uses Store, so a change to Store can break Shipping.Watchdog.SourceArgs.Esdb, while a change to Shipping.Watchdog.SourceArgs.Esdb can't break Store.
Position
Below the diagonal: Shipping.Watchdog.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.SourceArgs.Esdb uses Shipping.Watchdog.SourceArgs, so a change to Shipping.Watchdog.SourceArgs can break Shipping.Watchdog.SourceArgs.Esdb, while a change to Shipping.Watchdog.SourceArgs.Esdb can't break Shipping.Watchdog.SourceArgs.
Position
Below the diagonal: Shipping.Watchdog.SourceArgs.Esdb uses a module listed above it, which is the healthy direction.
ReactorTemplate.Program.Args uses ReactorTemplate.SourceArgs.Cosmos, so a change to ReactorTemplate.SourceArgs.Cosmos can break ReactorTemplate.Program.Args, while a change to ReactorTemplate.Program.Args can't break ReactorTemplate.SourceArgs.Cosmos.
Position
Below the diagonal: ReactorTemplate.Program.Args uses a module listed above it, which is the healthy direction.
ReactorTemplate.Program.Args uses ReactorTemplate.SourceArgs.Dynamo, so a change to ReactorTemplate.SourceArgs.Dynamo can break ReactorTemplate.Program.Args, while a change to ReactorTemplate.Program.Args can't break ReactorTemplate.SourceArgs.Dynamo.
Position
Below the diagonal: ReactorTemplate.Program.Args uses a module listed above it, which is the healthy direction.
ReactorTemplate.Program.Args uses ReactorTemplate.SourceArgs.Esdb, so a change to ReactorTemplate.SourceArgs.Esdb can break ReactorTemplate.Program.Args, while a change to ReactorTemplate.Program.Args can't break ReactorTemplate.SourceArgs.Esdb.
Position
Below the diagonal: ReactorTemplate.Program.Args uses a module listed above it, which is the healthy direction.
ReactorTemplate.Program.Args uses ReactorTemplate.SourceArgs.Sss, so a change to ReactorTemplate.SourceArgs.Sss can break ReactorTemplate.Program.Args, while a change to ReactorTemplate.Program.Args can't break ReactorTemplate.SourceArgs.Sss.
Position
Below the diagonal: ReactorTemplate.Program.Args uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Integration.WatchdogIntegrationTests uses Shipping.Domain.FinalizationProcess, so a change to Shipping.Domain.FinalizationProcess can break Shipping.Watchdog.Integration.WatchdogIntegrationTests, while a change to Shipping.Watchdog.Integration.WatchdogIntegrationTests can't break Shipping.Domain.FinalizationProcess.
Position
Below the diagonal: Shipping.Watchdog.Integration.WatchdogIntegrationTests uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Integration.WatchdogIntegrationTests uses Shipping.Watchdog.Integration, so a change to Shipping.Watchdog.Integration can break Shipping.Watchdog.Integration.WatchdogIntegrationTests, while a change to Shipping.Watchdog.Integration.WatchdogIntegrationTests can't break Shipping.Watchdog.Integration.
Position
Below the diagonal: Shipping.Watchdog.Integration.WatchdogIntegrationTests uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Program.Args uses Shipping.Watchdog.SourceArgs, so a change to Shipping.Watchdog.SourceArgs can break Shipping.Watchdog.Program.Args, while a change to Shipping.Watchdog.Program.Args can't break Shipping.Watchdog.SourceArgs.
Position
Below the diagonal: Shipping.Watchdog.Program.Args uses a module listed above it, which is the healthy direction.
Shipping.Watchdog.Program.Args uses Shipping.Watchdog.SourceArgs.Esdb, so a change to Shipping.Watchdog.SourceArgs.Esdb can break Shipping.Watchdog.Program.Args, while a change to Shipping.Watchdog.Program.Args can't break Shipping.Watchdog.SourceArgs.Esdb.
Position
Below the diagonal: Shipping.Watchdog.Program.Args uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 62% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
6
High / Critical
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
First, resolve the 91 orphaned files in the Knowledge Freshness dimension, prioritizing Infrastructure.fs, Program.fs, and Store.fs. Next, correct the README to accurately reflect the single-project structure and remove references to non-existent services and files. Then, establish a dedicated folder for Architecture Decision Records to document key design choices and their consequences. Finally, improve overall documentation quality by addressing assessment gaps and harden the web security posture by implementing essential response headers such as Content-Security-Policy and Strict-Transport-Security.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 91 Orphaned file finding(s) in Knowledge Freshness — start with Infrastructure.fs (15), Program.fs (13), Store.fs (4).
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists; README.md names the project `Equinox.EventStore`, but no project, folder or namespace of that name exists; README.md links to `propulsion-archiver/README.md`, but `propulsion-archiver/README.md` does not exist; README.md links to `propulsion-pruner/README.md`, but `propulsion-pruner/README.md` 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.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 11
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 199
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 — 147
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 2
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. 70 of 76 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 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 — 76 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, 321 of 357 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.
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 (11 contributor(s) across 378 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 10 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — measured, with a gap in what it reached — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'REDACTED' because the file extension '.fsproj' is not associated with a language.
D17 Explicit Debt — 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. The 2 deducted marker(s) and the 0.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (10,701 lines, 93% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
DM9 Scattered domain decisions — 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. Both arms resolve expressions to symbols (a comparison operand to the member it judges, a construction to the type it constructs) and that resolution comes from a Roslyn compilation, which this run has for the C#/VB projects only. The other languages in this repository were not walked for this dimension, so the counts above speak for part of the codebase.
P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
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.
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 (6): D19, D21, D24, D26, ED5, 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.
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being EsSourceParameters.Argu.IArgParserTemplate.get_Usage at 22 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: propulsion-indexer/Indexer/Program.fs (Parameters.Argu.IArgParserTemplate.get_Usage at 22), propulsion-sync/Program.fs (EsSourceParameters.Argu.IArgParserTemplate.get_Usage at 22), propulsion-reactor/SourceArgs.fs (Parameters.Argu.IArgParserTemplate.get_Usage at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
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.
0 method(s) exceeded the cognitive complexity threshold of 15.
✓ On the Gold path — maintain.
Detailed fixes: d2_recommendation.md.
Do you agree with this assessment?
D3 · God Classes9.6 / 10Stronggated by 1 serious finding✓ 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 1 FileTooLong finding(s) in God Classes — start with Program.fs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — 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.
Do you agree with this assessment?
D4 · Code Duplication4.0 / 10Weak✓ Tool-verified
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
161 duplicated block group(s) detected. A further 19 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 6 of the 180 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 86 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with SourceConfig.fs (4), Infrastructure.fs (3), Program.fs (3). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Program.fs (4), Args.fs (2), Infrastructure.fs (2). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 8 Duplicated block (5 lines × 3) finding(s) in Code Duplication — start with Store.fs (2), SourceArgs.fs (2), Program.fs (2). — One of this dimension's main actionable groups (8 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — 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.
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.
Resolve the 4 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), Web.csproj (2). — One of this dimension's main actionable groups (4 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — 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 380 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 41 direct `PackageReference`(s), and 210 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
2 deducted debt markers + unmeasured dead symbols across 775 LoC in the .NET projects (0.4/KLoC) → score 9.3. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (93% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
Resolve the 2 BareSuppressMessage finding(s) in Explicit Debt — start with ClientId.cs, Todo.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: 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.
The propulsion-indexer/Indexer/README is a focused README for the Indexer app directory, describing its purpose (consume ChangeFeed from Main Container via container config EQUINOX_COSMOS_CONTAINER and keep derived Views info in sync with EQUINOX_COSMOS_VIEWS), the command `index` that writes only to Views, usage as dotnet run --project Indexer -- -g defaultIndexer index, and a detailed Common-commandline-overrides section covering `-w`, `-r`, and settings after the subcommand name. It also references an Appendix listing indexing overview, snapshot commands, versioning events/snapshots, and regeneration examples, showing strong documentation outline. The README is focused on its directory rather than the repository's root, so the absence of a project-level overview/installation/usage/contributing/doc is not flagged. (17 of 18 sampled documents could not be assessed: 2 of 3 evaluation groups failed.)
What to do
Improve Documentation Quality — currently 8.0/10. — The propulsion-indexer/Indexer/README is a focused README for the Indexer app directory, describing its purpose (consume ChangeFeed from Main Container via container config EQUINOX_COSMOS_CONTAINER and keep derived Views info in sync with EQUINOX_COSMOS_VIEWS), the command `index` that writes only to Views, usage as dotnet run --project Indexer -- -g defaultIndexer index, and a detailed Common-commandline-overrides section covering `-w`, `-r`, and settings after the subcommand name. It also references an Appendix listing indexing overview, snapshot commands, versioning events/snapshots, and regeneration examples, showing strong documentation outline. The README is focused on its directory rather than the repository's root, so the absence of a project-level overview/installation/usage/contributing/doc is not flagged. (17 of 18 sampled documents could not be assessed: 2 of 3 evaluation groups failed.)
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.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
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.
90 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
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 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d30_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.
94 of 94 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is propulsion-sync/Program.fs. Counted over 94 of the 146 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3propulsion-sync/Program.fs:1
Dormant codebase
What to do
Resolve the 91 Orphaned file finding(s) in Knowledge Freshness — start with Infrastructure.fs (15), Program.fs (13), Store.fs (4). — One of this dimension's main actionable groups (91 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Program.fs (2), SourceArgs.fs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
✓ On the Gold path — maintain.
Detailed fixes: d37_recommendation.md.
Do you agree with this assessment?
D39 · IL Efficiency9.6 / 10Exemplary✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
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.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Web.csproj. — 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 — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
`Service` reads `DateTimeOffset.Now` inside `Favorite`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — equinox-testbed/Services.fs:68
What to do
Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — equinox-shipping/Domain/TransactionWatchdog.fs:17, equinox-shipping/Domain/TransactionWatchdog.fs:18
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — equinox-web-csharp/Web/Startup.cs:112
What to do
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
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 README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
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 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.
README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:939
README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists. 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.md:69
README.md names the project `Equinox.EventStore`, but no project, folder or namespace of that name exists. 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.md:71
README.md links to `propulsion-archiver/README.md`, but `propulsion-archiver/README.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.md:73
README.md links to `propulsion-pruner/README.md`, but `propulsion-pruner/README.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.md:76
README.md links to `propulsion-cosmos-reactor/README.md`, but `propulsion-cosmos-reactor/README.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.md:84
README.md links to `do-simplest-result`, but `do-simplest-result` 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.md:731
equinox-testbed/README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists. 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. — equinox-testbed/README.md:45
propulsion-hotel/README.md documents the environment variable `CONNSTR`, 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. — propulsion-hotel/README.md:168
propulsion-hotel/README.md documents the environment variable `CPCONNSTR`, 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. — propulsion-hotel/README.md:169
propulsion-indexer/Indexer/README.md runs `dotnet run --project Indexer -- -g deployYYMMDD snapshot` from `propulsion-indexer/Indexer/` or the repository root, but `Indexer` is not there: the project is `propulsion-indexer/Indexer`. 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. — propulsion-indexer/Indexer/README.md:250
What to do
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists; README.md names the project `Equinox.EventStore`, but no project, folder or namespace of that name exists; README.md links to `propulsion-archiver/README.md`, but `propulsion-archiver/README.md` does not exist; README.md links to `propulsion-pruner/README.md`, but `propulsion-pruner/README.md` does not exist.
Only 22/25 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `equinox-shipping/Watchdog.Integration`, `equinox-shipping/Watchdog.Lambda.Cdk`, `propulsion-dynamostore-cdk`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
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.
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.
`build` is async and calls Async.RunSynchronously — 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. — propulsion-indexer/Indexer/Program.fs:270
`run` is async and calls Async.RunSynchronously — 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. — propulsion-indexer/Indexer/Program.fs:340
What to do
F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
What to do
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/5 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×5) — equinox-web-csharp/Web/Controllers/TodosController.cs:40, equinox-web-csharp/Web/Controllers/TodosController.cs:44, equinox-web-csharp/Web/Controllers/TodosController.cs:52, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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 `ArgumentNullException` 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 a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. 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?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` 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?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX6 Interface segregation — no public interfaces
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 — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — ~696 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — no test run produced results
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences 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.
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): an event-store package (Marten/EventStore); 10 aggregate(s) with Apply/When folds
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
P8 Schema migrations — no EF Core usage detected
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
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.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog.Integration/DynamoConnector.fs:3— equinox-shipping/Watchdog.Integration/DynamoConnector.fs:3-7 | propulsion-hotel/Reactor.Integration/DynamoConnector.fs:3-7 — 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 (5 lines × 2) equinox-shipping/Watchdog/Handler.fs:21— equinox-shipping/Watchdog/Handler.fs:21-25 | propulsion-hotel/Reactor/Handler.fs:17-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog/Handler.fs:26— equinox-shipping/Watchdog/Handler.fs:26-30 | propulsion-indexer/Indexer/Indexer.fs:25-29 — 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 (5 lines × 2) equinox-shipping/Watchdog/Infrastructure.fs:60— equinox-shipping/Watchdog/Infrastructure.fs:60-64 | propulsion-reactor/Infrastructure.fs:89-93 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-reactor/Infrastructure.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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 `equinox-shipping/Watchdog/Infrastructure.fs:60` 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 (5 lines × 2) equinox-shipping/Watchdog/Program.fs:103— equinox-shipping/Watchdog/Program.fs:103-107 | propulsion-hotel/Reactor/Program.fs:89-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog/SourceArgs.fs:177— equinox-shipping/Watchdog/SourceArgs.fs:177-181 | propulsion-reactor/SourceArgs.fs:279-283 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-reactor/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:32— equinox-shipping/Watchdog/SourceConfig.fs:32-36 | propulsion-hotel/Reactor/SourceConfig.fs:21-27 — 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 (5 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:78— equinox-shipping/Watchdog/SourceConfig.fs:78-82 | propulsion-reactor/SourceConfig.fs:87-91 — before extracting anything, compare `equinox-shipping/Watchdog/SourceConfig.fs` and `propulsion-reactor/SourceConfig.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `equinox-shipping/Watchdog/SourceConfig.fs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:82— equinox-shipping/Watchdog/SourceConfig.fs:82-86 | propulsion-hotel/Reactor/SourceConfig.fs:55-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `equinox-shipping/Watchdog/SourceConfig.fs:87` calls `Cosmos`, `categories` and `propulsion-hotel/Reactor/SourceConfig.fs:60` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) propulsion-archiver/Infrastructure.fs:129— propulsion-archiver/Infrastructure.fs:129-133 | propulsion-pruner/Infrastructure.fs:71-75 — `propulsion-archiver/Infrastructure.fs` and `propulsion-pruner/Infrastructure.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 13 separate duplicated blocks between them, totalling at least 128 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 `propulsion-archiver/Infrastructure.fs:129` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog.Integration/DynamoConnector.fs:10— equinox-shipping/Watchdog.Integration/DynamoConnector.fs:10-14 | propulsion-hotel/Reactor.Integration/DynamoConnector.fs:10-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 (5 lines × 2) equinox-shipping/Watchdog/Program.fs:37— equinox-shipping/Watchdog/Program.fs:37-41 | propulsion-projector/Program.fs:55-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.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog/SourceArgs.fs:137— equinox-shipping/Watchdog/SourceArgs.fs:137-141 | propulsion-reactor/SourceArgs.fs:236-240 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-reactor/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:88— equinox-shipping/Watchdog/SourceConfig.fs:88-92 | propulsion-reactor/SourceConfig.fs:95-99 — before extracting anything, compare `equinox-shipping/Watchdog/SourceConfig.fs` and `propulsion-reactor/SourceConfig.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) propulsion-reactor/Infrastructure.fs:44— propulsion-reactor/Infrastructure.fs:44-48 | propulsion-summary-consumer/Infrastructure.fs:40-44 — `propulsion-reactor/Infrastructure.fs` and `propulsion-summary-consumer/Infrastructure.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 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) propulsion-sync/Program.fs:250— propulsion-sync/Program.fs:250-254 | propulsion-sync/Program.fs:343-347 — both copies are in the same file, so extract the 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) equinox-shipping/Watchdog.Integration/ReactorFixture.fs:60— equinox-shipping/Watchdog.Integration/ReactorFixture.fs:60-64 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:53-57 — before extracting anything, compare `equinox-shipping/Watchdog.Integration/ReactorFixture.fs` and `propulsion-hotel/Reactor.Integration/ReactorFixture.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) equinox-shipping/Watchdog.Integration/ReactorFixture.fs:141— equinox-shipping/Watchdog.Integration/ReactorFixture.fs:141-145 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:106-110 — before extracting anything, compare `equinox-shipping/Watchdog.Integration/ReactorFixture.fs` and `propulsion-hotel/Reactor.Integration/ReactorFixture.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) equinox-patterns/Domain/Store.fs:19— equinox-patterns/Domain/Store.fs:19-24 | equinox-shipping/Domain/Store.fs:24-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) equinox-shipping/Watchdog/Args.fs:15— equinox-shipping/Watchdog/Args.fs:15-20 | equinox-testbed/Storage.fs:6-12 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) equinox-shipping/Watchdog/Program.fs:43— equinox-shipping/Watchdog/Program.fs:43-48 | propulsion-hotel/Reactor/Program.fs:46-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) feed-consumer/Infrastructure.fs:228— feed-consumer/Infrastructure.fs:228-233 | periodic-ingester/Infrastructure.fs:232-237 — `feed-consumer/Infrastructure.fs` and `periodic-ingester/Infrastructure.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 15 separate duplicated blocks between them, totalling at least 238 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) propulsion-hotel/Domain/GroupCheckout.fs:121— propulsion-hotel/Domain/GroupCheckout.fs:121-126 | propulsion-hotel/Domain/GuestStay.fs:100-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) propulsion-projector/Program.fs:10— propulsion-projector/Program.fs:10-15 | propulsion-reactor/Program.fs:34-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) propulsion-projector/SourceArgs.fs:67— propulsion-projector/SourceArgs.fs:67-72 | propulsion-reactor/SourceArgs.fs:124-129 — `propulsion-projector/SourceArgs.fs` and `propulsion-reactor/SourceArgs.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 14 separate duplicated blocks between them, totalling at least 126 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 (6 lines × 2) propulsion-archiver/Program.fs:52— propulsion-archiver/Program.fs:52-57 | propulsion-pruner/Program.fs:44-49 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 before the matched lines, `propulsion-archiver/Program.fs:51` calls `GetResult` and `propulsion-pruner/Program.fs:43` 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) equinox-shipping/Watchdog/Program.fs:67— equinox-shipping/Watchdog/Program.fs:67-72 | propulsion-reactor/Program.fs:105-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) propulsion-archiver/Infrastructure.fs:69— propulsion-archiver/Infrastructure.fs:69-74 | propulsion-pruner/Infrastructure.fs:121-126 — `propulsion-archiver/Infrastructure.fs` and `propulsion-pruner/Infrastructure.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 13 separate duplicated blocks between them, totalling at least 128 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 (6 lines × 2) propulsion-indexer/App/Args.fs:42— propulsion-indexer/App/Args.fs:42-47 | propulsion-indexer/App/Args.fs:89-94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 3) equinox-patterns/Domain/Store.fs:14— equinox-patterns/Domain/Store.fs:14-18 | equinox-testbed/Store.fs:17-21 | feed-source/Domain/Store.fs:15-19 — 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 (5 lines × 3) equinox-patterns/Domain/Store.fs:22— equinox-patterns/Domain/Store.fs:22-26 | propulsion-summary-consumer/Store.fs:15-19 | propulsion-tracking-consumer/Store.fs:15-19 — `propulsion-summary-consumer/Store.fs` and `propulsion-tracking-consumer/Store.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 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 3) equinox-shipping/Watchdog/SourceArgs.fs:50— equinox-shipping/Watchdog/SourceArgs.fs:50-54 | propulsion-projector/SourceArgs.fs:66-70 | propulsion-reactor/SourceArgs.fs:123-127 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) equinox-shipping/Watchdog/SourceArgs.fs:113— equinox-shipping/Watchdog/SourceArgs.fs:113-117 | propulsion-projector/SourceArgs.fs:131-135 | propulsion-reactor/SourceArgs.fs:203-207 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) propulsion-consumer/Program.fs:18— propulsion-consumer/Program.fs:18-23 | propulsion-summary-consumer/Program.fs:25-30 | propulsion-tracking-consumer/Program.fs:25-29 — `propulsion-consumer/Program.fs` and `propulsion-summary-consumer/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 5 separate duplicated blocks between them, totalling at least 38 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, `propulsion-summary-consumer/Program.fs:34` calls `CliPrefix` and `propulsion-consumer/Program.fs:28` 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 × 3) propulsion-indexer/App/Infrastructure.fs:88— propulsion-indexer/App/Infrastructure.fs:88-92 | propulsion-reactor/Infrastructure.fs:65-69 | propulsion-sync/Infrastructure.fs:68-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `propulsion-indexer/App/Infrastructure.fs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) propulsion-indexer/Domain/Infrastructure.fs:29— propulsion-indexer/Domain/Infrastructure.fs:29-33 | propulsion-reactor/Infrastructure.fs:14-18 | propulsion-summary-consumer/Infrastructure.fs:14-18 — `propulsion-reactor/Infrastructure.fs` and `propulsion-summary-consumer/Infrastructure.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 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 3) propulsion-consumer/Program.fs:39— propulsion-consumer/Program.fs:39-43 | propulsion-summary-consumer/Program.fs:49-53 | propulsion-tracking-consumer/Program.fs:47-51 — `propulsion-consumer/Program.fs` and `propulsion-summary-consumer/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 5 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) equinox-shipping/Watchdog/Args.fs:125— equinox-shipping/Watchdog/Args.fs:125-131 | propulsion-reactor/SourceArgs.fs:32-38 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `propulsion-reactor/SourceArgs.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 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) equinox-shipping/Watchdog/SourceConfig.fs:61— equinox-shipping/Watchdog/SourceConfig.fs:61-67 | propulsion-hotel/Reactor/SourceConfig.fs:33-39 — 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) propulsion-consumer/Examples.fs:41— propulsion-consumer/Examples.fs:41-47 | propulsion-consumer/Examples.fs:64-70 — both copies are in the same file, so extract the 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) propulsion-projector/Args.fs:23— propulsion-projector/Args.fs:23-29 | propulsion-reactor/Args.fs:25-31 — `propulsion-projector/Args.fs` and `propulsion-reactor/Args.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 16 separate duplicated blocks between them, totalling at least 157 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) propulsion-projector/Infrastructure.fs:65— propulsion-projector/Infrastructure.fs:65-71 | propulsion-reactor/Infrastructure.fs:95-101 — `propulsion-projector/Infrastructure.fs` and `propulsion-reactor/Infrastructure.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 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 (7 lines × 2) equinox-shipping/Watchdog/Infrastructure.fs:98— equinox-shipping/Watchdog/Infrastructure.fs:98-104 | propulsion-reactor/Infrastructure.fs:148-154 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-reactor/Infrastructure.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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) equinox-shipping/Watchdog/Program.fs:75— equinox-shipping/Watchdog/Program.fs:75-81 | propulsion-reactor/Program.fs:118-124 — 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) equinox-patterns/Domain/Store.fs:14— equinox-patterns/Domain/Store.fs:14-21 | propulsion-hotel/Domain/Store.fs:15-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) equinox-testbed/Program.fs:113— equinox-testbed/Program.fs:113-120 | equinox-testbed/Program.fs:181-188 — both copies are in the same file, so extract the 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `equinox-testbed/Program.fs:180` calls `FromLogContext` and `equinox-testbed/Program.fs:112` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) propulsion-consumer/Infrastructure.fs:16— propulsion-consumer/Infrastructure.fs:16-23 | propulsion-reactor/Infrastructure.fs:33-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) propulsion-indexer/Domain/TodoIndex.fs:49— propulsion-indexer/Domain/TodoIndex.fs:49-56 | propulsion-summary-consumer/TodoSummary.fs:48-55 — before extracting anything, compare `propulsion-indexer/Domain/TodoIndex.fs` and `propulsion-summary-consumer/TodoSummary.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) propulsion-reactor/Handler.fs:77— propulsion-reactor/Handler.fs:77-84 | propulsion-reactor/Ingester.fs:66-73 — before extracting anything, compare `propulsion-reactor/Handler.fs` and `propulsion-reactor/Ingester.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 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 `propulsion-reactor/Handler.fs:77` 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) equinox-shipping/Watchdog.Integration/ReactorFixture.fs:94— equinox-shipping/Watchdog.Integration/ReactorFixture.fs:94-103 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:62-69 — before extracting anything, compare `equinox-shipping/Watchdog.Integration/ReactorFixture.fs` and `propulsion-hotel/Reactor.Integration/ReactorFixture.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) equinox-patterns/Domain/Store.fs:29— equinox-patterns/Domain/Store.fs:29-40 | feed-source/Domain/Store.fs:28-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) equinox-shipping/Watchdog/Program.fs:3— equinox-shipping/Watchdog/Program.fs:3-14 | propulsion-projector/Program.fs:3-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 (12 lines × 2) feed-consumer/Types.fs:6— feed-consumer/Types.fs:6-17 | feed-source/Domain/Types.fs:10-21 — before extracting anything, compare `feed-consumer/Types.fs` and `feed-source/Domain/Types.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 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feed-source/Domain/Types.fs:7` calls `toStringN` and `feed-consumer/Types.fs:3` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) propulsion-indexer/Domain/Todo.fs:62— propulsion-indexer/Domain/Todo.fs:62-73 | propulsion-reactor/Todo.fs:63-74 — before extracting anything, compare `propulsion-indexer/Domain/Todo.fs` and `propulsion-reactor/Todo.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 lines × 2) propulsion-reactor/Handler.fs:26— propulsion-reactor/Handler.fs:26-37 | propulsion-reactor/Ingester.fs:22-33 — before extracting anything, compare `propulsion-reactor/Handler.fs` and `propulsion-reactor/Ingester.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 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 (6 lines × 3) feed-consumer/Infrastructure.fs:83— feed-consumer/Infrastructure.fs:83-88 | feed-source/FeedApi/Infrastructure.fs:68-73 | periodic-ingester/Infrastructure.fs:87-92 — before extracting anything, compare `feed-consumer/Infrastructure.fs` and `feed-source/FeedApi/Infrastructure.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 62 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 `feed-consumer/Infrastructure.fs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) propulsion-consumer/Infrastructure.fs:79— propulsion-consumer/Infrastructure.fs:79-84 | propulsion-summary-consumer/Infrastructure.fs:77-82 | propulsion-tracking-consumer/Infrastructure.fs:51-56 — `propulsion-summary-consumer/Infrastructure.fs` and `propulsion-tracking-consumer/Infrastructure.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 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 (6 lines × 3) propulsion-indexer/Domain/TodoIndex.fs:18— propulsion-indexer/Domain/TodoIndex.fs:18-23 | propulsion-reactor/TodoSummary.fs:18-23 | propulsion-summary-consumer/TodoSummary.fs:18-23 — before extracting anything, compare `propulsion-indexer/Domain/TodoIndex.fs` and `propulsion-reactor/TodoSummary.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 (6 lines × 3) propulsion-archiver/Program.fs:128— propulsion-archiver/Program.fs:128-133 | propulsion-pruner/Program.fs:120-125 | propulsion-sync/Program.fs:294-302 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 (6 lines × 3) feed-consumer/Ingester.fs:19— feed-consumer/Ingester.fs:19-24 | periodic-ingester/Ingester.fs:19-24 | propulsion-summary-consumer/Ingester.fs:49-54 — 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.
X2 · Cancellation propagation· Async method without CancellationToken · ×5
Async method without CancellationToken: Get equinox-web-csharp/Web/Controllers/TodosController.cs:40— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Get equinox-web-csharp/Web/Controllers/TodosController.cs:44— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Post equinox-web-csharp/Web/Controllers/TodosController.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Patch equinox-web-csharp/Web/Controllers/TodosController.cs:56— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Connect equinox-web-csharp/Web/CosmosContext.cs:36— No CancellationToken parameter — this work can't be stopped early once started.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) equinox-patterns/Domain/ListEpoch.fs:1— equinox-patterns/Domain/ListEpoch.fs:1-79 | equinox-patterns/Domain/ListSeries.fs:4-58 | equinox-web/Domain/Aggregate.fs:1-67 | equinox-web/Domain/Todo.fs:1-152 — 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) equinox-shipping/Watchdog/Args.fs:2— equinox-shipping/Watchdog/Args.fs:2-131 | equinox-testbed/Storage.fs:1-118 | propulsion-projector/Args.fs:2-110 | propulsion-reactor/Args.fs:2-118 — 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) propulsion-consumer/Infrastructure.fs:1— propulsion-consumer/Infrastructure.fs:1-85 | propulsion-indexer/Domain/Streams.fs:1-20 | propulsion-reactor/Infrastructure.fs:1-154 | propulsion-summary-consumer/Infrastructure.fs:1-83 — 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) propulsion-hotel/Reactor/Handler.fs:1— propulsion-hotel/Reactor/Handler.fs:1-72 | propulsion-projector/Handler.fs:1-88 | propulsion-reactor/Handler.fs:1-88 | propulsion-reactor/Ingester.fs:1-77 — 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 (13 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:70— equinox-shipping/Watchdog/SourceConfig.fs:70-82 | propulsion-reactor/SourceConfig.fs:68-80 — before extracting anything, compare `equinox-shipping/Watchdog/SourceConfig.fs` and `propulsion-reactor/SourceConfig.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) feed-consumer/Infrastructure.fs:54— feed-consumer/Infrastructure.fs:54-66 | periodic-ingester/Infrastructure.fs:58-70 — `feed-consumer/Infrastructure.fs` and `periodic-ingester/Infrastructure.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 15 separate duplicated blocks between them, totalling at least 238 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 `feed-consumer/Infrastructure.fs:54` 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 × 2) propulsion-reactor/Infrastructure.fs:55— propulsion-reactor/Infrastructure.fs:55-67 | propulsion-sync/Infrastructure.fs:58-70 — `propulsion-reactor/Infrastructure.fs` and `propulsion-sync/Infrastructure.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 41 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) propulsion-summary-consumer/Program.fs:60— propulsion-summary-consumer/Program.fs:60-72 | propulsion-tracking-consumer/Program.fs:56-68 — `propulsion-summary-consumer/Program.fs` and `propulsion-tracking-consumer/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 11 separate duplicated blocks between them, totalling at least 113 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 before the matched lines, `propulsion-tracking-consumer/Program.fs:55` calls `CosmosArguments` and `propulsion-summary-consumer/Program.fs:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) equinox-shipping/Watchdog/Program.fs:122— equinox-shipping/Watchdog/Program.fs:122-128 | propulsion-archiver/Program.fs:185-191 | propulsion-pruner/Program.fs:177-184 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 `equinox-shipping/Watchdog/Program.fs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) equinox-web/Domain/Store.fs:51— equinox-web/Domain/Store.fs:51-57 | propulsion-projector/Store.fs:30-36 | propulsion-reactor/Store.fs:36-42 — before extracting anything, compare `equinox-web/Domain/Store.fs` and `propulsion-reactor/Store.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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 × 3) propulsion-indexer/Indexer/Indexer.fs:14— propulsion-indexer/Indexer/Indexer.fs:14-20 | propulsion-reactor/Handler.fs:24-30 | propulsion-reactor/Ingester.fs:20-26 — before extracting anything, compare `propulsion-reactor/Handler.fs` and `propulsion-reactor/Ingester.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 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 × 3) propulsion-reactor/SourceArgs.fs:135— propulsion-reactor/SourceArgs.fs:135-141 | propulsion-reactor/SourceArgs.fs:222-228 | propulsion-reactor/SourceArgs.fs:300-306 — 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 (9 lines × 2) periodic-ingester/Program.fs:132— periodic-ingester/Program.fs:132-140 | propulsion-hotel/Reactor/Program.fs:108-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `periodic-ingester/Program.fs:132` 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) propulsion-consumer/Program.fs:46— propulsion-consumer/Program.fs:46-54 | propulsion-summary-consumer/Program.fs:83-91 — `propulsion-consumer/Program.fs` and `propulsion-summary-consumer/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 5 separate duplicated blocks between them, totalling at least 38 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 (9 lines × 2) propulsion-pruner/Program.fs:71— propulsion-pruner/Program.fs:71-79 | propulsion-sync/Program.fs:145-154 — `propulsion-pruner/Program.fs` and `propulsion-sync/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 5 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 (8 lines × 3) equinox-shipping/Watchdog/SourceArgs.fs:23— equinox-shipping/Watchdog/SourceArgs.fs:23-30 | propulsion-indexer/App/Args.fs:67-74 | propulsion-projector/SourceArgs.fs:40-47 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) equinox-testbed/Infrastructure.fs:22— equinox-testbed/Infrastructure.fs:22-29 | feed-consumer/Infrastructure.fs:15-22 | periodic-ingester/Infrastructure.fs:19-26 — `feed-consumer/Infrastructure.fs` and `periodic-ingester/Infrastructure.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 15 separate duplicated blocks between them, totalling at least 238 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 `equinox-testbed/Infrastructure.fs:22` 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 × 3) propulsion-consumer/Program.fs:50— propulsion-consumer/Program.fs:50-57 | propulsion-summary-consumer/Program.fs:87-94 | propulsion-tracking-consumer/Program.fs:83-90 — `propulsion-consumer/Program.fs` and `propulsion-summary-consumer/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 5 separate duplicated blocks between them, totalling at least 38 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 (6 lines × 4) propulsion-consumer/Infrastructure.fs:12— propulsion-consumer/Infrastructure.fs:12-17 | propulsion-indexer/Domain/Streams.fs:12-17 | propulsion-reactor/Infrastructure.fs:29-34 | propulsion-summary-consumer/Infrastructure.fs:28-33 — `propulsion-reactor/Infrastructure.fs` and `propulsion-summary-consumer/Infrastructure.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 53 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 (6 lines × 4) propulsion-indexer/Indexer/Indexer.fs:13— propulsion-indexer/Indexer/Indexer.fs:13-18 | propulsion-reactor/Handler.fs:23-28 | propulsion-reactor/Ingester.fs:19-24 | propulsion-summary-consumer/Ingester.fs:45-50 — before extracting anything, compare `propulsion-reactor/Handler.fs` and `propulsion-reactor/Ingester.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 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 (6 lines × 4) propulsion-reactor/SourceArgs.fs:130— propulsion-reactor/SourceArgs.fs:130-135 | propulsion-reactor/SourceArgs.fs:217-222 | propulsion-reactor/SourceArgs.fs:295-300 | propulsion-reactor/SourceArgs.fs:366-371 — 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 × 4) equinox-shipping/Watchdog/Program.fs:126— equinox-shipping/Watchdog/Program.fs:126-130 | propulsion-projector/Program.fs:188-192 | propulsion-summary-consumer/Program.fs:114-118 | propulsion-tracking-consumer/Program.fs:114-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5 lines × 4) feed-consumer/Infrastructure.fs:83— feed-consumer/Infrastructure.fs:83-87 | feed-source/FeedApi/Infrastructure.fs:68-72 | periodic-ingester/Infrastructure.fs:87-91 | propulsion-archiver/Infrastructure.fs:63-67 — before extracting anything, compare `feed-consumer/Infrastructure.fs` and `feed-source/FeedApi/Infrastructure.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 62 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 `feed-consumer/Infrastructure.fs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) propulsion-hotel/Reactor/Handler.fs:67— propulsion-hotel/Reactor/Handler.fs:67-71 | propulsion-projector/Handler.fs:83-87 | propulsion-reactor/Handler.fs:83-87 | propulsion-reactor/Ingester.fs:72-76 — before extracting anything, compare `propulsion-reactor/Handler.fs` and `propulsion-reactor/Ingester.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 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 `propulsion-hotel/Reactor/Handler.fs:67` 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.
BareSuppressMessage equinox-web-csharp/Domain/ClientId.cs:17— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage equinox-web-csharp/Domain/Todo.cs:171— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
Near-duplicate member pair (56 shared lines) periodic-ingester/Infrastructure.fs:1— periodic-ingester/Infrastructure.fs:1-256 | propulsion-archiver/Infrastructure.fs:1-133 — These two members are variants of one another: 56 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 (56 shared lines) equinox-shipping/Watchdog.Integration/ReactorFixture.fs:1— equinox-shipping/Watchdog.Integration/ReactorFixture.fs:1-151 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:1-116 — These two members are variants of one another: 56 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) equinox-shipping/Watchdog/Args.fs:2— equinox-shipping/Watchdog/Args.fs:2-131 | equinox-shipping/Watchdog/SourceArgs.fs:1-201 | propulsion-hotel/Reactor/SourceArgs.fs:1-122 | propulsion-projector/Args.fs:2-110 | propulsion-projector/SourceArgs.fs:1-145 | propulsion-reactor/Args.fs:2-118 | propulsion-reactor/SourceArgs.fs:1-374 — These 7 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 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) equinox-shipping/Watchdog/Infrastructure.fs:1— equinox-shipping/Watchdog/Infrastructure.fs:1-104 | propulsion-archiver/Infrastructure.fs:1-133 | propulsion-indexer/App/Infrastructure.fs:1-165 | propulsion-projector/Infrastructure.fs:1-100 | propulsion-pruner/Infrastructure.fs:1-128 | propulsion-reactor/Infrastructure.fs:1-154 | propulsion-sync/Infrastructure.fs:1-104 — These 7 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 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Duplicated block (17–18 lines × 3) equinox-shipping/Watchdog/SourceArgs.fs:75— equinox-shipping/Watchdog/SourceArgs.fs:75-92 | propulsion-projector/SourceArgs.fs:93-110 | propulsion-reactor/SourceArgs.fs:162-178 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17–18 lines × 3) equinox-shipping/Watchdog/SourceConfig.fs:40— equinox-shipping/Watchdog/SourceConfig.fs:40-56 | propulsion-projector/SourceConfig.fs:50-67 | propulsion-reactor/SourceConfig.fs:39-56 — before extracting anything, compare `equinox-shipping/Watchdog/SourceConfig.fs` and `propulsion-reactor/SourceConfig.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) equinox-shipping/Watchdog/Args.fs:89— equinox-shipping/Watchdog/Args.fs:89-102 | propulsion-projector/Args.fs:83-96 | propulsion-reactor/Args.fs:92-105 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `propulsion-projector/Args.fs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 127 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) propulsion-indexer/Domain/TodoIndex.fs:29— propulsion-indexer/Domain/TodoIndex.fs:29-42 | propulsion-reactor/TodoSummary.fs:29-42 | propulsion-summary-consumer/TodoSummary.fs:29-42 — before extracting anything, compare `propulsion-indexer/Domain/TodoIndex.fs` and `propulsion-reactor/TodoSummary.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 lines × 3) equinox-shipping/Watchdog/SourceArgs.fs:63— equinox-shipping/Watchdog/SourceArgs.fs:63-74 | propulsion-projector/SourceArgs.fs:81-92 | propulsion-reactor/SourceArgs.fs:145-156 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 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 after the matched lines, `propulsion-reactor/SourceArgs.fs:158` calls `CliPrefix` and `equinox-shipping/Watchdog/SourceArgs.fs:75` 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 × 3) periodic-ingester/Infrastructure.fs:10— periodic-ingester/Infrastructure.fs:10-21 | propulsion-archiver/Infrastructure.fs:7-18 | propulsion-pruner/Infrastructure.fs:7-18 — `periodic-ingester/Infrastructure.fs` and `propulsion-archiver/Infrastructure.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 8 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 (11 lines × 6) equinox-shipping/Watchdog/Args.fs:47— equinox-shipping/Watchdog/Args.fs:47-57 | feed-consumer/Program.fs:67-77 | feed-source/FeedApi/Program.fs:39-49 | periodic-ingester/Program.fs:79-89 | propulsion-projector/Args.fs:41-51 | propulsion-reactor/Args.fs:51-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
Duplicated block (11 lines × 6) feed-consumer/Infrastructure.fs:44— feed-consumer/Infrastructure.fs:44-54 | feed-source/FeedApi/Infrastructure.fs:36-46 | periodic-ingester/Infrastructure.fs:48-58 | propulsion-archiver/Infrastructure.fs:23-33 | propulsion-indexer/App/Infrastructure.fs:17-27 | propulsion-pruner/Infrastructure.fs:75-85 — before extracting anything, compare `feed-consumer/Infrastructure.fs` and `feed-source/FeedApi/Infrastructure.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 62 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 `feed-consumer/Infrastructure.fs:44` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10–11 lines × 4) equinox-patterns/Domain/Store.fs:7— equinox-patterns/Domain/Store.fs:7-16 | equinox-testbed/Store.fs:10-19 | equinox-web/Domain/Store.fs:10-20 | propulsion-reactor/Store.fs:7-16 — before extracting anything, compare `equinox-web/Domain/Store.fs` and `propulsion-reactor/Store.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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–11 lines × 4) equinox-shipping/Watchdog/SourceArgs.fs:63— equinox-shipping/Watchdog/SourceArgs.fs:63-73 | propulsion-hotel/Reactor/SourceArgs.fs:19-28 | propulsion-projector/SourceArgs.fs:81-91 | propulsion-reactor/SourceArgs.fs:145-155 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 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 after the matched lines, `propulsion-reactor/SourceArgs.fs:158` calls `CliPrefix` and `equinox-shipping/Watchdog/SourceArgs.fs:75` 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 × 3) equinox-shipping/Watchdog/Args.fs:7— equinox-shipping/Watchdog/Args.fs:7-16 | propulsion-projector/Args.fs:6-15 | propulsion-reactor/Args.fs:8-18 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `propulsion-projector/Args.fs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 127 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 3) equinox-shipping/Watchdog/SourceArgs.fs:16— equinox-shipping/Watchdog/SourceArgs.fs:16-26 | propulsion-projector/SourceArgs.fs:33-43 | propulsion-reactor/SourceArgs.fs:83-92 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 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 after the matched lines, `propulsion-reactor/SourceArgs.fs:94` calls `CliPrefix` and `equinox-shipping/Watchdog/SourceArgs.fs:27` 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 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:22— equinox-shipping/Watchdog/SourceConfig.fs:22-32 | propulsion-reactor/SourceConfig.fs:28-38 — before extracting anything, compare `equinox-shipping/Watchdog/SourceConfig.fs` and `propulsion-reactor/SourceConfig.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) propulsion-summary-consumer/Program.fs:88— propulsion-summary-consumer/Program.fs:88-98 | propulsion-tracking-consumer/Program.fs:84-94 — `propulsion-summary-consumer/Program.fs` and `propulsion-tracking-consumer/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 11 separate duplicated blocks between them, totalling at least 113 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 × 2) equinox-web/Domain/Store.fs:51— equinox-web/Domain/Store.fs:51-61 | propulsion-reactor/Store.fs:36-45 — before extracting anything, compare `equinox-web/Domain/Store.fs` and `propulsion-reactor/Store.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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–11 lines × 2) feed-consumer/Infrastructure.fs:8— feed-consumer/Infrastructure.fs:8-17 | propulsion-sync/Infrastructure.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.
Duplicated block (10 lines × 3) equinox-shipping/Watchdog/Args.fs:77— equinox-shipping/Watchdog/Args.fs:77-86 | propulsion-projector/Args.fs:71-80 | propulsion-reactor/Args.fs:80-89 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `propulsion-projector/Args.fs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 127 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) propulsion-consumer/Program.fs:67— propulsion-consumer/Program.fs:67-76 | propulsion-summary-consumer/Program.fs:109-118 | propulsion-tracking-consumer/Program.fs:109-118 — `propulsion-consumer/Program.fs` and `propulsion-summary-consumer/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 5 separate duplicated blocks between them, totalling at least 38 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) equinox-web/Domain/Todo.fs:41— equinox-web/Domain/Todo.fs:41-50 | propulsion-reactor/Todo.fs:57-66 — 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 (10 lines × 2) propulsion-sync/Program.fs:263— propulsion-sync/Program.fs:263-272 | propulsion-sync/Program.fs:356-365 — both copies are in the same file, so extract the 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 × 6) equinox-shipping/Watchdog/Infrastructure.fs:24— equinox-shipping/Watchdog/Infrastructure.fs:24-32 | propulsion-archiver/Infrastructure.fs:88-96 | propulsion-indexer/App/Infrastructure.fs:76-84 | propulsion-projector/Infrastructure.fs:24-32 | propulsion-reactor/Infrastructure.fs:53-61 | propulsion-sync/Infrastructure.fs:56-64 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-archiver/Infrastructure.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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 × 6) feed-consumer/Infrastructure.fs:66— feed-consumer/Infrastructure.fs:66-74 | feed-source/FeedApi/Infrastructure.fs:50-58 | periodic-ingester/Infrastructure.fs:70-78 | propulsion-archiver/Infrastructure.fs:46-54 | propulsion-hotel/Reactor/Infrastructure.fs:72-80 | propulsion-pruner/Infrastructure.fs:98-106 — before extracting anything, compare `feed-consumer/Infrastructure.fs` and `feed-source/FeedApi/Infrastructure.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 62 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 after the matched lines, `feed-source/FeedApi/Infrastructure.fs:59` calls `Override` and `feed-consumer/Infrastructure.fs:75` 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 × 4) equinox-patterns/Domain/Store.fs:3— equinox-patterns/Domain/Store.fs:3-11 | propulsion-reactor/Store.fs:3-11 | propulsion-summary-consumer/Store.fs:3-11 | propulsion-tracking-consumer/Store.fs:3-11 — `propulsion-summary-consumer/Store.fs` and `propulsion-tracking-consumer/Store.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 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 4) equinox-shipping/Watchdog/Args.fs:73— equinox-shipping/Watchdog/Args.fs:73-81 | equinox-shipping/Watchdog/SourceArgs.fs:59-67 | propulsion-projector/Args.fs:67-75 | propulsion-reactor/Args.fs:76-84 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) equinox-shipping/Watchdog/Infrastructure.fs:81— equinox-shipping/Watchdog/Infrastructure.fs:81-89 | propulsion-hotel/Reactor/Infrastructure.fs:41-49 | propulsion-projector/Infrastructure.fs:92-100 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-hotel/Reactor/Infrastructure.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 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 × 3) equinox-shipping/Watchdog/SourceArgs.fs:119— equinox-shipping/Watchdog/SourceArgs.fs:119-127 | propulsion-projector/SourceArgs.fs:137-145 | propulsion-reactor/SourceArgs.fs:209-217 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 7) equinox-shipping/Watchdog/Args.fs:106— equinox-shipping/Watchdog/Args.fs:106-113 | equinox-shipping/Watchdog/SourceArgs.fs:102-109 | propulsion-hotel/Reactor/SourceArgs.fs:54-61 | propulsion-projector/Args.fs:100-107 | propulsion-projector/SourceArgs.fs:120-127 | propulsion-reactor/Args.fs:109-116 | propulsion-reactor/SourceArgs.fs:192-199 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 7) equinox-shipping/Watchdog/Args.fs:49— equinox-shipping/Watchdog/Args.fs:49-56 | feed-consumer/Program.fs:69-76 | feed-source/FeedApi/Program.fs:41-48 | periodic-ingester/Program.fs:81-88 | propulsion-indexer/App/Args.fs:28-35 | propulsion-projector/Args.fs:43-50 | propulsion-reactor/Args.fs:53-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times.
Duplicated block (7 lines × 11) equinox-shipping/Watchdog/Infrastructure.fs:12— equinox-shipping/Watchdog/Infrastructure.fs:12-18 | feed-consumer/Infrastructure.fs:69-75 | periodic-ingester/Infrastructure.fs:73-79 | propulsion-archiver/Infrastructure.fs:49-55 | propulsion-consumer/Infrastructure.fs:76-82 | propulsion-hotel/Reactor/Infrastructure.fs:75-81 | propulsion-indexer/App/Infrastructure.fs:49-55 | propulsion-projector/Infrastructure.fs:12-18 | propulsion-pruner/Infrastructure.fs:101-107 | propulsion-reactor/Infrastructure.fs:136-142 | propulsion-summary-consumer/Infrastructure.fs:74-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `propulsion-indexer/App/Infrastructure.fs:57` calls `Override` and `feed-consumer/Infrastructure.fs:77` 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 × 11) equinox-shipping/Watchdog/Infrastructure.fs:32— equinox-shipping/Watchdog/Infrastructure.fs:32-38 | equinox-testbed/Infrastructure.fs:26-32 | feed-consumer/Infrastructure.fs:19-25 | feed-source/FeedApi/Infrastructure.fs:11-17 | periodic-ingester/Infrastructure.fs:23-29 | propulsion-archiver/Infrastructure.fs:96-102 | propulsion-indexer/App/Infrastructure.fs:84-90 | propulsion-projector/Infrastructure.fs:32-38 | propulsion-pruner/Infrastructure.fs:38-44 | propulsion-summary-consumer/Infrastructure.fs:46-52 | propulsion-tracking-consumer/Infrastructure.fs:20-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times.
Duplicated block (7 lines × 7) equinox-shipping/Watchdog/Args.fs:44— equinox-shipping/Watchdog/Args.fs:44-50 | equinox-shipping/Watchdog/SourceArgs.fs:15-21 | periodic-ingester/Program.fs:76-82 | propulsion-projector/Args.fs:38-44 | propulsion-projector/SourceArgs.fs:32-38 | propulsion-reactor/Args.fs:48-54 | propulsion-reactor/SourceArgs.fs:82-88 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 7) equinox-shipping/Watchdog/Args.fs:46— equinox-shipping/Watchdog/Args.fs:46-52 | feed-consumer/Program.fs:66-72 | periodic-ingester/Program.fs:78-84 | propulsion-projector/Args.fs:40-46 | propulsion-reactor/Args.fs:50-56 | propulsion-summary-consumer/Program.fs:62-68 | propulsion-tracking-consumer/Program.fs:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `propulsion-tracking-consumer/Program.fs:55` calls `CosmosArguments` and `propulsion-summary-consumer/Program.fs:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (3–7 lines × 3) equinox-shipping/Watchdog/Program.fs:93— equinox-shipping/Watchdog/Program.fs:93-99 | propulsion-hotel/Reactor/Program.fs:79-85 | propulsion-projector/Program.fs:141-143 — 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 (3–7 lines × 3) propulsion-archiver/Program.fs:147— propulsion-archiver/Program.fs:147-153 | propulsion-pruner/Program.fs:137-143 | propulsion-reactor/Program.fs:232-234 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 `propulsion-archiver/Program.fs:147` 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.
Unfinished stub — raises a "not implemented" error equinox-shipping/Domain/TransactionWatchdog.fs:17— A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — raises a "not implemented" error equinox-shipping/Domain/TransactionWatchdog.fs:18— A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Sync-over-async blocking propulsion-indexer/Indexer/Program.fs:270— `build` is async and calls Async.RunSynchronously — 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 propulsion-indexer/Indexer/Program.fs:340— `run` is async and calls Async.RunSynchronously — 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.
FileTooLong: propulsion-sync/Program.fs propulsion-sync/Program.fs— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× 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· Near-duplicate member family (3 members, 31 shared lines) · ×1
Near-duplicate member family (3 members, 31 shared lines) propulsion-indexer/Domain/TodoIndex.fs:1— propulsion-indexer/Domain/TodoIndex.fs:1-57 | propulsion-reactor/TodoSummary.fs:1-62 | propulsion-summary-consumer/TodoSummary.fs:1-56 — These 3 members are variants of one another: a block of 31 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 28 shared lines) · ×1
Near-duplicate member family (3 members, 28 shared lines) propulsion-consumer/Program.fs:1— propulsion-consumer/Program.fs:1-80 | propulsion-summary-consumer/Program.fs:1-122 | propulsion-tracking-consumer/Program.fs:1-122 — These 3 members are variants of one another: a block of 28 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 27 shared lines) · ×1
Near-duplicate member family (3 members, 27 shared lines) feed-consumer/Program.fs:1— feed-consumer/Program.fs:1-134 | feed-source/FeedApi/Program.fs:1-114 | periodic-ingester/Program.fs:1-152 — These 3 members are variants of one another: a block of 27 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 (59 shared lines) equinox-shipping/Watchdog/SourceConfig.fs:1— equinox-shipping/Watchdog/SourceConfig.fs:1-92 | propulsion-reactor/SourceConfig.fs:1-101 — These two members are variants of one another: 59 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 (44 shared lines) feed-source/FeedApi/Infrastructure.fs:1— feed-source/FeedApi/Infrastructure.fs:1-74 | propulsion-archiver/Infrastructure.fs:1-133 — These two members are variants of one another: 44 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 (39 shared lines) feed-source/FeedApi/Infrastructure.fs:1— feed-source/FeedApi/Infrastructure.fs:1-74 | propulsion-pruner/Infrastructure.fs:1-128 — These two members are variants of one another: 39 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 (33 shared lines) propulsion-indexer/Domain/Todo.fs:1— propulsion-indexer/Domain/Todo.fs:1-79 | propulsion-reactor/Todo.fs:1-83 — These two members are variants of one another: 33 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (29 shared lines) propulsion-hotel/Reactor/Infrastructure.fs:1— propulsion-hotel/Reactor/Infrastructure.fs:1-94 | propulsion-projector/Infrastructure.fs:1-100 — These two members are variants of one another: 29 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (27 shared lines) equinox-web/Domain/Store.fs:1— equinox-web/Domain/Store.fs:1-83 | propulsion-reactor/Store.fs:1-66 — These two members are variants of one another: 27 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) equinox-testbed/Infrastructure.fs:1— equinox-testbed/Infrastructure.fs:1-57 | feed-consumer/Infrastructure.fs:1-252 | feed-source/FeedApi/Infrastructure.fs:1-74 | periodic-ingester/Infrastructure.fs:1-256 | propulsion-summary-consumer/Infrastructure.fs:1-83 | propulsion-tracking-consumer/Infrastructure.fs:1-57 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) periodic-ingester/Program.fs:1— periodic-ingester/Program.fs:1-152 | propulsion-archiver/Program.fs:1-197 | propulsion-hotel/Reactor/Program.fs:1-130 | propulsion-indexer/App/Infrastructure.fs:1-165 | propulsion-pruner/Program.fs:1-190 — 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 (66 lines × 2) feed-consumer/Infrastructure.fs:87— feed-consumer/Infrastructure.fs:87-152 | periodic-ingester/Infrastructure.fs:91-156 — `feed-consumer/Infrastructure.fs` and `periodic-ingester/Infrastructure.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 15 separate duplicated blocks between them, totalling at least 238 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 `feed-consumer/Infrastructure.fs:87` 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 (62 lines × 2) feed-consumer/Infrastructure.fs:162— feed-consumer/Infrastructure.fs:162-223 | periodic-ingester/Infrastructure.fs:166-227 — `feed-consumer/Infrastructure.fs` and `periodic-ingester/Infrastructure.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 15 separate duplicated blocks between them, totalling at least 238 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 `feed-consumer/Infrastructure.fs:162` 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 (25–26 lines × 2) propulsion-summary-consumer/Program.fs:12— propulsion-summary-consumer/Program.fs:12-37 | propulsion-tracking-consumer/Program.fs:12-36 — `propulsion-summary-consumer/Program.fs` and `propulsion-tracking-consumer/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 11 separate duplicated blocks between them, totalling at least 113 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–24 lines × 2) propulsion-archiver/Infrastructure.fs:4— propulsion-archiver/Infrastructure.fs:4-27 | propulsion-pruner/Infrastructure.fs:4-23 — `propulsion-archiver/Infrastructure.fs` and `propulsion-pruner/Infrastructure.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 13 separate duplicated blocks between them, totalling at least 128 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 (22–23 lines × 2) equinox-shipping/Watchdog/SourceArgs.fs:20— equinox-shipping/Watchdog/SourceArgs.fs:20-42 | propulsion-projector/SourceArgs.fs:37-58 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 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 (23 lines × 2) propulsion-projector/Args.fs:65— propulsion-projector/Args.fs:65-87 | propulsion-reactor/Args.fs:74-96 — `propulsion-projector/Args.fs` and `propulsion-reactor/Args.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 16 separate duplicated blocks between them, totalling at least 157 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–22 lines × 2) propulsion-reactor/Infrastructure.fs:4— propulsion-reactor/Infrastructure.fs:4-25 | propulsion-summary-consumer/Infrastructure.fs:4-22 — `propulsion-reactor/Infrastructure.fs` and `propulsion-summary-consumer/Infrastructure.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 53 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 (18–19 lines × 2) equinox-shipping/Watchdog/SourceConfig.fs:9— equinox-shipping/Watchdog/SourceConfig.fs:9-27 | propulsion-reactor/SourceConfig.fs:9-26 — before extracting anything, compare `equinox-shipping/Watchdog/SourceConfig.fs` and `propulsion-reactor/SourceConfig.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) propulsion-summary-consumer/Store.fs:1— propulsion-summary-consumer/Store.fs:1-19 | propulsion-tracking-consumer/Store.fs:1-19 — `propulsion-summary-consumer/Store.fs` and `propulsion-tracking-consumer/Store.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 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (18 lines × 2) propulsion-archiver/Program.fs:116— propulsion-archiver/Program.fs:116-133 | propulsion-pruner/Program.fs:108-125 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 (17 lines × 2) equinox-shipping/Watchdog/Infrastructure.fs:1— equinox-shipping/Watchdog/Infrastructure.fs:1-17 | propulsion-projector/Infrastructure.fs:1-17 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-projector/Infrastructure.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–17 lines × 2) propulsion-indexer/Domain/Todo.fs:4— propulsion-indexer/Domain/Todo.fs:4-19 | propulsion-reactor/Todo.fs:5-21 — before extracting anything, compare `propulsion-indexer/Domain/Todo.fs` and `propulsion-reactor/Todo.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) propulsion-archiver/Program.fs:75— propulsion-archiver/Program.fs:75-90 | propulsion-pruner/Program.fs:63-78 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 × 2) propulsion-reactor/TodoSummary.fs:33— propulsion-reactor/TodoSummary.fs:33-47 | propulsion-summary-consumer/TodoSummary.fs:33-46 — `propulsion-reactor/TodoSummary.fs` and `propulsion-summary-consumer/TodoSummary.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 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–14 lines × 7) feed-consumer/Program.fs:4— feed-consumer/Program.fs:4-16 | feed-source/FeedApi/Program.fs:4-16 | periodic-ingester/Program.fs:4-16 | propulsion-archiver/Program.fs:4-17 | propulsion-pruner/Program.fs:4-17 | propulsion-summary-consumer/Program.fs:4-16 | propulsion-tracking-consumer/Program.fs:4-16 — before extracting anything, compare `feed-consumer/Program.fs` and `feed-source/FeedApi/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 6) equinox-shipping/Watchdog/Infrastructure.fs:35— equinox-shipping/Watchdog/Infrastructure.fs:35-48 | feed-consumer/Infrastructure.fs:22-35 | periodic-ingester/Infrastructure.fs:26-39 | propulsion-projector/Infrastructure.fs:35-48 | propulsion-summary-consumer/Infrastructure.fs:49-62 | propulsion-tracking-consumer/Infrastructure.fs:23-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
Duplicated block (12–14 lines × 3) equinox-shipping/Watchdog/SourceArgs.fs:27— equinox-shipping/Watchdog/SourceArgs.fs:27-40 | propulsion-projector/SourceArgs.fs:44-57 | propulsion-reactor/SourceArgs.fs:98-109 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-projector/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) propulsion-archiver/Infrastructure.fs:31— propulsion-archiver/Infrastructure.fs:31-44 | propulsion-pruner/Infrastructure.fs:83-96 — `propulsion-archiver/Infrastructure.fs` and `propulsion-pruner/Infrastructure.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 13 separate duplicated blocks between them, totalling at least 128 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) equinox-shipping/Watchdog/Infrastructure.fs:68— equinox-shipping/Watchdog/Infrastructure.fs:68-78 | propulsion-hotel/Reactor/Infrastructure.fs:26-38 | propulsion-projector/Infrastructure.fs:78-90 | propulsion-reactor/Infrastructure.fs:108-120 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-hotel/Reactor/Infrastructure.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 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 × 3) equinox-shipping/Watchdog/Args.fs:51— equinox-shipping/Watchdog/Args.fs:51-63 | propulsion-projector/Args.fs:45-57 | propulsion-reactor/Args.fs:55-67 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `propulsion-projector/Args.fs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 127 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9–13 lines × 2) equinox-shipping/Watchdog/Infrastructure.fs:81— equinox-shipping/Watchdog/Infrastructure.fs:81-89 | propulsion-hotel/Reactor/Infrastructure.fs:41-53 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-hotel/Reactor/Infrastructure.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) equinox-shipping/Watchdog/SourceArgs.fs:152— equinox-shipping/Watchdog/SourceArgs.fs:152-164 | propulsion-reactor/SourceArgs.fs:254-265 — before extracting anything, compare `equinox-shipping/Watchdog/SourceArgs.fs` and `propulsion-reactor/SourceArgs.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 143 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 (1–13 lines × 5) equinox-patterns/Domain/ListEpoch.fs:72— equinox-patterns/Domain/ListEpoch.fs:72-75 | equinox-patterns/Domain/ListEpoch.fs:76-76 | equinox-patterns/Domain/ListSeries.fs:52-56 | equinox-web/Domain/Aggregate.fs:52-64 | equinox-web/Domain/Todo.fs:138-149 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 4) equinox-testbed/Store.fs:3— equinox-testbed/Store.fs:3-14 | equinox-web/Domain/Store.fs:3-14 | feed-source/Domain/Store.fs:3-14 | propulsion-hotel/Domain/Store.fs:3-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5–12 lines × 3) equinox-web/Domain/Todo.fs:26— equinox-web/Domain/Todo.fs:26-37 | propulsion-indexer/Domain/Todo.fs:52-56 | propulsion-reactor/Todo.fs:42-53 — before extracting anything, compare `propulsion-indexer/Domain/Todo.fs` and `propulsion-reactor/Todo.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 (4–11 lines × 7) feed-consumer/Infrastructure.fs:68— feed-consumer/Infrastructure.fs:68-78 | feed-source/FeedApi/Infrastructure.fs:62-65 | periodic-ingester/Infrastructure.fs:72-82 | propulsion-archiver/Infrastructure.fs:48-58 | propulsion-hotel/Reactor/Infrastructure.fs:74-84 | propulsion-indexer/App/Infrastructure.fs:59-62 | propulsion-pruner/Infrastructure.fs:100-110 — before extracting anything, compare `feed-consumer/Infrastructure.fs` and `feed-source/FeedApi/Infrastructure.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 62 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `feed-consumer/Infrastructure.fs:78` calls `Sinks`, `configure` and `feed-source/FeedApi/Infrastructure.fs:65` 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 (7–11 lines × 3) equinox-web/Domain/Store.fs:35— equinox-web/Domain/Store.fs:35-45 | propulsion-projector/Store.fs:16-25 | propulsion-reactor/Store.fs:22-28 — before extracting anything, compare `equinox-web/Domain/Store.fs` and `propulsion-reactor/Store.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `propulsion-reactor/Store.fs:28` calls `accessStrategy` and `propulsion-projector/Store.fs:25` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) propulsion-indexer/Domain/TodoIndex.fs:5— propulsion-indexer/Domain/TodoIndex.fs:5-15 | propulsion-reactor/TodoSummary.fs:5-15 | propulsion-summary-consumer/TodoSummary.fs:5-15 — before extracting anything, compare `propulsion-indexer/Domain/TodoIndex.fs` and `propulsion-reactor/TodoSummary.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 lines × 4) equinox-shipping/Watchdog/Infrastructure.fs:26— equinox-shipping/Watchdog/Infrastructure.fs:26-35 | propulsion-archiver/Infrastructure.fs:90-99 | propulsion-indexer/App/Infrastructure.fs:78-87 | propulsion-projector/Infrastructure.fs:26-35 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-archiver/Infrastructure.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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 `equinox-shipping/Watchdog/Infrastructure.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.
Duplicated block (9–10 lines × 2) propulsion-archiver/Program.fs:183— propulsion-archiver/Program.fs:183-191 | propulsion-pruner/Program.fs:175-184 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 `propulsion-archiver/Program.fs:183` 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–10 lines × 2) propulsion-indexer/Indexer/Program.fs:7— propulsion-indexer/Indexer/Program.fs:7-16 | propulsion-pruner/Program.fs:21-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 (7–9 lines × 5) equinox-shipping/Watchdog/Args.fs:41— equinox-shipping/Watchdog/Args.fs:41-49 | equinox-shipping/Watchdog/SourceArgs.fs:14-20 | propulsion-projector/Args.fs:35-43 | propulsion-projector/SourceArgs.fs:31-37 | propulsion-reactor/Args.fs:45-53 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 3) propulsion-archiver/Program.fs:66— propulsion-archiver/Program.fs:66-74 | propulsion-pruner/Program.fs:53-61 | propulsion-sync/Program.fs:129-136 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7–8 lines × 13) equinox-shipping/Watchdog/Infrastructure.fs:42— equinox-shipping/Watchdog/Infrastructure.fs:42-49 | equinox-testbed/Infrastructure.fs:36-43 | feed-consumer/Infrastructure.fs:29-36 | feed-source/FeedApi/Infrastructure.fs:21-28 | periodic-ingester/Infrastructure.fs:33-40 | propulsion-archiver/Infrastructure.fs:106-113 | propulsion-indexer/App/Infrastructure.fs:95-101 | propulsion-projector/Infrastructure.fs:42-49 | propulsion-pruner/Infrastructure.fs:48-55 | propulsion-reactor/Infrastructure.fs:72-78 | propulsion-summary-consumer/Infrastructure.fs:56-63 | propulsion-sync/Infrastructure.fs:75-81 | propulsion-tracking-consumer/Infrastructure.fs:30-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 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 13 times.
Duplicated block (8 lines × 6) equinox-shipping/Watchdog/Args.fs:76— equinox-shipping/Watchdog/Args.fs:76-83 | equinox-shipping/Watchdog/SourceArgs.fs:62-69 | propulsion-projector/Args.fs:70-77 | propulsion-projector/SourceArgs.fs:80-87 | propulsion-reactor/Args.fs:79-86 | propulsion-reactor/SourceArgs.fs:144-151 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 5) equinox-shipping/Watchdog/Infrastructure.fs:29— equinox-shipping/Watchdog/Infrastructure.fs:29-36 | propulsion-archiver/Infrastructure.fs:93-100 | propulsion-indexer/App/Infrastructure.fs:81-88 | propulsion-projector/Infrastructure.fs:29-36 | propulsion-pruner/Infrastructure.fs:35-42 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-archiver/Infrastructure.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) propulsion-archiver/Program.fs:122— propulsion-archiver/Program.fs:122-129 | propulsion-pruner/Program.fs:114-121 | propulsion-summary-consumer/Program.fs:65-72 | propulsion-tracking-consumer/Program.fs:61-68 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 4) periodic-ingester/Program.fs:127— periodic-ingester/Program.fs:127-133 | propulsion-archiver/Program.fs:170-176 | propulsion-indexer/App/Infrastructure.fs:158-164 | propulsion-pruner/Program.fs:161-167 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 (6–7 lines × 3) propulsion-archiver/Program.fs:117— propulsion-archiver/Program.fs:117-123 | propulsion-pruner/Program.fs:109-115 | propulsion-sync/Program.fs:280-285 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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, `propulsion-sync/Program.fs:288` calls `CliPrefix` and `propulsion-archiver/Program.fs:124` 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 × 7) equinox-shipping/Watchdog/Args.fs:99— equinox-shipping/Watchdog/Args.fs:99-104 | equinox-shipping/Watchdog/SourceArgs.fs:95-100 | propulsion-hotel/Reactor/SourceArgs.fs:47-52 | propulsion-projector/Args.fs:93-98 | propulsion-projector/SourceArgs.fs:113-118 | propulsion-reactor/Args.fs:102-107 | propulsion-reactor/SourceArgs.fs:185-190 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (3–6 lines × 7) equinox-shipping/Watchdog/Infrastructure.fs:50— equinox-shipping/Watchdog/Infrastructure.fs:50-52 | propulsion-archiver/Infrastructure.fs:116-121 | propulsion-indexer/App/Infrastructure.fs:104-109 | propulsion-projector/Infrastructure.fs:52-57 | propulsion-pruner/Infrastructure.fs:58-63 | propulsion-reactor/Infrastructure.fs:79-81 | propulsion-sync/Infrastructure.fs:84-89 — before extracting anything, compare `equinox-shipping/Watchdog/Infrastructure.fs` and `propulsion-archiver/Infrastructure.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 55 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `propulsion-archiver/Infrastructure.fs:116` calls `CreateAndInitialize` and `equinox-shipping/Watchdog/Infrastructure.fs:50` 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 (2–6 lines × 11) equinox-shipping/Watchdog/Args.fs:68— equinox-shipping/Watchdog/Args.fs:68-70 | equinox-shipping/Watchdog/SourceArgs.fs:48-49 | equinox-testbed/Storage.fs:55-56 | feed-consumer/Program.fs:86-88 | feed-source/FeedApi/Program.fs:59-64 | periodic-ingester/Program.fs:99-104 | propulsion-projector/Args.fs:62-64 | propulsion-projector/SourceArgs.fs:64-65 | propulsion-pruner/Program.fs:131-132 | propulsion-reactor/Args.fs:72-73 | propulsion-reactor/SourceArgs.fs:121-122 — before extracting anything, compare `equinox-shipping/Watchdog/Args.fs` and `equinox-shipping/Watchdog/SourceArgs.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feed-source/FeedApi/Program.fs:58` calls `GetResult`, `fun` and `equinox-shipping/Watchdog/Args.fs:67` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (4–5 lines × 3) feed-consumer/Program.fs:92— feed-consumer/Program.fs:92-95 | periodic-ingester/Program.fs:101-105 | propulsion-tracking-consumer/Program.fs:79-83 — `feed-consumer/Program.fs` and `periodic-ingester/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 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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, `periodic-ingester/Program.fs:105` calls `GetEntryAssembly`, `GetName` and `feed-consumer/Program.fs:95` 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 (2–5 lines × 3) propulsion-archiver/Program.fs:91— propulsion-archiver/Program.fs:91-95 | propulsion-pruner/Program.fs:80-84 | propulsion-sync/Program.fs:160-161 — `propulsion-archiver/Program.fs` and `propulsion-pruner/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 13 separate duplicated blocks between them, totalling at least 124 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 after the matched lines, `propulsion-archiver/Program.fs:95` calls `CosmosSourceArguments` and `propulsion-sync/Program.fs:161` 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 (5 lines × 6) equinox-testbed/Infrastructure.fs:44— equinox-testbed/Infrastructure.fs:44-48 | feed-consumer/Infrastructure.fs:37-41 | feed-source/FeedApi/Infrastructure.fs:29-33 | periodic-ingester/Infrastructure.fs:41-45 | propulsion-summary-consumer/Infrastructure.fs:64-68 | propulsion-tracking-consumer/Infrastructure.fs:38-42 — before extracting anything, compare `feed-consumer/Infrastructure.fs` and `feed-source/FeedApi/Infrastructure.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 62 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 (22 lines × 2) equinox-shipping/Watchdog.Integration/ReactorFixture.fs:36— equinox-shipping/Watchdog.Integration/ReactorFixture.fs:36-57 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:29-50 — before extracting anything, compare `equinox-shipping/Watchdog.Integration/ReactorFixture.fs` and `propulsion-hotel/Reactor.Integration/ReactorFixture.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (3–14 lines × 3) equinox-shipping/Watchdog.Integration/ReactorFixture.fs:109— equinox-shipping/Watchdog.Integration/ReactorFixture.fs:109-122 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:75-88 | propulsion-hotel/Reactor.Integration/ReactorFixture.fs:102-104 — before extracting anything, compare `equinox-shipping/Watchdog.Integration/ReactorFixture.fs` and `propulsion-hotel/Reactor.Integration/ReactorFixture.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `propulsion-hotel/Reactor.Integration/ReactorFixture.fs:102` 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.
End-of-life runtime: .NET net6.0 equinox-web-csharp/Web/Web.csproj:4— equinox-web-csharp/Web/Web.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-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: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences 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.
DM12 · Ambient inputs in the domain· Domain type reads the wall clock · ×1
Domain type reads the wall clock: Service equinox-testbed/Services.fs:68— `Service` reads `DateTimeOffset.Now` inside `Favorite`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
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.
Orphaned file propulsion-projector/SourceArgs.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-reactor/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-shipping/Watchdog/SourceArgs.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-archiver/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-consumer/Examples.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-pruner/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file periodic-ingester/Infrastructure.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file feed-consumer/Infrastructure.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-indexer/Domain/Store.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-testbed/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-projector/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-indexer/App/Infrastructure.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-web-csharp/Domain/Todo.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-hotel/Reactor/SourceArgs.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file periodic-ingester/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-shipping/Watchdog.Integration/ReactorFixture.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-patterns/Domain/Period.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file feed-source/Domain/TicketsIngester.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-shipping/Watchdog/Program.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file equinox-shipping/Watchdog/Args.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-reactor/Infrastructure.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-indexer/App/Args.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-reactor/Args.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file propulsion-archiver/Infrastructure.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
README/code drift README.md:939— README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift README.md:69— README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists. 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 README.md:71— README.md names the project `Equinox.EventStore`, but no project, folder or namespace of that name exists. 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 README.md:73— README.md links to `propulsion-archiver/README.md`, but `propulsion-archiver/README.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 README.md:76— README.md links to `propulsion-pruner/README.md`, but `propulsion-pruner/README.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 README.md:84— README.md links to `propulsion-cosmos-reactor/README.md`, but `propulsion-cosmos-reactor/README.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 README.md:731— README.md links to `do-simplest-result`, but `do-simplest-result` 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 equinox-testbed/README.md:45— equinox-testbed/README.md names the project `Equinox.Cosmos`, but no project, folder or namespace of that name exists. 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 propulsion-hotel/README.md:168— propulsion-hotel/README.md documents the environment variable `CONNSTR`, 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 propulsion-hotel/README.md:169— propulsion-hotel/README.md documents the environment variable `CPCONNSTR`, 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 propulsion-indexer/Indexer/README.md:250— propulsion-indexer/Indexer/README.md runs `dotnet run --project Indexer -- -g deployYYMMDD snapshot` from `propulsion-indexer/Indexer/` or the repository root, but `Indexer` is not there: the project is `propulsion-indexer/Indexer`. 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.
Outdated: Serilog.Sinks.Seq REDACTED:31— Serilog.Sinks.Seq 4.0.0 → 9.1.0 available (referenced by Sync).
Outdated: prometheus-net.AspNetCore equinox-web-csharp/Web/Web.csproj:14— prometheus-net.AspNetCore 3.6.0 → 8.2.1 available (referenced by Web).
Outdated: Serilog.AspNetCore equinox-web-csharp/Web/Web.csproj:15— Serilog.AspNetCore 3.2.0 → 10.0.0 available (referenced by Web).
Outdated: Microsoft.Extensions.DependencyInjection REDACTED:29— Microsoft.Extensions.DependencyInjection 5.0.2 → 10.0.13 available (referenced by Testbed).
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file propulsion-sync/Program.fs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file propulsion-indexer/Indexer/Program.fs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file propulsion-reactor/SourceArgs.fs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Dormant codebase — 94 of 94 significant files have no living knowledge — the codebase as a whole is dormant, not 94 separate risks. Counted over 94 of the 146 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
IL efficiency: 49 authored method(s) exceed the IL budget propulsion-sync/Program.fs:235— 49 of 2362 first-party methods compile to oversized IL bodies (> 250 instructions); worst: SyncTemplate.Program/Args/EsSourceArguments..ctor @ propulsion-sync/Program.fs:235, 966 IL instructions; that pulled this dimension to 9.6/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
Commented-out code equinox-web-csharp/Web/Startup.cs:112— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 22/25 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `equinox-shipping/Watchdog.Integration`, `equinox-shipping/Watchdog.Lambda.Cdk`, `propulsion-dynamostore-cdk`.
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
S1 · Web-Security Posture· No inbound model validation detected · ×1
No inbound model validation detected — No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
Duplicated predicate equinox-web/Domain/Aggregate.fs:50— `memoryStore || (!cosmos && !dynamo && !eventStore)` appears character-identically in 3 files — equinox-web/Domain/Aggregate.fs, equinox-web/Domain/Store.fs, equinox-web/Domain/Todo.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.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 0/5 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Nullable reference types not enabled everywhere — 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
TodoBackendTemplate: 3 contract type(s) expose producer-owned ids/enums — In TodoBackendTemplate, 3 contract type(s) (ClearedData, DeletedData, SnapshottedData) expose strong-typed ids/value objects (ClearedData, DeletedData, SnapshottedData); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a16496-b25b-7500-815b-a8a0c2542eaa · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 11 · Warnings: 199 · Recommendations: 124 · Info: 23 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 17:09 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.