zarusz/SlimMessageBus

Executive summary

zarusz/SlimMessageBus scores 48 out of 100 and is rated Weak, while six of its eight lenses score higher still: Event-Driven at 86, Architecture at 81 and Performance at 72, all rated Strong, and Domain Modelling at 70, Code Health at 63 and Production Readiness at 55, all rated Adequate.

The score is lower than those six because the weakest lens counts most, and here that is Maturity, which scores 41 and is rated Weak. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to reconcile the README with reality: README.md installs the package `SlimMessageBus` (`dotnet add package SlimMessageBus`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Kafka` (`dotnet add package SlimMessageBus.Host.Kafka`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), but no project or props file references it; docs/plugin_outbox_mongodb.md installs the package `SlimMessageBus.Host.Outbox.MongoDb` (`dotnet add package SlimMessageBus.Host.Outbox.MongoDb`), but no project or props file references it; docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), but no project or props file references it and to protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler, and if Maturity rose to 70, the score would rise from 48 to about 53.

86 findings are critical: 46 in Static Analysis (SAST), 16 in Explicit Debt, 12 in Domain ↔ infrastructure boundary, four in Dependency Vulnerabilities, three in Captive dependencies, two in REDACTED Scanning, one in Outbox / dual-write, one in Project dependency cycles and one in Secrets (history).

Watchdog couldn't measure 4 dimensions in this code, among them Code Coverage, Dependency Hygiene and IL Efficiency, so they are left out of the score. The product code is 26,861 lines, which would take an estimated 0.7 person-years, around €100,000, to rebuild.

Code Health 63 Adequate, capped by Nullable reference types Architecture 81 Strong Maturity 41 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 55 Adequate, capped by Schema migrations Security and Compliance 43 Weak, capped by Static Analysis (SAST) and Access Controls Domain Modelling 70 Adequate, capped by Domain ↔ infrastructure boundary Event-Driven 86 Strong Performance 72 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.

Maturity 41 · counts for 45%Security and Compliance 43 · counts for 25%Production Readiness 55 · counts for 14%Code Health 63 · counts for 8%Domain Modelling 70 · counts for 4%Performance 72 · counts for 2%Architecture 81 · counts for 1%Event-Driven 86 · counts for 1%

If Maturity rose from 41 to 70, the lowest score rated Strong, the score would rise from 48 to about 53.

Code composition: what the lines of code are

Business logic 20%Supporting code 30%Tests 49%Generated by tools 0%

New since the last survey: 75 findings

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

REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
Explicit Debt · EmptyCatchBlock src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs
Explicit Debt · EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Explicit Debt · EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Explicit Debt · EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Explicit Debt · EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Explicit Debt · EmptyCatchBlock src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs
Explicit Debt · Dead code: DeleteFile src/Samples/Sample.Images.FileStore/IFileStore.cs
Explicit Debt · Dead code: AuditingHandler src/Samples/Sample.DomainEvents.Application/DomainEventHandlers/AuditingHandler.cs
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Access Controls · No authorization REDACTED
Access Controls · No authorization src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Access Controls · No authorization src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs
Access Controls · No authorization src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs
Access Controls · No authorization src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs
Access Controls · No authorization src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs
Access Controls · No authorization src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs
Access Controls · No authorization src/Samples/Sample.Nats.WebApi/Program.cs
Access Controls · No authorization src/Samples/Sample.Nats.WebApi/Program.cs
Access Controls · No authorization src/Samples/Sample.OutboxWebApi/Program.cs
Access Controls · No authorization src/Samples/Sample.ValidatingWebApi/Program.cs
Access Controls · No authorization src/Samples/Sample.ValidatingWebApi/Program.cs
Access Controls · No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs
Access Controls · No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs
Access Controls · No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs
Access Controls · No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs
Async correctness · Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs
Async correctness · Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs
Async correctness · Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs
Cancellation propagation · Async method without CancellationToken: Start src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs
Cancellation propagation · Async method without CancellationToken: Stop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs
Cancellation propagation · Async method without CancellationToken: Start src/SlimMessageBus.Host/MessageBusBase.cs
Cancellation propagation · Async method without CancellationToken: Stop src/SlimMessageBus.Host/MessageBusBase.cs
Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs
Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs
Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs
Cancellation propagation · Async method without CancellationToken: OnStart src/SlimMessageBus.Host.AzureEventHub/Consumer/EhGroupConsumer.cs
Cancellation propagation · Async method without CancellationToken: OnStop src/SlimMessageBus.Host.AzureEventHub/Consumer/EhGroupConsumer.cs
Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs
Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs
Cancellation propagation · Async method without CancellationToken: OnStart src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs
Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Memory/MemoryMessageBus.cs
Exception handling · Swallowed exception (empty catch) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs
Exception handling · Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Exception handling · Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Exception handling · Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Exception handling · Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
Exception handling · Swallowed exception (empty catch) src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs
Captive dependencies · Captive dependency: singleton PendingRequestManager captures transient IPendingRequestStore src/SlimMessageBus.Host/RequestResponse/PendingRequestManager.cs
Captive dependencies · Captive dependency: singleton OutboxSendingTask captures transient OutboxSettings src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs
Captive dependencies · Captive dependency: singleton OutboxCleanUpTask captures transient OutboxSettings src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs
Stateful singletons · Stateful singleton: HybridMessageSerializerProvider src/SlimMessageBus.Host.Serialization.Hybrid/HybridMessageSerializerProvider.cs
Stateful singletons · Stateful singleton: HealthCheckBackgroundService src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations src/Samples/Sample.OutboxWebApi/Program.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs
Async & latency hygiene · Sync-over-async blocking src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs
Async & latency hygiene · Sync-over-async blocking src/SlimMessageBus.Host/MessageBusBase.cs
Async & latency hygiene · Sync-over-async blocking src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs

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

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

Coupling · Off the main sequence: SecretStore
Static Analysis (SAST) · Medium: REDACTED src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Static Analysis (SAST) · Medium: REDACTED src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs
Static Analysis (SAST) · Medium: REDACTED src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs
Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs

Rebuild cost: about €100,000 · Estimate

Cost to rebuild	€33,000 to €170,000, for 546 to 1,753 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem	Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 26,861 lines of product code, of which 36% is declarations and boilerplate, 24% straight logic and 41% logic with branches
Comment lines	The estimate prices 23,648 lines. Comment lines count towards the size of 26,861 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.

Reconcile the README with reality: README.md installs the package `SlimMessageBus` (`dotnet add package SlimMessageBus`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Kafka` (`dotnet add package SlimMessageBus.Host.Kafka`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), but no project or props file references it; docs/plugin_outbox_mongodb.md installs the package `SlimMessageBus.Host.Outbox.MongoDb` (`dotnet add package SlimMessageBus.Host.Outbox.MongoDb`), but no project or props file references it; docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), but no project or props file references it.

Raises the score by about 5 points · Medium effort · Documentation accuracy

Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

Raises the score by about 4 points · Medium effort · Access Controls

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.

Raises the score by about 4 points · Medium effort · Architecture documentation

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €100,000 to build again, about 0.7 person-years of work. Its weakest lens is Maturity, at 41 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.

Based on: the rebuild estimate · the Maturity grade · how much each lens counts

What to do: Start with the Maturity actions in Top priorities.

If you do one thing first · First action

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

55 modules, with 134 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 15 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 SlimMessageBus	2 SlimMessageBus.Host.Serialization	3 SlimMessageBus.Host.Sql.Common	4 SlimMessageBus.Host.Collections	5 SlimMessageBus.Host.Interceptor	6 SlimMessageBus.Host	7 SlimMessageBus.Host.Consumer.ErrorHandling	10 SlimMessageBus.Host.Outbox	11 SlimMessageBus.Host.Relational	12 SlimMessageBus.Host.Services	15 SlimMessageBus.Host.AzureServiceBus	21 SlimMessageBus.Host.Outbox.MongoDb	22 SlimMessageBus.Host.Outbox.MongoDb.Configuration	23 SlimMessageBus.Host.Outbox.MongoDb.Transactions	24 SlimMessageBus.Host.Outbox.PostgreSql.Configuration	26 SlimMessageBus.Host.Outbox.Sql	35 SlimMessageBus.Host.Outbox.PostgreSql.Transactions	37 SlimMessageBus.Host.Outbox.PostgreSql	38 SlimMessageBus.Host.Outbox.PostgreSql.Repositories
1 SlimMessageBus
2 SlimMessageBus.Host.Serialization
3 SlimMessageBus.Host.Sql.Common
4 SlimMessageBus.Host.Collections	2					4
5 SlimMessageBus.Host.Interceptor	6
6 SlimMessageBus.Host	26	4		5	2
7 SlimMessageBus.Host.Consumer.ErrorHandling	1					3
8 SlimMessageBus.Host.FluentValidation	3				3	2
9 SlimMessageBus.Host.Hybrid		1		1		7
10 SlimMessageBus.Host.Outbox						9
11 SlimMessageBus.Host.Relational				1		21
12 SlimMessageBus.Host.Services						7
13 SlimMessageBus.Host.AmazonSQS	1	3				23	1			2
14 SlimMessageBus.Host.AzureEventHub	1			2		24	1			2
15 SlimMessageBus.Host.AzureServiceBus	1			1		25	1			2
16 SlimMessageBus.Host.GooglePubSub	1					20	1			2
17 SlimMessageBus.Host.Kafka	1	8		1	1	25	1			2
18 SlimMessageBus.Host.Memory		3				12	1
19 SlimMessageBus.Host.Mqtt						12	1			2
20 SlimMessageBus.Host.Nats						16	1			2
21 SlimMessageBus.Host.Outbox.MongoDb								3
22 SlimMessageBus.Host.Outbox.MongoDb.Configuration						5		1
23 SlimMessageBus.Host.Outbox.MongoDb.Transactions								1
24 SlimMessageBus.Host.Outbox.PostgreSql.Configuration						1		1
25 SlimMessageBus.Host.Outbox.Services	2				4	5		7
26 SlimMessageBus.Host.Outbox.Sql			5			7		8
27 SlimMessageBus.Host.PostgreSql						21	1		5	2
28 SlimMessageBus.Host.RabbitMQ	1					40	1			2
29 SlimMessageBus.Host.Redis		3		1		22	1			2
30 SlimMessageBus.Host.Sql			5			21	1		5	2
31 SlimMessageBus.Host.AzureServiceBus.Consumer						7					6
32 SlimMessageBus.Host.Outbox.MongoDb.Interceptors	1				1									1
33 SlimMessageBus.Host.Outbox.MongoDb.Repositories								1				5		1
34 SlimMessageBus.Host.Outbox.MongoDb.Services								1				1	1
35 SlimMessageBus.Host.Outbox.PostgreSql.Transactions								1							1
36 SlimMessageBus.Host.Outbox.Sql.DbContext			3			2		1								4
37 SlimMessageBus.Host.Outbox.PostgreSql	1				1	4		3							2		1
38 SlimMessageBus.Host.Outbox.PostgreSql.Repositories								1							2		1	4
39 SlimMessageBus.Host.Outbox.PostgreSql.Services								1							1			2
40 SlimMessageBus.Host.Outbox.PostgreSql.DbContext						1									3		2	1	1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 63% · Adequate · gated by X5 ·

The Good

D1 · .NET / C# Cyclomatic Complexity 9.1 D2 · .NET / C# Cognitive Complexity 7.7 D3 · .NET / C# God Classes 9.7 D4 · .NET / C# Code Duplication 9.5 D17 · .NET / C# Explicit Debt 8.2 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.0 X1 · Repo Async correctness 7.4 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 X20 · Repo Mistyped argument guard 7.5 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 X4 · Repo Structured logging 10.0

