Public report of mizrael/OpenSleigh, 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 report Measured 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, 01:32 UTC · Survey ID cd_77b20a801ecf4822a9e49025c3fb9e93

mizrael/OpenSleigh

Measured 22 October 2026, 01:29 UTC, at code version 6c5ea27

CAI score 49out of 100 Provisional Down 6 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.

Performance 88 Strong Architecture 77 Strong Code Health 62 Adequate Security and Compliance 59 Adequate Maturity 46 Weak Production Readiness 42 Weak

A small codebase: 6,173 lines of product code in 86 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 42

Findings by how serious they are

44 critical 165 serious 131 minor

4 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, 01:29 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 code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 18 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0246: The type or namespace name 'ISagaExecutionContext<>' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ISagaExecutionContext' could not be found (are you missing a using directive or an assembly reference?)

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.
282of 340 findings point to an exact file and line, so you can open each one in the code. The other 58 concern the repository as a whole, such as missing documentation.
78dimensions across 6 lenses, read from 6,173 lines of product code in 86 projects.
Chapters

Executive summary

mizrael/OpenSleigh scores 49 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 42 and is rated Weak. Its Library API & versioning dimension scores 2 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 Leaked secret finding(s) in Secret Scanning and to resolve the 26 Orphaned file finding(s) in Knowledge Freshness, and if Production Readiness rose to 70, the score would rise from 49 to about 56.

44 findings are critical: 24 in Static Analysis (SAST), seven in Secrets (history), five in Explicit Debt, four in Dependency Vulnerabilities, two in Captive dependencies, one in Project dependency cycles and one in Secret Scanning.

Watchdog couldn't measure 4 dimensions in this code, among them Code Coverage, Test Reliability and IL Efficiency, so they are left out of the score. The product code is 6,173 lines, which would take an estimated 0.1 person-years, around €12,000, to rebuild.

Code Health 62 Adequate, capped by Solution Shape Architecture 77 Strong Maturity 46 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 42 Weak, capped by Schema migrations and Library API & versioning Security and Compliance 59 Adequate, capped by Secrets (history), Static Analysis (SAST) and Supply-chain Provenance & Signing Performance 88 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 42 · counts for 46%Maturity 46 · counts for 25%Security and Compliance 59 · counts for 14%Code Health 62 · counts for 8%Architecture 77 · counts for 4%Performance 88 · counts for 2%

If Production Readiness rose from 42 to 70, the lowest score rated Strong, the score would rise from 49 to about 56.

Code composition: what the lines of code are
Business logic 12%Supporting code 35%Tests 53%
New since the last survey: 73 findings

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

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

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

  • Dependency Hygiene · Deprecated: xunit
  • Supply-chain Provenance & Signing REDACTED
  • Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €12,000 · Estimate
Cost to rebuild€4,000 to €20,000, for 67 to 212 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemLow, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 6,173 lines of product code
Comment linesThe estimate prices 5,999 lines. Comment lines count towards the size of 6,173 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 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 6 points · Low effort · Secret Scanning
2
Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with SqlSagaStateRepository.cs, RabbitMessageSubscriber.cs, MongoSagaStateRepository.cs.
Raises the score by about 5 points · Medium effort · Knowledge Freshness
3
Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with OpenSleigh.Tests.csproj, OpenSleigh.E2ETests.csproj, OpenSleigh.Persistence.SQL.Tests.csproj.
Raises the score by about 5 points · Low effort · Dependency Hygiene

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.

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0246: The type or namespace name 'ISagaExecutionContext<>' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ISagaExecutionContext' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €12,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 42 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch OpenSleigh OpenSleigh OpenSleigh.InMemory InMemory OpenSleigh.InMemory->OpenSleigh OpenSleigh.Persistence.Mongo Mongo OpenSleigh.Persistence.Mongo->OpenSleigh OpenSleigh.Persistence.PostgreSQL PostgreSQL OpenSleigh.Persistence.SQL SQL OpenSleigh.Persistence.PostgreSQL->OpenSleigh.Persistence.SQL OpenSleigh.Persistence.SQL->OpenSleigh OpenSleigh.Persistence.SQLServer SQLServer OpenSleigh.Persistence.SQLServer->OpenSleigh.Persistence.SQL OpenSleigh.Reporting Reporting OpenSleigh.Reporting->OpenSleigh OpenSleigh.Transport.Kafka Kafka OpenSleigh.Transport.Kafka->OpenSleigh OpenSleigh.Transport.RabbitMQ RabbitMQ OpenSleigh.Transport.RabbitMQ->OpenSleigh

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.

22 modules, with 61 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 OpenSleigh.Persistence3 OpenSleigh.Queries4 OpenSleigh.Reporting5 OpenSleigh.Utils6 OpenSleigh.Transport7 OpenSleigh.Outbox8 OpenSleigh9 OpenSleigh.InMemory.Messaging10 OpenSleigh.InMemory.Outbox11 OpenSleigh.Persistence.Mongo.Entities12 OpenSleigh.Persistence.SQL.Entities13 OpenSleigh.Benchmarks14 OpenSleigh.DependencyInjection15 OpenSleigh.Persistence.SQL16 OpenSleigh.Reporting.Endpoints17 OpenSleigh.InMemory18 OpenSleigh.Persistence.Mongo19 OpenSleigh.Persistence.PostgreSQL20 OpenSleigh.Persistence.SQLServer21 OpenSleigh.Transport.Kafka22 OpenSleigh.Transport.RabbitMQ
1 (global)
2 OpenSleigh.Persistence
3 OpenSleigh.Queries
4 OpenSleigh.Reporting
5 OpenSleigh.Utils
6 OpenSleigh.Transport299
7 OpenSleigh.Outbox1123
8 OpenSleigh3174
9 OpenSleigh.InMemory.Messaging42
10 OpenSleigh.InMemory.Outbox3
11 OpenSleigh.Persistence.Mongo.Entities21
12 OpenSleigh.Persistence.SQL.Entities21
13 OpenSleigh.Benchmarks237
14 OpenSleigh.DependencyInjection22
15 OpenSleigh.Persistence.SQL4461395
16 OpenSleigh.Reporting.Endpoints11
17 OpenSleigh.InMemory24131
18 OpenSleigh.Persistence.Mongo4613971
19 OpenSleigh.Persistence.PostgreSQL2115
20 OpenSleigh.Persistence.SQLServer2116
21 OpenSleigh.Transport.Kafka33741
22 OpenSleigh.Transport.RabbitMQ32621
Uses a module listed above itPart of a loopThe module itself
1 (global)2 OpenSleigh.Persistence3 OpenSleigh.Queries4 OpenSleigh.Reporting5 OpenSleigh.Utils6 OpenSleigh.Transport7 OpenSleigh.Outbox8 OpenSleigh9 OpenSleigh.InMemory.Messaging10 OpenSleigh.InMemory.Outbox11 OpenSleigh.Persistence.Mongo.Entities12 OpenSleigh.Persistence.SQL.Entities13 OpenSleigh.Benchmarks14 OpenSleigh.DependencyInjection15 OpenSleigh.Persistence.SQL16 OpenSleigh.Reporting.Endpoints17 OpenSleigh.InMemory18 OpenSleigh.Persistence.Mongo19 OpenSleigh.Persistence.PostgreSQL20 OpenSleigh.Persistence.SQLServer21 OpenSleigh.Transport.Kafka22 OpenSleigh.Transport.RabbitMQ(global)1OpenSleigh.Persistence2OpenSleigh.Queries3OpenSleigh.Reporting4OpenSleigh.Utils5OpenSleigh.Transport6OpenSleigh.Outbox7OpenSleigh8OpenSleigh.InMemory.Messaging9OpenSleigh.InMemory.Outbox10OpenSleigh.Persistence.Mongo.Entities11OpenSleigh.Persistence.SQL.Entities12OpenSleigh.Benchmarks13OpenSleigh.DependencyInjection14OpenSleigh.Persistence.SQL15OpenSleigh.Reporting.Endpoints16OpenSleigh.InMemory17OpenSleigh.Persistence.Mongo18OpenSleigh.Persistence.PostgreSQL19OpenSleigh.Persistence.SQLServer20OpenSleigh.Transport.Kafka21OpenSleigh.Transport.RabbitMQ2229911233174423212123722446139511241314613971211521163374132621

At a glance — Code Health · 62% · Adequate · gated by D18 ·

The Good
D1 · .NET / C# Cyclomatic Complexity 9.6 D2 · .NET / C# Cognitive Complexity 9.7 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.3 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.2 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.5 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X5 · Repo Nullable reference types 9.2
The Bad
X18 · Repo Disposal-pattern correctness 5.6 X3 · Repo Exception handling 5.3
The Ugly
D17 · .NET / C# Explicit Debt 5.0 D18 · .NET / C# Solution Shape 3.0 X4 · Repo Structured logging 4.7

At a glance — Architecture · 77% · Strong ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D22 · .NET / C# Internal API Consistency 9.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 8.0 D35 · .NET / C# Change Coupling 9.9 AX1 · Repo Captive dependencies 7.6 AX10 · Repo Code composition 7.2 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0
The Bad
AX2 · Repo Stateful singletons 5.5

At a glance — Maturity · 46% · Weak · gated by D34, M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.5 D21 · .NET / C# Naming Consistency 9.0 D24 · .NET / C# Comment Value 9.0 M3 · Repo Folder & project structure 10.0
The Bad
M4 · Repo Documentation accuracy 6.0
The Ugly
D34 · .NET / C# Knowledge Freshness 0.0 M1 · Repo Documentation (README) 4.7 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 42% · Weak · gated by P8, P10 ·

