Public report of RayTale/Vertex, 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, 03:22 UTC · Survey ID cd_6ea722a8f83740bfb06757eebe3361b1
RayTale/Vertex
Measured 22 October 2026, 03:21 UTC, at code version c52f0ef
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 4 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A small codebase: 10,329 lines of product code in 20 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Maturity, 40
Findings by how serious they are
50 critical225 serious115 minor
3 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, 03:21 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 ▸
73of 78 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
339of 390 findings point to an exact file and line, so you can open each one in the code. The other 51 concern the repository as a whole, such as missing documentation.
78dimensions across 7 lenses, read from 10,329 lines of product code in 20 projects.
RayTale/Vertex scores 50 out of 100 and is rated Adequate, while five of its seven lenses score higher still: Architecture at 99, rated Exemplary, Event-Driven at 86 and Performance at 81, both rated Strong, and Security and Compliance and Production Readiness at 63, both rated Adequate.
The score is lower than those five because the weakest lens counts most, and here that is Maturity, which scores 40 and is rated Weak. 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 1 redundant comment finding(s) in Comment Value and to resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt, and if Maturity rose to 70, the score would rise from 50 to about 58.
50 findings are critical: 30 in Explicit Debt, 12 in Static Analysis (SAST), six in Dependency Vulnerabilities, one in Outbox / dual-write and one in Project dependency cycles.
Watchdog couldn't measure Test Reliability and License Compliance in this code, so those dimensions are left out of the score. The product code is 10,329 lines, which would take an estimated 0.2 person-years, around €35,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
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: 4 findings
These 4 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
€11,000 to €58,000, for 189 to 612 hours of work, about 0.2 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 50. 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: 10,329 lines of product code, of which 36% is declarations and boilerplate, 18% straight logic and 45% logic with branches
Comment lines
The estimate prices 9,759 lines. Comment lines count towards the size of 10,329 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 1 redundant comment finding(s) in Comment Value — start with MurmurHash2.cs.
Raises the score by about 6 points · Low effort · Comment Value
2
Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with EventStreamFactory.cs (3).
Raises the score by about 4 points · Low effort · Explicit Debt
3
Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4).
Raises the score by about 4 points · Low effort · Explicit Debt
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €35,000 to build again, about 0.2 person-years of work. Its weakest lens is Maturity, at 40 (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 1 redundant comment finding(s) in Comment Value. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 Comment Value 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.
62 modules, with 102 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 22 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.
Abstractions.EventStream uses Abstractions.Actor, so a change to Abstractions.Actor can break Abstractions.EventStream, while a change to Abstractions.EventStream can't break Abstractions.Actor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Abstractions.Snapshot uses Abstractions.Event, so a change to Abstractions.Event can break Abstractions.Snapshot, while a change to Abstractions.Snapshot can't break Abstractions.Event.
Position
Below the diagonal: Abstractions.Snapshot uses a module listed above it, which is the healthy direction.
Runtime.Event uses Abstractions.Event, so a change to Abstractions.Event can break Runtime.Event, while a change to Runtime.Event can't break Abstractions.Event.
Position
Below the diagonal: Runtime.Event uses a module listed above it, which is the healthy direction.
Runtime.Serialization uses Abstractions.Event, so a change to Abstractions.Event can break Runtime.Serialization, while a change to Runtime.Serialization can't break Abstractions.Event.
Position
Below the diagonal: Runtime.Serialization uses a module listed above it, which is the healthy direction.
Runtime.Serialization uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Runtime.Serialization, while a change to Runtime.Serialization can't break Abstractions.Serialization.
Position
Below the diagonal: Runtime.Serialization uses a module listed above it, which is the healthy direction.
Storage.Linq2db uses Storage.Linq2db.Core, so a change to Storage.Linq2db.Core can break Storage.Linq2db, while a change to Storage.Linq2db can't break Storage.Linq2db.Core.
Position
Below the diagonal: Storage.Linq2db uses a module listed above it, which is the healthy direction.
Storage.Linq2db uses Storage.Linq2db.Options, so a change to Storage.Linq2db.Options can break Storage.Linq2db, while a change to Storage.Linq2db can't break Storage.Linq2db.Options.
Position
Below the diagonal: Storage.Linq2db uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Db uses Storage.Linq2db.Entities, so a change to Storage.Linq2db.Entities can break Storage.Linq2db.Db, while a change to Storage.Linq2db.Db can't break Storage.Linq2db.Entities.
Position
Below the diagonal: Storage.Linq2db.Db uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Db uses Storage.Linq2db.Options, so a change to Storage.Linq2db.Options can break Storage.Linq2db.Db, while a change to Storage.Linq2db.Db can't break Storage.Linq2db.Options.
Position
Below the diagonal: Storage.Linq2db.Db uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ.Client uses Stream.RabbitMQ.Options, so a change to Stream.RabbitMQ.Options can break Stream.RabbitMQ.Client, while a change to Stream.RabbitMQ.Client can't break Stream.RabbitMQ.Options.
Position
Below the diagonal: Stream.RabbitMQ.Client uses a module listed above it, which is the healthy direction.
Transaction.Events uses Abstractions.Event, so a change to Abstractions.Event can break Transaction.Events, while a change to Transaction.Events can't break Abstractions.Event.
Position
Below the diagonal: Transaction.Events uses a module listed above it, which is the healthy direction.
Transaction.Events uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Transaction.Events, while a change to Transaction.Events can't break Abstractions.Serialization.
Position
Below the diagonal: Transaction.Events uses a module listed above it, which is the healthy direction.
Transaction.Events.TxUnit uses Abstractions.Event, so a change to Abstractions.Event can break Transaction.Events.TxUnit, while a change to Transaction.Events.TxUnit can't break Abstractions.Event.
Position
Below the diagonal: Transaction.Events.TxUnit uses a module listed above it, which is the healthy direction.
Transaction.Events.TxUnit uses Transaction.Abstractions, so a change to Transaction.Abstractions can break Transaction.Events.TxUnit, while a change to Transaction.Events.TxUnit can't break Transaction.Abstractions.
Position
Below the diagonal: Transaction.Events.TxUnit uses a module listed above it, which is the healthy direction.
Abstractions.Actor uses Abstractions.Event, so a change to Abstractions.Event can break Abstractions.Actor, while a change to Abstractions.Actor can't break Abstractions.Event.
Position
Below the diagonal: Abstractions.Actor uses a module listed above it, which is the healthy direction.
Abstractions.Actor uses Abstractions.EventStream, so a change to Abstractions.EventStream can break Abstractions.Actor, while a change to Abstractions.Actor can't break Abstractions.EventStream.
Position
Below the diagonal: Abstractions.Actor uses a module listed above it, which is the healthy direction.
Runtime.Snapshot uses Abstractions.Attributes, so a change to Abstractions.Attributes can break Runtime.Snapshot, while a change to Runtime.Snapshot can't break Abstractions.Attributes.
Position
Below the diagonal: Runtime.Snapshot uses a module listed above it, which is the healthy direction.
Runtime.Snapshot uses Abstractions.Event, so a change to Abstractions.Event can break Runtime.Snapshot, while a change to Runtime.Snapshot can't break Abstractions.Event.
Position
Below the diagonal: Runtime.Snapshot uses a module listed above it, which is the healthy direction.
Runtime.Snapshot uses Abstractions.Snapshot, so a change to Abstractions.Snapshot can break Runtime.Snapshot, while a change to Runtime.Snapshot can't break Abstractions.Snapshot.
Position
Below the diagonal: Runtime.Snapshot uses a module listed above it, which is the healthy direction.
Stream.Common uses Abstractions.EventStream, so a change to Abstractions.EventStream can break Stream.Common, while a change to Stream.Common can't break Abstractions.EventStream.
Position
Below the diagonal: Stream.Common uses a module listed above it, which is the healthy direction.
Transaction.Abstractions.Snapshot uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Transaction.Abstractions.Snapshot, while a change to Transaction.Abstractions.Snapshot can't break Abstractions.Serialization.
Position
Below the diagonal: Transaction.Abstractions.Snapshot uses a module listed above it, which is the healthy direction.
Transaction.Abstractions.Snapshot uses Transaction.Abstractions, so a change to Transaction.Abstractions can break Transaction.Abstractions.Snapshot, while a change to Transaction.Abstractions.Snapshot can't break Transaction.Abstractions.
Position
Below the diagonal: Transaction.Abstractions.Snapshot uses a module listed above it, which is the healthy direction.
Transaction.Abstractions.Snapshot uses Abstractions.Snapshot, so a change to Abstractions.Snapshot can break Transaction.Abstractions.Snapshot, while a change to Transaction.Abstractions.Snapshot can't break Abstractions.Snapshot.
Position
Below the diagonal: Transaction.Abstractions.Snapshot uses a module listed above it, which is the healthy direction.
Abstractions.Storage uses Abstractions.Event, so a change to Abstractions.Event can break Abstractions.Storage, while a change to Abstractions.Storage can't break Abstractions.Event.
Position
Below the diagonal: Abstractions.Storage uses a module listed above it, which is the healthy direction.
Abstractions.Storage uses Abstractions.Snapshot, so a change to Abstractions.Snapshot can break Abstractions.Storage, while a change to Abstractions.Storage can't break Abstractions.Snapshot.
Position
Below the diagonal: Abstractions.Storage uses a module listed above it, which is the healthy direction.
Abstractions.Storage uses Abstractions.Actor, so a change to Abstractions.Actor can break Abstractions.Storage, while a change to Abstractions.Storage can't break Abstractions.Actor.
Position
Below the diagonal: Abstractions.Storage uses a module listed above it, which is the healthy direction.
Stream.InMemory uses Stream.InMemory.Options, so a change to Stream.InMemory.Options can break Stream.InMemory, while a change to Stream.InMemory can't break Stream.InMemory.Options.
Position
Below the diagonal: Stream.InMemory uses a module listed above it, which is the healthy direction.
Stream.InMemory uses Abstractions.EventStream, so a change to Abstractions.EventStream can break Stream.InMemory, while a change to Stream.InMemory can't break Abstractions.EventStream.
Position
Below the diagonal: Stream.InMemory uses a module listed above it, which is the healthy direction.
Stream.InMemory uses Abstractions.Actor, so a change to Abstractions.Actor can break Stream.InMemory, while a change to Stream.InMemory can't break Abstractions.Actor.
Position
Below the diagonal: Stream.InMemory uses a module listed above it, which is the healthy direction.
Stream.InMemory uses Stream.Common, so a change to Stream.Common can break Stream.InMemory, while a change to Stream.InMemory can't break Stream.Common.
Position
Below the diagonal: Stream.InMemory uses a module listed above it, which is the healthy direction.
Stream.InMemory.Consumer uses Stream.InMemory.Options, so a change to Stream.InMemory.Options can break Stream.InMemory.Consumer, while a change to Stream.InMemory.Consumer can't break Stream.InMemory.Options.
Position
Below the diagonal: Stream.InMemory.Consumer uses a module listed above it, which is the healthy direction.
Stream.InMemory.Consumer uses Stream.Common, so a change to Stream.Common can break Stream.InMemory.Consumer, while a change to Stream.InMemory.Consumer can't break Stream.Common.
Position
Below the diagonal: Stream.InMemory.Consumer uses a module listed above it, which is the healthy direction.
Stream.Kafka uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Stream.Kafka, while a change to Stream.Kafka can't break Abstractions.Serialization.
Position
Below the diagonal: Stream.Kafka uses a module listed above it, which is the healthy direction.
Stream.Kafka uses Stream.Kafka.Options, so a change to Stream.Kafka.Options can break Stream.Kafka, while a change to Stream.Kafka can't break Stream.Kafka.Options.
Position
Below the diagonal: Stream.Kafka uses a module listed above it, which is the healthy direction.
Stream.Kafka uses Abstractions.EventStream, so a change to Abstractions.EventStream can break Stream.Kafka, while a change to Stream.Kafka can't break Abstractions.EventStream.
Position
Below the diagonal: Stream.Kafka uses a module listed above it, which is the healthy direction.
Stream.Kafka uses Abstractions.Actor, so a change to Abstractions.Actor can break Stream.Kafka, while a change to Stream.Kafka can't break Abstractions.Actor.
Position
Below the diagonal: Stream.Kafka uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ uses Stream.RabbitMQ.Options, so a change to Stream.RabbitMQ.Options can break Stream.RabbitMQ, while a change to Stream.RabbitMQ can't break Stream.RabbitMQ.Options.
Position
Below the diagonal: Stream.RabbitMQ uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ uses Abstractions.EventStream, so a change to Abstractions.EventStream can break Stream.RabbitMQ, while a change to Stream.RabbitMQ can't break Abstractions.EventStream.
Position
Below the diagonal: Stream.RabbitMQ uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ uses Stream.RabbitMQ.Client, so a change to Stream.RabbitMQ.Client can break Stream.RabbitMQ, while a change to Stream.RabbitMQ can't break Stream.RabbitMQ.Client.
Position
Below the diagonal: Stream.RabbitMQ uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ uses Abstractions.Actor, so a change to Abstractions.Actor can break Stream.RabbitMQ, while a change to Stream.RabbitMQ can't break Abstractions.Actor.
Position
Below the diagonal: Stream.RabbitMQ uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ uses Stream.Common, so a change to Stream.Common can break Stream.RabbitMQ, while a change to Stream.RabbitMQ can't break Stream.Common.
Position
Below the diagonal: Stream.RabbitMQ uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ.Consumer uses Stream.RabbitMQ.Options, so a change to Stream.RabbitMQ.Options can break Stream.RabbitMQ.Consumer, while a change to Stream.RabbitMQ.Consumer can't break Stream.RabbitMQ.Options.
Position
Below the diagonal: Stream.RabbitMQ.Consumer uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ.Consumer uses Stream.RabbitMQ.Client, so a change to Stream.RabbitMQ.Client can break Stream.RabbitMQ.Consumer, while a change to Stream.RabbitMQ.Consumer can't break Stream.RabbitMQ.Client.
Position
Below the diagonal: Stream.RabbitMQ.Consumer uses a module listed above it, which is the healthy direction.
Stream.RabbitMQ.Consumer uses Stream.Common, so a change to Stream.Common can break Stream.RabbitMQ.Consumer, while a change to Stream.RabbitMQ.Consumer can't break Stream.Common.
Position
Below the diagonal: Stream.RabbitMQ.Consumer uses a module listed above it, which is the healthy direction.
Transaction.Abstractions.IActor uses Abstractions.Actor, so a change to Abstractions.Actor can break Transaction.Abstractions.IActor, while a change to Transaction.Abstractions.IActor can't break Abstractions.Actor.
Position
Below the diagonal: Transaction.Abstractions.IActor uses a module listed above it, which is the healthy direction.
Transaction.Abstractions.Storage uses Abstractions.Event, so a change to Abstractions.Event can break Transaction.Abstractions.Storage, while a change to Transaction.Abstractions.Storage can't break Abstractions.Event.
Position
Below the diagonal: Transaction.Abstractions.Storage uses a module listed above it, which is the healthy direction.
Transaction.Abstractions.Storage uses Abstractions.Actor, so a change to Abstractions.Actor can break Transaction.Abstractions.Storage, while a change to Transaction.Abstractions.Storage can't break Abstractions.Actor.
Position
Below the diagonal: Transaction.Abstractions.Storage uses a module listed above it, which is the healthy direction.
Transaction.Snapshot uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Transaction.Snapshot, while a change to Transaction.Snapshot can't break Abstractions.Serialization.
Position
Below the diagonal: Transaction.Snapshot uses a module listed above it, which is the healthy direction.
Transaction.Snapshot uses Transaction.Abstractions, so a change to Transaction.Abstractions can break Transaction.Snapshot, while a change to Transaction.Snapshot can't break Transaction.Abstractions.
Position
Below the diagonal: Transaction.Snapshot uses a module listed above it, which is the healthy direction.
Transaction.Snapshot uses Transaction.Events.TxUnit, so a change to Transaction.Events.TxUnit can break Transaction.Snapshot, while a change to Transaction.Snapshot can't break Transaction.Events.TxUnit.
Position
Below the diagonal: Transaction.Snapshot uses a module listed above it, which is the healthy direction.
Transaction.Snapshot uses Runtime.Snapshot, so a change to Runtime.Snapshot can break Transaction.Snapshot, while a change to Transaction.Snapshot can't break Runtime.Snapshot.
Position
Below the diagonal: Transaction.Snapshot uses a module listed above it, which is the healthy direction.
Transaction.Snapshot uses Transaction.Abstractions.Snapshot, so a change to Transaction.Abstractions.Snapshot can break Transaction.Snapshot, while a change to Transaction.Snapshot can't break Transaction.Abstractions.Snapshot.
Position
Below the diagonal: Transaction.Snapshot uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.Attributes, so a change to Abstractions.Attributes can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.Attributes.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.Event, so a change to Abstractions.Event can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.Event.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.Serialization.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.EventStream, so a change to Abstractions.EventStream can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.EventStream.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.Snapshot, so a change to Abstractions.Snapshot can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.Snapshot.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.Actor, so a change to Abstractions.Actor can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.Actor.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Runtime.Actor uses Abstractions.Storage, so a change to Abstractions.Storage can break Runtime.Actor, while a change to Runtime.Actor can't break Abstractions.Storage.
Position
Below the diagonal: Runtime.Actor uses a module listed above it, which is the healthy direction.
Storage.EFCore.Storage uses Abstractions.Event, so a change to Abstractions.Event can break Storage.EFCore.Storage, while a change to Storage.EFCore.Storage can't break Abstractions.Event.
Position
Below the diagonal: Storage.EFCore.Storage uses a module listed above it, which is the healthy direction.
Storage.EFCore.Storage uses Storage.Linq2db.Entities, so a change to Storage.Linq2db.Entities can break Storage.EFCore.Storage, while a change to Storage.EFCore.Storage can't break Storage.Linq2db.Entities.
Position
Below the diagonal: Storage.EFCore.Storage uses a module listed above it, which is the healthy direction.
Storage.EFCore.Storage uses Utils.Channels, so a change to Utils.Channels can break Storage.EFCore.Storage, while a change to Storage.EFCore.Storage can't break Utils.Channels.
Position
Below the diagonal: Storage.EFCore.Storage uses a module listed above it, which is the healthy direction.
Storage.EFCore.Storage uses Storage.Linq2db.Db, so a change to Storage.Linq2db.Db can break Storage.EFCore.Storage, while a change to Storage.EFCore.Storage can't break Storage.Linq2db.Db.
Position
Below the diagonal: Storage.EFCore.Storage uses a module listed above it, which is the healthy direction.
Storage.EFCore.Storage uses Abstractions.Storage, so a change to Abstractions.Storage can break Storage.EFCore.Storage, while a change to Storage.EFCore.Storage can't break Abstractions.Storage.
Position
Below the diagonal: Storage.EFCore.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Abstractions.Event, so a change to Abstractions.Event can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Abstractions.Event.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Abstractions.Serialization, so a change to Abstractions.Serialization can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Abstractions.Serialization.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Storage.Linq2db.Core, so a change to Storage.Linq2db.Core can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Storage.Linq2db.Core.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Storage.Linq2db.Entities, so a change to Storage.Linq2db.Entities can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Storage.Linq2db.Entities.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Utils.Channels, so a change to Utils.Channels can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Utils.Channels.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Abstractions.Snapshot, so a change to Abstractions.Snapshot can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Abstractions.Snapshot.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Storage.Linq2db.Db, so a change to Storage.Linq2db.Db can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Storage.Linq2db.Db.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Abstractions.Actor, so a change to Abstractions.Actor can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Abstractions.Actor.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Abstractions.Storage, so a change to Abstractions.Storage can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Abstractions.Storage.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Storage.Linq2db.Storage uses Transaction.Abstractions.Storage, so a change to Transaction.Abstractions.Storage can break Storage.Linq2db.Storage, while a change to Storage.Linq2db.Storage can't break Transaction.Abstractions.Storage.
Position
Below the diagonal: Storage.Linq2db.Storage uses a module listed above it, which is the healthy direction.
Stream.Kafka.Consumer uses Stream.Kafka.Options, so a change to Stream.Kafka.Options can break Stream.Kafka.Consumer, while a change to Stream.Kafka.Consumer can't break Stream.Kafka.Options.
Position
Below the diagonal: Stream.Kafka.Consumer uses a module listed above it, which is the healthy direction.
Stream.Kafka.Consumer uses Stream.Common, so a change to Stream.Common can break Stream.Kafka.Consumer, while a change to Stream.Kafka.Consumer can't break Stream.Common.
Position
Below the diagonal: Stream.Kafka.Consumer uses a module listed above it, which is the healthy direction.
Stream.Kafka.Consumer uses Stream.Kafka, so a change to Stream.Kafka can break Stream.Kafka.Consumer, while a change to Stream.Kafka.Consumer can't break Stream.Kafka.
Position
Below the diagonal: Stream.Kafka.Consumer uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Abstractions.Event, so a change to Abstractions.Event can break Transaction.Actor, while a change to Transaction.Actor can't break Abstractions.Event.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Transaction.Abstractions, so a change to Transaction.Abstractions can break Transaction.Actor, while a change to Transaction.Actor can't break Transaction.Abstractions.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Utils.Channels, so a change to Utils.Channels can break Transaction.Actor, while a change to Transaction.Actor can't break Utils.Channels.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Abstractions.Snapshot, so a change to Abstractions.Snapshot can break Transaction.Actor, while a change to Transaction.Actor can't break Abstractions.Snapshot.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Transaction.Events, so a change to Transaction.Events can break Transaction.Actor, while a change to Transaction.Actor can't break Transaction.Events.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Transaction.Abstractions.Snapshot, so a change to Transaction.Abstractions.Snapshot can break Transaction.Actor, while a change to Transaction.Actor can't break Transaction.Abstractions.Snapshot.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Transaction.Abstractions.IActor, so a change to Transaction.Abstractions.IActor can break Transaction.Actor, while a change to Transaction.Actor can't break Transaction.Abstractions.IActor.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Transaction.Abstractions.Storage, so a change to Transaction.Abstractions.Storage can break Transaction.Actor, while a change to Transaction.Actor can't break Transaction.Abstractions.Storage.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
Transaction.Actor uses Runtime.Actor, so a change to Runtime.Actor can break Transaction.Actor, while a change to Transaction.Actor can't break Runtime.Actor.
Position
Below the diagonal: Transaction.Actor uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 47% · Weak · 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
15
High / Critical
A05:2025 — Injection
14
High / Critical
Roadmap
Begin by resolving the 36 orphaned files in Knowledge Freshness, prioritizing ConsumerManager.cs, ConsumerRunner.cs, and EventStreamFactory.cs, and address the 23 explicit debt issues in .editorconfig. Simultaneously, eliminate the redundant comment in MurmurHash2 and expand the README with essential getting-started and architecture details. Finally, establish a structured ADR folder to document significant design decisions, ensuring each entry captures the date, context, decision, and consequences.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 redundant comment finding(s) in Comment Value — start with MurmurHash2.cs.
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.
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 — 50
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 — 225
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 — 115
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 3
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. 73 of 78 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 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 — 78 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, 339 of 390 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 included — no test tier completed within its budget.
D14 License Compliance — 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. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
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.
X2 Cancellation propagation — 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. 95 further occurrence(s) are not listed individually; the score already reflects all 135.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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.
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.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (5): D19, D21, D24, 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.
Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with FlowActor.FlowActor.ctor (cyclomatic 38), SnapshotHandlerBase.SnapshotHandlerBase.ctor (cyclomatic 32), EventArchive.GetList (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with FlowActor.FlowActor.ctor (cognitive 64), SnapshotHandlerBase.SnapshotHandlerBase.ctor (cognitive 54), EventArchive.GetList (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.3 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God 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 MethodTooLong finding(s) in God Classes — start with FlowActor.cs. — 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.
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.
55 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 3 of the 58 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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with BufferBlockChannel.cs (2), ShadowActor.cs, EventArchive.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with EventStorage.cs (2), FlowActor.cs, BufferBlockChannel.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with EventStorage.cs, EventStorageFactory.cs, SnapshotStorage.cs. — One of this dimension's main actionable groups (3 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 · Coupling9.2 / 10Stronggated by 2 serious findings✓ 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.
Off the main sequence: Vertex.Utils · ×2src/Vertex.Utils/Vertex.Utils.csproj:1
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling — start with Vertex.Utils.csproj, Vertex.Protocol.csproj. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 Low coverage finding(s) in Code Coverage — start with ManualResetValueTaskSource.cs, PooledTaskSourcePolicy.cs, TxSnapshotException.cs. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 2 CRAP 56 finding(s) in Code Coverage — start with ShadowActor.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 No test project references Vertex.Stream.Kafka finding(s) in Code Coverage — start with Vertex.Stream.Kafka.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
62 test methods: 62 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
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 Deprecated finding(s) in Dependency Hygiene — start with Vertex.Utils.Test.csproj, REDACTED, Vertex.Runtime.Test.csproj. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — 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.
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: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Vertex.Runtime/Actor/ShadowActor.cs. Counted over 26 of the 196 production source files in this repository: 158 are under the ~2,400-byte size floor this dimension measures over, and the remaining 12 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D17 · Explicit Debt4.2 / 10Weak✓ Tool-verified
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.
Resolve the 23 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (23). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with EventStreamFactory.cs (3). — One of this dimension's main actionable groups (3 issue-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 solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
20 projects, 288 source files, 13699 hand-written lines of code (10329 production / 3370 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 47 inter-project edges.
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.
This is a single README.md file (the repository root) that describes Vertex as an Orleans-based distributed framework with event sourcing for high-throughput, low-latency, and eventual-consistency transactional applications. It gives a strong overview of the project's purpose and origins, explains what it does (distributed actors, saga/event sourcing), and lists core features. The document is well written but clipped mid-sentence in its outline; no installation, usage, or contribution guidance is present for the repository as a whole.
Resolve the 15 Low XML-doc coverage finding(s) in Documentation Quality — start with Vertex.Abstractions.csproj, Vertex.Runtime.csproj, Vertex.Transaction.Abstractions.csproj. — One of this dimension's main actionable groups (15 warning-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
2 naming inconsistencies across 200 sampled symbols.
Inconsistent spelling of 'Committed': 'OnTxCommited' and 'TxCommitedEvent' use the non-standard spelling 'Commited' (missing one 't'), whereas the standard English spelling is 'Committed'.
Inconsistent spelling of 'TopUp': The test method 'Tx_Topup_Rollback_1' uses 'Topup' (lowercase 'u' and missing 'U' capitalization if following PascalCase, or just inconsistent casing/spelling) while the actual implementation methods use 'TopUp'.
What to do
Resolve the 1 Inconsistent spelling of 'Committed' finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Inconsistent spelling of 'TopUp' finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueAdequate◐ 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.
Resolve the 1 redundant comment finding(s) in Comment Value — start with MurmurHash2.cs. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 20 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability8.6 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
85 % of calls cross a namespace and 14 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What to do
Improve Navigability — currently 8.6/10. — 85 % of calls cross a namespace and 14 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
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).
14 finding(s): 0 critical, 12 high, 2 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-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.
38 of 38 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Vertex.Runtime/Actor/FlowActor.cs. Counted over 38 of the 196 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×2src/Vertex.Runtime/Actor/FlowActor.cs:1
Dormant codebase
What to do
Resolve the 36 Orphaned file finding(s) in Knowledge Freshness — start with ConsumerManager.cs (3), ConsumerRunner.cs (3), EventStreamFactory.cs (2). — One of this dimension's main actionable groups (36 recommendation-level).
Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with FlowActor.cs, VertexActor.cs. — One of this dimension's main actionable groups (2 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 build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D39 · IL Efficiency9.9 / 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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — 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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
The namespaces Vertex.Abstractions.Actor ↔ Vertex.Abstractions.EventStream depend on each other. The lightest dependency in the cycle is Vertex.Abstractions.Actor → Vertex.Abstractions.EventStream (Vertex.Abstractions.Actor.IFlowActor → Vertex.Abstractions.EventStream.IStreamHandler, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Vertex.Abstractions/Actor/IFlowActor.cs:1
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
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 · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`FlowActor.SaveSnapshotToDbAsync` writes to the database while `FlowActor` publishes to the message bus in the same command-handling flow, with no outbox referenced on either path. Splitting the persist and the publish across sibling methods (or two collaborating actors) doesn't make them atomic — a crash between the two either loses the message or emits a phantom event. Use the transactional outbox pattern so the message is committed in the same transaction as the state change and dispatched afterwards. — src/Vertex.Runtime/Actor/FlowActor.cs:785
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
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.
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.
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.
The root README is 55 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 20 of 20 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.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2958 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
P9 · Domain vs controller coverage10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.
Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
9 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×9) — src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:86, src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:87, src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:88, …
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
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.
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×2) — src/Vertex.Utils/Channels/BufferBlockChannel.cs:117, src/Vertex.Utils/Channels/ThreadChannel.cs:119
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×9) — src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:86, src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:87, src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:88, …
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 11/145 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. (×39) — src/Vertex.Runtime/Actor/FlowActor.cs:344, src/Vertex.Runtime/Actor/FlowActor.cs:411, src/Vertex.Runtime/Actor/FlowActor.cs:466, …
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.
The guard on line 287 rejects `flowId` and line 289 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(flowId)` is true of a value that is NOT null: it is satisfied by an EMPTY `flowId`, and on that path `flowId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Vertex.Runtime/Actor/VertexActor.cs:289
The guard on line 291 rejects `flowId` and line 293 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(flowId)` is true of a value that is NOT null: it is satisfied by an EMPTY `flowId`, and on that path `flowId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Vertex.Transaction/Actor/InnerTxActor.cs:293
The guard on line 48 rejects `flowId` and line 50 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(flowId)` is true of a value that is NOT null: it is satisfied by an EMPTY `flowId`, and on that path `flowId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Vertex.Transaction/Actor/ReentryActor.cs:50
The guard on line 99 rejects `txId` and line 101 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(txId)` is true of a value that is NOT null: it is satisfied by an EMPTY `txId`, and on that path `txId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Vertex.Transaction/Actor/ReentryDTxActor.cs:101
The guard on line 110 rejects `txId` and line 112 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(txId)` is true of a value that is NOT null: it is satisfied by an EMPTY `txId`, and on that path `txId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Vertex.Transaction/Actor/ReentryDTxActor.cs:112
The guard on line 120 rejects `txId` and line 122 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(txId)` is true of a value that is NOT null: it is satisfied by an EMPTY `txId`, and on that path `txId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Vertex.Transaction/Actor/ReentryDTxActor.cs:122
What to do
Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×16) — src/Vertex.Transaction/Actor/DTxActor.cs:129, src/Vertex.Transaction/Actor/InnerTxActor.cs:100, src/Vertex.Transaction/Actor/InnerTxActor.cs:185, …
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/16 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 — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 42 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.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
AXB2 Runtime readiness — 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 — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
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.
D11 Test Reliability — Test reliability not included
D14 License Compliance — Licence collector did not produce a result
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — small single-context codebase (10,329 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
ED3 Event naming — no domain or integration events detected — event-naming check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
P8 Schema migrations — no EF Core usage detected
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
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.
AnalyzerSeverityNone .editorconfig:4— SA1200 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:5— SA1600 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:6— CS1591 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:8— SA1633 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:10— SA1202 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:12— SA1623 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:14— SA1629 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:16— SA1316 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:18— SA1116 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:20— SA1413 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:22— SA1513 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:24— SA1106 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:26— SA1616 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:28— CA1720 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:30— SA1602 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:32— SA1124 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:34— SA1129 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:36— SA1117 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:37— SA0001 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:39— IDE0022 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:41— CA1031 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:43— CA1062 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:45— CA2007 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
NoWarnInCsproj Directory.Build.props:24— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:24— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:24— 1705 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:24— 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
WriteOnlyPrivateField src/Stream/Vertex.Stream.InMemory/EventStreamFactory.cs:26— private ConcurrentDictionary<Type, ConsistentHash> hashDict — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Stream/Vertex.Stream.RabbitMQ/EventStreamFactory.cs:18— private ConcurrentDictionary<Type, ConsistentHash> hashDict — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Stream/Vertex.Stream.RabbitMQ/EventStreamFactory.cs:20— private IGrainFactory grainFactory — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
Namespace dependency cycle src/Vertex.Abstractions/Actor/IFlowActor.cs:1— The namespaces Vertex.Abstractions.Actor ↔ Vertex.Abstractions.EventStream depend on each other. The lightest dependency in the cycle is Vertex.Abstractions.Actor → Vertex.Abstractions.EventStream (Vertex.Abstractions.Actor.IFlowActor → Vertex.Abstractions.EventStream.IStreamHandler, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Dual write (no outbox): FlowActor.SaveSnapshotToDbAsync persists, FlowActor publishes src/Vertex.Runtime/Actor/FlowActor.cs:785— `FlowActor.SaveSnapshotToDbAsync` writes to the database while `FlowActor` publishes to the message bus in the same command-handling flow, with no outbox referenced on either path. Splitting the persist and the publish across sibling methods (or two collaborating actors) doesn't make them atomic — a crash between the two either loses the message or emits a phantom event. Use the transactional outbox pattern so the message is committed in the same transaction as the state change and dispatched afterwards.
Serious — 225 finding(s)
X2 · Cancellation propagation· Async method without CancellationToken · ×39
Async method without CancellationToken: DependencyInjection src/Vertex.Runtime/Actor/FlowActor.cs:344— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadSnapshotAsync src/Vertex.Runtime/Actor/FlowActor.cs:411— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Recovery src/Vertex.Runtime/Actor/FlowActor.cs:466— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnNext src/Vertex.Runtime/Actor/FlowActor.cs:504— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnNext src/Vertex.Runtime/Actor/FlowActor.cs:543— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Tell src/Vertex.Runtime/Actor/FlowActor.cs:590— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConcurrentTell src/Vertex.Runtime/Actor/FlowActor.cs:637— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UnsafeTell src/Vertex.Runtime/Actor/FlowActor.cs:672— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveSnapshotAsync src/Vertex.Runtime/Actor/FlowActor.cs:727— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveSnapshotToDbAsync src/Vertex.Runtime/Actor/FlowActor.cs:785— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveSnapshotToCacheAsync src/Vertex.Runtime/Actor/FlowActor.cs:812— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DependencyInjection src/Vertex.Runtime/Actor/ShadowActor.cs:60— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RecoverySnapshot src/Vertex.Runtime/Actor/ShadowActor.cs:93— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadSnapshotAsync src/Vertex.Runtime/Actor/ShadowActor.cs:137— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnNext src/Vertex.Runtime/Actor/ShadowActor.cs:177— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnNext src/Vertex.Runtime/Actor/ShadowActor.cs:185— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Tell src/Vertex.Runtime/Actor/ShadowActor.cs:223— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: EventDelivered src/Vertex.Runtime/Actor/ShadowActor.cs:269— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DependencyInjection src/Vertex.Runtime/Actor/VertexActor.cs:72— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RecoverySnapshot src/Vertex.Runtime/Actor/VertexActor.cs:129— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadSnapshotAsync src/Vertex.Runtime/Actor/VertexActor.cs:169— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveSnapshotAsync src/Vertex.Runtime/Actor/VertexActor.cs:193— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RaiseEvent src/Vertex.Runtime/Actor/VertexActor.cs:282— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnRaiseStart src/Vertex.Runtime/Actor/VertexActor.cs:372— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Archive src/Vertex.Runtime/Actor/VertexActor.cs:423— No CancellationToken parameter — this work can't be stopped early once started.
Dead code: DeleteAll src/Vertex.Abstractions/Storage/IEventStorage.cs:63— Method DeleteAll — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Abstractions, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: UpdateMinEventTimestamp src/Vertex.Abstractions/Storage/ISnapshotStorage.cs:17— Method UpdateMinEventTimestamp — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Abstractions, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Delete src/Vertex.Abstractions/Storage/ISnapshotStorage.cs:21— Method Delete — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Abstractions, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Delete src/Vertex.Abstractions/Storage/ISubSnapshotStorage.cs:14— Method Delete — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Abstractions, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetEventId src/Vertex.Runtime/Actor/Extentions.cs:52— Method GetEventId — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Runtime, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CreateIndexIfNotExists src/Storage/Vertex.Storage.Linq2db/Index/IIndexGenerator.cs:10— Method CreateIndexIfNotExists — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Storage.Linq2db, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle examples/Transfer.Grains/Snapshot/AccountSnapshotHandler.cs:8— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Transfer.Grains, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle examples/Transfer.Grains/Snapshot/AccountSnapshotHandler.cs:13— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Transfer.Grains, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle examples/Transfer.Grains/Snapshot/AccountSnapshotHandler.cs:18— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Transfer.Grains, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle examples/Transfer.Grains/Snapshot/AccountSnapshotHandler.cs:23— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Transfer.Grains, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.Runtime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:9— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Runtime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.Runtime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:14— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Runtime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.Runtime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:19— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Runtime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.Runtime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:24— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Runtime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.Runtime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:29— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.Runtime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.TxRuntime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:9— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.TxRuntime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.TxRuntime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:14— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.TxRuntime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.TxRuntime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:19— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.TxRuntime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.TxRuntime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:24— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.TxRuntime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EventHandle test/Vertex.TxRuntime.Test/Biz/Snapshot/AccountSnapshotHandler.cs:29— Method EventHandle — Roslyn's SymbolFinder walked every project the solution loads, including Vertex.TxRuntime.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Sync-over-async blocking — 9 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:86— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:87— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:88— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:87— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:88— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:89— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:89— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:90— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:91— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:86— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:87— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:88— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:87— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:88— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:89— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:89— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:90— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:91— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×6
Argument guard throws the exception its own condition disproves src/Vertex.Runtime/Actor/VertexActor.cs:289— The guard on line 287 rejects `flowId` and line 289 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(flowId)` is true of a value that is NOT null: it is satisfied by an EMPTY `flowId`, and on that path `flowId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Vertex.Transaction/Actor/InnerTxActor.cs:293— The guard on line 291 rejects `flowId` and line 293 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(flowId)` is true of a value that is NOT null: it is satisfied by an EMPTY `flowId`, and on that path `flowId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Vertex.Transaction/Actor/ReentryActor.cs:50— The guard on line 48 rejects `flowId` and line 50 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(flowId)` is true of a value that is NOT null: it is satisfied by an EMPTY `flowId`, and on that path `flowId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Vertex.Transaction/Actor/ReentryDTxActor.cs:101— The guard on line 99 rejects `txId` and line 101 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(txId)` is true of a value that is NOT null: it is satisfied by an EMPTY `txId`, and on that path `txId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Vertex.Transaction/Actor/ReentryDTxActor.cs:112— The guard on line 110 rejects `txId` and line 112 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(txId)` is true of a value that is NOT null: it is satisfied by an EMPTY `txId`, and on that path `txId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Vertex.Transaction/Actor/ReentryDTxActor.cs:122— The guard on line 120 rejects `txId` and line 122 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(txId)` is true of a value that is NOT null: it is satisfied by an EMPTY `txId`, and on that path `txId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Deprecated: xunit test/Vertex.Utils.Test/Vertex.Utils.Test.csproj:11— xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit REDACTED:9— xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/Vertex.Runtime.Test/Vertex.Runtime.Test.csproj:12— xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/Vertex.TxRuntime.Test/Vertex.TxRuntime.Test.csproj:12— xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Duplicated block (11 lines × 2) src/Vertex.Utils/Channels/BufferBlockChannel.cs:134— src/Vertex.Utils/Channels/BufferBlockChannel.cs:134-144 | src/Vertex.Utils/Channels/ThreadChannel.cs:136-146 — before extracting anything, compare `src/Vertex.Utils/Channels/BufferBlockChannel.cs` and `src/Vertex.Utils/Channels/ThreadChannel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `src/Vertex.Utils/Channels/BufferBlockChannel.cs:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Vertex.Runtime/Actor/ShadowActor.cs:125— src/Vertex.Runtime/Actor/ShadowActor.cs:125-135 | src/Vertex.Runtime/Actor/VertexActor.cs:157-167 — before extracting anything, compare `src/Vertex.Runtime/Actor/ShadowActor.cs` and `src/Vertex.Runtime/Actor/VertexActor.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `src/Vertex.Runtime/Actor/ShadowActor.cs:125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:199— src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:199-209 | src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:83-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:199` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) src/Vertex.Utils/Channels/BufferBlockChannel.cs:103— src/Vertex.Utils/Channels/BufferBlockChannel.cs:103-113 | src/Vertex.Utils/Channels/ThreadChannel.cs:105-115 — before extracting anything, compare `src/Vertex.Utils/Channels/BufferBlockChannel.cs` and `src/Vertex.Utils/Channels/ThreadChannel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:545— src/Vertex.Runtime/Actor/FlowActor.cs:545-557 | src/Vertex.Runtime/Actor/ShadowActor.cs:187-199 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Actor/ShadowActor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:48— src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:48-60 | src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs:45-57 — before extracting anything, compare `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs` and `src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:48` 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) src/Vertex.Utils/Channels/BufferBlockChannel.cs:48— src/Vertex.Utils/Channels/BufferBlockChannel.cs:48-60 | src/Vertex.Utils/Channels/ThreadChannel.cs:50-62 — before extracting anything, compare `src/Vertex.Utils/Channels/BufferBlockChannel.cs` and `src/Vertex.Utils/Channels/ThreadChannel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:104— src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:104-116 | src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs:76-88 — before extracting anything, compare `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs` and `src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:119— src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:119-143 | src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:146-170 | src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:173-197 | src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs:91-115 — 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) src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventStorageFactory.cs:33— src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventStorageFactory.cs:33-63 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs:31-57 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SubSnapshotStorageFactory.cs:31-57 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/TxEventStorageFactory.cs:32-63 — 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) src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:30— src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:30-54 | src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:132-156 | src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:159-183 | src/Storage/Vertex.Storage.Linq2db/Storage/SubSnapshotStorage.cs:26-50 — 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 (12 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:174— src/Vertex.Runtime/Actor/FlowActor.cs:174-185 | src/Vertex.Runtime/Actor/FlowActor.cs:187-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Vertex.Runtime/Actor/FlowActor.cs:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Vertex.Runtime/Actor/ShadowActor.cs:114— src/Vertex.Runtime/Actor/ShadowActor.cs:114-125 | src/Vertex.Runtime/Actor/VertexActor.cs:140-152 — before extracting anything, compare `src/Vertex.Runtime/Actor/ShadowActor.cs` and `src/Vertex.Runtime/Actor/VertexActor.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `src/Vertex.Runtime/Actor/ShadowActor.cs:114` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) src/Vertex.Transaction/Actor/DTxActor.cs:102— src/Vertex.Transaction/Actor/DTxActor.cs:102-114 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:136-147 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 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.
ConsumerManager.DistributedStart (cognitive 24) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:121— ConsumerManager.DistributedStart has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ConsumerManager.DistributedStart (cognitive 24) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:123— ConsumerManager.DistributedStart has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ConsumerManager.DistributedHold (cognitive 16) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:168— ConsumerManager.DistributedHold has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ConsumerManager.DistributedHold (cognitive 16) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:171— ConsumerManager.DistributedHold has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Duplicated block (22 lines × 3) src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:109— src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:109-130 | src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:137-158 | src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:165-186 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) src/Stream/Vertex.Stream.InMemory/EventStreamFactory.cs:41— src/Stream/Vertex.Stream.InMemory/EventStreamFactory.cs:41-62 | src/Stream/Vertex.Stream.Kafka/EventStreamFactory.cs:25-46 | src/Stream/Vertex.Stream.RabbitMQ/EventStreamFactory.cs:31-52 — 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 `src/Stream/Vertex.Stream.InMemory/EventStreamFactory.cs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Stream/Vertex.Stream.InMemory/EventStreamFactory.cs:63` calls `GetId` and `src/Stream/Vertex.Stream.Kafka/EventStreamFactory.cs:47` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 2) src/Vertex.Transaction/Actor/DTxActor.cs:160— src/Vertex.Transaction/Actor/DTxActor.cs:160-181 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:175-196 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) examples/Transfer.Client/Program.cs:50— examples/Transfer.Client/Program.cs:50-71 | examples/Transfer.Client/Program.cs:109-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/Transfer.Client/Program.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:561— src/Vertex.Runtime/Actor/FlowActor.cs:561-579 | src/Vertex.Runtime/Actor/ShadowActor.cs:203-221 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Actor/ShadowActor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:133— src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:133-151 | src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:160-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Vertex.Utils/Channels/BufferBlockChannel.cs:85— src/Vertex.Utils/Channels/BufferBlockChannel.cs:85-99 | src/Vertex.Utils/Channels/ThreadChannel.cs:87-101 — before extracting anything, compare `src/Vertex.Utils/Channels/BufferBlockChannel.cs` and `src/Vertex.Utils/Channels/ThreadChannel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) src/Vertex.Utils/Channels/BufferBlockChannel.cs:149— src/Vertex.Utils/Channels/BufferBlockChannel.cs:149-163 | src/Vertex.Utils/Channels/ThreadChannel.cs:151-165 — before extracting anything, compare `src/Vertex.Utils/Channels/BufferBlockChannel.cs` and `src/Vertex.Utils/Channels/ThreadChannel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `src/Vertex.Utils/Channels/BufferBlockChannel.cs:149` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:133— src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:133-144 | src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:147-158 | src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:163-174 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:207— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:207-218 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:204-215 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:218-229 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 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 `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:207` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:58— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:58-68 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:49-59 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:46-56 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 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 `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:60` calls `SingleOrDefault` and `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:69` 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) src/Vertex.Runtime/Actor/FlowActor.cs:388— src/Vertex.Runtime/Actor/FlowActor.cs:388-398 | src/Vertex.Runtime/Actor/ShadowActor.cs:81-91 | src/Vertex.Runtime/Actor/VertexActor.cs:117-127 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Actor/ShadowActor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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 `src/Vertex.Runtime/Actor/FlowActor.cs:388` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Vertex.Runtime/Actor/ShadowActor.cs:79` calls `RecoverySnapshot` and `src/Vertex.Runtime/Actor/VertexActor.cs:116` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) src/Vertex.Protocol/EventConverter.cs.cs:37— src/Vertex.Protocol/EventConverter.cs.cs:37-42 | src/Vertex.Protocol/EventConverter.cs.cs:98-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Vertex.Protocol/EventConverter.cs.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Vertex.Transaction/Actor/DTxActor.cs:233— src/Vertex.Transaction/Actor/DTxActor.cs:233-238 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:276-281 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/Vertex.Transaction/Actor/DTxActor.cs:34— src/Vertex.Transaction/Actor/DTxActor.cs:34-38 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:36-40 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/Storage/Vertex.Storage.Linq2db/Index/Postgresql/PGIndexGenerator.cs:15— src/Storage/Vertex.Storage.Linq2db/Index/Postgresql/PGIndexGenerator.cs:15-19 | src/Storage/Vertex.Storage.Linq2db/Index/SQLite/SQLiteIndexGenerator.cs:15-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Index/Postgresql/PGIndexGenerator.cs:15` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Off the main sequence: Vertex.Utils src/Vertex.Utils/Vertex.Utils.csproj:1— Vertex.Utils: abstractness 0.13, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: Vertex.Protocol src/Vertex.Protocol/Vertex.Protocol.csproj:1— Vertex.Protocol: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
CRAP 56: ShadowActor.RecoverySnapshot src/Vertex.Runtime/Actor/ShadowActor.cs:93— Cyclomatic 7 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 56: ShadowActor.Tell src/Vertex.Runtime/Actor/ShadowActor.cs:223— Cyclomatic 7 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
Sync-over-async (deadlock risk) through `.Result` src/Vertex.Utils/Channels/BufferBlockChannel.cs:117— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/Vertex.Utils/Channels/ThreadChannel.cs:119— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
FlowActor.FlowActor.ctor (cyclomatic 38) src/Vertex.Runtime/Actor/FlowActor.cs:43— FlowActor.FlowActor.ctor has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 71, LdEventArgs, a function literal at line 46, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SnapshotHandlerBase.SnapshotHandlerBase.ctor (cyclomatic 32) src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:20— SnapshotHandlerBase.SnapshotHandlerBase.ctor has cyclomatic complexity 32 (threshold 15). Of this number, 22 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventArchive.GetList (cyclomatic 19) src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:94— EventArchive.GetList has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Prerelease dependency: StyleCop.Analyzers — StyleCop.Analyzers resolves to 1.2.0-beta.321, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
FlowActor.FlowActor.ctor (cognitive 64) src/Vertex.Runtime/Actor/FlowActor.cs:43— FlowActor.FlowActor.ctor has cognitive complexity 64 (threshold 15). None of this is in the body itself: all 64 points belong to 7 function items inside it that branch (a function literal at line 71, LdEventArgs, a function literal at line 46, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SnapshotHandlerBase.SnapshotHandlerBase.ctor (cognitive 54) src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:20— SnapshotHandlerBase.SnapshotHandlerBase.ctor has cognitive complexity 54 (threshold 15). Of this number, 40 points are the body's own statements and 14 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventArchive.GetList (cognitive 31) src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:94— EventArchive.GetList has cognitive complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 3 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ConsumerManager.ConsumerManager.ctor (cognitive 29) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:37— ConsumerManager.ConsumerManager.ctor has cognitive complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConsumerRunner.Run (cognitive 27) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:41— ConsumerRunner.Run has cognitive complexity 27 (threshold 15). None of this is in the body itself: all 27 points belong to one function literal inside it that branches (line 47). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ConsumerManager.DistributedStart (cognitive 26) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:120— ConsumerManager.DistributedStart has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FlowActor.SaveSnapshotAsync (cognitive 25) src/Vertex.Runtime/Actor/FlowActor.cs:727— FlowActor.SaveSnapshotAsync has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ConsumerRunner.Run (cognitive 25) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerRunner.cs:45— ConsumerRunner.Run has cognitive complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to one function literal inside it that branches (line 57). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ConsumerManager.ConsumerManager.ctor (cognitive 24) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:39— ConsumerManager.ConsumerManager.ctor has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InnerTxActor.Finish (cognitive 21) src/Vertex.Transaction/Actor/InnerTxActor.cs:153— InnerTxActor.Finish has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventArchive.Arichive (cognitive 19) src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:39— EventArchive.Arichive has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
InnerTxActor.Rollback (cognitive 17) src/Vertex.Transaction/Actor/InnerTxActor.cs:201— InnerTxActor.Rollback has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConsumerManager.DistributedHold (cognitive 17) src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:171— ConsumerManager.DistributedHold has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ConsumerManager.ConsumerManager.ctor (cognitive 17) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:46— ConsumerManager.ConsumerManager.ctor has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventTypeContainer.EventTypeContainer.ctor (cognitive 16) src/Vertex.Runtime/Serialization/EventTypeContainer.cs:16— EventTypeContainer.EventTypeContainer.ctor has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: FlowActor.FlowActor(…) src/Vertex.Runtime/Actor/FlowActor.cs:43— MethodTooLong — FlowActor(…) runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (46 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:119— src/Vertex.Runtime/Actor/FlowActor.cs:119-164 | src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:85-130 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 `src/Vertex.Runtime/Actor/FlowActor.cs:119` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (37 lines × 3) src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:201— src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:201-237 | src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:255-291 | src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs:119-155 — before extracting anything, compare `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs` and `src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:79— src/Vertex.Runtime/Actor/FlowActor.cs:79-113 | src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:47-81 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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, `src/Vertex.Runtime/Actor/FlowActor.cs:114` calls `DefineLabel`, `DeclareLocal` and `src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:82` 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 (34 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:128— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:128-161 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:125-158 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:124-157 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 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 `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:158` calls `IsEnabled`, `LogInformation` and `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:162` 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 (33 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:248— src/Vertex.Runtime/Actor/FlowActor.cs:248-280 | src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:191-223 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 (27–28 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:175— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:175-201 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:172-198 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:180-207 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 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 `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–26 lines × 2) src/Vertex.Transaction/Actor/DTxActor.cs:41— src/Vertex.Transaction/Actor/DTxActor.cs:41-66 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:43-66 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 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 (23 lines × 2) src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:32— src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:32-54 | src/Storage/Vertex.Storage.Linq2db/Storage/SubSnapshotStorage.cs:28-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 3) src/Vertex.Transaction/Actor/DTxActor.cs:185— src/Vertex.Transaction/Actor/DTxActor.cs:185-205 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:200-220 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:224-244 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) src/Vertex.Transaction/Actor/DTxActor.cs:136— src/Vertex.Transaction/Actor/DTxActor.cs:136-156 | src/Vertex.Transaction/Actor/ReentryDTxActor.cs:151-171 — before extracting anything, compare `src/Vertex.Transaction/Actor/DTxActor.cs` and `src/Vertex.Transaction/Actor/ReentryDTxActor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18–20 lines × 2) src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:116— src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:116-133 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerRunner.cs:122-141 — 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 `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Vertex.Runtime/Actor/ShadowActor.cs:139— src/Vertex.Runtime/Actor/ShadowActor.cs:139-156 | src/Vertex.Runtime/Actor/VertexActor.cs:171-188 — before extracting anything, compare `src/Vertex.Runtime/Actor/ShadowActor.cs` and `src/Vertex.Runtime/Actor/VertexActor.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `src/Vertex.Runtime/Actor/ShadowActor.cs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs:32— src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs:32-48 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SubSnapshotStorageFactory.cs:32-48 — before extracting anything, compare `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs` and `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SubSnapshotStorageFactory.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerRunner.cs:67— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerRunner.cs:67-79 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:128-140 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerRunner.cs:136-148 — 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 `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerRunner.cs: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.
Duplicated block (14 lines × 2) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:108— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:108-121 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:106-119 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9–13 lines × 2) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:32— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:32-44 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:27-35 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 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) src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventStorageFactory.cs:46— src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventStorageFactory.cs:46-53 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs:44-51 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SubSnapshotStorageFactory.cs:44-51 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/TxEventStorageFactory.cs:45-52 — before extracting anything, compare `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SnapshotStorageFactory.cs` and `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/SubSnapshotStorageFactory.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventStorageFactory.cs:46` 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) src/Vertex.Runtime/Actor/FlowActor.cs:442— src/Vertex.Runtime/Actor/FlowActor.cs:442-447 | src/Vertex.Runtime/Actor/ShadowActor.cs:154-159 | src/Vertex.Runtime/Actor/VertexActor.cs:186-191 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Actor/ShadowActor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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 `src/Vertex.Runtime/Actor/FlowActor.cs:442` 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 × 4) src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:120— src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:120-126 | src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:147-153 | src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:174-180 | src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs:92-98 — before extracting anything, compare `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs` and `src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 `src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:120` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:31— src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:31-37 | src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:133-139 | src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:160-166 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Vertex.Runtime/Actor/FlowActor.cs:282— src/Vertex.Runtime/Actor/FlowActor.cs:282-290 | src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:225-233 — before extracting anything, compare `src/Vertex.Runtime/Actor/FlowActor.cs` and `src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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) src/Vertex.Protocol/EventConverter.cs.cs:110— src/Vertex.Protocol/EventConverter.cs.cs:110-116 | src/Vertex.Protocol/EventConverter.cs.cs:120-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Vertex.Protocol/EventConverter.cs.cs:110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (4–9 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:83— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:83-91 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:81-89 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:86-89 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 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 `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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, `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:91` calls `Timer`, `HeathCheck`, `Wait` and `src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:89` 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 × 3) src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventArchiveFactory.cs:66— src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventArchiveFactory.cs:66-70 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventStorageFactory.cs:54-58 | src/Storage/Vertex.Storage.Linq2db/Storage/Factory/TxEventStorageFactory.cs:53-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventArchiveFactory.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/Storage/Vertex.Storage.Linq2db/Db/EventDb.cs:14— src/Storage/Vertex.Storage.Linq2db/Db/EventDb.cs:14-22 | src/Storage/Vertex.Storage.Linq2db/Db/SnapshotDb.cs:14-22 | src/Storage/Vertex.Storage.Linq2db/Db/SubSnapshotDb.cs:14-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:97— src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs:97-104 | src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs:95-102 | src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:94-101 — before extracting anything, compare `src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs` and `src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) examples/Transfer.Client/Program.cs:84— examples/Transfer.Client/Program.cs:84-91 | examples/Transfer.Client/Program.cs:149-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/Transfer.Client/Program.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) examples/Transfer.Client/Program.cs:56— examples/Transfer.Client/Program.cs:56-61 | examples/Transfer.Client/Program.cs:75-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/Transfer.Client/Program.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D8 · Code Coverage· No test project references Vertex.Stream.Kafka · ×1
No test project references Vertex.Stream.Kafka src/Stream/Vertex.Stream.Kafka/Vertex.Stream.Kafka.csproj— No test project in this repository references Vertex.Stream.Kafka (14 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 69.0% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Vertex.Stream.RabbitMQ · ×1
No test project references Vertex.Stream.RabbitMQ src/Stream/Vertex.Stream.RabbitMQ/Vertex.Stream.RabbitMQ.csproj— No test project in this repository references Vertex.Stream.RabbitMQ (13 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 69.0% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
CRAP 93: FlowActor.FlowActor.ctor src/Vertex.Runtime/Actor/FlowActor.cs:43— Cyclomatic 38 with 66.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 72: EventArchive.GetList src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:94— Cyclomatic 19 with 47.1% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 51: SnapshotHandlerBase.SnapshotHandlerBase.ctor src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:20— Cyclomatic 32 with 73.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
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 src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.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 src/Vertex.Transaction/Actor/InnerTxActor.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 src/Vertex.Transaction/Actor/ReentryDTxActor.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 src/Vertex.Runtime/Actor/ShadowActor.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 src/Vertex.Transaction/Actor/DTxActor.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 src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.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 src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.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 src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.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 src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.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 src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.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 src/Storage/Vertex.Storage.Linq2db/Storage/SnapshotStorage.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 src/Vertex.Protocol/EventConverter.cs.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 src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.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 src/Vertex.Transaction/Actor/DTxUnitActor.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 src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerRunner.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 src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.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 src/Vertex.Transaction/Actor/ReentryActor.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 src/Vertex.Utils/Channels/ThreadChannel.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 src/Vertex.Utils/Channels/BufferBlockChannel.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 src/Vertex.Utils/Buffer/SharedArray.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 src/Stream/Vertex.Stream.Common/StreamSubHandler.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 src/Storage/Vertex.Storage.Linq2db/Storage/SubSnapshotStorage.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 src/Vertex.Runtime/Actor/Extentions.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 src/Storage/Vertex.Storage.Linq2db/Storage/Factory/EventArchiveFactory.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 src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerRunner.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.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/DTxActor.cs:129— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/InnerTxActor.cs:100— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/InnerTxActor.cs:185— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/ReentryActor.cs:112— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/ReentryActor.cs:120— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/ReentryActor.cs:142— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Transaction/Actor/ReentryDTxActor.cs:89— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs:50— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Storage/Vertex.Storage.Linq2db/Storage/TxEventStorage.cs:47— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Utils/AssemblyHelper.cs:26— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Utils/Channels/BufferBlockChannel.cs:95— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Vertex.Utils/Channels/ThreadChannel.cs:97— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerRunner.cs:97— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:83— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:98— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerRunner.cs:103— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Duplicated predicate src/Vertex.Transaction/Actor/DTxActor.cs:137— `!string.IsNullOrEmpty(txId) && this.EventTypeContainer.TryGet(typeof(TxCommitEvent), out var eventName)` appears character-identically in 2 files — src/Vertex.Transaction/Actor/DTxActor.cs, src/Vertex.Transaction/Actor/ReentryDTxActor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Vertex.Transaction/Actor/DTxActor.cs:161— `!string.IsNullOrEmpty(txId) && this.EventTypeContainer.TryGet(typeof(TxCommitedEvent), out var eventName)` appears character-identically in 2 files — src/Vertex.Transaction/Actor/DTxActor.cs, src/Vertex.Transaction/Actor/ReentryDTxActor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Vertex.Transaction/Actor/DTxActor.cs:185— `!string.IsNullOrEmpty(txId) && this.EventTypeContainer.TryGet(typeof(TxFinishedEvent), out var eventName)` appears character-identically in 2 files — src/Vertex.Transaction/Actor/DTxActor.cs, src/Vertex.Transaction/Actor/ReentryDTxActor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Vertex.Runtime/Actor/FlowActor.cs:561— `EventConverter.TryParseWithNoId(bytes, out var transport) && this.EventTypeContainer.TryGet(transport.EventName, out var type)` appears character-identically in 2 files — src/Vertex.Runtime/Actor/FlowActor.cs, src/Vertex.Runtime/Actor/ShadowActor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:51— `attributes.Length > 0 && attributes.First() is StreamSubAttribute attribute` appears character-identically in 3 files — src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs, src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs, src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Vertex.Runtime/Actor/FlowActor.cs:122— `item.DeclareLocal.LocalIndex > 0 && item.DeclareLocal.LocalIndex <= 255` appears character-identically in 2 files — src/Vertex.Runtime/Actor/FlowActor.cs, src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:199— `o.ActorId == paramId && o.Name == entity.Name && o.FlowId == entity.FlowId` appears character-identically in 2 files — src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs, src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs:109— `o.ActorId == paramId && o.Version >= startVersion && o.Version <= endVersion` appears character-identically in 2 files — src/Storage/Vertex.Storage.Linq2db/Storage/EventArchive.cs, src/Storage/Vertex.Storage.Linq2db/Storage/EventStorage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Vertex.Utils/Channels/BufferBlockChannel.cs:117— `this.waitToReadTask.IsCompletedSuccessfully && this.waitToReadTask.Result` appears character-identically in 2 files — src/Vertex.Utils/Channels/BufferBlockChannel.cs, src/Vertex.Utils/Channels/ThreadChannel.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Vertex.Runtime/Actor/FlowActor.cs:76— `typeof(IEvent).IsAssignableFrom(p.ParameterType) && !p.ParameterType.IsInterface` appears character-identically in 2 files — src/Vertex.Runtime/Actor/FlowActor.cs, src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs:56— `typeof(IFlowActor).IsAssignableFrom(t) && !t.IsGenericType && t != typeof(IFlowActor)` appears character-identically in 3 files — src/Stream/Vertex.Stream.InMemory/Consumer/ConsumerManager.cs, src/Stream/Vertex.Stream.Kafka/Consumer/ConsumerManager.cs, src/Stream/Vertex.Stream.RabbitMQ/Consumer/ConsumerManager.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Outdated: Microsoft.Data.Sqlite REDACTED:9— Microsoft.Data.Sqlite 6.0.7 → 10.0.13 available (referenced by Transfer.Server).
Outdated: coverlet.collector REDACTED:11— coverlet.collector 3.1.2 → 10.1.0 available (referenced by Vertex.Utils.Test).
D34 · Knowledge Freshness· Most significant orphaned file · ×2
Most significant orphaned file src/Vertex.Runtime/Actor/FlowActor.cs: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 src/Vertex.Runtime/Actor/VertexActor.cs: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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: src/Vertex.Runtime/Actor/ShadowActor.cs. Pair on, review, or document these before any departure.
D21 · Naming Consistency· Inconsistent spelling of 'Committed' · ×1
Inconsistent spelling of 'Committed': 'OnTxCommited' and 'TxCommitedEvent' use the non-standard spelling 'Commited' (missing one 't'), whereas the standard English spelling is 'Committed'. — Rename 'OnTxCommited' to 'OnTxCommitted' and 'TxCommitedEvent' to 'TxCommittedEvent'. (symbols: Method: protected ValueTask Vertex.Transaction.Actor.InnerTxActor<TPrimaryKey, T>.OnTxCommited(string), Type: public Vertex.Transaction.Events.TxCommitedEvent)
D21 · Naming Consistency· Inconsistent spelling of 'TopUp' · ×1
Inconsistent spelling of 'TopUp': The test method 'Tx_Topup_Rollback_1' uses 'Topup' (lowercase 'u' and missing 'U' capitalization if following PascalCase, or just inconsistent casing/spelling) while the actual implementation methods use 'TopUp'. — Rename 'Tx_Topup_Rollback_1' to 'Tx_TopUp_Rollback_1' to match the implementation method name 'TopUp'. (symbols: Method: [Theory] public Task Vertex.TxRuntime.Test.ActorTest.ReentryDTxAccount_Test.Tx_Topup_Rollback_1(int, int), Method: public Task Vertex.TxRuntime.Test.Biz.Actors.InnerTxAccount.TopUp(decimal, string, string), Method: public Task<bool> Vertex.Runtime.Test.IActors.IAccount.TopUp(decimal), Method: public Task<bool> Vertex.Runtime.Test.IActors.IAccount.TopUp(decimal, string), Method: public Task Vertex.TxRuntime.Test.Biz.Actors.InnerTxAccount.TopUp(decimal, string, string))
redundant comment src/Vertex.Utils/Hash/MurmurHash2.cs:58— "Do a few final mixes of the hash to ensure the last few bytes are well-incorporated." — keep as WHY - explains a non-obvious hash mixing step
Dormant codebase — 38 of 38 significant files have no living knowledge — the codebase as a whole is dormant, not 38 separate risks. Counted over 38 of the 196 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: 3 authored method(s) exceed the IL budget src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:20— 3 of 542 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Vertex.Runtime.Snapshot.SnapshotHandlerBase`2..ctor @ src/Vertex.Runtime/Snapshot/SnapshotHandlerBase.cs:20, 496 IL instructions; that pulled this dimension to 9.9/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.
Thin README — The root README is 55 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
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.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2958 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 11/145 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/16 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.
Outdated: Lindhart.Analyser.MissingAwaitWarning — Lindhart.Analyser.MissingAwaitWarning 2.0.0 → 3.2.0 available (referenced by Vertex.Abstractions).
Outdated: Microsoft.CodeAnalysis.BannedApiAnalyzers — Microsoft.CodeAnalysis.BannedApiAnalyzers 3.3.4 → 5.6.0 available (referenced by Vertex.Abstractions).
Outdated: Microsoft.CodeAnalysis.NetAnalyzers — Microsoft.CodeAnalysis.NetAnalyzers 8.0.0 → 10.0.402 available (referenced by Vertex.Abstractions).
Outdated: Microsoft.Orleans.CodeGenerator — Microsoft.Orleans.CodeGenerator 8.2.0 → 10.4.0 available (referenced by Vertex.Abstractions).
Outdated: Microsoft.Orleans.Core.Abstractions — Microsoft.Orleans.Core.Abstractions 8.2.0 → 10.4.0 available (referenced by Vertex.Abstractions).
Outdated: Microsoft.SourceLink.GitHub — Microsoft.SourceLink.GitHub 8.0.0 → 10.0.402 available (referenced by Vertex.Abstractions).
Outdated: Nerdbank.GitVersioning — Nerdbank.GitVersioning 3.6.143 → 3.10.94 available (referenced by Vertex.Abstractions).
Outdated: Microsoft.Extensions.Caching.Abstractions — Microsoft.Extensions.Caching.Abstractions 8.0.0 → 10.0.13 available (referenced by Vertex.Runtime).
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 8.0.1 → 10.0.13 available (referenced by Vertex.Runtime).
Outdated: Microsoft.Orleans.Sdk — Microsoft.Orleans.Sdk 8.2.0 → 10.4.0 available (referenced by Vertex.Runtime).
Outdated: Microsoft.Orleans.Reminders — Microsoft.Orleans.Reminders 8.2.0 → 10.4.0 available (referenced by Vertex.Transaction).
Outdated: linq2db — linq2db 5.4.1 → 6.5.0 available (referenced by Vertex.Storage.Linq2db).
Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 8.0.2 → 10.0.13 available (referenced by Vertex.Storage.Linq2db).
Outdated: Microsoft.Extensions.DependencyModel — Microsoft.Extensions.DependencyModel 8.0.2 → 10.0.13 available (referenced by Vertex.Utils).
Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 8.0.2 → 10.0.13 available (referenced by Vertex.Utils).
Outdated: Microsoft.Extensions.ObjectPool — Microsoft.Extensions.ObjectPool 8.0.10 → 10.0.13 available (referenced by Vertex.Utils).
Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 8.0.1 → 10.0.13 available (referenced by Vertex.Stream.RabbitMQ).
Outdated: RabbitMQ.Client — RabbitMQ.Client 6.8.1 → 7.2.2 available (referenced by Vertex.Stream.RabbitMQ).
Outdated: Microsoft.Data.SqlClient — Microsoft.Data.SqlClient 6.0.1 → 7.1.1 available (referenced by Transfer.Server).
Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 8.0.1 → 10.0.13 available (referenced by Transfer.Server).
Outdated: Microsoft.Orleans.Persistence.Memory — Microsoft.Orleans.Persistence.Memory 8.2.0 → 10.4.0 available (referenced by Transfer.Server).
Outdated: Microsoft.Orleans.Server — Microsoft.Orleans.Server 8.2.0 → 10.4.0 available (referenced by Transfer.Server).
Outdated: MySqlConnector — MySqlConnector 2.2.0 → 2.6.2 available (referenced by Transfer.Server).
Outdated: Npgsql — Npgsql 9.0.3 → 10.0.3 available (referenced by Transfer.Server).
Outdated: Confluent.Kafka — Confluent.Kafka 2.6.1 → 2.16.0 available (referenced by Vertex.Stream.Kafka).
+ 7 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 01a161a0-6969-72f5-a6d8-b80ee8a74d08 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 50 · Warnings: 225 · Recommendations: 83 · Info: 32 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 03:21 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.