The Bad

X18 · Repo Disposal-pattern correctness 5.7 X2 · Repo Cancellation propagation 6.5 X3 · Repo Exception handling 6.5

The Ugly

X5 · Repo Nullable reference types 3.8

At a glance — Architecture · 81% · Strong ·

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.9 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 8.9 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 7.5 AX10 · Repo Code composition 8.1 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

The Bad

AX2 · Repo Stateful singletons 6.0

At a glance — Maturity · 41% · Weak · gated by M2, M4 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 9.0 D21 · .NET / C# Naming Consistency 9.0 D24 · .NET / C# Comment Value 10.0 D34 · .NET / C# Knowledge Freshness 9.1 M3 · Repo Folder & project structure 10.0

The Bad

M1 · Repo Documentation (README) 6.9

The Ugly

M2 · Repo Architecture documentation 2.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 55% · Adequate · gated by P8 ·

The Good

D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.3 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0

The Bad

D13 · .NET / C# REDACTED Scanning 5.0 ED5 · Repo Idempotency 6.5 P3 · Repo Security & performance tooling 5.0

The Ugly

P5 · Repo DR & Backup 4.0 P8 · Repo Schema migrations 3.0

At a glance — Security · 43% · Weak · gated by D29, C2 ·

The Good

D28 · .NET / C# Secrets (history) 9.0 D30 · .NET / C# Dependency Vulnerabilities 7.3 D31 · .NET / C# IaC & Container Security 8.9 D32 · .NET / C# Data Compliance (PII/GDPR) 9.0 D44 · .NET / C# Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.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 Bad

C1 · Repo Data Protection 5.0 C4 · Repo Data Retention 6.5

The Ugly

D29 · .NET / C# Static Analysis (SAST) 0.1 C2 · Repo Access Controls 0.0

At a glance — Domain Modelling · 70% · Adequate · gated by DM6 ·

The Good

DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 10.0 DM12 · Repo Ambient inputs in the domain 9.5 DM4 · Repo Rich vs anemic model 10.0 DM5 · Repo Encapsulated state 10.0 DM7 · Repo Repository granularity 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0

The Bad

DM11 · Repo Constructible invalid state 6.5

The Ugly

DM6 · Repo Domain ↔ infrastructure boundary 2.0

At a glance — Event-Driven · 86% · Strong ·

The Good

ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0

The Bad

ED4 · Repo Outbox / dual-write 6.8

At a glance — Performance · 72% · Strong ·

The Good

PF1 · Repo Benchmark discipline 10.0

The Bad

PF2 · Repo Allocation hygiene 6.7 PF3 · Repo Async & latency hygiene 6.0

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 category	Findings	Severity
A05:2025 — Injection	47	High / Critical
A02:2025 — Security Misconfiguration	11	Medium
A03:2025 — Software Supply Chain Failures	5	High / Critical
A07:2025 — Authentication Failures	4	High / Critical
A01:2025 — Broken Access Control	1	Medium

Roadmap

First, reconcile all documentation to accurately reflect the current codebase by removing references to packages that are no longer present. Next, enforce strict access controls by implementing default-deny authorization on all endpoints and handlers. Additionally, document significant architectural decisions in a dedicated folder to preserve design context and rationale. Finally, address data protection gaps by encrypting sensitive data at rest and immediately resolve the two leaked secrets found in the repository.

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