The Good
D9 · .NET / C# Test Distribution 9.8 D10 · .NET / C# Test Quality 9.9 D12 · .NET / C# Dependency Hygiene 8.1 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P6 · Repo Release Hygiene 8.0
The Bad
D13 · .NET / C# Secret Scanning 5.0 P2 · Repo Observability 6.0 P3 · Repo Security & performance tooling 5.0 P4 · Repo Deployment & Rollback 5.0
The Ugly
P10 · Repo Library API & versioning 2.0 P5 · Repo DR & Backup 4.0 P8 · Repo Schema migrations 3.0

At a glance — Security · 59% · Adequate · gated by D28, D29, D36 ·

The Good
D30 · .NET / C# Dependency Vulnerabilities 7.1 D31 · .NET / C# IaC & Container Security 10.0 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D28 · .NET / C# Secrets (history) 3.0 D29 · .NET / C# Static Analysis (SAST) 0.9 D36 · .NET / C# Supply-chain Provenance & Signing 0.0

At a glance — Performance · 88% · Strong ·

The Good
PF1 · Repo Benchmark discipline 9.5 PF2 · Repo Allocation hygiene 10.0 PF3 · Repo Async & latency hygiene 7.6

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection26High / Critical
A03:2025 — Software Supply Chain Failures15High / Critical
A07:2025 — Authentication Failures9High / Critical

Roadmap

Immediately resolve the leaked secret in REDACTED and address the 26 orphaned files, prioritizing SqlSagaStateRepository.cs, RabbitMessageSubscriber.cs, and MongoSagaStateRepository.cs. Next, update the seven deprecated dependencies in the test projects to ensure system stability. Finally, document significant design decisions in a dedicated folder and restrict public API exposure by making types internal by default to protect against breaking changes.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+5.9 ptsLowSecret Scanning
Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with SqlSagaStateRepository.cs, RabbitMessageSubscriber.cs, MongoSagaStateRepository.cs.+5.4 ptsMediumKnowledge Freshness
Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with OpenSleigh.Tests.csproj, OpenSleigh.E2ETests.csproj, OpenSleigh.Persistence.SQL.Tests.csproj.+4.7 ptsLowDependency Hygiene
Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with OpenSleigh.E2ETests.csproj, OpenSleigh.Persistence.Mongo.Tests.csproj.+1.9 ptsLowDependency Hygiene
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+3.8 ptsMediumArchitecture documentation
Resolve the 25 CoverageExclusion finding(s) in Explicit Debt — start with IBusConfiguratorExtensions.cs (3), SqlBusConfiguratorExtensions.cs (2), InMemoryBusConfiguratorExtensions.cs.+1.6 ptsMediumExplicit Debt
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.+3.0 ptsMediumLibrary API & versioning
Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with DbContext.cs, MongoSagaStateQuery.cs, SqlSagaStateQuery.cs.+1.4 ptsLowExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 105 files carrying findings, judged against the Production bar: 3% slop · 27% mixed · 70% near-clean.

FileScoreBandWorst signal
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.6SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.7MixedDependency Vulnerabilities: High CVE: REDACTED
src/OpenSleigh.Persistence.Mongo/DbContext.cs5.8MixedExplicit Debt: EmptyCatchBlock
src/OpenSleigh/Transport/MessageDispatcher.cs5.8MixedExplicit Debt: EmptyCatchBlock
src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs6.0MixedExplicit Debt: CoverageExclusion
src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs6.0MixedExplicit Debt: CoverageExclusion
src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs6.1MixedExplicit Debt: EmptyCatchBlock
REDACTED6.4MixedDependency Vulnerabilities: Medium CVE: REDACTED
src/OpenSleigh/SagaExecutionService.cs6.7MixedExplicit Debt: TodoComment
src/OpenSleigh/ISagaInstance.cs6.9MixedExplicit Debt: TodoComment
REDACTED7.2MixedSecret Scanning: Leaked secret: REDACTED
REDACTED7.2MixedSecrets (history): High secret: REDACTED
REDACTED7.2MixedSecrets (history): High secret: REDACTED
REDACTED7.2MixedSecrets (history): High secret: REDACTED

How the grades work

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

Critical — 44

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

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

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