Do this	Helps	Effort	Dimension
Reconcile the README with reality: README.md installs the package `SlimMessageBus` (`dotnet add package SlimMessageBus`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Kafka` (`dotnet add package SlimMessageBus.Host.Kafka`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), but no project or props file references it; docs/plugin_outbox_mongodb.md installs the package `SlimMessageBus.Host.Outbox.MongoDb` (`dotnet add package SlimMessageBus.Host.Outbox.MongoDb`), but no project or props file references it; docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), but no project or props file references it.	+5.0 pts	Medium	Documentation accuracy
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.	+4.4 pts	Medium	Access Controls
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.	+4.2 pts	Medium	Architecture documentation
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).	+1.9 pts	Low	REDACTED Scanning
Resolve the 1 Typo in type name finding(s) in Naming Consistency.	+1.1 pts	Low	Naming Consistency
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2).	+1.1 pts	Low	Static Analysis (SAST)
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).	+2.1 pts	Medium	Data Protection
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED.	+0.9 pts	Low	Dependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 138 files carrying findings, judged against the Production bar: 1% slop · 31% mixed · 68% near-clean.

File	Score	Band	Worst signal
REDACTED	1.6	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	3.3	Slop	Dependency Vulnerabilities: High CVE: REDACTED
src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs	4.0	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	4.3	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs	5.0	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	5.5	Mixed	Explicit Debt: WriteOnlyPrivateField
src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs	5.8	Mixed	Explicit Debt: EmptyCatchBlock
src/.editorconfig	5.8	Mixed	Explicit Debt: AnalyzerSeverityNone
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs	6.0	Mixed	Explicit Debt: TodoComment
src/Samples/Sample.DomainEvents.WebApi/Sample.DomainEvents.WebApi.csproj	6.1	Mixed	Explicit Debt: NoWarnInCsproj
src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs	6.7	Mixed	Explicit Debt: TodoComment

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

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

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

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

Could not be resolved — 6

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. 90 of 95 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 — 95 dimensions across the health lenses

D1D2D3D4D5D6D9D10D11D13D14D15D17D18D19D21D24D26D27D28D29D30D31D32D34D35D44AX1AX10AX2AX3AX4AX5AX6AX8AX9C1C2C4DM1DM10DM11DM12DM4DM5DM6DM7DM8DM9ED1ED2ED4ED5GD1IC1M1M2M3M4P1P2P3P4P5P6P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.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 measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16139-6583-70c6-a3e4-5c838e88d984.

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.
D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
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 (20 contributor(s) across 766 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 19 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — 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. Large codebase (26,861 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
D32 Data Compliance (PII/GDPR) — 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. `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs`, … (+75 more) 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) — sqldb Error context canceled storage Error context canceled mongodb Error context canceled nats Error context canceled kafka-init Error context canceled rabbitmq Error context canceled psqldb Error context canceled mqtt Error context canceled kafka Error context canceled redis Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redis Error Get "https://registry-1.docker.io/v2/": Forbidden sqldb Error context canceled mqtt Error context canceled rabbitmq Error context canceled mongodb Error context canceled kafka-init Error context canceled nats Error context canceled storage Error context canceled psqldb Error context canceled 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.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 132 further occurrence(s) are not listed individually; the score already reflects all 172.

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.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.1 / 10Stronggated by 4 serious findings✓ 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.1 / 10 · rule-coverage 100% · ceiling Prevented

4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MemoryMessageBusBuilder.AutoDeclareFrom at 25. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DefaultGooglePubSubHeaderSerializer.Deserialize at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/SlimMessageBus.Host.GooglePubSub/Headers/DefaultGooglePubSubHeaderSerializer.cs (DefaultGooglePubSubHeaderSerializer.Deserialize at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

MemoryMessageBusBuilder.AutoDeclareFrom (cyclomatic 25)src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:41

ServiceBusTopologyService.PrepareSubscription (cyclomatic 21)src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:153

MessageProcessor.ProcessMessage (cyclomatic 18)src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:82

MessageHandler.DoHandle (cyclomatic 17)src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:57

What to do

Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MemoryMessageBusBuilder.AutoDeclareFrom (cyclomatic 25), ServiceBusTopologyService.PrepareSubscription (cyclomatic 21), MessageProcessor.ProcessMessage (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity7.7 / 10Strong✓ 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 7.7 / 10 · rule-coverage 100% · ceiling Prevented

12 method(s) exceeded the cognitive complexity threshold of 15; the worst was MemoryMessageBusBuilder.AutoDeclareFrom at 53.

MemoryMessageBusBuilder.AutoDeclareFrom (cognitive 53)src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:41

ServiceBusTopologyService.PrepareSubscription (cognitive 37)src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:153

MessageProcessor.ProcessMessage (cognitive 36)src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:82

RedisListCheckerConsumer.Run (cognitive 30)src/SlimMessageBus.Host.Redis/Consumers/RedisListCheckerConsumer.cs:57

MessageHandler.DoHandle (cognitive 25)src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:57

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

What to do

Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with MemoryMessageBusBuilder.AutoDeclareFrom (cognitive 53), ServiceBusTopologyService.PrepareSubscription (cognitive 37), MessageProcessor.ProcessMessage (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.7 to about 8.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.7 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 god class(es) detected.

TooManyMethods: MessageBusBase · ×2src/SlimMessageBus.Host/MessageBusBase.cs

What to do

Resolve the 2 TooManyMethods finding(s) in God Classes — start with MessageBusBase.cs, RabbitMqChannelManager.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.5 / 10Stronggated by 27 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.5 / 10 · rule-coverage 100% · ceiling Verified

26 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 1 of the 27 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 (6 lines × 2) · ×4src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:85

Duplicated block (9 lines × 2) · ×3src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:22

Duplicated block (8 lines × 2) · ×2src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyService.cs:286

Duplicated block (11 lines × 2) · ×2src/SlimMessageBus.Host.PostgreSql/PostgreSqlSequentialGuidGenerator.cs:7

Duplicated block (7 lines × 2) · ×2src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:115

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

What to do

Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with MongoDbOutboxMessageRepository.cs (2), MemoryMessageBusBuilder.cs, PostgreSqlOutboxMessageRepository.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with PostgreSqlHelper.cs, RabbitMqMessageBus.cs, ServiceScopeExtensions.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SqsTopologyService.cs, ObjectToInferredTypesConverter.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 103 classes have LCOM4 above 3.

Low cohesion: RuntimeTypeCache (LCOM4 4)src/SlimMessageBus.Host/Collections/RuntimeTypeCache.cs:3

What to do

Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with RuntimeTypeCache.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

791 test methods: 632 unit, 159 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Stronggated by 3 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 1 zero-assertion, 2 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 791 tests.

Fixed-sleep synchronisation: Wait_ShouldBlockUntilSet · ×2src/Tests/SlimMessageBus.Host.Outbox.Test/AsyncManualResetEventTests.cs:58

No assertions: Given_MemoryConsumer_When_MessageScopeAccessorCalledInsideConsumer_Then_LooksUpInTheMessageScopesrc/Tests/SlimMessageBus.Host.Integration.Test/MessageScopeAccessor/MessageScopeAccessorTests.cs:30

Mock-dominated test: When_ExecuteConsumer_Given_ConsumerWithContext_Then_ConsumerContextSet · ×5src/Tests/SlimMessageBus.Host.Test/Consumer/MessageHandlerTest.cs:68

What to do

Resolve the 5 Mock-dominated test finding(s) in Test Quality — start with HybridMessageSerializerProviderTests.cs (2), MessageHandlerTest.cs, ServiceBusMessageBusSettingsTests.cs. — One of this dimension's main actionable groups (5 recommendation-level).
Resolve the 2 Fixed-sleep synchronisation finding(s) in Test Quality — start with AsyncManualResetEventTests.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 No assertions finding(s) in Test Quality — start with MessageScopeAccessorTests.cs. — One of this dimension's main actionable groups (1 warning-level).
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.

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). integration: measured (0 flaky); other: not included — too large to re-run within its budget.

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D13 · REDACTED 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

Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce REDACTED 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.

Do you agree with this assessment?

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 337 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 62 direct `PackageReference`(s), and 188 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt8.2 / 10Adequategated by 16 critical findings✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Prevented

47 deducted debt markers + 5 dead symbols across 26861 LoC in the .NET projects (0.9/KLoC) → score 8.2.

EmptyCatchBlock · ×6src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:123

WriteOnlyPrivateField · ×5REDACTED:14

AnalyzerSeverityNone · ×3src/.editorconfig:188

NoWarnInCsproj · ×2src/Samples/Sample.DomainEvents.WebApi/Sample.DomainEvents.WebApi.csproj:8

TodoComment · ×16src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:65

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

What to do

Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with RabbitMqChannelManager.cs (4), SqsTopologyCache.cs, MessageProcessor.cs. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 5 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED, OutboxBenchmarkTests.cs, OutboxForwardingPublishInterceptorTests.cs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (3). — One of this dimension's main actionable groups (3 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D18 · Solution Shape10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

177 projects, 2329 source files, 49995 hand-written lines of code (26861 production / 23134 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), plus 117 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 377 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

Do you agree with this assessment?

D19 · Documentation QualityStronggated by 50 serious findings◐ 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 repository's root README is excellent at conveying what SlimMessageBus is (a lightweight .NET messaging framework supporting multiple transports and plugins) with a strong license badge plus links to the GitHub Actions build status, SonarCloud quality gate, duplication, vulnerabilities, and maintainability ratings. The docs/ directory contains focused architecture documentation for each transport/plugin (Amazon SQS/SNS, Kafka, Azure EventHubs, etc.) plus usage examples for every major plugin in an outlineable format. The src/Samples/READMEs document the samples directories with clear quick-start commands and a running WebApi example showing how SlimMessageBus is used to publish domain events across memory, web request scoped scopes, and ASP.NET Core. The project's documentation is comprehensive and well-structured: the root README gives an overview of SlimMessageBus and its features (Pub/Sub communication, request-response, static accessor, dependency resolver), with a dedicated architecture/plugin docs directory covering every plugin type (AsyncAPI, FluentValidation, Outbox) plus detailed configuration for each transport. The XML-doc coverage is low (<10%) but the visible content is clear — an Introduction to SlimMessageBus that explains what the project does and where to find usage examples. The project's READMEs and architecture/Docs files are well documented: a single root README gives an overview of the outbox plugin for MongoDB (Transactional Outbox pattern backed by MongoDB), installation, and usage; the plugin_outbox_mongoDB.md document is a fully fleshed-out plugin guide with Configuration, Options, How it works, Collections, Migration versioning, Clean up, and an Important note section. The XML-doc coverage shows strong coverage of outbox plugins (26% missing from SlimMessageBus.Host.Outbox.MongoDb to 45% for AmazonSQS), but the visible document is a plugin guide rather than a root overview.

Low XML-doc coverage: SlimMessageBus(net10.0) · ×50src/SlimMessageBus/SlimMessageBus.csproj

XML-doc coverage: SlimMessageBus.Host.AspNetCore(net10.0) · ×2src/SlimMessageBus.Host.AspNetCore/SlimMessageBus.Host.AspNetCore.csproj

What to do

Resolve the 50 Low XML-doc coverage finding(s) in Documentation Quality — start with SlimMessageBus.csproj, SlimMessageBus.Host.csproj, SlimMessageBus.Host.Serialization.Json.csproj. — One of this dimension's main actionable groups (50 warning-level).

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

Do you agree with this assessment?

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

1 naming inconsistencies across 200 sampled symbols.

Typo in type name: 'Stategy' is used in DictionaryMessageCreationStategy, while 'Strategy' is used in ReflectionMessageCreationStrategy. These are parallel concepts within the same serialization strategy namespace.

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

62 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

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 90 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability8.9 / 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.9 / 10 · rule-coverage 100% · ceiling Documented

67 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

What to do

Improve Navigability — currently 8.9/10. — 67 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.1 / 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.1 / 10 · rule-coverage 100% · ceiling Documented

47 finding(s): 0 critical, 46 high, 1 medium, 0 low. 20 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 122 file(s) — `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs` (line 3), `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs` (line 3), `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs` (line 3), `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs` (line 5), `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs` (line 3), … (+117 more) — 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. In 103 of those file(s) — `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs`, … (+98 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `src/SlimMessageBus.Host.Memory/Consumers/ConcurrentMessageProcessorQueue.cs`, `src/Tests/SlimMessageBus.Host.Test/Consumer/AbstractConsumerTests.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

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

What to do

Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
No action in Static Analysis (SAST) — all 20 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 (20 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities7.3 / 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.3 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security8.9 / 10Strong✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 80 file(s) — `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs`, … (+75 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness9.1 / 10Exemplary✓ Tool-verified

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

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

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

12 of 137 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs. Counted over 137 of the 564 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×12src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs:1

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies7.5 / 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.

`PendingRequestManager` is registered as a SINGLETON but its constructor takes `IPendingRequestStore store`, 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 `IPendingRequestStore` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/SlimMessageBus.Host/RequestResponse/PendingRequestManager.cs:19
`OutboxSendingTask` is registered as a SINGLETON but its constructor takes `OutboxSettings outboxSettings`, 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 `OutboxSettings` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:5
`OutboxCleanUpTask` is registered as a SINGLETON but its constructor takes `OutboxSettings outboxSettings`, 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 `OutboxSettings` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs:20

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.

Do you agree with this assessment?

AX10 · Code composition8.1 / 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.

Do you agree with this assessment?

AX2 · Stateful singletons6.0 / 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.

`HybridMessageSerializerProvider` is a singleton (one shared instance) but mutates instance state outside any lock (DefaultSerializer, _serializerProviderByType; e.g. `DefaultSerializer` at line 34). — src/SlimMessageBus.Host.Serialization.Hybrid/HybridMessageSerializerProvider.cs:10
`OutboxSendingTask` is a singleton (one shared instance) but mutates instance state outside any lock (_loopCts, _loopTask, _startBusTask, _stopBusTask; e.g. `_loopCts` at line 51). — src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:3
`HealthCheckBackgroundService` is a singleton (one shared instance) but mutates instance state outside any lock (_onChangeDelegates; e.g. `_onChangeDelegates` at line 52). — src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:3

What to do

Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.

Do you agree with this assessment?

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 SlimMessageBus.Host ↔ SlimMessageBus.Host.Collections depend on each other. The lightest dependency in the cycle is SlimMessageBus.Host.Collections → SlimMessageBus.Host (SlimMessageBus.Host.Collections.KindMapping → SlimMessageBus.Host.MessageBusSettings, 4 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/SlimMessageBus.Host/Collections/KindMapping.cs:3

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

C1 · Data Protection5.0 / 10Adequate✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).

Do you agree with this assessment?

C2 · Access Controls0.0 / 10Critical✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
`WeatherForecastController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:22
`OrdersController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
`ValuesController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9, src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:10, src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:17
`ImageController.GetImageThumbnail` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:25
`ImageController.GetImage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:53
`MapGet("/publish-message")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Nats.WebApi/Program.cs:59
`MapGet("/publish-message-queue")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Nats.WebApi/Program.cs:65
`MapPost("/customer")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/Samples/Sample.OutboxWebApi/Program.cs:183, src/Samples/Sample.ValidatingWebApi/Program.cs:67
`MapPost("/customer/search")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.ValidatingWebApi/Program.cs:71
`KafkaGroupConsumer.Commit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×4) — src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275, src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275, src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275, …

What to do

Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

Do you agree with this assessment?

C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.

What to do

Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.

Do you agree with this assessment?

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

Do you agree with this assessment?

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

Do you agree with this assessment?

DM11 · Constructible invalid state6.5 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

`Customer`'s public constructor takes `firstname`, `lastname` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Customer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:20

What to do

Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

Do you agree with this assessment?

DM12 · Ambient inputs in the domain9.5 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

`Customer` reads `DateTime.UtcNow` inside `ChangeEmail` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:28

What to do

Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.

Do you agree with this assessment?

DM4 · Rich vs anemic model10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

Do you agree with this assessment?

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary2.0 / 10Critical✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

`OrdersController` (domain layer) names `RouteAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:7
`OrdersController` (domain layer) names `ApiControllerAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:8
`OrdersController` (domain layer) names `Controller` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:9
`OrdersController` (domain layer) names `HttpPostAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:15
`OrdersController` (domain layer) names `IActionResult` from `Microsoft.AspNetCore.Mvc` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
`ValuesController` (domain layer) names `RouteAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:3
`ValuesController` (domain layer) names `ApiControllerAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:4
`ValuesController` (domain layer) names `Controller` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:5
`ValuesController` (domain layer) names `HttpGetAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:8
`ValuesController` (domain layer) names `IActionResult` from `Microsoft.AspNetCore.Mvc` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9
`Startup` (domain layer) names `IApplicationBuilder` from `Microsoft.AspNetCore.Builder` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Startup.cs:49
`Program` (domain layer) uses `ASP.NET` inside a method body — infrastructure reached without it appearing in any signature. — src/Samples/Sample.DomainEvents.WebApi/Program.cs:6

What to do

Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).

Do you agree with this assessment?

DM7 · Repository granularity10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

Do you agree with this assessment?

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

Do you agree with this assessment?

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

Do you agree with this assessment?

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

Do you agree with this assessment?

ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

Do you agree with this assessment?

ED4 · Outbox / dual-write6.8 / 10Adequate✓ Tool-verified

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

`CreateCustomerCommandHandler.OnHandle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommandHandler.cs:8

What to do

Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.

Do you agree with this assessment?

ED5 · Idempotency6.5 / 10Adequate◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

`DomainEventHandlers.AuditingHandler.OnHandle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Samples/Sample.DomainEvents.Application/DomainEventHandlers/AuditingHandler.cs:13
`HealthCheck.IntermittentMessagePublisher.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Samples/Sample.CircuitBreaker.HealthCheck/IntermittentMessagePublisher.cs:6

What to do

Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.

Do you agree with this assessment?

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 shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEventConsumer.cs:11, src/Samples/Sample.AsyncApi.Service/Messages/CustomerEventConsumer.cs:14

What to do

Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.0 / 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.

`CloseAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:31
`ProcessErrorAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:59
`ProcessErrorAsyncInternal` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:231
`CreateConsumers` 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/SlimMessageBus.Host.Mqtt/MqttMessageBus.cs:39

What to do

Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.

Do you agree with this assessment?

M1 · Documentation (README)6.9 / 10Adequate✓ Tool-verified

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

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

What to do

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 80 of 90 project(s) that lack one — worth up to 1.8 pts.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

M4 · Documentation accuracy0.0 / 10Critical◐ 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.

README.md installs the package `SlimMessageBus` (`dotnet add package SlimMessageBus`), 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.md:20
README.md installs the package `SlimMessageBus.Host.Kafka` (`dotnet add package SlimMessageBus.Host.Kafka`), 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.md:22
README.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), 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.md:24
docs/plugin_outbox_mongodb.md installs the package `SlimMessageBus.Host.Outbox.MongoDb` (`dotnet add package SlimMessageBus.Host.Outbox.MongoDb`), 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/plugin_outbox_mongodb.md:30
docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), 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/provider_google_pubsub.md:10
docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), 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/provider_google_pubsub.md:11
docs/provider_google_pubsub.md documents the environment variable `PUBSUB_EMULATOR_HOST`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/provider_google_pubsub.md:267
docs/provider_google_pubsub.t.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), 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/provider_google_pubsub.t.md:10
docs/provider_google_pubsub.t.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), 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/provider_google_pubsub.t.md:11
docs/provider_google_pubsub.t.md documents the environment variable `PUBSUB_EMULATOR_HOST`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/provider_google_pubsub.t.md:267
docs/provider_memory.md installs the package `SlimMessageBus.Host.Memory` (`dotnet add package SlimMessageBus.Host.Memory`), 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/provider_memory.md:38
docs/provider_memory.t.md installs the package `SlimMessageBus.Host.Memory` (`dotnet add package SlimMessageBus.Host.Memory`), 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/provider_memory.t.md:38
docs/provider_postgresql.md installs the package `SlimMessageBus.Host.PostgreSql` (`dotnet add package SlimMessageBus.Host.PostgreSql`), 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/provider_postgresql.md:27
docs/provider_sql.md installs the package `SlimMessageBus.Host.Sql` (`dotnet add package SlimMessageBus.Host.Sql`), 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/provider_sql.md:34

What to do

Reconcile the README with reality: README.md installs the package `SlimMessageBus` (`dotnet add package SlimMessageBus`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Kafka` (`dotnet add package SlimMessageBus.Host.Kafka`), but no project or props file references it; README.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), but no project or props file references it; docs/plugin_outbox_mongodb.md installs the package `SlimMessageBus.Host.Outbox.MongoDb` (`dotnet add package SlimMessageBus.Host.Outbox.MongoDb`), but no project or props file references it; docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), but no project or props file references it.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P2 · Observability7.3 / 10Strong✓ 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 35/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 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.
Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.

Do you agree with this assessment?

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).
No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

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.

This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. — src/Samples/Sample.OutboxWebApi/Program.cs:160

What to do

Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.

Do you agree with this assessment?

PF1 · Benchmark discipline10.0 / 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.

Do you agree with this assessment?

PF2 · Allocation hygiene6.7 / 10Adequate✓ 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.

What to do

Raise allocation-aware density on the hot paths — currently 42 use(s) across 30,781 production line(s) (~1.4/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

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

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

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

3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92, src/SlimMessageBus.Host/MessageBusBase.cs:290, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458

What to do

Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×6) — src/Samples/Sample.AsyncApi.Service/Program.cs:19, src/Samples/Sample.DomainEvents.WebApi/Program.cs:9, src/Samples/Sample.Images.WebApi/Program.cs:9, …

What to do

Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.

Do you agree with this assessment?

X1 · Async correctness7.4 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×3) — src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:172, src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:198, src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:218
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. (×3) — src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92, src/SlimMessageBus.Host/MessageBusBase.cs:290, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:37

What to do

Sync-over-async (deadlock risk) through `.Result`

Do you agree with this assessment?

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.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness5.7 / 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.

`AbstractConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 6), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 166), `DisposeAsyncCore` (line 172) — 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/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:6
`MessageBusBase` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_cancellationTokenSource` itself (line 24), which makes that instance its own. But `_cancellationTokenSource` is named in none of the methods the disposal search covered: `Dispose` (line 280), `Dispose` (line 286), `DisposeAsync` (line 294), `Dispose` (line 280), `Dispose` (line 286), `DisposeAsyncInternal` (line 300) — 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` (`_cancellationTokenSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host/MessageBusBase.cs:24
`providers` is a `LoggerProviderCollection`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `BaseIntegrationTest` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var providers = …;`), which releases it at the end of the scope on every path including a throw. — src/Tests/SlimMessageBus.Host.Test.Common/IntegrationTest/BaseIntegrationTest.cs:30
`OutboxSendingTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_loopCts` itself (line 15), which makes that instance its own. But `_loopCts` is named in none of the methods the disposal search covered: `DisposeAsync` (line 25), `DisposeAsyncCore` (line 43) — 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` (`_loopCts?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:15
`Settings.ServiceProvider.CreateScope()` (line 18) creates an `IServiceScope`, and it is bound to the local `scope`, which this method only reads through and never disposes. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. (×2) — src/SlimMessageBus.Host.Sql/SqlMessageBus.cs:18, src/SlimMessageBus.Host.PostgreSql/PostgreSqlMessageBus.cs:18
`HealthCheckBackgroundService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 8), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `Dispose` (line 118) — 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/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:8
`AbstractTemporaryCredentialsSqsClientProvider` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphoreSlim` itself (line 22), which makes that instance its own. But `_semaphoreSlim` is named in none of the methods the disposal search covered: `Dispose` (line 85), `Dispose` (line 99), `Dispose` (line 85), `Dispose` (line 99) — 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` (`_semaphoreSlim?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host.AmazonSQS/ClientFactory/AbstractTemporaryCredentialsSqsClientProvider.cs:22

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X2 · Cancellation propagation6.5 / 10Adequate✓ 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 130/294 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. (×29) — src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:52, src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:65, src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:71, …
No CancellationToken parameter, and the token `consumerContext.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `consumerContext.CancellationToken` on, or take a CancellationToken. — src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:141
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. (×8) — src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:216, src/SlimMessageBus.Host/Producer/InterceptorPipelines/PublishInterceptorPipeline.cs:19, src/SlimMessageBus.Host/Producer/InterceptorPipelines/SendInterceptorPipeline.cs:21, …
No CancellationToken parameter, and the token `args.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `args.CancellationToken` on, or take a CancellationToken. — src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:70

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X20 · Mistyped argument guard7.5 / 10Strong✓ Tool-verified

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

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

The guard on line 19 rejects `queueName` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(queueName)` is true of a value that is NOT null: it is satisfied by an EMPTY `queueName`, and on that path `queueName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:19
The guard on line 58 rejects `exchangeName` and line 58 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:58
The guard on line 81 rejects `exchangeName` and line 81 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:81
The guard on line 34 rejects `exchangeName` and line 34 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqProducerBuilderExtensions.cs:34
The guard on line 18 rejects `exchangeName` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqRequestResponseBuilderExtensions.cs:18

What to do

Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling6.5 / 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. (×6) — src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:169, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:385, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:395, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:191

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X5 · Nullable reference types3.8 / 10Weak✓ 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.

14/53 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~1.0 `!` suppressions per 1k syntax nodes — 23 suppression(s) across the 23089 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 `!`.

Do you agree with this assessment?

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	63%	Adequate — gated by X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	81%	Strong	Solid.
Maturity	41%	Weak — gated by M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	55%	Adequate — gated by P8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	43%	Weak — gated by D29, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	70%	Adequate — gated by DM6	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven	86%	Strong	Strongest area.
Performance	72%	Strong	Solid.

Unscored — 3 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 — 2 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 — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 2 control(s) we could not find positive evidence for

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

C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.

Not included — 34 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.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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) — sqldb Error context canceled storage Error context canceled mongodb Error context canceled nats Error context canceled kafka-init Error context canceled rabbitmq Error context canceled psqldb Error context canceled mqtt Error context canceled kafka Error context canceled redis Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redis Error Get "https://registry-1.docker.io/v2/": Forbidden sqldb Error context canceled mqtt Error context canceled rabbitmq Error context canceled mongodb Error context canceled kafka-init Error context canceled nats Error context canceled storage Error context canceled psqldb Error context canceled 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.
D12 Dependency Hygiene — Dependency hygiene not measured
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.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
ED3 Event naming — no domain or integration events detected — event-naming check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 86 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×11

Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:7 — `OrdersController` (domain layer) names `RouteAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:8 — `OrdersController` (domain layer) names `ApiControllerAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:9 — `OrdersController` (domain layer) names `Controller` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:15 — `OrdersController` (domain layer) names `HttpPostAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16 — `OrdersController` (domain layer) names `IActionResult` from `Microsoft.AspNetCore.Mvc` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:3 — `ValuesController` (domain layer) names `RouteAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:4 — `ValuesController` (domain layer) names `ApiControllerAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:5 — `ValuesController` (domain layer) names `Controller` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:8 — `ValuesController` (domain layer) names `HttpGetAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9 — `ValuesController` (domain layer) names `IActionResult` from `Microsoft.AspNetCore.Mvc` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Startup src/Samples/Sample.DomainEvents.WebApi/Startup.cs:49 — `Startup` (domain layer) names `IApplicationBuilder` from `Microsoft.AspNetCore.Builder` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · EmptyCatchBlock · ×6

EmptyCatchBlock src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:123 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:385 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:395 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:414 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:424 — 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/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:169 — 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.

D17 · Explicit Debt · WriteOnlyPrivateField · ×5

WriteOnlyPrivateField REDACTED:14 — private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.Outbox.PostgreSql.DbContext.Test/OutboxBenchmarkTests.cs:24 — private string _databaseName — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.Outbox.Test/Interceptors/OutboxForwardingPublishInterceptorTests.cs:44 — private Mock<IOutboxMessageRepository<OutboxMessage>> _mockOutboxRepository — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.RabbitMQ.Test/Config/RabbitMqProducerBuilderExtensionsTests.cs:5 — private MessageBusSettings _busSettings — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.Test/Consumer/MessageProcessorTest.cs:11 — private Mock<IMessageTypeResolver> messageTypeResolverMock — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

AX1 · Captive dependencies · Captive dependency · ×3

Captive dependency: singleton PendingRequestManager captures transient IPendingRequestStore src/SlimMessageBus.Host/RequestResponse/PendingRequestManager.cs:19 — `PendingRequestManager` is registered as a SINGLETON but its constructor takes `IPendingRequestStore store`, 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 `IPendingRequestStore` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton OutboxSendingTask captures transient OutboxSettings src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:5 — `OutboxSendingTask` is registered as a SINGLETON but its constructor takes `OutboxSettings outboxSettings`, 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 `OutboxSettings` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton OutboxCleanUpTask captures transient OutboxSettings src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs:20 — `OutboxCleanUpTask` is registered as a SINGLETON but its constructor takes `OutboxSettings outboxSettings`, 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 `OutboxSettings` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.

D17 · Explicit Debt · AnalyzerSeverityNone · ×3

AnalyzerSeverityNone src/.editorconfig:188 — VSTHRD200 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/.editorconfig:190 — CA1510 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/.editorconfig:191 — CA1512 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.

D13 · REDACTED Scanning · Leaked secret · ×2

REDACTED
REDACTED

D17 · Explicit Debt · NoWarnInCsproj · ×2

NoWarnInCsproj src/Samples/Sample.DomainEvents.WebApi/Sample.DomainEvents.WebApi.csproj:8 — 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
NoWarnInCsproj REDACTED:8 — 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

AX3 · Project dependency cycles · Namespace dependency cycle · ×1