Could not be resolved — 4

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
D1D2D3D4D5D6D9D10D12D13D14D15D17D18D19D21D22D24D26D27D28D29D30D31D34D35D36D43D44AX1AX10AX2AX3AX5AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P5P6P8PF1PF2PF3X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 282 of 340 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16139-d8ea-7205-9e0a-cfd764544420.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and the real number is read on the next scan.
  • 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 — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Bundler dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 998 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 5 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D32 Data Compliance (PII/GDPR) — 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. `src/OpenSleigh/NoOpSagaInstance.cs`, `src/OpenSleigh/Outbox/MessageEnvelope.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — openSleigh.samples.ecommerce.rabbitmq Pulling openSleigh.samples.ecommerce.postgresql Pulling openSleigh.samples.ecommerce.postgresql Error Get "https://registry-1.docker.io/v2/": Forbidden openSleigh.samples.ecommerce.rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: openSleigh.samples.ecommerce.postgresql Pulling openSleigh.samples.ecommerce.rabbitmq Pulling openSleigh.samples.ecommerce.rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden openSleigh.samples.ecommerce.postgresql Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • PF3 Async & latency hygiene — 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. 50 further occurrence(s) are not listed individually; the score already reflects all 90.

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.
  • 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").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • 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.
  • D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
  • 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.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (5): D19, D21, D22, D24, 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.

Dimensions

D1 · Cyclomatic Complexity9.6 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SqlSagaStateRepository.LockAsyncCore at 20.

SqlSagaStateRepository.LockAsyncCore (cyclomatic 20)src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:86

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with SqlSagaStateRepository.LockAsyncCore (cyclomatic 20). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
  2. 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.

D2 · Cognitive Complexity9.7 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was SqlSagaStateRepository.LockAsyncCore at 19.

SqlSagaStateRepository.LockAsyncCore (cognitive 19)src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:86

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with SqlSagaStateRepository.LockAsyncCore (cognitive 19). — Refactoring it lifts Cognitive Complexity from 9.7 to about 10.0/10.
  2. 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.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication9.3 / 10Stronggated by 11 serious findings✓ Tool-verified

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

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

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

11 duplicated block group(s) detected. 4 of the 11 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.

Duplicated block (33–34 lines × 2)src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:52
Duplicated block (27–28 lines × 2)src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs:95
Duplicated block (19 lines × 2)src/OpenSleigh.Persistence.Mongo/Entities/OutboxMessage.cs:27
Duplicated block (16–17 lines × 2)src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:156
Duplicated block (12 lines × 2)src/OpenSleigh.Persistence.Mongo/Entities/SagaState.cs:8

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

What to do

  1. Resolve the 1 Duplicated block (33–34 lines × 2) finding(s) in Code Duplication — start with MongoSagaStateRepository.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Duplicated block (27–28 lines × 2) finding(s) in Code Duplication — start with MongoSagaStateQuery.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with OutboxMessage.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. 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.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

0 of 29 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution9.8 / 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.

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

1005 test methods: 987 unit, 0 integration, 0 BDD, 18 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.9 / 10Stronggated by 2 serious findings✓ 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.

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

0 skipped, 2 zero-assertion, 7 mock references across 335 tests.

No assertions: ReleaseAsync_should_unlock_instance · ×2tests/OpenSleigh.Tests/InMemorySagaStateRepositoryTests.cs:105
Mock-dominated test: Should_process_messages_from_channel · ×21tests/OpenSleigh.Tests/InMemorySubscriberTests.cs:26
Mock framework: NSubstitute · ×7

What to do

  1. Resolve the 21 Mock-dominated test finding(s) in Test Quality — start with OutboxProcessorTests.cs (5), SubscribersBackgroundServiceTests.cs (3), DefaultMessageBusTests.cs (2). — One of this dimension's main actionable groups (21 recommendation-level).
  2. Resolve the 2 No assertions finding(s) in Test Quality — start with InMemorySagaStateRepositoryTests.cs, InMemorySubscriberTests.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene8.1 / 10Strong✓ Tool-verified

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.

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

29 outdated, 0 vulnerable, 1 deprecated packages.

Deprecated: xunit · ×7tests/OpenSleigh.Tests/OpenSleigh.Tests.csproj:14
Outdated: coverlet.collector · ×2tests/OpenSleigh.E2ETests/OpenSleigh.E2ETests.csproj:23
Outdated: Microsoft.Extensions.DependencyInjection.Abstractions · ×27

What to do

  1. Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with OpenSleigh.Tests.csproj, OpenSleigh.E2ETests.csproj, OpenSleigh.Persistence.SQL.Tests.csproj. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with OpenSleigh.E2ETests.csproj, OpenSleigh.Persistence.Mongo.Tests.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
  3. 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.

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 317 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 33 direct `PackageReference`(s), and 211 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs (5×20=100) Repeated repair below the complexity floor: src/OpenSleigh/SagaExecutionService.cs (3 of 5 changes were fixes); src/OpenSleigh.Transport.Kafka/KafkaMessageParser.cs (3 of 4 changes were fixes); src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs (3 of 4 changes were fixes)

Repeated repair: src/OpenSleigh/SagaExecutionService.cs · ×3src/OpenSleigh/SagaExecutionService.cs:22
Hotspot: src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cssrc/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:86

What to do

  1. Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with SagaExecutionService.cs, KafkaMessageParser.cs, KafkaMessageSubscriber.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with SqlSagaStateRepository.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D17 · Explicit Debt5.0 / 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.

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

40 deducted debt markers + 8 dead symbols across 6168 LoC in the .NET projects (2.5/KLoC) → score 5.0.

EmptyCatchBlock · ×5src/OpenSleigh.Persistence.Mongo/DbContext.cs:64
CoverageExclusion · ×25src/OpenSleigh.InMemory/InMemoryBusConfiguratorExtensions.cs:14
TodoComment · ×10src/OpenSleigh.Persistence.Mongo/DbContext.cs:72
Dead code: MessageWithCorrelationId · ×8tests/OpenSleigh.Tests/Outbox/MessageEnvelopeTests.cs:338

What to do

  1. Resolve the 25 CoverageExclusion finding(s) in Explicit Debt — start with IBusConfiguratorExtensions.cs (3), SqlBusConfiguratorExtensions.cs (2), InMemoryBusConfiguratorExtensions.cs. — One of this dimension's main actionable groups (25 warning-level).
  2. Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with DbContext.cs, MongoSagaStateQuery.cs, SqlSagaStateQuery.cs. — One of this dimension's main actionable groups (5 issue-level).
  3. Resolve the 10 TodoComment finding(s) in Explicit Debt — start with ISagaInstance.cs (3), DbContext.cs, SqlBusConfiguratorExtensions.cs. — One of this dimension's main actionable groups (10 warning-level).
  4. 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.

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

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.

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

86 projects, 891 source files, 12823 hand-written lines of code (6168 production / 6655 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), 193 inter-project edges (build failed). Measured across 3 solutions loaded as one workspace: `src/OpenSleigh.sln`, `samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.sln`, `samples/OpenSleigh.Samples.Blazor/OpenSleigh.Samples.Blazor.sln`.

Build failed

What to do

  1. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation QualityStrong◐ Sampled · advisory

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.

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

The OpenSleigh repository is well documented: the root README gives a clear overview and a donation link; each directory's README (e.g. samples/OpenSleigh.Samples.ECommerce) documents its own tier with prerequisites, running commands, and an API endpoint table for that directory. The architecture/Docs markdown files cover topics like saga state query APIs, persistence transports, and the InMemory transport guide. XML-doc coverage is low (<5%), so most documentation resides in prose rather than code comments. OpenSleigh's documentation is clear and complete for a distributed Saga library. The repository root README (docs/index.md) gives an overview of what the project is, its purpose, and where to find installation/usage information; it also links to Use Cases, first steps, handling messages, idempotency, and reporting & monitoring sections. A dedicated How-To guide covers every aspect a library user needs: installation, configure transport/persistence, adding Sagas, starting/handling/messages/stopping Sagas, idempotency, publishing, publish-only mode, and reporting/monitoring with setup, endpoints, query parameters, and response format. The architecture/design docs are not visible in the summary but an outline would confirm all sections exist.

Low XML-doc coverage: OpenSleigh(net8.0) · ×23src/OpenSleigh/OpenSleigh.csproj

What to do

  1. Resolve the 23 Low XML-doc coverage finding(s) in Documentation Quality — start with OpenSleigh.csproj, REDACTED, OpenSleigh.Samples.Sample1.csproj. — One of this dimension's main actionable groups (23 warning-level).

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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.

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

2 naming inconsistencies across 200 sampled symbols.

Inconsistent use of 'by_type' in test names. Some tests use 'Create_by_type_should_...' while others use 'Create_should_...' or 'Create_by_type_should_...'. The prefix 'by_type' is used inconsistently to describe the same input mechanism (creating by type vs by other means or just general creation).
Inconsistent naming of the action being tested. One test uses 'Create_by_type_should_throw...' while another uses 'Create_should_use_provided_creator...'. The first implies a specific input method ('by_type') while the second is more generic ('Create').

✓ On the Gold path — maintain.

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

D22 · Internal API ConsistencyStronggated by 1 serious finding◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

1 API inconsistencies across a 400-member sample of 387 exposed types.

Redundant operations for infrastructure setup. One is an interface method on a specific creator, the other is an extension method on IHost. This creates two entry points for the same logical action.

What to do

  1. Resolve the 1 Redundant operations for infrastructure setup. One is an interface… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

D24 · Comment ValueExemplary◐ Sampled · advisory

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

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

70 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

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

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

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

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

0 of 30 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability8.0 / 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.

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

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

What to do

  1. Improve Navigability — currently 8.0/10. — 84 % of calls cross a namespace and 19 % go through an interface, but 74 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)3.0 / 10Weak✓ Tool-verified

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.

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

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

REDACTED
REDACTED

What to do

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

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

D29 · Static Analysis (SAST)0.9 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

26 finding(s): 0 critical, 24 high, 2 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `src/OpenSleigh/NoOpSagaInstance.cs` (line 37), `src/OpenSleigh/Outbox/MessageEnvelope.cs` (line 93, line 121) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 11 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (11 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities7.1 / 10Adequategated by 4 critical findings✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

6 finding(s): 0 critical, 4 high, 2 medium, 0 low.

REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

26 of 26 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs. Counted over 26 of the 147 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×26src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:1
Dormant codebase

What to do

  1. Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with SqlSagaStateRepository.cs, RabbitMessageSubscriber.cs, MongoSagaStateRepository.cs. — One of this dimension's main actionable groups (26 recommendation-level).
  2. 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.

D35 · Change Coupling9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: SagaExecutionService.cs↔SagaInstance.cs 70%

Change coupling: SagaExecutionService.cs ↔ SagaInstance.cssrc/OpenSleigh/SagaExecutionService.cs:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with SagaExecutionService.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies7.6 / 10Strong✓ Tool-verified

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.

  • `InMemorySubscriber` is registered as a SINGLETON but its constructor takes `IMessageProcessor messageProcessor`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IMessageProcessor` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:20
  • `KafkaMessageHandler` is registered as a SINGLETON but its constructor takes `IMessageProcessor messageProcessor`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IMessageProcessor` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/OpenSleigh.Transport.Kafka/KafkaMessageHandler.cs:18

What to do

  • Don't inject scoped/transient services into singletons; resolve them per-use via IServiceScopeFactory or a factory delegate, or align the lifetimes.
AX10 · Code composition7.2 / 10Strong✓ Tool-verified

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

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.
AX2 · Stateful singletons5.5 / 10Adequate✓ Tool-verified

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.

  • `InMemorySubscriber` is a singleton (one shared instance) but mutates instance state outside any lock (_stoppingCts, _consumerTask; e.g. `_stoppingCts` at line 35). — src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:8
  • `ChannelFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_publishChannel, _consumeChannel; e.g. `_publishChannel` at line 70). — src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:7
  • `RabbitMessageSubscriber` is a singleton (one shared instance) but mutates instance state outside any lock (_channel, _linkedCts; e.g. `_channel` at line 44). — src/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.cs:9
  • `KafkaMessageSubscriber` is a singleton (one shared instance) but mutates instance state outside any lock (_stoppingCts, _consumerTask; e.g. `_stoppingCts` at line 43). — src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs:10

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The namespaces OpenSleigh ↔ OpenSleigh.Outbox ↔ OpenSleigh.Transport depend on each other. The lightest dependency in the cycle is OpenSleigh.Outbox → OpenSleigh.Transport (OpenSleigh.Outbox.MessageEnvelope → OpenSleigh.Transport.IMessage, 2 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/OpenSleigh/Outbox/MessageEnvelope.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.
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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.

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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A placeholder string ("lorem ipsum") is still in shipped code — typical of generated boilerplate that was never filled in. — samples/OpenSleigh.Samples.Sample1/SagaWithState.cs:43

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.2 / 10Strong✓ Tool-verified

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.

  • `AddOpenSleighReporting` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/OpenSleigh.Reporting/ServiceCollectionExtensions.cs:7
  • `ParseMessageAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/OpenSleigh.Transport.RabbitMQ/RabbitMessageParser.cs:21
  • 1 guard above `return true;` also returns `true`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/OpenSleigh/SagaInstance.cs:47
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/OpenSleigh.Transport.Kafka/IBusConfiguratorExtensions.cs:60

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)4.7 / 10Weak✓ Tool-verified

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

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

  • The root README is 63 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 30 project(s) that lack one — worth up to 1.3 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

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

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

M4 · Documentation accuracy6.0 / 10Adequate◐ Sampled · advisory

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.

  • docs/how-to/reporting.md installs the package `OpenSleigh.Reporting` (`dotnet add package OpenSleigh.Reporting`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/how-to/reporting.md:17
  • src/OpenSleigh.Reporting/README.md installs the package `OpenSleigh.Reporting` (`dotnet add package OpenSleigh.Reporting`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/OpenSleigh.Reporting/README.md:8

What to do

  • Reconcile the README with reality: docs/how-to/reporting.md installs the package `OpenSleigh.Reporting` (`dotnet add package OpenSleigh.Reporting`), but no project or props file references it; src/OpenSleigh.Reporting/README.md installs the package `OpenSleigh.Reporting` (`dotnet add package OpenSleigh.Reporting`), but no project or props file references it.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P10 · Library API & versioning2.0 / 10Critical✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 387/526 types (74%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
  • No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.

What to do

  • Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
  • Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P2 · Observability6.0 / 10Adequate✓ Tool-verified

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

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

  • Only 13/20 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 20, 11 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified

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

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

  • The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

  • `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. — src/OpenSleigh.Persistence.SQL/SagaDbContext.cs:13

What to do

  • Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.
PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

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.

PF2 · Allocation hygiene10.0 / 10Exemplary✓ Tool-verified

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.

PF3 · Async & latency hygiene7.6 / 10Strong✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from 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.

  • Only 59/148 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • `await creator.SetupAsync(host)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/DependencyInjection/IHostExtensions.cs:15
  • `await ProcessMessagesAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/Outbox/OutboxBackgroundService.cs:31
  • `await base.StopAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/OpenSleigh/Outbox/OutboxBackgroundService.cs:59, src/OpenSleigh/SubscribersBackgroundService.cs:48
  • `await using … = await _transactionManager.StartTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/Outbox/OutboxProcessor.cs:30
  • `await _transactionManager.StartTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/Outbox/OutboxProcessor.cs:30
  • `await _outboxRepository.ReadPendingAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/Outbox/OutboxProcessor.cs:34
  • `await transaction.CommitAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/Outbox/OutboxProcessor.cs:65
  • `await transaction.RollbackAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/Outbox/OutboxProcessor.cs:70
  • `await _sagaStateRepository.FindAsync(descriptor, messageContext, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/SagaExecutionService.cs:110
  • `await Task.WhenAll(subscriberTasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/SubscribersBackgroundService.cs:37
  • `await Task.WhenAll(_subscribers.Select(s => s.StopAsync(cancellationToken).AsTask()))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh/SubscribersBackgroundService.cs:45
  • `await ConsumeMessagesAsync(_stoppingCts.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:37
  • `await Task.WhenAll(tasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:67
  • `await this.Database.BeginTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Persistence.SQL/SagaDbContext.cs:25
  • `await _appendSemaphore.WaitAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Persistence.SQL/SqlOutboxRepository.cs:56
  • `await _dbContext.BeginTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Persistence.SQL/SqlTransactionManager.cs:14
  • `await DbContext.OutboxMessages .AsNoTracking() .Take(_options.MaxMessagesToPull) //...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Persistence.SQLServer/MSSqlOutboxRepository.cs:21
  • `await _semaphore.WaitAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:26, src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:47
  • `await _connection.CreateChannelAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:33, src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:54
  • `await _publishChannel.CloseAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:68
  • `await _consumeChannel.CloseAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:76
  • `await EnsureExchangesAsync(queueReferences, channel, rabbitCfg, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:33
  • `await EnsureQueuesAsync(queueReferences, channel, rabbitCfg, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:34
  • `await channel.ExchangeDeclareAsync( exchange: queueReferences.ExchangeName, type: E...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:46
  • `await channel.ExchangeDeclareAsync( exchange: queueReferences.DeadLetterExchangeNam...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:52
  • `await channel.ExchangeDeclareAsync( exchange: queueReferences.RetryExchangeName, ty...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:58
  • `await channel.QueueDeclareAsync(queue: queueReferences.DeadLetterQueue, durable: ra...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:68
  • `await channel.QueueBindAsync(queueReferences.DeadLetterQueue, queueReferences.DeadL...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:74
  • `await channel.QueueDeclareAsync(queue: queueReferences.RetryQueueName, durable: rab...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:80
  • `await channel.QueueBindAsync(queue: queueReferences.RetryQueueName, exchange: queue...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:90
  • `await channel.QueueDeclareAsync(queue: queueReferences.QueueName, durable: rabbitCf...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:96
  • `await channel.QueueBindAsync(queue: queueReferences.QueueName, exchange: queueRefer...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:107
  • `await channel.ExchangeDeleteAsync(queueRef.ExchangeName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:116
  • `await channel.QueueDeleteAsync(queueRef.QueueName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:117
  • `await channel.ExchangeDeleteAsync(queueRef.DeadLetterExchangeName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:119
  • `await channel.QueueDeleteAsync(queueRef.DeadLetterQueue)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:120

What to do

  • In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

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.

X18 · Disposal-pattern correctness5.6 / 10Adequate✓ Tool-verified

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.

  • `RabbitPersistentConnection` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 15), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `Dispose` (line 25) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/OpenSleigh.Transport.RabbitMQ/RabbitPersistentConnection.cs:15

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

X2 · Cancellation propagation9.5 / 10Exemplary✓ Tool-verified

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 92/100 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. (×6) — src/OpenSleigh/DependencyInjection/IHostExtensions.cs:10, src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:114, src/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.cs:130, …
  • No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — src/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.cs:72
  • This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. — samples/OpenSleigh.Samples.PizzaTracker/Program.cs:24

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `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.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

X3 · Exception handling5.3 / 10Adequate✓ Tool-verified

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.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — src/OpenSleigh/SagaInstance.cs:114, src/OpenSleigh/Transport/MessageDispatcher.cs:30, src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.cs:86, …

What to do

  • Swallowed exception (empty catch)
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.

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.

X4 · Structured logging4.7 / 10Weak✓ Tool-verified

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. (×20) — src/OpenSleigh/SubscribersBackgroundService.cs:27, src/OpenSleigh/SubscribersBackgroundService.cs:31, src/OpenSleigh/SubscribersBackgroundService.cs:44, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types9.2 / 10Exemplary✓ Tool-verified

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.9 `!` suppressions per 1k syntax nodes — 31 suppression(s) across the 32681 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health62%Adequate — gated by D18Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture77%StrongSolid.
Maturity46%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness42%Weak — gated by P8, P10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security59%Adequate — gated by D28, D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance88%StrongStrongest area.
Unscored — 4 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.

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • 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 — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 39 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 transaction-script/CRUD 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
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — openSleigh.samples.ecommerce.rabbitmq Pulling openSleigh.samples.ecommerce.postgresql Pulling openSleigh.samples.ecommerce.postgresql Error Get "https://registry-1.docker.io/v2/": Forbidden openSleigh.samples.ecommerce.rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: openSleigh.samples.ecommerce.postgresql Pulling openSleigh.samples.ecommerce.rabbitmq Pulling openSleigh.samples.ecommerce.rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden openSleigh.samples.ecommerce.postgresql Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — 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
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • 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.
  • D23 Boundary Type-Coupling — small single-context codebase (6,168 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
  • D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — analyzer environment
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (15 value object(s))
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 event handler(s); a message-bus package
  • ED5 Idempotency — 9 mutating command handler(s)/consumer(s) detected and 9 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • 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.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 44 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×5
  • EmptyCatchBlock src/OpenSleigh.Persistence.Mongo/DbContext.cs:64 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs:103 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.cs:86 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/OpenSleigh/SagaInstance.cs:114 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/OpenSleigh/Transport/MessageDispatcher.cs:30 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D30 · Dependency Vulnerabilities · High CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX1 · Captive dependencies · Captive dependency · ×2
  • Captive dependency: singleton InMemorySubscriber captures transient IMessageProcessor src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:20 — `InMemorySubscriber` is registered as a SINGLETON but its constructor takes `IMessageProcessor messageProcessor`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IMessageProcessor` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
  • Captive dependency: singleton KafkaMessageHandler captures transient IMessageProcessor src/OpenSleigh.Transport.Kafka/KafkaMessageHandler.cs:18 — `KafkaMessageHandler` is registered as a SINGLETON but its constructor takes `IMessageProcessor messageProcessor`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IMessageProcessor` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/OpenSleigh/Outbox/MessageEnvelope.cs:1 — The namespaces OpenSleigh ↔ OpenSleigh.Outbox ↔ OpenSleigh.Transport depend on each other. The lightest dependency in the cycle is OpenSleigh.Outbox → OpenSleigh.Transport (OpenSleigh.Outbox.MessageEnvelope → OpenSleigh.Transport.IMessage, 2 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.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 165 finding(s)
PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×40
  • Awaits without ConfigureAwait(false) — Only 59/148 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/DependencyInjection/IHostExtensions.cs:15 — `await creator.SetupAsync(host)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxBackgroundService.cs:31 — `await ProcessMessagesAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxBackgroundService.cs:59 — `await base.StopAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxProcessor.cs:30 — `await using … = await _transactionManager.StartTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxProcessor.cs:30 — `await _transactionManager.StartTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxProcessor.cs:34 — `await _outboxRepository.ReadPendingAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxProcessor.cs:65 — `await transaction.CommitAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/Outbox/OutboxProcessor.cs:70 — `await transaction.RollbackAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/SagaExecutionService.cs:110 — `await _sagaStateRepository.FindAsync(descriptor, messageContext, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/SubscribersBackgroundService.cs:37 — `await Task.WhenAll(subscriberTasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/SubscribersBackgroundService.cs:45 — `await Task.WhenAll(_subscribers.Select(s => s.StopAsync(cancellationToken).AsTask()))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh/SubscribersBackgroundService.cs:48 — `await base.StopAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:37 — `await ConsumeMessagesAsync(_stoppingCts.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:67 — `await Task.WhenAll(tasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Persistence.SQL/SagaDbContext.cs:25 — `await this.Database.BeginTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Persistence.SQL/SqlOutboxRepository.cs:56 — `await _appendSemaphore.WaitAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Persistence.SQL/SqlTransactionManager.cs:14 — `await _dbContext.BeginTransactionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Persistence.SQLServer/MSSqlOutboxRepository.cs:21 — `await DbContext.OutboxMessages .AsNoTracking() .Take(_options.MaxMessagesToPull) //...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:26 — `await _semaphore.WaitAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:33 — `await _connection.CreateChannelAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:47 — `await _semaphore.WaitAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:54 — `await _connection.CreateChannelAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:68 — `await _publishChannel.CloseAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:76 — `await _consumeChannel.CloseAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • + 15 more in this group — see findings.md.
D17 · Explicit Debt · CoverageExclusion · ×25
  • CoverageExclusion src/OpenSleigh.InMemory/InMemoryBusConfiguratorExtensions.cs:14 — class InMemoryBusConfiguratorExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.Mongo/MongoBusConfiguratorExtensions.cs:10 — class MongoBusConfiguratorExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.Mongo/MongoConfiguration.cs:5 — record MongoConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:10 — record MongoSagaStateRepositoryOptions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.PostgreSQL/SqlBusConfiguratorExtensions.cs:13 — class SqlBusConfiguratorExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.SQLServer/SqlBusConfiguratorExtensions.cs:12 — class SqlBusConfiguratorExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.SQL/SagaDbContext.cs:7 — class SagaDbContext — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.SQL/SqlConfiguration.cs:5 — record SqlConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.SQL/SqlOutboxRepository.cs:9 — record SqlOutboxRepositoryOptions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:10 — record SqlSagaStateRepositoryOptions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Persistence.SQLServer/QueryHintInterceptor.cs:8 — class QueryHintInterceptor — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Transport.Kafka/IBusConfiguratorExtensions.cs:8 — record KafkaConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Transport.Kafka/IBusConfiguratorExtensions.cs:11 — class IBusConfiguratorExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Transport.RabbitMQ/IBusConfiguratorExtensions.cs:9 — class IBusConfiguratorExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Transport.Kafka/KafkaInfrastructureCreator.cs:11 — class KafkaInfrastructureCreator — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh.Transport.RabbitMQ/RabbitConfiguration.cs:5 — record RabbitConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/DependencyInjection/BusConfigurator.cs:8 — class BusConfigurator — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/DependencyInjection/IHostExtensions.cs:7 — class IHostExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/DependencyInjection/ServiceCollectionExtensions.cs:10 — class ServiceCollectionExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/LockException.cs:5 — class LockException — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/NoOpSagaInstance.cs:7 — class NoOpSagaInstance — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/OptimisticLockException.cs:5 — class OptimisticLockException — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/Persistence/NoOpTransaction.cs:5 — class NoOpTransaction — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/SagaException.cs:5 — class SagaException — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/OpenSleigh/Transport/DefaultMessageContext.cs:6 — record DefaultMessageContext — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
D19 · Documentation Quality · Low XML-doc coverage · ×23
  • Low XML-doc coverage: OpenSleigh(net8.0) src/OpenSleigh/OpenSleigh.csproj — OpenSleigh(net8.0): 4 % XML-doc coverage (8/192).
  • Low XML-doc coverage: OpenSleigh.InMemory(net8.0) REDACTED — OpenSleigh.InMemory(net8.0): 6 % XML-doc coverage (2/32).
  • Low XML-doc coverage: OpenSleigh.Samples.Sample1(net8.0) samples/OpenSleigh.Samples.Sample1/OpenSleigh.Samples.Sample1.csproj — OpenSleigh.Samples.Sample1(net8.0): 0 % XML-doc coverage (0/16).
  • Low XML-doc coverage: OpenSleigh.Persistence.SQL(net8.0) src/OpenSleigh.Persistence.SQL/OpenSleigh.Persistence.SQL.csproj — OpenSleigh.Persistence.SQL(net8.0): 0 % XML-doc coverage (0/68).
  • Low XML-doc coverage: OpenSleigh.Persistence.SQLServer(net8.0) REDACTED — OpenSleigh.Persistence.SQLServer(net8.0): 0 % XML-doc coverage (0/13).
  • Low XML-doc coverage: OpenSleigh.Transport.RabbitMQ(net8.0) src/OpenSleigh.Transport.RabbitMQ/OpenSleigh.Transport.RabbitMQ.csproj — OpenSleigh.Transport.RabbitMQ(net8.0): 9 % XML-doc coverage (5/54).
  • Low XML-doc coverage: OpenSleigh.Persistence.PostgreSQL(net8.0) src/OpenSleigh.Persistence.PostgreSQL/OpenSleigh.Persistence.PostgreSQL.csproj — OpenSleigh.Persistence.PostgreSQL(net8.0): 0 % XML-doc coverage (0/4).
  • Low XML-doc coverage: OpenSleigh.Persistence.Mongo(net8.0) REDACTED — OpenSleigh.Persistence.Mongo(net8.0): 0 % XML-doc coverage (0/63).
  • Low XML-doc coverage: OpenSleigh.Samples.Sample2.Common(net8.0) samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.Common/OpenSleigh.Samples.Sample2.Common.csproj — OpenSleigh.Samples.Sample2.Common(net8.0): 0 % XML-doc coverage (0/2).
  • Low XML-doc coverage: OpenSleigh.Samples.Sample2.API(net8.0) samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.API/OpenSleigh.Samples.Sample2.API.csproj — OpenSleigh.Samples.Sample2.API(net8.0): 0 % XML-doc coverage (0/11).
  • Low XML-doc coverage: OpenSleigh.Samples.Sample2.Worker(net8.0) samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.Worker/OpenSleigh.Samples.Sample2.Worker.csproj — OpenSleigh.Samples.Sample2.Worker(net8.0): 0 % XML-doc coverage (0/25).
  • Low XML-doc coverage: OpenSleigh.Transport.Kafka(net8.0) src/OpenSleigh.Transport.Kafka/OpenSleigh.Transport.Kafka.csproj — OpenSleigh.Transport.Kafka(net8.0): 0 % XML-doc coverage (0/42).
  • Low XML-doc coverage: OpenSleigh.Reporting(net8.0) REDACTED — OpenSleigh.Reporting(net8.0): 12 % XML-doc coverage (1/8).
  • Low XML-doc coverage: OpenSleigh.Samples.PizzaTracker samples/OpenSleigh.Samples.PizzaTracker/OpenSleigh.Samples.PizzaTracker.csproj — OpenSleigh.Samples.PizzaTracker: 0 % XML-doc coverage (0/25).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.API(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.API/OpenSleigh.Samples.ECommerce.API.csproj — OpenSleigh.Samples.ECommerce.API(net8.0): 0 % XML-doc coverage (0/11).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.Common(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Common/OpenSleigh.Samples.ECommerce.Common.csproj — OpenSleigh.Samples.ECommerce.Common(net8.0): 0 % XML-doc coverage (0/8).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.InventoryService(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.InventoryService/OpenSleigh.Samples.ECommerce.InventoryService.csproj — OpenSleigh.Samples.ECommerce.InventoryService(net8.0): 0 % XML-doc coverage (0/4).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.NotificationsService(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.NotificationsService/OpenSleigh.Samples.ECommerce.NotificationsService.csproj — OpenSleigh.Samples.ECommerce.NotificationsService(net8.0): 0 % XML-doc coverage (0/4).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.Orchestrator(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/OpenSleigh.Samples.ECommerce.Orchestrator.csproj — OpenSleigh.Samples.ECommerce.Orchestrator(net8.0): 0 % XML-doc coverage (0/10).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.PaymentService(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.PaymentService/OpenSleigh.Samples.ECommerce.PaymentService.csproj — OpenSleigh.Samples.ECommerce.PaymentService(net8.0): 0 % XML-doc coverage (0/4).
  • Low XML-doc coverage: OpenSleigh.Samples.ECommerce.ShippingService(net8.0) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.ShippingService/OpenSleigh.Samples.ECommerce.ShippingService.csproj — OpenSleigh.Samples.ECommerce.ShippingService(net8.0): 0 % XML-doc coverage (0/4).
  • Low XML-doc coverage: OpenSleigh.Samples.Blazor(net8.0) REDACTED — OpenSleigh.Samples.Blazor(net8.0): 0 % XML-doc coverage (0/16).
  • Low XML-doc coverage: OpenSleigh.Benchmarks benchmarks/OpenSleigh.Benchmarks/OpenSleigh.Benchmarks.csproj — OpenSleigh.Benchmarks: 9 % XML-doc coverage (2/22).
D17 · Explicit Debt · TodoComment · ×10
  • TodoComment src/OpenSleigh.Persistence.Mongo/DbContext.cs:72 — //TODO: not sure this one is necessary — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh.Persistence.PostgreSQL/SqlBusConfiguratorExtensions.cs:43 — // TODO: this sucks hard — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh.Transport.Kafka/KafkaInfrastructureCreator.cs:10 — //TODO: not sure I want to keep this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs:56 — // TODO: check if it's possible to get rid of this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh/ISagaInstance.cs:37 — //TODO: this might become an enum — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh/ISagaInstance.cs:39 — //TODO: this should be private — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh/ISagaInstance.cs:42 — //TODO: do we really need this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh/SagaExecutionService.cs:91 — // TODO: transaction — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenSleigh/Transport/MessageDispatcher.cs:32 — // TODO: send outboxMessage + descriptor to deadletter — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment tests/OpenSleigh.E2ETests/E2ETestsBase.cs:36 — //TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D17 · Explicit Debt · Dead code · ×8
  • Dead code: MessageWithCorrelationId tests/OpenSleigh.Tests/Outbox/MessageEnvelopeTests.cs:338 — NamedType MessageWithCorrelationId — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.Tests(net8.0), 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: InMemoryIdempotentMessageScenario tests/OpenSleigh.E2ETests/InMemory/InMemoryIdempotentMessageScenario.cs:7 — NamedType InMemoryIdempotentMessageScenario — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.E2ETests(net8.0), 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: InMemoryMultipleSagasSameMessagesScenario tests/OpenSleigh.E2ETests/InMemory/InMemoryMultipleSagasSameMessagesScenario.cs:7 — NamedType InMemoryMultipleSagasSameMessagesScenario — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.E2ETests(net8.0), 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: InMemoryParallelMultiStartSagaScenario tests/OpenSleigh.E2ETests/InMemory/InMemoryParallelMultiStartSagaScenario.cs:7 — NamedType InMemoryParallelMultiStartSagaScenario — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.E2ETests(net8.0), 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: InMemoryParentChildScenario tests/OpenSleigh.E2ETests/InMemory/InMemoryParentChildScenario.cs:7 — NamedType InMemoryParentChildScenario — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.E2ETests(net8.0), 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: InMemorySequentialMultiStartSagaScenario tests/OpenSleigh.E2ETests/InMemory/InMemorySequentialMultiStartSagaScenario.cs:7 — NamedType InMemorySequentialMultiStartSagaScenario — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.E2ETests(net8.0), 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: InMemorySimpleSagaScenario tests/OpenSleigh.E2ETests/InMemory/InMemorySimpleSagaScenario.cs:7 — NamedType InMemorySimpleSagaScenario — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.E2ETests(net8.0), 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: KafkaPublisherExecutorTests tests/OpenSleigh.Transport.Kafka.Tests/Unit/KafkaPublisherExecutorTests.cs:3 — NamedType KafkaPublisherExecutorTests — Roslyn's SymbolFinder walked every project the solution loads, including OpenSleigh.Transport.Kafka.Tests(net8.0), 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.
D12 · Dependency Hygiene · Deprecated · ×7
  • Deprecated: xunit tests/OpenSleigh.Tests/OpenSleigh.Tests.csproj:14 — xunit 2.9.3 — 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 tests/OpenSleigh.E2ETests/OpenSleigh.E2ETests.csproj:18 — xunit 2.9.3 — 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 tests/OpenSleigh.Persistence.SQL.Tests/OpenSleigh.Persistence.SQL.Tests.csproj:22 — xunit 2.9.3 — 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 tests/OpenSleigh.Transport.RabbitMQ.Tests/OpenSleigh.Transport.RabbitMQ.Tests.csproj:16 — xunit 2.9.3 — 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 tests/OpenSleigh.Persistence.Mongo.Tests/OpenSleigh.Persistence.Mongo.Tests.csproj:16 — xunit 2.9.3 — 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 tests/OpenSleigh.Transport.Kafka.Tests/OpenSleigh.Transport.Kafka.Tests.csproj:16 — xunit 2.9.3 — 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 tests/OpenSleigh.Reporting.Tests/OpenSleigh.Reporting.Tests.csproj:13 — xunit 2.9.3 — 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.
X2 · Cancellation propagation · Async method without CancellationToken · ×6
  • Async method without CancellationToken: SetupInfrastructureAsync src/OpenSleigh/DependencyInjection/IHostExtensions.cs:10 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteAsync src/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.cs:114 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HandleConsumerException src/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.cs:130 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetupAsync src/OpenSleigh.Transport.Kafka/KafkaInfrastructureCreator.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StartSaga samples/OpenSleigh.Samples.Blazor/OpenSleigh.Samples.Blazor/Hubs/SagaHub.cs:15 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendNotification samples/OpenSleigh.Samples.Blazor/OpenSleigh.Samples.Blazor/Sagas/StepsSaga.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
X3 · Exception handling · Swallowed exception (empty catch) · ×5
  • Swallowed exception (empty catch) src/OpenSleigh/SagaInstance.cs:114 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/OpenSleigh/Transport/MessageDispatcher.cs:30 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.cs:86 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/OpenSleigh.Persistence.Mongo/DbContext.cs:64 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs:103 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AX2 · Stateful singletons · Stateful singleton · ×4
  • Stateful singleton: InMemorySubscriber src/OpenSleigh.InMemory/Messaging/InMemorySubscriber.cs:8 — `InMemorySubscriber` is a singleton (one shared instance) but mutates instance state outside any lock (_stoppingCts, _consumerTask; e.g. `_stoppingCts` at line 35).
  • Stateful singleton: ChannelFactory src/OpenSleigh.Transport.RabbitMQ/ChannelFactory.cs:7 — `ChannelFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_publishChannel, _consumeChannel; e.g. `_publishChannel` at line 70).
  • Stateful singleton: RabbitMessageSubscriber src/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.cs:9 — `RabbitMessageSubscriber` is a singleton (one shared instance) but mutates instance state outside any lock (_channel, _linkedCts; e.g. `_channel` at line 44).
  • Stateful singleton: KafkaMessageSubscriber src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs:10 — `KafkaMessageSubscriber` is a singleton (one shared instance) but mutates instance state outside any lock (_stoppingCts, _consumerTask; e.g. `_stoppingCts` at line 43).
D15 · Churn × Complexity Hotspots · Repeated repair · ×3
  • Repeated repair: src/OpenSleigh/SagaExecutionService.cs src/OpenSleigh/SagaExecutionService.cs:22 — src/OpenSleigh/SagaExecutionService.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is SagaExecutionService.BeginProcessingAsync at line 22), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix E2E test flakiness caused by concurrency issues in multi-host scenarios”; “minor fixes”; “multiple fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-11-15..2026-02-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-15 12:12:13 -05:00' --until='2026-02-13 12:12:13 -05:00' --full-history --no-merges -- src/OpenSleigh/SagaExecutionService.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/OpenSleigh.Transport.Kafka/KafkaMessageParser.cs src/OpenSleigh.Transport.Kafka/KafkaMessageParser.cs:18 — src/OpenSleigh.Transport.Kafka/KafkaMessageParser.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is KafkaMessageParser.Parse at line 18), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “minor fixes”; “fixed tests”; “fixed message type resolution”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-11-15..2026-02-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-15 12:12:13 -05:00' --until='2026-02-13 12:12:13 -05:00' --full-history --no-merges -- src/OpenSleigh.Transport.Kafka/KafkaMessageParser.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs:65 — src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is KafkaMessageSubscriber.ConsumeMessageAsync at line 65), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fixed message type resolution”; “minor fixes”; “minor fixes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-11-15..2026-02-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-15 12:12:13 -05:00' --until='2026-02-13 12:12:13 -05:00' --full-history --no-merges -- src/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D10 · Test Quality · No assertions · ×2
  • No assertions: ReleaseAsync_should_unlock_instance tests/OpenSleigh.Tests/InMemorySagaStateRepositoryTests.cs:105 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: StartAsync_and_StopAsync_should_work tests/OpenSleigh.Tests/InMemorySubscriberTests.cs:11 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D1 · Cyclomatic Complexity · SqlSagaStateRepository.LockAsyncCore (cyclomatic 20) · ×1
  • SqlSagaStateRepository.LockAsyncCore (cyclomatic 20) src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:86 — SqlSagaStateRepository.LockAsyncCore has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 90, 139). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:86 — src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in SqlSagaStateRepository.LockAsyncCore at line 86. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-11-15..2026-02-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-11-15 12:12:13 -05:00' --until='2026-02-13 12:12:13 -05:00' --full-history --no-merges -- src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 18), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0246: The type or namespace name 'ISagaExecutionContext<>' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ISagaExecutionContext' could not be found (are you missing a using directive or an assembly reference?).
D2 · Cognitive Complexity · SqlSagaStateRepository.LockAsyncCore (cognitive 19) · ×1
  • SqlSagaStateRepository.LockAsyncCore (cognitive 19) src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:86 — SqlSagaStateRepository.LockAsyncCore has cognitive complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D22 · Internal API Consistency · Redundant operations for infrastructure setup. One is an interface method on a specific creator, the other is an extension method on IHost. This creates two entry points for the same logical action. · ×1
  • Redundant operations for infrastructure setup. One is an interface method on a specific creator, the other is an extension method on IHost. This creates two entry points for the same logical action. — Remove the extension method and require users to inject IInfrastructureCreator, or remove the interface and keep only the extension method for simplicity. Given the interface exists, the extension method is likely redundant boilerplate. (signatures: IInfrastructureCreator.SetupAsync(IHost host) | IHostExtensions.SetupInfrastructureAsync(IHost host))
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: SagaExecutionService.cs ↔ SagaInstance.cs src/OpenSleigh/SagaExecutionService.cs:1 — `src/OpenSleigh/SagaExecutionService.cs` and `src/OpenSleigh/SagaInstance.cs` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `3b395872` fix E2E test flakiness caused by concurrency issues in multi-host sce…; `3ed2f9a5` Allow a saga to be started by multiple message types; `e7e3bb98` updated tests — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (33–34 lines × 2) · ×1
  • Duplicated block (33–34 lines × 2) src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:52 — src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:52-84 | src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:44-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:52` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs:95 — src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs:95-122 | src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.cs:78-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/OpenSleigh.Persistence.Mongo/Entities/OutboxMessage.cs:27 — src/OpenSleigh.Persistence.Mongo/Entities/OutboxMessage.cs:27-45 | src/OpenSleigh.Persistence.SQL/Entities/OutboxMessage.cs:23-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:156 — src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:156-171 | src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:186-202 — 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/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs:156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/OpenSleigh.Persistence.Mongo/Entities/SagaState.cs:8 — src/OpenSleigh.Persistence.Mongo/Entities/SagaState.cs:8-19 | src/OpenSleigh.Persistence.SQL/Entities/SagaState.cs:8-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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) src/OpenSleigh.Persistence.Mongo/Entities/OutboxMessage.cs:14 — src/OpenSleigh.Persistence.Mongo/Entities/OutboxMessage.cs:14-20 | src/OpenSleigh.Persistence.SQL/Entities/OutboxMessage.cs:10-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:92 — src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:92-96 | src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:141-145 — 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/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:92` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19–28 lines × 2) · ×1
  • Duplicated block (19–28 lines × 2) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.NotificationsService/Program.cs:11 — samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.NotificationsService/Program.cs:11-38 | samples/OpenSleigh.Samples.Sample1/Program.cs:12-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.API/Program.cs:13 — samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.API/Program.cs:13-18 | samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.API/Program.cs:13-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (51 lines × 2) · ×1
  • Duplicated block (51 lines × 2) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.API/Startup.cs:21 — samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.API/Startup.cs:21-71 | samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.API/Startup.cs:20-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (32 lines × 5) · ×1
  • Duplicated block (32 lines × 5) samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.InventoryService/Program.cs:17 — samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.InventoryService/Program.cs:17-49 | samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/Program.cs:17-48 | samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.PaymentService/Program.cs:17-48 | samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.ShippingService/Program.cs:17-48 | samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.Worker/Program.cs:15-52 — `samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.InventoryService/Program.cs` and `samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
IC1 · Incompleteness & stubs · Hollow method · ×1
  • Hollow method — returns a constant without doing the work src/OpenSleigh.Reporting/ServiceCollectionExtensions.cs:7 — `AddOpenSleighReporting` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits src/OpenSleigh.Transport.RabbitMQ/RabbitMessageParser.cs:21 — `ParseMessageAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to src/OpenSleigh/SagaInstance.cs:47 — 1 guard above `return true;` also returns `true`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
P8 · Schema migrations · Schema created with EnsureCreated() (no migration path) · ×1
  • Schema created with EnsureCreated() (no migration path) src/OpenSleigh.Persistence.SQL/SagaDbContext.cs:13 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
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.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×1
  • Owned disposable field is never released src/OpenSleigh.Transport.RabbitMQ/RabbitPersistentConnection.cs:15 — `RabbitPersistentConnection` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 15), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `Dispose` (line 25) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X2 · Cancellation propagation · Async endpoint handler without CancellationToken · ×1
  • Async endpoint handler without CancellationToken: /orders samples/OpenSleigh.Samples.PizzaTracker/Program.cs:24 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Minor — 97 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×26
  • Orphaned file src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.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/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.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/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.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/OpenSleigh.InMemory/InMemorySagaStateRepository.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/OpenSleigh.Transport.RabbitMQ/IChannelExtensions.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/OpenSleigh/SagaInstance.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/OpenSleigh.Transport.Kafka/KafkaMessageHandler.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/OpenSleigh/SagaExecutionService.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/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.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/OpenSleigh.Persistence.Mongo/DbContext.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/OpenSleigh.Persistence.Mongo/MongoOutboxRepository.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/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.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/OpenSleigh.InMemory/Messaging/InMemorySubscriber.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/OpenSleigh/Outbox/MessageEnvelope.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/OpenSleigh.Transport.Kafka/KafkaMessageSubscriber.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/OpenSleigh.Transport.Kafka/KafkaPublisher.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/OpenSleigh.Persistence.SQL/SqlOutboxRepository.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/OpenSleigh.Transport.RabbitMQ/RabbitPublisher.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/OpenSleigh/Outbox/OutboxProcessor.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/OpenSleigh.Persistence.SQLServer/QueryHintInterceptor.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/OpenSleigh.Transport.Kafka/IBusConfiguratorExtensions.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/OpenSleigh.Reporting/EndpointRouteBuilderExtensions.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/OpenSleigh.Transport.RabbitMQ/RabbitPersistentConnection.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/OpenSleigh.Transport.Kafka/KafkaMessageParser.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/OpenSleigh.Transport.RabbitMQ/ChannelFactory.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.
  • + 1 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×21
  • Mock-dominated test: Should_process_messages_from_channel tests/OpenSleigh.Tests/InMemorySubscriberTests.cs:26 — This test sets up 3 test doubles (for example `Substitute.For<IMessageProcessor>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessAsync_should_invoke_handler tests/OpenSleigh.Tests/MessageHandlerManagerTests.cs:8 — This test sets up 4 test doubles (for example `Substitute.For<IHandleMessage<FakeSagaStarter>>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ExecuteAsync_should_process_messages_and_stop_on_cancellation tests/OpenSleigh.Tests/Outbox/OutboxBackgroundServiceTests.cs:9 — This test sets up 6 test doubles (for example `Substitute.For<IOutboxProcessor>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessPendingMessagesAsync_should_publish_and_delete_messages tests/OpenSleigh.Tests/Outbox/OutboxProcessorTests.cs:10 — This test sets up 5 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessPendingMessagesAsync_should_skip_null_messages tests/OpenSleigh.Tests/Outbox/OutboxProcessorTests.cs:34 — This test sets up 5 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessPendingMessagesAsync_should_handle_LockException_gracefully tests/OpenSleigh.Tests/Outbox/OutboxProcessorTests.cs:56 — This test sets up 5 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessPendingMessagesAsync_should_handle_general_exception_per_message tests/OpenSleigh.Tests/Outbox/OutboxProcessorTests.cs:82 — This test sets up 5 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessPendingMessagesAsync_should_rollback_on_outer_exception tests/OpenSleigh.Tests/Outbox/OutboxProcessorTests.cs:108 — This test sets up 5 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: CommitAsync_should_not_append_when_outbox_empty tests/OpenSleigh.Tests/SagaExecutionServiceAdditionalTests.cs:143 — This test sets up 3 test doubles (for example `Substitute.For<ISagaStateRepository>()`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ReleaseAsync_should_delegate_to_repository tests/OpenSleigh.Tests/SagaExecutionServiceTests.cs:142 — This test sets up 3 test doubles (for example `Substitute.For<ISagaStateRepository>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessAsync_should_call_ProcessAsync_on_instance_and_commit tests/OpenSleigh.Tests/SagaRunnerAdditionalTests.cs:8 — This test sets up 4 test doubles (for example `Substitute.For<ILogger<SagaRunner>>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessAsync_should_do_nothing_when_context_not_found tests/OpenSleigh.Tests/SagaRunnerTests.cs:7 — This test sets up 4 test doubles (for example `Substitute.For<ILogger<SagaRunner>>()`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ExecuteAsync_should_skip_subscribers_when_publish_only tests/OpenSleigh.Tests/SubscribersBackgroundServiceTests.cs:8 — This test sets up 3 test doubles (for example `Substitute.For<ISystemInfo>()`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ExecuteAsync_should_start_subscribers_when_not_publish_only tests/OpenSleigh.Tests/SubscribersBackgroundServiceTests.cs:28 — This test sets up 3 test doubles (for example `Substitute.For<ISystemInfo>()`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: StopAsync_should_stop_subscribers_when_not_publish_only tests/OpenSleigh.Tests/SubscribersBackgroundServiceTests.cs:49 — This test sets up 3 test doubles (for example `Substitute.For<ISystemInfo>()`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: PublishAsync_should_register_message_type tests/OpenSleigh.Tests/Transport/DefaultMessageBusTests.cs:22 — This test sets up 4 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: PublishAsync_should_append_message_to_outbox tests/OpenSleigh.Tests/Transport/DefaultMessageBusTests.cs:38 — This test sets up 4 test doubles (for example `Substitute.For<IOutboxRepository>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ProcessAsync_should_resolve_descriptors_and_dispatch tests/OpenSleigh.Tests/Transport/MessageProcessorTests.cs:22 — This test sets up 3 test doubles (for example `Substitute.For<ISagaRunner>()`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: StartAsync_should_republish_to_deadletter_when_exception_occurs tests/OpenSleigh.Transport.Kafka.Tests/Unit/KafkaMessageHandlerTests.cs:68 — This test sets up 6 test doubles (for example `NSubstitute.Substitute.For<IKafkaMessageParser>()`) against 5 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: StartAsync_should_not_republish_to_deadletter_when_exception_occurs_and_no_deadletter_available tests/OpenSleigh.Transport.Kafka.Tests/Unit/KafkaMessageHandlerTests.cs:105 — This test sets up 6 test doubles (for example `NSubstitute.Substitute.For<IKafkaMessageParser>()`) against 4 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: PublishAsync_publish_message tests/OpenSleigh.Transport.Kafka.Tests/Unit/KafkaPublisherTests.cs:45 — This test sets up 4 test doubles (for example `NSubstitute.Substitute.For<IProducer<string, byte[]>>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
X4 · Structured logging · Interpolated log message defeats structured logging · ×20
  • Interpolated log message defeats structured logging src/OpenSleigh/SubscribersBackgroundService.cs:27 — 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/OpenSleigh/SubscribersBackgroundService.cs:31 — 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/OpenSleigh/SubscribersBackgroundService.cs:44 — 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/OpenSleigh.Transport.RabbitMQ/RabbitMessageSubscriber.cs:56 — 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/OpenSleigh.Transport.RabbitMQ/RabbitPersistentConnection.cs:59 — 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 samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.Worker/Sagas/SimpleSaga.cs:33 — 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 samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.Worker/Sagas/SimpleSaga.cs:41 — 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 samples/OpenSleigh.Samples.Sample2/OpenSleigh.Samples.Sample2.Worker/Sagas/SimpleSaga.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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.InventoryService/Sagas/InventoryCheckSaga.cs:27 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.InventoryService/Sagas/InventoryCheckSaga.cs:32 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.NotificationsService/EventHandlers/NotificationsHandlers.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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.NotificationsService/EventHandlers/NotificationsHandlers.cs:33 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/Sagas/OrderSaga.cs:35 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/Sagas/OrderSaga.cs:48 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/Sagas/OrderSaga.cs:61 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.Orchestrator/Sagas/OrderSaga.cs:74 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.PaymentService/Sagas/CreditCheckSaga.cs:27 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.PaymentService/Sagas/CreditCheckSaga.cs:32 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.ShippingService/Sagas/ShippingSaga.cs:27 — 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 samples/OpenSleigh.Samples.ECommerce/OpenSleigh.Samples.ECommerce.ShippingService/Sagas/ShippingSaga.cs:32 — 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.
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.cs:98 — `entity.LockId is not null && entity.LockTime is not null` appears character-identically in 2 files — src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs, src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.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/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:113 — `entity.LockId is not null && entity.LockTime is not null && entity.LockTime > DateTimeOffset.UtcNow - _options.LockMaxDuration` appears character-identically in 2 files — src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs, src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.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/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.cs:80 — `entity.StateData is not null && entity.StateData.Length > 0 && entity.SagaStateType is not null` appears character-identically in 2 files — src/OpenSleigh.Persistence.Mongo/MongoSagaStateQuery.cs, src/OpenSleigh.Persistence.SQL/SqlSagaStateQuery.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/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.cs:194 — `state.Descriptor.SagaStateType is not null && state.GetType().IsGenericType` appears character-identically in 2 files — src/OpenSleigh.Persistence.Mongo/MongoSagaStateRepository.cs, src/OpenSleigh.Persistence.SQL/SqlSagaStateRepository.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.
D12 · Dependency Hygiene · Outdated · ×2
  • Outdated: coverlet.collector tests/OpenSleigh.E2ETests/OpenSleigh.E2ETests.csproj:23 — coverlet.collector 6.0.4 → 10.1.0 available (referenced by OpenSleigh.Tests).
  • Outdated: coverlet.msbuild tests/OpenSleigh.Persistence.Mongo.Tests/OpenSleigh.Persistence.Mongo.Tests.csproj:25 — coverlet.msbuild 6.0.4 → 10.1.0 available (referenced by OpenSleigh.Persistence.SQL.Tests).
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift docs/how-to/reporting.md:17 — docs/how-to/reporting.md installs the package `OpenSleigh.Reporting` (`dotnet add package OpenSleigh.Reporting`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift src/OpenSleigh.Reporting/README.md:8 — src/OpenSleigh.Reporting/README.md installs the package `OpenSleigh.Reporting` (`dotnet add package OpenSleigh.Reporting`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch src/OpenSleigh.Persistence.SQL/SqlOutboxRepository.cs:65 — `AppendAsyncCore` swallows `Exception` into `return OutboxAppendResult.Duplicate;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/OpenSleigh.Persistence.Mongo/MongoOutboxRepository.cs:49 — `AppendAsyncCore` swallows `MongoBulkWriteException` into `return OutboxAppendResult.Duplicate;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D21 · Naming Consistency · Inconsistent use of 'by_type' in test names. Some tests use 'Create_by_type_should_...' while others use 'Create_should_...' or 'Create_by_type_should_...'. The prefix 'by_type' is used inconsistently to describe the same input mechanism (creating by type vs by other means or just general creation). · ×1
  • Inconsistent use of 'by_type' in test names. Some tests use 'Create_by_type_should_...' while others use 'Create_should_...' or 'Create_by_type_should_...'. The prefix 'by_type' is used inconsistently to describe the same input mechanism (creating by type vs by other means or just general creation). — Standardize to 'Create_should_...' for all tests in this class, or consistently use 'CreateByType_should_...' if distinguishing from 'CreateByMessage_should_...'. Given the other test 'Create_should_use_provided_creator', 'Create_should_...' seems to be the preferred base pattern. (symbols: OpenSleigh.Transport.RabbitMQ.Tests.Unit.QueueReferenceFactoryTests.Create_by_type_should_throw_if_type_does_not_implement_IMessage, OpenSleigh.Transport.RabbitMQ.Tests.Unit.QueueReferenceFactoryTests.Create_should_use_provided_creator, OpenSleigh.Transport.RabbitMQ.Tests.Unit.QueueReferenceFactoryTests.Create_by_type_should_return_valid_references)
D21 · Naming Consistency · Inconsistent naming of the action being tested. One test uses 'Create_by_type_should_throw...' while another uses 'Create_should_use_provided_creator...'. The first implies a specific input method ('by_type') while the second is more generic ('Create'). · ×1
  • Inconsistent naming of the action being tested. One test uses 'Create_by_type_should_throw...' while another uses 'Create_should_use_provided_creator...'. The first implies a specific input method ('by_type') while the second is more generic ('Create'). — Align with the more specific naming if 'by_type' is a distinct scenario, or align with the generic naming if 'by_type' is just one way to call Create. Given 'Create_should_use_provided_creator' exists, 'Create_by_type_should_throw' should likely be 'Create_should_throw_if_type_does_not_implement_IMessage'. (symbols: OpenSleigh.Transport.RabbitMQ.Tests.Unit.QueueReferenceFactoryTests.Create_by_type_should_throw_if_type_does_not_implement_IMessage, OpenSleigh.Transport.RabbitMQ.Tests.Unit.QueueReferenceFactoryTests.Create_should_use_provided_creator)
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 26 of 26 significant files have no living knowledge — the codebase as a whole is dormant, not 26 separate risks. Counted over 26 of the 147 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×1
  • Placeholder literal left in code samples/OpenSleigh.Samples.Sample1/SagaWithState.cs:43 — A placeholder string ("lorem ipsum") is still in shipped code — typical of generated boilerplate that was never filled in.
IC1 · Incompleteness & stubs · Commented-out code · ×1
  • Commented-out code src/OpenSleigh.Transport.Kafka/IBusConfiguratorExtensions.cs:60 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
M1 · Documentation (README) · Thin README · ×1
  • Thin README — The root README is 63 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.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 387/526 types (74%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P10 · Library API & versioning · No explicit versioning · ×1
  • No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 12 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 13/20 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 20, 11 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 92/100 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.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.9 `!` suppressions per 1k syntax nodes — 31 suppression(s) across the 32681 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 34 finding(s)
D12 · Dependency Hygiene · Outdated · ×27
  • Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 10.0.3 → 10.0.13 available (referenced by OpenSleigh).
  • Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 10.0.3 → 10.0.13 available (referenced by OpenSleigh).
  • Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.3 → 10.0.13 available (referenced by OpenSleigh).
  • Outdated: Microsoft.SourceLink.GitHub — Microsoft.SourceLink.GitHub 10.0.103 → 10.0.402 available (referenced by OpenSleigh).
  • Outdated: System.Threading.Channels — System.Threading.Channels 10.0.3 → 10.0.13 available (referenced by OpenSleigh.InMemory).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.0.1 → 18.11.0 available (referenced by OpenSleigh.Tests).
  • Outdated: NSubstitute — NSubstitute 5.3.0 → 6.2.0 available (referenced by OpenSleigh.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 3.1.5 → 4.0.1 available (referenced by OpenSleigh.Tests).
  • Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Samples.Sample1).
  • Outdated: System.Text.Json — System.Text.Json 10.0.3 → 10.0.13 available (referenced by OpenSleigh.E2ETests).
  • Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQL).
  • Outdated: Microsoft.EntityFrameworkCore.InMemory — Microsoft.EntityFrameworkCore.InMemory 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQL.Tests).
  • Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQL.Tests).
  • Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables — Microsoft.Extensions.Configuration.EnvironmentVariables 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQL.Tests).
  • Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQL.Tests).
  • Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQLServer).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Persistence.SQLServer).
  • Outdated: Polly — Polly 8.6.5 → 8.8.0 available (referenced by OpenSleigh.Transport.RabbitMQ).
  • Outdated: RabbitMQ.Client — RabbitMQ.Client 7.2.0 → 7.2.2 available (referenced by OpenSleigh.Transport.RabbitMQ).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Transport.RabbitMQ.Tests).
  • Outdated: Npgsql.EntityFrameworkCore.PostgreSQL — Npgsql.EntityFrameworkCore.PostgreSQL 10.0.0 → 10.0.3 available (referenced by OpenSleigh.Persistence.PostgreSQL).
  • Outdated: Mongodb.Driver — Mongodb.Driver 3.6.0 → 3.12.0 available (referenced by OpenSleigh.Persistence.Mongo).
  • Outdated: Swashbuckle.AspNetCore — Swashbuckle.AspNetCore 9.0.6 → 10.3.1 available (referenced by OpenSleigh.Samples.Sample2.API).
  • Outdated: Microsoft.Extensions.Logging.Console — Microsoft.Extensions.Logging.Console 10.0.3 → 10.0.13 available (referenced by OpenSleigh.Samples.Sample2.Worker).
  • Outdated: Confluent.Kafka — Confluent.Kafka 2.13.0 → 2.16.0 available (referenced by OpenSleigh.Transport.Kafka).
  • + 2 more in this group — see findings.md.
D10 · Test Quality · Mock framework · ×7
  • Mock framework: NSubstitute — OpenSleigh.Tests(net8.0) references NSubstitute.
  • Mock framework: NSubstitute — OpenSleigh.E2ETests(net8.0) references NSubstitute.
  • Mock framework: NSubstitute — OpenSleigh.Persistence.SQL.Tests(net8.0) references NSubstitute.
  • Mock framework: NSubstitute — OpenSleigh.Transport.RabbitMQ.Tests(net8.0) references NSubstitute.
  • Mock framework: NSubstitute — OpenSleigh.Persistence.Mongo.Tests(net8.0) references NSubstitute.
  • Mock framework: NSubstitute — OpenSleigh.Transport.Kafka.Tests(net8.0) references NSubstitute.
  • Mock framework: NSubstitute — OpenSleigh.Reporting.Tests(net8.0) references NSubstitute.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-594e3e88e57a4b6088ecdfd2293ae822/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-594e3e88e57a4b6088ecdfd2293ae822/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .26artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list src/OpenSleigh.sln package --vulnerable --include-transitive --format json6artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `src/OpenSleigh/NoOpSagaInstance.cs`, `src/OpenSleigh/Outbox/MessageEnvelope.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a16139-d8ea-7205-9e0a-cfd764544420 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 44 · Warnings: 165 · Recommendations: 97 · Info: 34 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 01:29 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.

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