Namespace dependency cycle src/SlimMessageBus.Host/Collections/KindMapping.cs:3 — The namespaces SlimMessageBus.Host ↔ SlimMessageBus.Host.Collections depend on each other. The lightest dependency in the cycle is SlimMessageBus.Host.Collections → SlimMessageBus.Host (SlimMessageBus.Host.Collections.KindMapping → SlimMessageBus.Host.MessageBusSettings, 4 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.

D28 · Secrets (history) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

DM6 · Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body · ×1

Domain uses infrastructure in a method body: Program src/Samples/Sample.DomainEvents.WebApi/Program.cs:6 — `Program` (domain layer) uses `ASP.NET` inside a method body — infrastructure reached without it appearing in any signature.

ED4 · Outbox / dual-write · Dual write (no outbox) · ×1

Dual write (no outbox): CreateCustomerCommandHandler.OnHandle src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommandHandler.cs:8 — `CreateCustomerCommandHandler.OnHandle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).

Serious — 246 finding(s)

D19 · Documentation Quality · Low XML-doc coverage · ×50

Low XML-doc coverage: SlimMessageBus(net10.0) src/SlimMessageBus/SlimMessageBus.csproj — SlimMessageBus(net10.0): 26 % XML-doc coverage (11/42).
Low XML-doc coverage: SlimMessageBus.Host(net10.0) src/SlimMessageBus.Host/SlimMessageBus.Host.csproj — SlimMessageBus.Host(net10.0): 13 % XML-doc coverage (50/391).
Low XML-doc coverage: SlimMessageBus.Host.Serialization.Json(net10.0) src/SlimMessageBus.Host.Serialization.Json/SlimMessageBus.Host.Serialization.Json.csproj — SlimMessageBus.Host.Serialization.Json(net10.0): 11 % XML-doc coverage (1/9).
Low XML-doc coverage: SlimMessageBus.Host.Kafka(net10.0) src/SlimMessageBus.Host.Kafka/SlimMessageBus.Host.Kafka.csproj — SlimMessageBus.Host.Kafka(net10.0): 31 % XML-doc coverage (24/78).
Low XML-doc coverage: SlimMessageBus.Host.AzureEventHub(net10.0) src/SlimMessageBus.Host.AzureEventHub/SlimMessageBus.Host.AzureEventHub.csproj — SlimMessageBus.Host.AzureEventHub(net10.0): 32 % XML-doc coverage (22/68).
Low XML-doc coverage: SlimMessageBus.Host.Memory(net10.0) src/SlimMessageBus.Host.Memory/SlimMessageBus.Host.Memory.csproj — SlimMessageBus.Host.Memory(net10.0): 29 % XML-doc coverage (9/31).
Low XML-doc coverage: Sample.ConsoleApp src/Samples/Sample.Simple.ConsoleApp/Sample.ConsoleApp.csproj — Sample.ConsoleApp: 0 % XML-doc coverage (0/9).
Low XML-doc coverage: Sample.Images.FileStore src/Samples/Sample.Images.FileStore/Sample.Images.FileStore.csproj — Sample.Images.FileStore: 0 % XML-doc coverage (0/6).
Low XML-doc coverage: Sample.Images.Messages src/Samples/Sample.Images.Messages/Sample.Images.Messages.csproj — Sample.Images.Messages: 0 % XML-doc coverage (0/13).
Low XML-doc coverage: Sample.Images.WebApi src/Samples/Sample.Images.WebApi/Sample.Images.WebApi.csproj — Sample.Images.WebApi: 0 % XML-doc coverage (0/15).
Low XML-doc coverage: Sample.Images.Worker src/Samples/Sample.Images.Worker/Sample.Images.Worker.csproj — Sample.Images.Worker: 0 % XML-doc coverage (0/2).
Low XML-doc coverage: Sample.DomainEvents.Domain src/Samples/Sample.DomainEvents.Domain/Sample.DomainEvents.Domain.csproj — Sample.DomainEvents.Domain: 21 % XML-doc coverage (4/19).
Low XML-doc coverage: Sample.DomainEvents.WebApi src/Samples/Sample.DomainEvents.WebApi/Sample.DomainEvents.WebApi.csproj — Sample.DomainEvents.WebApi: 9 % XML-doc coverage (1/11).
Low XML-doc coverage: SlimMessageBus.Host.AzureServiceBus(net10.0) src/SlimMessageBus.Host.AzureServiceBus/SlimMessageBus.Host.AzureServiceBus.csproj — SlimMessageBus.Host.AzureServiceBus(net10.0): 34 % XML-doc coverage (42/124).
Low XML-doc coverage: SecretStore src/Tools/SecretStore/SecretStore.csproj — SecretStore: 0 % XML-doc coverage (0/15).
Low XML-doc coverage: Sample.Hybrid.ConsoleApp src/Samples/Sample.Hybrid.ConsoleApp/Sample.Hybrid.ConsoleApp.csproj — Sample.Hybrid.ConsoleApp: 4 % XML-doc coverage (1/28).
Low XML-doc coverage: SlimMessageBus.Host.Serialization.Avro(net10.0) src/SlimMessageBus.Host.Serialization.Avro/SlimMessageBus.Host.Serialization.Avro.csproj — SlimMessageBus.Host.Serialization.Avro(net10.0): 39 % XML-doc coverage (13/33).
Low XML-doc coverage: Sample.Serialization.ConsoleApp src/Samples/Sample.Serialization.ConsoleApp/Sample.Serialization.ConsoleApp.csproj — Sample.Serialization.ConsoleApp: 7 % XML-doc coverage (1/14).
Low XML-doc coverage: Sample.Serialization.MessagesAvro src/Samples/Sample.Serialization.MessagesAvro/Sample.Serialization.MessagesAvro.csproj — Sample.Serialization.MessagesAvro: 4 % XML-doc coverage (1/28).
Low XML-doc coverage: SlimMessageBus.Host.Serialization.Hybrid(net10.0) src/SlimMessageBus.Host.Serialization.Hybrid/SlimMessageBus.Host.Serialization.Hybrid.csproj — SlimMessageBus.Host.Serialization.Hybrid(net10.0): 12 % XML-doc coverage (3/24).
Low XML-doc coverage: SlimMessageBus.Host.Redis(net10.0) src/SlimMessageBus.Host.Redis/SlimMessageBus.Host.Redis.csproj — SlimMessageBus.Host.Redis(net10.0): 26 % XML-doc coverage (10/39).
Low XML-doc coverage: Sample.DomainEvents.Application src/Samples/Sample.DomainEvents.Application/Sample.DomainEvents.Application.csproj — Sample.DomainEvents.Application: 29 % XML-doc coverage (2/7).
Low XML-doc coverage: SlimMessageBus.Host.Serialization.GoogleProtobuf(net10.0) src/SlimMessageBus.Host.Serialization.GoogleProtobuf/SlimMessageBus.Host.Serialization.GoogleProtobuf.csproj — SlimMessageBus.Host.Serialization.GoogleProtobuf(net10.0): 10 % XML-doc coverage (1/10).
Low XML-doc coverage: SlimMessageBus.Host.Interceptor(net10.0) src/SlimMessageBus.Host.Interceptor/SlimMessageBus.Host.Interceptor.csproj — SlimMessageBus.Host.Interceptor(net10.0): 11 % XML-doc coverage (1/9).
Low XML-doc coverage: SlimMessageBus.Host.Serialization.SystemTextJson(net10.0) src/SlimMessageBus.Host.Serialization.SystemTextJson/SlimMessageBus.Host.Serialization.SystemTextJson.csproj — SlimMessageBus.Host.Serialization.SystemTextJson(net10.0): 31 % XML-doc coverage (4/13).
+ 25 more in this group — see findings.md.

X2 · Cancellation propagation · Async method without CancellationToken · ×31

Async method without CancellationToken: DoStart src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:52 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InternalOnStart src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:65 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InternalOnStop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DoStop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:81 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:94 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Stop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:125 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:172 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: NextOfTyped src/SlimMessageBus.Host/Consumer/InterceptorPipelines/ConsumerInterceptorPipeline.cs:56 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DoHandleInternal src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:141 — No CancellationToken parameter, and the token `consumerContext.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `consumerContext.CancellationToken` on, or take a CancellationToken.
Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:107 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnBusLifecycle src/SlimMessageBus.Host/MessageBusBase.cs:150 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start src/SlimMessageBus.Host/MessageBusBase.cs:182 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Stop src/SlimMessageBus.Host/MessageBusBase.cs:220 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DisposeAsyncInternal src/SlimMessageBus.Host/MessageBusBase.cs:300 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host/MessageBusBase.cs:321 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DestroyConsumers src/SlimMessageBus.Host/MessageBusBase.cs:339 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: NextOfObject src/SlimMessageBus.Host/Producer/InterceptorPipelines/SendInterceptorPipeline.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnMessage src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:233 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:60 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:125 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnStart src/SlimMessageBus.Host.AzureEventHub/Consumer/EhGroupConsumer.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnStop src/SlimMessageBus.Host.AzureEventHub/Consumer/EhGroupConsumer.cs:58 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Checkpoint src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:70 — No CancellationToken parameter, and the token `args.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `args.CancellationToken` on, or take a CancellationToken.
Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
+ 6 more in this group — see findings.md.

C2 · Access Controls · No authorization · ×17

No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization REDACTED:22 — `WeatherForecastController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16 — `OrdersController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9 — `ValuesController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:25 — `ImageController.GetImageThumbnail` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:53 — `ImageController.GetImage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:10 — `ValuesController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:17 — `ValuesController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.Nats.WebApi/Program.cs:59 — `MapGet("/publish-message")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.Nats.WebApi/Program.cs:65 — `MapGet("/publish-message-queue")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.OutboxWebApi/Program.cs:183 — `MapPost("/customer")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.ValidatingWebApi/Program.cs:67 — `MapPost("/customer")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/Samples/Sample.ValidatingWebApi/Program.cs:71 — `MapPost("/customer/search")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275 — `KafkaGroupConsumer.Commit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275 — `KafkaGroupConsumer.Commit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275 — `KafkaGroupConsumer.Commit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275 — `KafkaGroupConsumer.Commit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.

D17 · Explicit Debt · TodoComment · ×16

TodoComment src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:65 — // ToDo: determine media type — 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/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:67 — // ToDo: add cache-control headers — 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/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:142 — // ToDo: DLQ handling — 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/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:125 — // ToDo: See issue in v4 SDK: https://github.com/awsdocs/aws-doc-sdk-examples/issues/7615
TodoComment src/SlimMessageBus.Host.AsyncApi/MessageBusDocumentGenerator.cs:38 — // ToDo: implement — 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/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:50 — // ToDo: Retry logic in the future — 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/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:61 — // ToDo: add retry mechanism and dlq support — 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/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:78 — // ToDo: add support for auto commit — 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/SlimMessageBus.Host.Kafka/Consumer/KafkaPartitionConsumer.cs:40 — // ToDo: Add support for Kafka driven automatic commit (https://github.com/zarusz/SlimMessageBus/issues/131)
TodoComment src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:195 — // ToDo: Introduce a setting for allowing the client to allow for batching acks — 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/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:201 — // ToDo: Introduce a setting for allowing the client to allow for batching acks — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs:51 — // ToDo: Ability to create server generated queue names — 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/SlimMessageBus.Host.Serialization.Avro/AvroMessageSerializer.cs:120 — // ToDo: Leverage to implement Avro specific feature: https://github.com/zarusz/SlimMessageBus/issues/370
TodoComment src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:93 — // ToDo: Call interceptor — 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/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:61 — // ToDo: defer start of buses until here — 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/SlimMessageBus.Host/MessageWithHeaders.cs:5 — // ToDo: Change to ReadOnlyMemory<byte> — 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.

D31 · IaC & Container Security · Medium IaC · ×11

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · BareSuppressMessage · ×6

BareSuppressMessage src/Samples/Sample.Images.Worker/GlobalSuppressions.cs:8 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/SlimMessageBus.Host.Redis/GlobalSuppressions.cs:9 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/SlimMessageBus.Host/GlobalSuppressions.cs:12 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/SlimMessageBus.Host/GlobalSuppressions.cs:13 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/SlimMessageBus.Host.Redis/GlobalSuppressions.cs:8 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/Tests/SlimMessageBus.Host.Memory.Test/GlobalSuppressions.cs:8 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.

X3 · Exception handling · Swallowed exception (empty catch) · ×6

Swallowed exception (empty catch) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:169 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:385 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:395 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:414 — 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/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:424 — 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/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:123 — 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.

D17 · Explicit Debt · Dead code · ×5

Dead code: DeleteFile src/Samples/Sample.Images.FileStore/IFileStore.cs:12 — Method DeleteFile — Roslyn's SymbolFinder walked every project the solution loads, including Sample.Images.FileStore, 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: CustomerUpdated src/Tests/SlimMessageBus.Host.Memory.Test/MemoryMessageBusBuilderTests.cs:193 — NamedType CustomerUpdated — Roslyn's SymbolFinder walked every project the solution loads, including SlimMessageBus.Host.Memory.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GenericConsumer src/Tests/SlimMessageBus.Host.Memory.Test/MemoryMessageBusTests.cs:627 — NamedType GenericConsumer — Roslyn's SymbolFinder walked every project the solution loads, including SlimMessageBus.Host.Memory.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AuditingHandler src/Samples/Sample.DomainEvents.Application/DomainEventHandlers/AuditingHandler.cs:11 — NamedType AuditingHandler — Roslyn's SymbolFinder walked every project the solution loads, including Sample.DomainEvents.Application, 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: CustomerEventConsumer src/Samples/Sample.AsyncApi.Service/Messages/CustomerEventConsumer.cs:3 — NamedType CustomerEventConsumer — Roslyn's SymbolFinder walked every project the solution loads, including Sample.AsyncApi.Service, 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.

X18 · Disposal-pattern correctness · Owned disposable field is never released · ×5

Owned disposable field is never released src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:6 — `AbstractConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 6), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 166), `DisposeAsyncCore` (line 172) — 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.
Owned disposable field is never released src/SlimMessageBus.Host/MessageBusBase.cs:24 — `MessageBusBase` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_cancellationTokenSource` itself (line 24), which makes that instance its own. But `_cancellationTokenSource` is named in none of the methods the disposal search covered: `Dispose` (line 280), `Dispose` (line 286), `DisposeAsync` (line 294), `Dispose` (line 280), `Dispose` (line 286), `DisposeAsyncInternal` (line 300) — 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` (`_cancellationTokenSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:15 — `OutboxSendingTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_loopCts` itself (line 15), which makes that instance its own. But `_loopCts` is named in none of the methods the disposal search covered: `DisposeAsync` (line 25), `DisposeAsyncCore` (line 43) — 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` (`_loopCts?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:8 — `HealthCheckBackgroundService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 8), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `Dispose` (line 118) — 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.
Owned disposable field is never released src/SlimMessageBus.Host.AmazonSQS/ClientFactory/AbstractTemporaryCredentialsSqsClientProvider.cs:22 — `AbstractTemporaryCredentialsSqsClientProvider` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphoreSlim` itself (line 22), which makes that instance its own. But `_semaphoreSlim` is named in none of the methods the disposal search covered: `Dispose` (line 85), `Dispose` (line 99), `Dispose` (line 85), `Dispose` (line 99) — 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` (`_semaphoreSlim?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.

X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×5

Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:19 — The guard on line 19 rejects `queueName` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(queueName)` is true of a value that is NOT null: it is satisfied by an EMPTY `queueName`, and on that path `queueName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:58 — The guard on line 58 rejects `exchangeName` and line 58 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:81 — The guard on line 81 rejects `exchangeName` and line 81 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqProducerBuilderExtensions.cs:34 — The guard on line 34 rejects `exchangeName` and line 34 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqRequestResponseBuilderExtensions.cs:18 — The guard on line 18 rejects `exchangeName` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.

D17 · Explicit Debt · CommentedOutCode · ×4

CommentedOutCode src/Samples/Sample.Serialization.ConsoleApp/Program.cs:78 — 3 consecutive commented-code lines
CommentedOutCode src/Tests/SlimMessageBus.Host.Memory.Benchmark/Program.cs:13 — 3 consecutive commented-code lines
CommentedOutCode src/Samples/Sample.Serialization.ConsoleApp/Program.cs:87 — 4 consecutive commented-code lines
CommentedOutCode src/Tests/SlimMessageBus.Host.Memory.Benchmark/Program.cs:17 — 6 consecutive commented-code lines

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×4

Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:85 — src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:85-90 | src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:112-117 — 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/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:162 — src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:162-167 | src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:180-185 — 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/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs:148 — src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs:148-153 | src/SlimMessageBus.Host.PostgreSql/PostgreSqlRepository.cs:95-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:105 — src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:105-110 | src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:129-134 — 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/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:105` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:127` calls `In` and `src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:103` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×4

Sync-over-async blocking — 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/SlimMessageBus.Host/MessageBusBase.cs:290 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).

AX2 · Stateful singletons · Stateful singleton · ×3

Stateful singleton: HybridMessageSerializerProvider src/SlimMessageBus.Host.Serialization.Hybrid/HybridMessageSerializerProvider.cs:10 — `HybridMessageSerializerProvider` is a singleton (one shared instance) but mutates instance state outside any lock (DefaultSerializer, _serializerProviderByType; e.g. `DefaultSerializer` at line 34).
Stateful singleton: OutboxSendingTask src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:3 — `OutboxSendingTask` is a singleton (one shared instance) but mutates instance state outside any lock (_loopCts, _loopTask, _startBusTask, _stopBusTask; e.g. `_loopCts` at line 51).
Stateful singleton: HealthCheckBackgroundService src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:3 — `HealthCheckBackgroundService` is a singleton (one shared instance) but mutates instance state outside any lock (_onChangeDelegates; e.g. `_onChangeDelegates` at line 52).

D17 · Explicit Debt · CoverageExclusion · ×3

CoverageExclusion src/SlimMessageBus.Host.Kafka/Configs/KafkaAbstractConsumerBuilderExtensions.cs:14 — method Group — 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/SlimMessageBus.Host.Kafka/Configs/KafkaAbstractConsumerBuilderExtensions.cs:26 — method Group — 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/SlimMessageBus.Host/PlatformExtensions.cs:11 — method CancelAsync — 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.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3

Duplicated block (9 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:22 — src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:22-30 | src/SlimMessageBus.Host.PostgreSql/PostgreSqlHelper.cs:21-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs:89 — src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs:89-97 | src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs:122-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/SlimMessageBus.Host.PostgreSql/ServiceScopeExtensions.cs:7 — src/SlimMessageBus.Host.PostgreSql/ServiceScopeExtensions.cs:7-15 | src/SlimMessageBus.Host.Sql/ServiceScopeExtensions.cs:7-15 — `src/SlimMessageBus.Host.PostgreSql/ServiceScopeExtensions.cs` and `src/SlimMessageBus.Host.Sql/ServiceScopeExtensions.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 9 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

IC1 · Incompleteness & stubs · Hollow method · ×3

Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:31 — `CloseAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:59 — `ProcessErrorAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:231 — `ProcessErrorAsyncInternal` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×3

Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:172 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:198 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:218 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.

X1 · Async correctness · Sync-over-async (deadlock risk) · ×3

Sync-over-async (deadlock risk) src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/SlimMessageBus.Host/MessageBusBase.cs:290 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.

D10 · Test Quality · Fixed-sleep synchronisation · ×2

Fixed-sleep synchronisation: Wait_ShouldBlockUntilSet src/Tests/SlimMessageBus.Host.Outbox.Test/AsyncManualResetEventTests.cs:58 — This test starts a background task and then orders itself against it with `Task.Delay(100)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: Wait_ShouldCancel src/Tests/SlimMessageBus.Host.Outbox.Test/AsyncManualResetEventTests.cs:95 — This test starts a background task and then orders itself against it with `Task.Delay(100)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.

D17 · Explicit Debt · BarePragmaDisable · ×2

BarePragmaDisable src/SlimMessageBus.Host.Outbox.Sql/SqlOutboxMigrationService.cs:16 — #pragma warning disable CA1861 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable src/Tests/SlimMessageBus.Host.Outbox.MongoDb.Test/MongoDbOutboxRepositoryTests.cs:69 — #pragma warning disable EXTEXP0004 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.

D3 · God Classes · TooManyMethods · ×2

TooManyMethods: MessageBusBase src/SlimMessageBus.Host/MessageBusBase.cs — TooManyMethods — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RabbitMqChannelManager src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs — TooManyMethods — 333 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2

Duplicated block (8 lines × 2) src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyService.cs:286 — src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyService.cs:286-293 | src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyService.cs:333-340 — 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/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyService.cs:286` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:9 — src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:9-16 | src/SlimMessageBus.Host.Sql/ObjectToInferredTypesConverter.cs:9-16 — `src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs` and `src/SlimMessageBus.Host.Sql/ObjectToInferredTypesConverter.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 8 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2

Duplicated block (11 lines × 2) src/SlimMessageBus.Host.PostgreSql/PostgreSqlSequentialGuidGenerator.cs:7 — src/SlimMessageBus.Host.PostgreSql/PostgreSqlSequentialGuidGenerator.cs:7-17 | src/SlimMessageBus.Host.Sql/SqlSequentialGuidGenerator.cs:7-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:56 — src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:56-66 | src/SlimMessageBus.Host.PostgreSql/PostgreSqlHelper.cs:80-90 — 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) · ×2

Duplicated block (7 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:115 — src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:115-121 | src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:240-246 — 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/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:115` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Samples/Sample.DomainEvents.WebApi/Program.cs:9 — src/Samples/Sample.DomainEvents.WebApi/Program.cs:9-15 | src/Samples/Sample.Images.WebApi/Program.cs:9-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

ED5 · Idempotency · Non-idempotent mutation · ×2

Non-idempotent mutation: DomainEventHandlers.AuditingHandler.OnHandle src/Samples/Sample.DomainEvents.Application/DomainEventHandlers/AuditingHandler.cs:13 — `DomainEventHandlers.AuditingHandler.OnHandle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Non-idempotent mutation: HealthCheck.IntermittentMessagePublisher.ExecuteAsync src/Samples/Sample.CircuitBreaker.HealthCheck/IntermittentMessagePublisher.cs:6 — `HealthCheck.IntermittentMessagePublisher.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.

GD1 · Unfinished & placeholder code · Unfinished stub · ×2

Unfinished stub — throws NotImplementedException src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEventConsumer.cs:11 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Samples/Sample.AsyncApi.Service/Messages/CustomerEventConsumer.cs:14 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

X18 · Disposal-pattern correctness · DI scope created and never disposed · ×2

DI scope created and never disposed src/SlimMessageBus.Host.Sql/SqlMessageBus.cs:18 — `Settings.ServiceProvider.CreateScope()` (line 18) creates an `IServiceScope`, and it is bound to the local `scope`, which this method only reads through and never disposes. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`.
DI scope created and never disposed src/SlimMessageBus.Host.PostgreSql/PostgreSqlMessageBus.cs:18 — `Settings.ServiceProvider.CreateScope()` (line 18) creates an `IServiceScope`, and it is bound to the local `scope`, which this method only reads through and never disposes. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`.

C1 · Data Protection · No data-protection/encryption · ×1

No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

D1 · Cyclomatic Complexity · MemoryMessageBusBuilder.AutoDeclareFrom (cyclomatic 25) · ×1

MemoryMessageBusBuilder.AutoDeclareFrom (cyclomatic 25) src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:41 — MemoryMessageBusBuilder.AutoDeclareFrom has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 93, 124, 143, …). 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.

D1 · Cyclomatic Complexity · ServiceBusTopologyService.PrepareSubscription (cyclomatic 21) · ×1

ServiceBusTopologyService.PrepareSubscription (cyclomatic 21) src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:153 — ServiceBusTopologyService.PrepareSubscription has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MessageProcessor.ProcessMessage (cyclomatic 18) · ×1

MessageProcessor.ProcessMessage (cyclomatic 18) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:82 — MessageProcessor.ProcessMessage has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MessageHandler.DoHandle (cyclomatic 17) · ×1

MessageHandler.DoHandle (cyclomatic 17) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:57 — MessageHandler.DoHandle has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D10 · Test Quality · No assertions · ×1

No assertions: Given_MemoryConsumer_When_MessageScopeAccessorCalledInsideConsumer_Then_LooksUpInTheMessageScope src/Tests/SlimMessageBus.Host.Integration.Test/MessageScopeAccessor/MessageScopeAccessorTests.cs:30 — 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.

D2 · Cognitive Complexity · MemoryMessageBusBuilder.AutoDeclareFrom (cognitive 53) · ×1

MemoryMessageBusBuilder.AutoDeclareFrom (cognitive 53) src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:41 — MemoryMessageBusBuilder.AutoDeclareFrom has cognitive complexity 53 (threshold 15). Of this number, 18 points are the body's own statements and 35 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ServiceBusTopologyService.PrepareSubscription (cognitive 37) · ×1

ServiceBusTopologyService.PrepareSubscription (cognitive 37) src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:153 — ServiceBusTopologyService.PrepareSubscription has cognitive complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MessageProcessor.ProcessMessage (cognitive 36) · ×1

MessageProcessor.ProcessMessage (cognitive 36) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:82 — MessageProcessor.ProcessMessage has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RedisListCheckerConsumer.Run (cognitive 30) · ×1

RedisListCheckerConsumer.Run (cognitive 30) src/SlimMessageBus.Host.Redis/Consumers/RedisListCheckerConsumer.cs:57 — RedisListCheckerConsumer.Run has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MessageHandler.DoHandle (cognitive 25) · ×1

MessageHandler.DoHandle (cognitive 25) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:57 — MessageHandler.DoHandle has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · KafkaMessageBus.ProduceToTransport (cognitive 24) · ×1

KafkaMessageBus.ProduceToTransport (cognitive 24) src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:138 — KafkaMessageBus.ProduceToTransport has cognitive complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · OutboxSendingTask.ProcessMessages (cognitive 24) · ×1

OutboxSendingTask.ProcessMessages (cognitive 24) src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:235 — OutboxSendingTask.ProcessMessages has cognitive complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ServiceBusTopologyService.DoProvisionTopology (cognitive 20) · ×1

ServiceBusTopologyService.DoProvisionTopology (cognitive 20) src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:248 — ServiceBusTopologyService.DoProvisionTopology has cognitive complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MessageProcessor.TryMatchConsumerInvoker (cognitive 17) · ×1

MessageProcessor.TryMatchConsumerInvoker (cognitive 17) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:214 — MessageProcessor.TryMatchConsumerInvoker has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Retry.WithDelay (cognitive 17) · ×1

Retry.WithDelay (cognitive 17) src/SlimMessageBus.Host/Helpers/Retry.cs:7 — Retry.WithDelay has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AsbBaseConsumer.AsbBaseConsumer.ctor (cognitive 17) · ×1

AsbBaseConsumer.AsbBaseConsumer.ctor (cognitive 17) src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:14 — AsbBaseConsumer.AsbBaseConsumer.ctor has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SqsBaseConsumer.Run (cognitive 16) · ×1

SqsBaseConsumer.Run (cognitive 16) src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:119 — SqsBaseConsumer.Run has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Medium CVE · ×1

REDACTED

D32 · Data Compliance (PII/GDPR) · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (5 members, 50+ identical tokens) src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9 — src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9-18 | src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.cs:12-21 | src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:9-19 | src/SlimMessageBus.Host.Serialization.SystemTextJson/ObjectToInferredTypesConverter.cs:12-21 | src/SlimMessageBus.Host.Sql/ObjectToInferredTypesConverter.cs:9-19 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1

Duplicated block (22 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/Interceptors/PostgreSqlTransactionConsumerInterceptor.cs:14 — src/SlimMessageBus.Host.Outbox.PostgreSql/Interceptors/PostgreSqlTransactionConsumerInterceptor.cs:14-35 | src/SlimMessageBus.Host.Outbox.Sql/Interceptors/SqlTransactionConsumerInterceptor.cs:16-37 — before extracting anything, compare `src/SlimMessageBus.Host.Outbox.PostgreSql/Interceptors/PostgreSqlTransactionConsumerInterceptor.cs` and `src/SlimMessageBus.Host.Outbox.Sql/Interceptors/SqlTransactionConsumerInterceptor.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 lines × 2) · ×1

Duplicated block (16 lines × 2) src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:77 — src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:77-92 | src/SlimMessageBus.Host/Collections/GenericTypeCache2.cs:70-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1

Duplicated block (13 lines × 2) src/SlimMessageBus.Host.FluentValidation/FluentValidationMessageBusBuilder.cs:57 — src/SlimMessageBus.Host.FluentValidation/FluentValidationMessageBusBuilder.cs:57-69 | src/SlimMessageBus.Host.FluentValidation/FluentValidationMessageBusBuilder.cs:96-108 — 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/SlimMessageBus.Host.FluentValidation/FluentValidationMessageBusBuilder.cs:57` 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 (12 lines × 2) · ×1

Duplicated block (12 lines × 2) src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBusSettingsValidationService.cs:45 — src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBusSettingsValidationService.cs:45-56 | src/SlimMessageBus.Host/Services/MessageBusSettingsValidatorService.cs:71-82 — 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 (8–10 lines × 2) · ×1

Duplicated block (8–10 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Configuration/MessageBusBuilderExtensions.cs:44 — src/SlimMessageBus.Host.Outbox.MongoDb/Configuration/MessageBusBuilderExtensions.cs:44-53 | src/SlimMessageBus.Host.Outbox.PostgreSql/Configuration/MessageBusBuilderExtensions.cs:21-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host.Outbox.MongoDb/Configuration/MessageBusBuilderExtensions.cs:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1

Duplicated block (9 lines × 3) src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9 — src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9-17 | src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.cs:12-20 | src/SlimMessageBus.Host.Serialization.SystemTextJson/ObjectToInferredTypesConverter.cs:12-20 — `src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs` and `src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.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 2 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1

Duplicated block (6 lines × 4) src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:13 — src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:13-18 | src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.cs:16-21 | src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:14-19 | src/SlimMessageBus.Host.Serialization.SystemTextJson/ObjectToInferredTypesConverter.cs:16-21 — `src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs` and `src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.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 2 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:13` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:13` calls `TryGetInt32` and `src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:12` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1

Duplicated block (5 lines × 2) src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:25 — src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:25-29 | src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSqsHeaderSerializer.cs:25-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1

Duplicated block (17 lines × 2) src/SlimMessageBus.Host.Nats/Config/NatsConsumerBuilderExtensions.cs:6 — src/SlimMessageBus.Host.Nats/Config/NatsConsumerBuilderExtensions.cs:6-23 | src/SlimMessageBus.Host.Redis/Config/RedisConsumerBuilderExtensions.cs:6-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1

Duplicated block (27 lines × 2) src/SlimMessageBus.Host.Nats/Config/NatsProducerBuilderExtensions.cs:15 — src/SlimMessageBus.Host.Nats/Config/NatsProducerBuilderExtensions.cs:15-41 | src/SlimMessageBus.Host.Redis/Config/RedisProducerBuilderExtensions.cs:15-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1

Duplicated block (19 lines × 2) src/SlimMessageBus.Host.Nats/Config/NatsRequestResponseBuilderExtensions.cs:6 — src/SlimMessageBus.Host.Nats/Config/NatsRequestResponseBuilderExtensions.cs:6-24 | src/SlimMessageBus.Host.Redis/Config/RedisRequestResponseBuilderExtensions.cs:6-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (60 lines × 2) · ×1

Duplicated block (60 lines × 2) src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:18 — src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:18-77 | src/SlimMessageBus.Host.Sql.Common/Transactions/AbstractSqlTransactionService.cs:16-78 — 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 (10 lines × 2) · ×1

Duplicated block (10 lines × 2) src/SlimMessageBus.Host.PostgreSql/Config/PostgreSqlConsumerBuilderExtensions.cs:8 — src/SlimMessageBus.Host.PostgreSql/Config/PostgreSqlConsumerBuilderExtensions.cs:8-17 | src/SlimMessageBus.Host.Sql/Config/SqlConsumerBuilderExtensions.cs:8-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D6 · Cohesion (LCOM4) · Low cohesion · ×1

Low cohesion: RuntimeTypeCache (LCOM4 4) src/SlimMessageBus.Host/Collections/RuntimeTypeCache.cs:3 — RuntimeTypeCache's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

DM11 · Constructible invalid state · Constructible in an invalid state · ×1

Constructible in an invalid state: Customer src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:20 — `Customer`'s public constructor takes `firstname`, `lastname` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Customer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.

DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×1

Domain type reads the wall clock: Customer src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:28 — `Customer` reads `DateTime.UtcNow` inside `ChangeEmail` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.

IC1 · Incompleteness & stubs · Fake-async · ×1

Fake-async — async method never awaits src/SlimMessageBus.Host.Mqtt/MqttMessageBus.cs:39 — `CreateConsumers` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

P12 · CI test-gate honesty · Coverage collected but not gated · ×1

Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.

P8 · Schema migrations · Schema created with EnsureCreated() outside the migrations · ×1

Schema created with EnsureCreated() outside the migrations src/Samples/Sample.OutboxWebApi/Program.cs:160 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.

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.

X1 · Async correctness · async void method · ×1

async void method: OnChannelRecovered src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:37 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.

X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×1

Disposable created and abandoned in the method that made it src/Tests/SlimMessageBus.Host.Test.Common/IntegrationTest/BaseIntegrationTest.cs:30 — `providers` is a `LoggerProviderCollection`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `BaseIntegrationTest` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var providers = …;`), which releases it at the end of the scope on every path including a throw.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1

Swallowed exception (caught, then discarded) src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:191 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.

Minor — 58 finding(s)

M4 · Documentation accuracy · README/code drift · ×14

README/code drift README.md:20 — README.md installs the package `SlimMessageBus` (`dotnet add package SlimMessageBus`), 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 README.md:22 — README.md installs the package `SlimMessageBus.Host.Kafka` (`dotnet add package SlimMessageBus.Host.Kafka`), 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 README.md:24 — README.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), 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 docs/plugin_outbox_mongodb.md:30 — docs/plugin_outbox_mongodb.md installs the package `SlimMessageBus.Host.Outbox.MongoDb` (`dotnet add package SlimMessageBus.Host.Outbox.MongoDb`), 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 docs/provider_google_pubsub.md:10 — docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), 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 docs/provider_google_pubsub.md:11 — docs/provider_google_pubsub.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), 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 docs/provider_google_pubsub.md:267 — docs/provider_google_pubsub.md documents the environment variable `PUBSUB_EMULATOR_HOST`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/provider_google_pubsub.t.md:10 — docs/provider_google_pubsub.t.md installs the package `SlimMessageBus.Host.GooglePubSub` (`dotnet add package SlimMessageBus.Host.GooglePubSub`), 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 docs/provider_google_pubsub.t.md:11 — docs/provider_google_pubsub.t.md installs the package `SlimMessageBus.Host.Serialization.SystemTextJson` (`dotnet add package SlimMessageBus.Host.Serialization.SystemTextJson`), 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 docs/provider_google_pubsub.t.md:267 — docs/provider_google_pubsub.t.md documents the environment variable `PUBSUB_EMULATOR_HOST`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/provider_memory.md:38 — docs/provider_memory.md installs the package `SlimMessageBus.Host.Memory` (`dotnet add package SlimMessageBus.Host.Memory`), 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 docs/provider_memory.t.md:38 — docs/provider_memory.t.md installs the package `SlimMessageBus.Host.Memory` (`dotnet add package SlimMessageBus.Host.Memory`), 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 docs/provider_postgresql.md:27 — docs/provider_postgresql.md installs the package `SlimMessageBus.Host.PostgreSql` (`dotnet add package SlimMessageBus.Host.PostgreSql`), 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 docs/provider_sql.md:34 — docs/provider_sql.md installs the package `SlimMessageBus.Host.Sql` (`dotnet add package SlimMessageBus.Host.Sql`), 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.

D34 · Knowledge Freshness · Orphaned file · ×12

Orphaned file src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.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/SlimMessageBus.Host.Outbox.PostgreSql/Services/PostgreSqlOutboxMigrationService.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 REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/SlimMessageBus.Host.Serialization.Hybrid/SerializationBuilderExtensions.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/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.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 REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/SlimMessageBus.Host.Outbox/Services/OutboxLockRenewalTimer.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/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.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/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.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/SlimMessageBus.Host.Outbox.PostgreSql/Configuration/MessageBusBuilderExtensions.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/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckCircuitBreaker.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/SlimMessageBus.Host.Outbox.PostgreSql/Configuration/BuilderExtensions.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.

X10 · Duplicated predicate · Duplicated predicate · ×9

Duplicated predicate src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:63 — `!_transactionCompleted && (_transactionCount == 0 || transactionFailed)` appears character-identically in 2 files — src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs, src/SlimMessageBus.Host.Sql.Common/Transactions/AbstractSqlTransactionService.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/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:25 — `!_transactionCompleted && _transactionCount > 0` appears character-identically in 2 files — src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs, src/SlimMessageBus.Host.Sql.Common/Transactions/AbstractSqlTransactionService.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/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:29 — `detectStringType && bool.TryParse(value.StringValue, out var b)` appears character-identically in 2 files — src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs, src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSqsHeaderSerializer.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/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:28 — `detectStringType && key != ReqRespMessageHeaders.RequestId && Guid.TryParse(value.StringValue, out var guid)` appears character-identically in 2 files — src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs, src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSqsHeaderSerializer.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/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:237 — `ex is not ProducerMessageBusException && ex is not TaskCanceledException` appears character-identically in 9 files — src/SlimMessageBus.Host.AmazonSQS/SqsMessageBus.cs, src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs, src/SlimMessageBus.Host.AzureServiceBus/ServiceBusMessageBus.cs, src/SlimMessageBus.Host.Kafka/KafkaMessageBus.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/SlimMessageBus.Host/Collections/GenericTypeCache.cs:86 — `interceptors != null && interceptors.OfType<IInterceptorWithOrder>().Any()` appears character-identically in 2 files — src/SlimMessageBus.Host/Collections/GenericTypeCache.cs, src/SlimMessageBus.Host/Collections/GenericTypeCache2.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/SlimMessageBus.Host/Collections/GenericTypeCache.cs:85 — `interceptors == null || !interceptors.Any()` appears character-identically in 2 files — src/SlimMessageBus.Host/Collections/GenericTypeCache.cs, src/SlimMessageBus.Host/Collections/GenericTypeCache2.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/SlimMessageBus.Host.Sql.Common/SqlHelper.cs:17 — `tries <= retrySettings.RetryCount && !token.IsCancellationRequested` appears character-identically in 3 files — src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs, src/SlimMessageBus.Host.PostgreSql/PostgreSqlHelper.cs, src/SlimMessageBus.Host.Sql.Common/SqlHelper.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/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:13 — `x is long || x is int || x is short || x is byte` appears character-identically in 2 files — src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs, src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSqsHeaderSerializer.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.

S1 · Web-Security Posture · No security response headers detected · ×7

No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected src/Samples/Sample.AsyncApi.Service/Program.cs:19 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Samples/Sample.DomainEvents.WebApi/Program.cs:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Samples/Sample.Images.WebApi/Program.cs:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Samples/Sample.Nats.WebApi/Program.cs:13 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Samples/Sample.OutboxWebApi/Program.cs:23 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Samples/Sample.ValidatingWebApi/Program.cs:16 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.

D10 · Test Quality · Mock-dominated test · ×5

Mock-dominated test: When_ExecuteConsumer_Given_ConsumerWithContext_Then_ConsumerContextSet src/Tests/SlimMessageBus.Host.Test/Consumer/MessageHandlerTest.cs:68 — This test sets up 4 test doubles (for example `new Mock<IConsumerWithContext>()`) 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: When_WithModifier_Given_SeveralModifiers_Then_ExecutesThemAll src/Tests/SlimMessageBus.Host.AzureServiceBus.Test/ServiceBusMessageBusSettingsTests.cs:59 — This test sets up 5 test doubles (for example `new Mock<ServiceBusMessage>()`) against 1 real object(s) of its own, and its only verification is 4 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: When_ASpecialisedMessageIsSerialized_Then_UseSpecializedSerializer src/Tests/SlimMessageBus.Host.Serialization.Hybrid.Test/HybridMessageSerializerProviderTests.cs:48 — This test sets up 6 test doubles (for example `new Mock<IMessageSerializerProvider>()`) against 3 real object(s) of its own, and its only verification is 6 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: When_AGenericMessageIsSerialized_Then_UseDefaultSerializer src/Tests/SlimMessageBus.Host.Serialization.Hybrid.Test/HybridMessageSerializerProviderTests.cs:88 — This test sets up 5 test doubles (for example `new Mock<IDictionary<string, object>>()`) against 3 real object(s) of its own, and its only verification is 5 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: When_Create_Given_ActiveSession_Then_InsertsDocumentWithSession src/Tests/SlimMessageBus.Host.Outbox.MongoDb.Test/MongoDbOutboxMessageRepositoryTests.cs:90 — This test sets up 3 test doubles (for example `new Mock<IClientSessionHandle>()`) 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.

C4 · Data Retention · Partial data-retention evidence · ×1

Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.

D21 · Naming Consistency · Typo in type name · ×1

Typo in type name: 'Stategy' is used in DictionaryMessageCreationStategy, while 'Strategy' is used in ReflectionMessageCreationStrategy. These are parallel concepts within the same serialization strategy namespace. — Rename 'DictionaryMessageCreationStategy' to 'DictionaryMessageCreationStrategy' to match the spelling in 'ReflectionMessageCreationStrategy'. (symbols: SlimMessageBus.Host.Serialization.Avro.DictionaryMessageCreationStategy, SlimMessageBus.Host.Serialization.Avro.ReflectionMessageCreationStrategy)

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 12 of 137 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 137 of the 564 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs, src/SlimMessageBus.Host.Outbox.PostgreSql/Services/PostgreSqlOutboxMigrationService.cs, REDACTED, src/SlimMessageBus.Host.Serialization.Hybrid/SerializationBuilderExtensions.cs, src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs, REDACTED, src/SlimMessageBus.Host.Outbox/Services/OutboxLockRenewalTimer.cs, src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs (and 4 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

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

P12 · CI test-gate honesty · Sleep-based test synchronization · ×1

Sleep-based test synchronization — 15 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 35/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 11 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1

Not all async methods take a CancellationToken — Only 130/294 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 · Nullable reference types not enabled everywhere · ×1

Nullable reference types not enabled everywhere — 14/53 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1

Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.0 `!` suppressions per 1k syntax nodes — 23 suppression(s) across the 23089 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 — 2 finding(s)

D19 · Documentation Quality · XML-doc coverage · ×2

XML-doc coverage: SlimMessageBus.Host.AspNetCore(net10.0) src/SlimMessageBus.Host.AspNetCore/SlimMessageBus.Host.AspNetCore.csproj — SlimMessageBus.Host.AspNetCore(net10.0): 50 % XML-doc coverage (2/4).
XML-doc coverage: SlimMessageBus.Host.Serialization(net10.0) src/SlimMessageBus.Host.Serialization/SlimMessageBus.Host.Serialization.csproj — SlimMessageBus.Host.Serialization(net10.0): 67 % XML-doc coverage (2/3).

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3ee08c9cdcd4430ba50bcefffe3db4a2/history.json --exit-code 0 --source .	2	artifacts/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-3ee08c9cdcd4430ba50bcefffe3db4a2/tree.json --exit-code 0 --source .	0	artifacts/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 .	47	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list src/SlimMessageBus.sln package --vulnerable --include-transitive --format json	5	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	11	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	1	artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policy	disclosure	—	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 Confinement	runtime-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 Confinement	runtime-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 Enforcement	runtime-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 Dependencies	none (no readable dependency manifest)	—	none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).	0	—

Run 01a16139-6583-70c6-a3e4-5c838e88d984 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 24 field(s) across 3 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 18 field(s)

CustomerCreatedEvent.Firstname src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEvent.cs:9
CustomerCreatedEvent.Lastname src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEvent.cs:9
Customer.Firstname src/Samples/Sample.DomainEvents.Domain/Customer.cs:9
Customer.Lastname src/Samples/Sample.DomainEvents.Domain/Customer.cs:10
Customer.Firstname src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:11
Customer.Lastname src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:12
CreateCustomerCommand.Firstname src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommand.cs:3
CreateCustomerCommand.Lastname src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommand.cs:3
CustomerCreatedEvent.Firstname src/Samples/Sample.OutboxWebApi/Application/CustomerCreatedEvent.cs:3
CustomerCreatedEvent.Lastname src/Samples/Sample.OutboxWebApi/Application/CustomerCreatedEvent.cs:3
Customer.Firstname src/Samples/Sample.OutboxWebApi/DataAccess/Customer.cs:6
Customer.Lastname src/Samples/Sample.OutboxWebApi/DataAccess/Customer.cs:7
CreateCustomerCommand.FirstName src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:6
CreateCustomerCommand.LastName src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:7
CustomerModel.FirstName src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3
CustomerModel.LastName src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3
SearchCustomerQuery.FirstName src/Samples/Sample.ValidatingWebApi/Queries/SearchCustomerQuery.cs:6
SearchCustomerQuery.LastName src/Samples/Sample.ValidatingWebApi/Queries/SearchCustomerQuery.cs:7

Email — 4 field(s)

Customer.Email src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:14
CustomerEmailChangedEvent.OldEmail src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/CustomerEmailChangedEvent.cs:10
CreateCustomerCommand.Email src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:8
CustomerModel.Email src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3

Phone — 2 field(s)

CreateCustomerCommand.Phone src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:9
CustomerModel.Phone src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — bounded-context dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 63% · Adequate · gated by X5 ·

At a glance — Architecture · 81% · Strong ·

At a glance — Maturity · 41% · Weak · gated by M2, M4 ·

At a glance — Readiness · 55% · Adequate · gated by P8 ·

At a glance — Security · 43% · Weak · gated by D29, C2 ·

At a glance — Domain Modelling · 70% · Adequate · gated by DM6 ·

At a glance — Event-Driven · 86% · Strong ·

At a glance — Performance · 72% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts