osstotalsoft/nbb

Executive summary

osstotalsoft/nbb scores 38 out of 100 and is rated Weak, while seven of its nine lenses score higher still: Event Sourcing at 100 and Domain Modelling at 97, both rated Exemplary, Event-Driven at 83, Architecture at 78 and Performance at 76, all rated Strong, and Production Readiness at 63 and Code Health at 52, both rated Adequate.

The score is lower than those seven because the weakest lens counts most, and here that is Security and Compliance, which scores 23 and is rated Critical. Its Supply-chain Provenance & Signing dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault, and if Security and Compliance rose to 70, the score would rise from 38 to about 50.

67 findings are critical: 48 in Explicit Debt, ten in Static Analysis (SAST), three in Project dependency cycles, two in Dependency Vulnerabilities, two in Secrets (history), one in Coupling and one in Outbox / dual-write.

Watchdog couldn't measure Runtime accessibility in this code, so that dimension is left out of the score. The product code is 17,594 lines, which would take an estimated 0.3 person-years, around €39,000, to rebuild.

Code Health 52 Adequate, capped by Nullable reference types Architecture 78 Strong Maturity 36 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 63 Adequate, capped by Schema migrations Security and Compliance 23 ⚠ Critical, capped by Supply-chain Provenance & Signing, Data Protection and Access Controls Domain Modelling 97 ★ Exemplary Event-Driven 83 Strong Event Sourcing 100 ★ Exemplary Performance 76 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.

Security and Compliance 23 · counts for 45%Maturity 36 · counts for 25%Code Health 52 · counts for 14%Production Readiness 63 · counts for 8%Performance 76 · counts for 4%Architecture 78 · counts for 2%Event-Driven 83 · counts for 1%Domain Modelling 97 · counts for 1%Event Sourcing 100 · counts for 0%

If Security and Compliance rose from 23 to 70, the lowest score rated Strong, the score would rise from 38 to about 50.

Code composition: what the lines of code are

Business logic 12%Supporting code 46%Tests 40%Generated by tools 2%

New since the last survey: 85 findings

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

Coupling · Unstable project NBB.Messaging.MultiTenancy src/Messaging/NBB.Messaging.MultiTenancy/NBB.Messaging.MultiTenancy.csproj
Coupling · Unstable project NBB.ProcessManager.Definition src/Orchestration/NBB.ProcessManager.Definition/NBB.ProcessManager.Definition.csproj
Dependency Hygiene · Deprecated: xunit test/Integration/NBB.EventStore.IntegrationTests/NBB.EventStore.IntegrationTests.csproj
Dependency Hygiene · Deprecated: xunit test/Integration/NBB.Messaging.Rusi.IntegrationTests/NBB.Messaging.Rusi.IntegrationTests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Application/NBB.Application.Effects.Tests/NBB.Application.Effects.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/NBB.Application.Mediator.FSharp.Tests.fsproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Application/NBB.Application.Mediator.Tests/NBB.Application.Mediator.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Application/NBB.Application.MediatR.Tests/NBB.Application.MediatR.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Core/NBB.Core.Configuration.Tests/NBB.Core.Configuration.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Core/NBB.Core.DependencyInjection.Tests/NBB.Core.DependencyInjection.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Core/NBB.Core.Effects.FSharp.Tests/NBB.Core.Effects.FSharp.Tests.fsproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Core/NBB.Core.Effects.Tests/NBB.Core.Effects.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/NBB.Core.Evented.FSharp.Tests.fsproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Core/NBB.Core.Pipeline.Tests/NBB.Core.Pipeline.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Data/NBB.Data.Abstractions.Tests/NBB.Data.Abstractions.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Data/NBB.Data.EntityFramework.MultiTenancy.Tests/NBB.Data.EntityFramework.MultiTenancy.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Data/NBB.Data.EntityFramework.Tests/NBB.Data.EntityFramework.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Data/NBB.Data.EventSourcing.Tests/NBB.Data.EventSourcing.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Domain/NBB.Domain.Tests/NBB.Domain.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/EventStore/NBB.EventStore.AdoNet.Tests/NBB.EventStore.AdoNet.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/EventStore/NBB.EventStore.InMemory.Tests/NBB.EventStore.InMemory.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/EventStore/NBB.EventStore.Tests/NBB.EventStore.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Http/NBB.Http.Effects.Tests/NBB.Http.Effects.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Abstractions.Tests/NBB.Messaging.Abstractions.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.DataContracts.Tests/NBB.Messaging.DataContracts.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Effects.Tests/NBB.Messaging.Effects.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Host.Tests/NBB.Messaging.Host.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.InProcessMessaging.Tests/NBB.Messaging.InProcessMessaging.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Mediator.Tests/NBB.Messaging.Mediator.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.MediatR.Tests/NBB.Messaging.MediatR.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.MultiTenancy.Tests/NBB.Messaging.MultiTenancy.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Rusi.Tests/NBB.Messaging.Rusi.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/MultiTenancy/NBB.MultiTenancy.Configuration.Tests/NBB.MultiTenancy.Abstractions.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Http.Tests/NBB.MultiTenancy.Identification.Http.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Messaging.Tests/NBB.MultiTenancy.Identification.Messaging.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Tests/NBB.MultiTenancy.Identification.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Orchestration/NBB.ProcessManager.Mediator.Tests/NBB.ProcessManager.Mediator.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Orchestration/NBB.ProcessManager.Tests/NBB.ProcessManager.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Projections/NBB.ProjectR.Mediator.Tests/NBB.ProjectR.Mediator.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Projections/NBB.ProjectR.Tests/NBB.ProjectR.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Tools/NBB.Tools.Serilog.Enrichers.ServiceIdentifier.Tests/NBB.Tools.Serilog.Enrichers.ServiceIdentifier.Tests.csproj
Dependency Hygiene · Deprecated: xunit test/UnitTests/Tools/NBB.Tools.Serilog.Enrichers.TenantId.Tests/NBB.Tools.Serilog.Enrichers.TenantId.Tests.csproj
Explicit Debt · EmptyCatchBlock src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs
Explicit Debt · EmptyCatchBlock src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs
Explicit Debt · EmptyCatchBlock src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Access Controls · No authorization samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Access Controls · No authorization samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Access Controls · No authorization samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Access Controls · No authorization samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Access Controls · No authorization samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Access Controls · No authorization samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs
Access Controls · No authorization samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs
Access Controls · No authorization samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs
Access Controls · No authorization samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs
Access Controls · No authorization samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs
Access Controls · No authorization samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs
Access Controls · No authorization samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs
Access Controls · No authorization REDACTED
Access Controls · No authorization REDACTED
Async correctness · Blocking `WaitHandle.WaitOne` inside an `async` method src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs
Cancellation propagation · Async method without CancellationToken: Get samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Cancellation propagation · Async method without CancellationToken: Get samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Cancellation propagation · Async method without CancellationToken: Get samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs
Cancellation propagation · Async method without CancellationToken: Get samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs
Cancellation propagation · Async method without CancellationToken: Get REDACTED
Cancellation propagation · Async method without CancellationToken: GetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/Identifiers/HostTenantIdentifier.cs
Cancellation propagation · Async method without CancellationToken: GetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/Services/DefaultTenantIdentificationService.cs
Cancellation propagation · Async method without CancellationToken: TryGetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/Services/DefaultTenantIdentificationService.cs
Cancellation propagation · Async method drops its CancellationToken: PublishAsync src/Messaging/NBB.Messaging.Rusi/RusiMessagingTransport.cs
Exception handling · Swallowed exception (empty catch) src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs
Exception handling · Swallowed exception (empty catch) src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs
Exception handling · Swallowed exception (empty catch) src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/ContractsReadDatabaseMigrator.cs
Schema migrations · Schema created with EnsureCreated() outside the migrations samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/Migrator.cs
Async & latency hygiene · Sync-over-async blocking src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.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: 13 findings

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

Coupling · Off the main sequence: NBB.MultiTenancy.Abstractions
Dependency Hygiene · Deprecated: xunit
Static Analysis (SAST) · Medium: REDACTED samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs
Static Analysis (SAST) · Medium: REDACTED samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs
Static Analysis (SAST) · Medium: REDACTED samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs
Supply-chain Provenance & Signing REDACTED
Supply-chain Provenance & Signing REDACTED
Supply-chain Provenance & Signing REDACTED
Async correctness · Sync-over-async (deadlock risk) samples/Monolith/NBB.Mono.Migrations/Program.cs
Async correctness · Sync-over-async (deadlock risk) samples/Monolith/NBB.Mono.Migrations/Program.cs
Async correctness · Sync-over-async (deadlock risk) samples/Monolith/NBB.Mono.Migrations/Program.cs
Async correctness · Sync-over-async (deadlock risk) samples/Monolith/NBB.Mono.Migrations/Program.cs
Async correctness · Sync-over-async (deadlock risk) src/EventStore/NBB.EventStore.AdoNet.Migrations/Program.cs

Rebuild cost: about €39,000 · Estimate

Cost to rebuild	€13,000 to €65,000, for 216 to 685 hours of work, about 0.3 person-years for one engineer
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 38. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Small: 17,594 lines of product code
Comment lines	The estimate prices 15,818 lines. Comment lines count towards the size of 17,594 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.

Resolve the 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 5 points · Low effort · ADR Quality

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.).

Raises the score by about 8 points · Medium effort · Data Protection

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 8 points · Medium effort · Access Controls

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 €39,000 to build again, about 0.3 person-years of work. Its weakest lens is Security and Compliance, at 23 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.

Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts

What to do: Start with the Security and Compliance actions in Top priorities.

If you do one thing first · First action

Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.

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

Architecture — bounded-context dependency graph

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

Architecture: which parts of the code depend on which

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

203 modules, with 147 dependencies between them. 3 loops run through 6 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 163 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 NBB.Application.Mediator.FSharp	2 NBB.Core.Abstractions	3 NBB.Core.Abstractions.Paging	4 NBB.Core.Effects	6 NBB.Core.Evented.FSharp	7 NBB.Core.Pipeline	8 NBB.EventStore.AdoNet.Internal	9 NBB.MultiTenancy.Abstractions.Options	10 NBB.MultiTenancy.Identification.Resolvers	12 NBB.Data.Abstractions	13 NBB.EventStore.Abstractions	14 NBB.Invoices.FSharp.Domain.InvoiceAggregate	15 NBB.Messaging.Abstractions	16 NBB.MultiTenancy.Abstractions	17 NBB.ProcessManager.Definition	22 NBB.EventStore	24 NBB.Messaging.Host	25 NBB.Messaging.Nats.Internal	26 NBB.MultiTenancy.Abstractions.Context	27 NBB.MultiTenancy.Abstractions.Repositories	28 NBB.ProcessManager.Runtime.Persistence	30 NBB.EventStore.AdoNet	32 NBB.Messaging.Nats	34 NBB.MultiTenancy.Identification.Identifiers	35 NBB.ProcessManager.Runtime	37 NBB.MultiTenancy.Identification	38 NBB.MultiTenancy.Identification.Services
1 NBB.Application.Mediator.FSharp
2 NBB.Core.Abstractions
3 NBB.Core.Abstractions.Paging
4 NBB.Core.Effects
5 NBB.Core.Effects.FSharp.EffectBuilder
6 NBB.Core.Evented.FSharp
7 NBB.Core.Pipeline
8 NBB.EventStore.AdoNet.Internal
9 NBB.MultiTenancy.Abstractions.Options
10 NBB.MultiTenancy.Identification.Resolvers
11 Application	10
12 NBB.Data.Abstractions		3	2
13 NBB.EventStore.Abstractions		2
14 NBB.Invoices.FSharp.Domain.InvoiceAggregate	1				1
15 NBB.Messaging.Abstractions						1
16 NBB.MultiTenancy.Abstractions																			1
17 NBB.ProcessManager.Definition				4
18 NBB.ProcessManager.Runtime.SideEffectHandlers				4
19 NBB.Application.MediatR		4								1
20 NBB.Data.EntityFramework		2	4							2
21 NBB.Data.EventSourcing		1								1	2
22 NBB.EventStore											3
23 NBB.Invoices.FSharp.Domain.InvoiceRepository					1							3
24 NBB.Messaging.Host				2		12							20
25 NBB.Messaging.Nats.Internal													2										1
26 NBB.MultiTenancy.Abstractions.Context														2
27 NBB.MultiTenancy.Abstractions.Repositories								1						3
28 NBB.ProcessManager.Runtime.Persistence				1							1				2										2
29 NBB.ProjectR				3							2
30 NBB.EventStore.AdoNet							2									4
31 NBB.Messaging.Host.Internal						2							9				3
32 NBB.Messaging.Nats													4					1
33 NBB.MultiTenancy.Abstractions.Configuration								1											2	1
34 NBB.MultiTenancy.Identification.Identifiers																				1
35 NBB.ProcessManager.Runtime				2											3						1
36 NBB.EventStore.AdoNet.Multitenancy							2												2			4
37 NBB.MultiTenancy.Identification									1															1
38 NBB.MultiTenancy.Identification.Services																										1
39 NBB.Messaging.MultiTenancy		1				2		2					4	1					2	1							1
40 NBB.MultiTenancy.AspNet								1											1	1							1

Uses a module listed above itPart of a loopThe module itself

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

The Good

D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.6 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.5 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.9 X1 · Repo Async correctness 7.5 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.3 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 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

The Bad

X23 · Repo Unguarded diagnostic materialisation 5.5 X3 · Repo Exception handling 5.3 X4 · Repo Structured logging 6.2

The Ugly

D17 · .NET / C# Explicit Debt 4.6 X18 · Repo Disposal-pattern correctness 4.3 X5 · Repo Nullable reference types 2.3

At a glance — Architecture · 78% · Strong ·

The Good

D5 · .NET / C# Coupling 9.6 D6 · .NET / C# Cohesion (LCOM4) 10.0 D22 · .NET / C# Internal API Consistency 9.0 D23 · .NET / C# Boundary Type-Coupling 10.0 D26 · .NET / C# Project Cohesion 10.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 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

D27 · .NET / C# Navigability 5.9 AX10 · Repo Code composition 5.3 AX2 · Repo Stateful singletons 5.9

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

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 9.9 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 8.5 M3 · Repo Folder & project structure 10.0

The Bad

M1 · Repo Documentation (README) 5.2

The Ugly

D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 4.1 M2 · Repo Architecture documentation 2.0 M4 · Repo Documentation accuracy 0.0

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

The Good

D8 · .NET / C# Code Coverage 8.7 D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 9.8 D11 · .NET / C# Test Reliability 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 8.4 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 8.3 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 P7 · Repo Outbound HTTP resilience 10.0

The Bad

D12 · .NET / C# Dependency Hygiene 6.8 P3 · Repo Security & performance tooling 5.0

The Ugly

P8 · Repo Schema migrations 3.0

At a glance — Security · 23% · Critical · gated by D36, C1, C2 ·

The Good

D28 · .NET / C# Secrets (history) 8.0 D30 · .NET / C# Dependency Vulnerabilities 8.6 D31 · .NET / C# IaC & Container Security 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D29 · .NET / C# Static Analysis (SAST) 6.5 S1 · Repo Web-Security Posture 6.0

The Ugly

D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 0.0 C2 · Repo Access Controls 0.0

At a glance — Domain Modelling · 97% · Exemplary ·

The Good

DM12 · Repo Ambient inputs in the domain 9.7

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

The Good

ED1 · Repo Handler temporal coupling 10.0 ED3 · Repo Event naming 9.2

The Bad

ED4 · Repo Outbox / dual-write 7.0

At a glance — Event Sourcing · 100% · Exemplary ·

The Good

ES1 · Repo Fold determinism 10.0 ES2 · Repo Immutable events 10.0 ES3 · Repo PII in the event store 10.0

At a glance — Performance · 76% · Strong ·

The Good

PF1 · Repo Benchmark discipline 8.5 PF3 · Repo Async & latency hygiene 8.5

The Bad

PF2 · Repo Allocation hygiene 6.5

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	15	High / Critical
A03:2025 — Software Supply Chain Failures	11	High / Critical
A07:2025 — Authentication Failures	3	High / Critical

Roadmap

First, secure sensitive data by implementing encryption at rest and managing keys in a vault, while enforcing strict default-deny access controls on all endpoints. Next, address the lack of architectural decision records to ensure design rationale is documented. Finally, improve codebase hygiene by reconciling outdated documentation with the actual project structure and removing orphaned files to maintain knowledge freshness.

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

Do this	Helps	Effort	Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+5.2 pts	Low	ADR Quality
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.).	+8.3 pts	Medium	Data Protection
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.	+8.3 pts	Medium	Access Controls
Reconcile the README with reality: src/Orchestration/README.md installs the package `NBB.ProcessManager.Definition` (`dotnet add package NBB.ProcessManager.Definition`), but no project or props file references it; src/Orchestration/README.md installs the package `NBB.ProcessManager.Runtime` (`dotnet add package NBB.ProcessManager.Runtime`), but no project or props file references it; src/Application/NBB.Application.DataContracts.Schema/Readme.md installs the package `NBB.Application.DataContracts.Schema` (`dotnet add package NBB.Application.DataContracts.Schema`), but no project or props file references it; src/Application/NBB.Application.DataContracts/Readme.md installs the package `NBB.Application.DataContracts` (`dotnet add package NBB.Application.DataContracts`), but no project or props file references it; src/Application/NBB.Application.MediatR.Effects/Readme.md installs the package `NBB.Application.MediatR.Effects` (`dotnet add package NBB.Application.MediatR.Effects`), but no project or props file references it.	+4.9 pts	Medium	Documentation accuracy
Resolve the 45 Orphaned file finding(s) in Knowledge Freshness — start with DefaultMessageTypeRegistry.cs, AdoNetEventRepository.cs, MessagingHost.cs.	+4.4 pts	Medium	Knowledge Freshness
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PipelineTests.cs.	+2.2 pts	Low	Explicit Debt
Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with DefaultDeadLetterQueue.cs (2), ServiceCollectionExtension.cs, AdoNetEventStoreDatabaseMigrator.cs.	+2.2 pts	Low	Explicit Debt
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+3.9 pts	Medium	Architecture documentation

File quality

Per-file score 0–10 — a quality signature. Of 135 files carrying findings, judged against the Production bar: 4% slop · 21% mixed · 75% near-clean.

File	Score	Band	Worst signal
REDACTED	2.1	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
samples/MicroServices/NBB.Payments/NBB.Payments.Application/NBB.Payments.Application.csproj	3.5	Slop	Explicit Debt: NoWarnInCsproj
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs	4.2	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	4.8	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
samples/MicroServices/NBB.Payments/NBB.Payments.Worker/NBB.Payments.Worker.csproj	5.4	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Invoices/NBB.Invoices.Worker/NBB.Invoices.Worker.csproj	5.4	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Contracts/NBB.Contracts.Worker/NBB.Contracts.Worker.csproj	5.4	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Payments/NBB.Payments.Api/NBB.Payments.Api.csproj	5.5	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/NBB.Invoices.Application.csproj	5.5	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/NBB.Invoices.Api.csproj	5.5	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/NBB.Contracts.Application.csproj	5.5	Mixed	Explicit Debt: NoWarnInCsproj
samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/NBB.Contracts.Api.csproj	5.5	Mixed	Explicit Debt: NoWarnInCsproj
REDACTED	5.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs	5.9	Mixed	Cognitive Complexity: TypeInfo.ParseInternal (cognitive 20)
src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs	6.0	Mixed	Explicit Debt: CommentedOutCode
test/UnitTests/Orchestration/NBB.ProcessManager.Mediator.Tests/NBB.ProcessManager.Mediator.Tests.csproj	6.1	Mixed	Explicit Debt: NoWarnInCsproj
test/UnitTests/Projections/NBB.ProjectR.Mediator.Tests/NBB.ProjectR.Mediator.Tests.csproj	6.1	Mixed	Explicit Debt: NoWarnInCsproj

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

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

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

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

Could not be resolved — 5

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. 89 of 95 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 1.0 — 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

D1D2D3D4D5D6D8D9D10D11D12D13D14D15D16D17D18D19D20D21D22D23D24D26D27D28D29D30D31D34D35D36D39D44AX1AX10AX2AX3AX4AX5AX6AX8AX9C1C2DM12ED1ED3ED4ED5ES1ES2ES3GD1IC1M1M2M3M4P1P2P3P4P6P7P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 491 of 622 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 01a16148-2bb8-7718-8f40-e620f4838dd1.

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.

D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 326 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 18 test source file(s) (.fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'samples/NBB.Samples.ServiceDefaults/NBB.Samples.ServiceDefaults.csproj' with message: The URL of repository remote 'origin' is invalid: ''.
D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/EventStore/NBB.EventStore.AdoNet.Migrations/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Application/NBB.Application.MediatR.Effects/Mediator.cs`, `src/Application/NBB.Application.MediatR/MediatREventPublisher.cs`, `src/Application/NBB.Application.MediatR/MediatorUowDecorator.cs`, `src/Application/NBB.Application.Mediator.Effects/MediatorEff.cs`, `src/Application/NBB.Application.Mediator/MediatorEventPublisher.cs`, … (+20 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.
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 AspireAppHost (samples/MicroServices/NBB.MicroServices.AppHost/NBB.MicroServices.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
M4 Documentation accuracy — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (6): D19, D21, D22, 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 Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

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

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

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

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

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was TypeInfo.ParseInternal at 20.

TypeInfo.ParseInternal (cognitive 20)src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs:228

What to do

Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with TypeInfo.ParseInternal (cognitive 20). — Refactoring it lifts Cognitive Complexity from 9.6 to about 10.0/10.
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 Classes10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

Do you agree with this assessment?

D4 · Code Duplication9.5 / 10Stronggated by 17 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

17 duplicated block group(s) detected. 4 of the 17 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 (17 lines × 2) · ×2src/Core/NBB.Core.Abstractions/TypeExtensions.cs:27

Duplicated block (10 lines × 2) · ×2src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:96

Duplicated block (12 lines × 2) · ×2src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:184

Duplicated block (30 lines × 2)src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:109

Duplicated block (23 lines × 2)src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:60

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

What to do

Resolve the 2 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with TypeExtensions.cs, ReflectionExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ReflectionExtensions.cs, DependencyInjectionExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with ReflectionExtensions.cs (2). — 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 · Coupling9.6 / 10Adequategated by 1 critical finding✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Prevented

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

Layer violation: Application → Infrastructuresamples/MicroServices/NBB.Payments/NBB.Payments.Application/NBB.Payments.Application.csproj:25

Off the main sequence: NBB.Core.DependencyInjection · ×4src/Core/NBB.Core.DependencyInjection/NBB.Core.DependencyInjection.csproj:1

Unstable project NBB.Messaging.MultiTenancysrc/Messaging/NBB.Messaging.MultiTenancy/NBB.Messaging.MultiTenancy.csproj:1

Unstable project NBB.ProcessManager.Definitionsrc/Orchestration/NBB.ProcessManager.Definition/NBB.ProcessManager.Definition.csproj:1

What to do

Resolve the 1 Layer violation finding(s) in Coupling — start with NBB.Payments.Application.csproj. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 Off the main sequence finding(s) in Coupling — start with NBB.Core.DependencyInjection.csproj, NBB.Correlation.csproj, NBB.Domain.csproj. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Unstable project NBB.Messaging.MultiTenancy finding(s) in Coupling — start with NBB.Messaging.MultiTenancy.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

0 of 75 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D8 · Code Coverage8.7 / 10Strong✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 51.6% — 38 file(s) below 50% · 9 method(s) over the CRAP-30 risk line.

Low coverage: src/Core/NBB.Core.Effects/GenericSideEffectHandler.cs · ×38src/Core/NBB.Core.Effects/GenericSideEffectHandler.cs:1

CRAP 42: AdoNetEventRepository.AppendEventsToStreamExpectedVersionAsync · ×3src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:122

CRAP 30: ActivityExtensions.SetException · ×2src/Core/NBB.Core.Abstractions/ActivityExtensions.cs:48

No test project references NBB.Application.DataContracts.Schemasrc/Application/NBB.Application.DataContracts.Schema/NBB.Application.DataContracts.Schema.csproj

No test project references NBB.Messaging.Noopsrc/Messaging/NBB.Messaging.Noop/NBB.Messaging.Noop.csproj

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

What to do

Resolve the 38 Low coverage finding(s) in Code Coverage — start with DependencyInjectionExtensions.cs (3), GenericSideEffectHandler.cs, Unit.cs. — One of this dimension's main actionable groups (38 warning-level).
Resolve the 3 CRAP 42 finding(s) in Code Coverage — start with AdoNetEventRepository.cs, DefaultDeadLetterQueue.cs, MessageBusSubscriber.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 CRAP 30 finding(s) in Code Coverage — start with ActivityExtensions.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

326 test methods: 326 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.8 / 10Stronggated by 6 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 5 zero-assertion, 1 synchronised by a fixed sleep, 34 mock references across 326 tests. Measured on the C# suite only — at least 18 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: RequireRegistration_should_accept_a_registration_made_after_the_call · ×5test/UnitTests/Core/NBB.Core.DependencyInjection.Tests/ServiceRegistrationValidationExtensionsTests.cs:27

Fixed-sleep synchronisation: Shoud_reject_subsequent_restarts_When_restart_scheduledtest/UnitTests/Messaging/NBB.Messaging.Host.Tests/HostTests.cs:181

Mock framework: Moq · ×34

What to do

Resolve the 5 No assertions finding(s) in Test Quality — start with ServiceRegistrationValidationExtensionsTests.cs (3), TenantMiddlewareTests.cs, ProcessManagerInstanceUnitTests.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with HostTests.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 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene6.8 / 10Adequate✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

64 outdated, 0 vulnerable, 2 deprecated, 1 prerelease packages.

Deprecated: STAN.Client · ×41src/Messaging/NBB.Messaging.Nats/NBB.Messaging.Nats.csproj:28

Prerelease dependency: OpenTelemetry.SemanticConventions

Outdated: coverlet.collectortest/Integration/NBB.Messaging.Rusi.IntegrationTests/NBB.Messaging.Rusi.IntegrationTests.csproj:38

Outdated: Microsoft.Extensions.Http.Resilience · ×63

What to do

Resolve the 41 Deprecated finding(s) in Dependency Hygiene — start with NBB.Messaging.Nats.csproj, NBB.EventStore.IntegrationTests.csproj, NBB.Messaging.Rusi.IntegrationTests.csproj. — One of this dimension's main actionable groups (41 warning-level).
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with NBB.Messaging.Rusi.IntegrationTests.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 155 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 77 direct `PackageReference`(s), and 131 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?

D16 · Bus Factor9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs. Counted over 61 of the 337 production source files in this repository: 264 are under the ~2,400-byte size floor this dimension measures over, and the remaining 12 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D17 · Explicit Debt4.6 / 10Weak✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

57 deducted debt markers + unmeasured dead symbols across 16325 LoC in the .NET projects (2.7/KLoC) → score 4.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

NoWarnInCsproj · ×43REDACTED:13

EmptyCatchBlock · ×4src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs:309

WriteOnlyPrivateFieldtest/UnitTests/Core/NBB.Core.Pipeline.Tests/PipelineTests.cs:268

CommentedOutCode · ×5samples/Monolith/NBB.Mono/Program.cs:36

TodoComment · ×4samples/MultiTenancy/NBB.Todo.Api/ProblemDetailsConfiguration.cs:14

What to do

Resolve the 43 NoWarnInCsproj finding(s) in Explicit Debt — start with NBB.Payments.Worker.csproj (5), NBB.Invoices.Worker.csproj (5), NBB.Contracts.Worker.csproj (5). — One of this dimension's main actionable groups (43 issue-level).
Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with DefaultDeadLetterQueue.cs (2), ServiceCollectionExtension.cs, AdoNetEventStoreDatabaseMigrator.cs. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PipelineTests.cs. — One of this dimension's main actionable groups (1 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

131 projects, 530 source files, 25327 hand-written lines of code (16325 production / 9002 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 497 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 319 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's READMEs document the source directories (process manager, event store, multi-tenancy, messaging) rather than the root project. The XML-doc coverage is thin across most packages but shows promising coverage for application data contracts and MediatR effects: NBB.Application.DataContracts.Schema at 12% and NBB.Application.MediatR.Effects at 4%. There are no visible missing-overview or missing-installation defects in the shown documents. The repository's READMEs and XML-doc coverage are strong: the visible documents (NBB.Application.Mediator.Effects, NBB.Application.Mediator.FSharp, NBB.Core.Configuration) each document their own directory and provide NuGet install commands, registration code examples, usage snippets, and a clear overview of what they do. The architecture/design docs and some XML-doc coverage are thin but present; the visible documents all have an overview to judge (the first line of each README is the project name or its purpose). There are no findings for missing-overview, missing-installation, missing-usage, missing-contributing, missing-license, or internal-focused jargon because those are not shown and the outline lists only the sections present. (9 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)

XML-doc coverage: NBB.Samples.ServiceDefaults · ×87samples/NBB.Samples.ServiceDefaults/NBB.Samples.ServiceDefaults.csproj

What to do

Improve Documentation Quality — currently 8.0/10. — The repository's READMEs document the source directories (process manager, event store, multi-tenancy, messaging) rather than the root project. The XML-doc coverage is thin across most packages but shows promising coverage for application data contracts and MediatR effects: NBB.Application.DataContracts.Schema at 12% and NBB.Application.MediatR.Effects at 4%. There are no visible missing-overview or missing-installation defects in the shown documents. The repository's READMEs and XML-doc coverage are strong: the visible documents (NBB.Application.Mediator.Effects, NBB.Application.Mediator.FSharp, NBB.Core.Configuration) each document their own directory and provide NuGet install commands, registration code examples, usage snippets, and a clear overview of what they do. The architecture/design docs and some XML-doc coverage are thin but present; the visible documents all have an overview to judge (the first line of each README is the project name or its purpose). There are no findings for missing-overview, missing-installation, missing-usage, missing-contributing, missing-license, or internal-focused jargon because those are not shown and the outline lists only the sections present. (9 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)

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

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

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

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

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

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

1 API inconsistencies across 36 exposed types.

The API exposes two distinct entry points for the same logical operations: the HTTP Controller and the Mediator. While this is a common architectural pattern (Controller as facade, Mediator as internal dispatcher), the signatures are nearly identical in intent. Specifically, `ContractsController.Post` and `Mediator.Send` accept the exact same command types (`CreateContract`, `AddContractLine`, `ValidateContract`). This creates redundancy for consumers who might wonder which entry point to use, although typically the Controller is the public API and Mediator is internal. However, the presence of both in the public surface without clear separation of concerns (e.g., one being internal or hidden) is a minor consistency issue.

What to do

Resolve the 1 The API exposes two distinct entry points for the same logical… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types are scored-flagged across 16 context boundaries; 7 contract project(s) carry advisory strong-ID notes.

Domain: 1 contract type(s) expose producer-owned ids/enums

EventStore: 1 contract type(s) expose producer-owned ids/enums

EventStoreDnIntegrationTests: 1 contract type(s) expose producer-owned ids/enums

NBB: 4 contract type(s) expose producer-owned ids/enums

SnapshotStoreDbIntegrationTests: 1 contract type(s) expose producer-owned ids/enums

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

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D24 · Comment ValueStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

62 valuable / 0 redundant across 200 sampled comments.

What to do

Improve Comment Value — currently 8.5/10. — 62 valuable / 0 redundant across 200 sampled comments.

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

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability5.9 / 10Adequate✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

98 % of calls cross a namespace and 9 % go through an interface, but 67 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.

What to do

Improve Navigability — currently 5.9/10. — 98 % of calls cross a namespace and 9 % go through an interface, but 67 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

2 finding(s): 0 critical, 2 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 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 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)6.5 / 10Adequate✓ 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 6.5 / 10 · rule-coverage 100% · ceiling Documented

15 finding(s): 0 critical, 10 high, 5 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 29 file(s) — `samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/Migrator.cs` (lines 14–15, line 34), `samples/MicroServices/NBB.Invoices/NBB.Invoices.Migrations/Migrator.cs` (lines 14–15, line 32), `samples/MicroServices/NBB.Payments/NBB.Payments.Migrations/Migrator.cs` (lines 14–15, line 32), `samples/MultiTenancy/NBB.Todo.Migrations/Migrator.cs` (lines 16–17, line 28), `src/Application/NBB.Application.MediatR.Effects/Mediator.cs` (lines 17–18, lines 22–23, line 27, …), … (+24 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 27 of those file(s) — `samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/Migrator.cs`, `samples/MicroServices/NBB.Invoices/NBB.Invoices.Migrations/Migrator.cs`, `samples/MicroServices/NBB.Payments/NBB.Payments.Migrations/Migrator.cs`, `samples/MultiTenancy/NBB.Todo.Migrations/Migrator.cs`, `src/Application/NBB.Application.MediatR.Effects/Mediator.cs`, … (+22 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 1 of those file(s) — `src/Core/NBB.Core.Configuration/ConnectionStringConfigurationExtensions.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.

REDACTED

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities8.6 / 10Adequategated by 2 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 8.6 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 2 high, 1 medium, 0 low.

REDACTED

What to do

Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

Do you agree with this assessment?

D34 · Knowledge Freshness4.1 / 10Weak✓ 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 4.1 / 10 · rule-coverage 100% · ceiling Documented

46 of 73 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs. Counted over 73 of the 337 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×45src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs:1

Concentrated knowledge decay

Most significant orphaned filesrc/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs:1

What to do

Resolve the 45 Orphaned file finding(s) in Knowledge Freshness — start with DefaultMessageTypeRegistry.cs, AdoNetEventRepository.cs, MessagingHost.cs. — One of this dimension's main actionable groups (45 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtension.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

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?

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

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

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

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

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

0 of 2137 first-party methods have an oversized IL body.

✓ On the Gold path — maintain.

Detailed fixes: d39_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 143 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 dependencies10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

AX10 · Code composition5.3 / 10Adequate✓ 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 singletons5.9 / 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.

`MessagingHost` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions, _subscriberStopSource, _stoppingSource; e.g. `_subscriptions` at line 116). — src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:21
`Storage` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions; e.g. `_subscriptions` at line 65). — src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs:12
`StanConnectionProvider` is a singleton (one shared instance) but mutates instance state outside any lock (_connection, _lazyConnection; e.g. `_connection` at line 68). — src/Messaging/NBB.Messaging.Nats/Internal/StanConnectionManager.cs:15
`TimeoutsManager` is a singleton (one shared instance) but mutates instance state outside any lock (_startSlice; e.g. `_startSlice` at line 82). — src/Orchestration/NBB.ProcessManager.Runtime/Timeouts/TimeoutsManager.cs:13

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 NBB.MultiTenancy.Abstractions ↔ NBB.MultiTenancy.Abstractions.Context depend on each other. The lightest dependency in the cycle is NBB.MultiTenancy.Abstractions → NBB.MultiTenancy.Abstractions.Context (NBB.MultiTenancy.Abstractions.TenantLogScope → NBB.MultiTenancy.Abstractions.Context.TenantContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/MultiTenancy/NBB.MultiTenancy.Abstractions/TenantLogScope.cs:4
The namespaces NBB.Messaging.Nats ↔ NBB.Messaging.Nats.Internal depend on each other. The lightest dependency in the cycle is NBB.Messaging.Nats → NBB.Messaging.Nats.Internal (NBB.Messaging.Nats.StanMessagingTransport → NBB.Messaging.Nats.Internal.StanConnectionProvider, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Messaging/NBB.Messaging.Nats/StanMessagingTransport.cs:6
The namespaces NBB.ProcessManager.Runtime ↔ NBB.ProcessManager.Runtime.Persistence depend on each other. The lightest dependency in the cycle is NBB.ProcessManager.Runtime → NBB.ProcessManager.Runtime.Persistence (NBB.ProcessManager.Runtime.ProcessExecutionCoordinator → NBB.ProcessManager.Runtime.Persistence.IInstanceDataRepository, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Orchestration/NBB.ProcessManager.Runtime/ProcessExecutionCoordinator.cs:5

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 Protection0.0 / 10Critical✓ 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.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.

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.
`ContractsController.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. (×2) — samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:34, samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:42
`ContractsController.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. (×3) — samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:57, samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:64, samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:71
`InvoicesController.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. (×2) — samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:32, samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:39
`InvoicesController.Create` 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. — samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:48
`InvoicesController.Process` 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. — samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:55
`PayablesController.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. (×2) — samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:30, samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:38
`PayablesController.Pay` 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. — samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:45
`TodoController.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:32
`TodoController.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. — REDACTED:37

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?

DM12 · Ambient inputs in the domain9.7 / 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.

`InvoiceLock` reads `DateTime.Now` inside `Acquire`, `Release`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — samples/MicroServices/NBB.Invoices/NBB.Invoices.Domain/InvoiceAggregate/InvoiceLock.cs:38
`Payable` reads `DateTime.Now` inside `Pay`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — samples/MicroServices/NBB.Payments/NBB.Payments.Domain/PayableAggregate/Payable.cs:31

What to do

Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.

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?

ED3 · Event naming9.2 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

`InvoiceEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — samples/MicroServices/NBB.Invoices.FSharp/NBB.Invoices.FSharp/Domain/InvoiceAggregate.fs:20
`SomeEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/EventPipelineTests.fs:13
`SomeOtherEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/EventPipelineTests.fs:18
`Event1` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/Sample.fs:85
`Event2` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/Sample.fs:97
`DomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. (×3) — test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/Tests.fs:12, test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/Sample2.fs:15, test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/Sample.fs:11

What to do

Name events in the past tense — they record facts that already happened.

Do you agree with this assessment?

ED4 · Outbox / dual-write7.0 / 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.

`ReadModelGenerator.Handle` writes to the database while `ContractDomainEventHandlers.Handle` publishes to the message bus in the same command-handling flow, with no outbox referenced on either path. Splitting the persist and the publish across sibling methods (or two collaborating actors) doesn't make them atomic — a crash between the two either loses the message or emits a phantom event. Use the transactional outbox pattern so the message is committed in the same transaction as the state change and dispatched afterwards. — samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/DomainEventHandlers/ReadModelGenerator.cs:27

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 · Idempotency8.4 / 10Strong◐ 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.

`CommandHandlers.ContractCommandHandlers.Handle` mutates persistent state (a database save) 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. — samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/CommandHandlers/ContractCommandHandlers.cs:39
`DomainEventHandlers.ReadModelGenerator.Handle` mutates persistent state (a database save) 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. — samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/DomainEventHandlers/ReadModelGenerator.cs:73
`CommandHandlers.ProcessInvoiceCommandHandler.Handle` mutates persistent state (a database save) 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. — samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/CommandHandlers/ProcessInvoiceCommandHandler.cs:25
`CommandHandlers.PayPayableCommandHandler.Handle` mutates persistent state (a database save) 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. — samples/MicroServices/NBB.Payments/NBB.Payments.Application/CommandHandlers/PayPayableCommandHandler.cs:23
`SideEffectHandlers.RequestTimeoutHandler.Handle` 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/Orchestration/NBB.ProcessManager.Runtime/SideEffectHandlers/RequestTimeoutHandler.cs:27

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?

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether Apply/When folds reconstruct state purely from the event (no DateTime.Now, Guid.NewGuid, Random or IO) so replay is reproducible.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

Do you agree with this assessment?

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether persisted events are immutable facts (init-only/readonly) — a settable event member lets stored history be rewritten.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

Do you agree with this assessment?

ES3 · PII in the event store10.0 / 10Exemplary○ Nothing flagged

Other · Event Sourcing — Whether the append-only event log avoids un-erasable personal data (or has a crypto-shredding strategy) — a GDPR right-to-erasure risk.

Method: Roslyn (event-sourcing gated): high-confidence PII flagged Warning; ambiguous name-like fields adjudicated by language model as person versus fictional. Advisory without model, definitive with.

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/MultiTenancy/NBB.MultiTenancy.Abstractions/Configuration/TenantConfiguration.cs:23, src/MultiTenancy/NBB.MultiTenancy.Abstractions/Repositories/ConfigurationTenantRepository.cs:56

What to do

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.9 / 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.

`GetByHost` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/MultiTenancy/NBB.MultiTenancy.Abstractions/Repositories/ConfigurationTenantRepository.cs:56
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — src/Messaging/NBB.Messaging.InProcessMessaging/Internal/InProcessMessagingTransport.cs:49, src/Messaging/NBB.Messaging.JetStream/DependencyInjectionExtensions.cs:22, src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:24, …

What to do

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

Do you agree with this assessment?

M1 · Documentation (README)5.2 / 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.

64 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 83 of 131 project(s) that lack one — worth up to 1.3 pts.
Review the README against recent changes; refresh the parts that drifted.

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.

src/Orchestration/README.md installs the package `NBB.ProcessManager.Definition` (`dotnet add package NBB.ProcessManager.Definition`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Orchestration/README.md:6
src/Orchestration/README.md installs the package `NBB.ProcessManager.Runtime` (`dotnet add package NBB.ProcessManager.Runtime`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Orchestration/README.md:7
src/Application/NBB.Application.DataContracts.Schema/Readme.md installs the package `NBB.Application.DataContracts.Schema` (`dotnet add package NBB.Application.DataContracts.Schema`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.DataContracts.Schema/Readme.md:6
src/Application/NBB.Application.DataContracts/Readme.md installs the package `NBB.Application.DataContracts` (`dotnet add package NBB.Application.DataContracts`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.DataContracts/Readme.md:11
src/Application/NBB.Application.MediatR.Effects/Readme.md installs the package `NBB.Application.MediatR.Effects` (`dotnet add package NBB.Application.MediatR.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.MediatR.Effects/Readme.md:7
src/Application/NBB.Application.MediatR/Readme.md installs the package `NBB.Application.MediatR` (`dotnet add package NBB.Application.MediatR`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.MediatR/Readme.md:7
src/Application/NBB.Application.Mediator.Effects/README.md installs the package `NBB.Application.Mediator.Effects` (`dotnet add package NBB.Application.Mediator.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.Mediator.Effects/README.md:7
src/Application/NBB.Application.Mediator.FSharp/Readme.md installs the package `NBB.Application.Mediator.FSharp` (`dotnet add package NBB.Application.Mediator.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.Mediator.FSharp/Readme.md:7
src/Application/NBB.Application.Mediator/README.md installs the package `NBB.Application.Mediator` (`dotnet add package NBB.Application.Mediator`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Application/NBB.Application.Mediator/README.md:7
src/Core/NBB.Core.Abstractions/README.md installs the package `NBB.Core.Abstractions` (`dotnet add package NBB.Core.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.Abstractions/README.md:10
src/Core/NBB.Core.Configuration/README.md installs the package `NBB.Core.Configuration` (`dotnet add package NBB.Core.Configuration`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.Configuration/README.md:7
src/Core/NBB.Core.DependencyInjection/README.md installs the package `NBB.Core.DependencyInjection` (`dotnet add package NBB.Core.DependencyInjection`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.DependencyInjection/README.md:11
src/Core/NBB.Core.Effects.FSharp/README.md installs the package `NBB.Core.Effects.FSharp` (`dotnet add package NBB.Core.Effects.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.Effects.FSharp/README.md:7
src/Core/NBB.Core.Effects/README.md installs the package `NBB.Core.Effects` (`dotnet add package NBB.Core.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.Effects/README.md:10
src/Core/NBB.Core.Evented.FSharp/README.md installs the package `NBB.Core.Evented.FSharp` (`dotnet add package NBB.Core.Evented.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.Evented.FSharp/README.md:7
src/Core/NBB.Core.FSharp/README.md installs the package `NBB.Core.FSharp` (`dotnet add package NBB.Core.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.FSharp/README.md:7
src/Core/NBB.Core.Pipeline/README.md installs the package `NBB.Core.Pipeline` (`dotnet add package NBB.Core.Pipeline`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/NBB.Core.Pipeline/README.md:7
src/Correlation/NBB.Correlation.AspNet/README.md installs the package `NBB.Correlation.AspNet` (`dotnet add package NBB.Correlation.AspNet`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Correlation/NBB.Correlation.AspNet/README.md:7
src/Correlation/NBB.Correlation.Serilog.SqlServer/README.md installs the package `NBB.Serilog.SqlServer` (`dotnet add package NBB.Serilog.SqlServer`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Correlation/NBB.Correlation.Serilog.SqlServer/README.md:8
src/Correlation/NBB.Correlation.Serilog/README.md installs the package `NBB.Correlation.Serilog` (`dotnet add package NBB.Correlation.Serilog`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Correlation/NBB.Correlation.Serilog/README.md:7
src/Correlation/NBB.Correlation/README.md installs the package `NBB.Correlation` (`dotnet add package NBB.Correlation`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Correlation/NBB.Correlation/README.md:7
src/Data/NBB.Data.Abstractions/README.md installs the package `NBB.Data.Abstractions` (`dotnet add package NBB.Data.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Data/NBB.Data.Abstractions/README.md:12
src/Data/NBB.Data.EntityFramework.MultiTenancy/README.md installs the package `NBB.Data.EntityFramework.MultiTenancy` (`dotnet add package NBB.Data.EntityFramework.MultiTenancy`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Data/NBB.Data.EntityFramework.MultiTenancy/README.md:9
src/Data/NBB.Data.EntityFramework/README.md installs the package `NBB.Data.EntityFramework` (`dotnet add package NBB.Data.EntityFramework`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Data/NBB.Data.EntityFramework/README.md:13
src/Data/NBB.Data.EventSourcing/README.md installs the package `NBB.Data.EventSourcing` (`dotnet add package NBB.Data.EventSourcing`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Data/NBB.Data.EventSourcing/README.md:9
src/Domain/NBB.Domain.Abstractions/README.md installs the package `NBB.Domain.Abstractions` (`dotnet add package NBB.Domain.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Domain/NBB.Domain.Abstractions/README.md:12
src/Domain/NBB.Domain/README.md installs the package `NBB.Domain` (`dotnet add package NBB.Domain`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Domain/NBB.Domain/README.md:18
src/EventStore/NBB.EventStore.Abstractions/README.md installs the package `NBB.EventStore.Abstractions` (`dotnet add package NBB.EventStore.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EventStore/NBB.EventStore.Abstractions/README.md:7
src/EventStore/NBB.EventStore.AdoNet.Multitenancy/README.md installs the package `NBB.EventStore.AdoNet.MultiTenancy` (`dotnet add package NBB.EventStore.AdoNet.MultiTenancy`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EventStore/NBB.EventStore.AdoNet.Multitenancy/README.md:8
src/EventStore/NBB.EventStore.AdoNet/README.md installs the package `NBB.EventStore.AdoNet` (`dotnet add package NBB.EventStore.AdoNet`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EventStore/NBB.EventStore.AdoNet/README.md:7
src/EventStore/NBB.EventStore.Effects/Readme.md installs the package `NBB.EventStore.Effects` (`dotnet add package NBB.EventStore.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EventStore/NBB.EventStore.Effects/Readme.md:7
src/EventStore/NBB.EventStore.InMemory/README.md installs the package `NBB.EventStore.InMemory` (`dotnet add package NBB.EventStore.InMemory`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EventStore/NBB.EventStore.InMemory/README.md:10
src/EventStore/NBB.EventStore/README.md installs the package `NBB.EventStore` (`dotnet add package NBB.EventStore`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EventStore/NBB.EventStore/README.md:10
src/Messaging/NBB.Messaging.Abstractions/README.md installs the package `NBB.Messaging.Abstractions` (`dotnet add package NBB.Messaging.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.Abstractions/README.md:6
src/Messaging/NBB.Messaging.DataContracts/README.md installs the package `NBB.Messaging.DataContracts` (`dotnet add package NBB.Messaging.DataContracts`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.DataContracts/README.md:7
src/Messaging/NBB.Messaging.Host/README.md installs the package `NBB.Messaging.Host` (`dotnet add package NBB.Messaging.Host`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.Host/README.md:7
src/Messaging/NBB.Messaging.MediatR/README.md installs the package `NBB.Messaging.MediatR` (`dotnet add package NBB.Messaging.MediatR`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.MediatR/README.md:11
src/Messaging/NBB.Messaging.Mediator/README.md installs the package `NBB.Messaging.Mediator` (`dotnet add package NBB.Messaging.Mediator`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.Mediator/README.md:11
src/Messaging/NBB.Messaging.MultiTenancy/README.md installs the package `NBB.MultiTenancy.AspNet` (`dotnet add package NBB.MultiTenancy.AspNet`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.MultiTenancy/README.md:6
src/Messaging/NBB.Messaging.OpenTelemetry/README.md installs the package `NBB.Messaging.OpenTelemetry` (`dotnet add package NBB.Messaging.OpenTelemetry`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Messaging/NBB.Messaging.OpenTelemetry/README.md:8

What to do

Reconcile the README with reality: src/Orchestration/README.md installs the package `NBB.ProcessManager.Definition` (`dotnet add package NBB.ProcessManager.Definition`), but no project or props file references it; src/Orchestration/README.md installs the package `NBB.ProcessManager.Runtime` (`dotnet add package NBB.ProcessManager.Runtime`), but no project or props file references it; src/Application/NBB.Application.DataContracts.Schema/Readme.md installs the package `NBB.Application.DataContracts.Schema` (`dotnet add package NBB.Application.DataContracts.Schema`), but no project or props file references it; src/Application/NBB.Application.DataContracts/Readme.md installs the package `NBB.Application.DataContracts` (`dotnet add package NBB.Application.DataContracts`), but no project or props file references it; src/Application/NBB.Application.MediatR.Effects/Readme.md installs the package `NBB.Application.MediatR.Effects` (`dotnet add package NBB.Application.MediatR.Effects`), 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 · Observability8.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 28/65 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 65, 13 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.

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

Add an approval/environment gate (required reviewers / protection rules) before production promotion.

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?

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). 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. (×2) — samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/ContractsReadDatabaseMigrator.cs:14, samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/Migrator.cs:24

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 discipline8.5 / 10Strong✓ 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.

A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way hot code pressures the GC) aren't being measured.

What to do

Add [MemoryDiagnoser] to the benchmarks so allocation regressions are visible, not just time.

Do you agree with this assessment?

PF2 · Allocation hygiene6.5 / 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 22 use(s) across 21,015 production line(s) (~1.0/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 hygiene8.5 / 10Strong✓ Tool-verified

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

1 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).
`t.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:89

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 Posture6.0 / 10Adequate✓ 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. (×5) — samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Program.cs:13, samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Program.cs:10, samples/MicroServices/NBB.Payments/NBB.Payments.Api/Program.cs:10, …
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×5) — samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Program.cs:13, samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Program.cs:10, samples/MicroServices/NBB.Payments/NBB.Payments.Api/Program.cs:10, …

What to do

Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.

Do you agree with this assessment?

X1 · Async correctness7.5 / 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.

`WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`). — src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs:78
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:89

What to do

Blocking `WaitHandle.WaitOne` inside an `async` method

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 correctness4.3 / 10Weak✓ 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.

`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 79). Every use of it in `CreateDatabaseObjectsAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:79
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `DropDatabaseObjectsAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:88
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 73). Every use of it in `GetEventsFromStreamAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:73
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 104). Every use of it in `DeleteStreamAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:104
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 132). Every use of it in `AppendEventsToStreamExpectedVersionAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:132
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 178). Every use of it in `AppendEventsToStreamExpectedVersionAnyAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:178
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `LoadSnapshotAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet/AdoNetSnapshotRepository.cs:44
`cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 86). Every use of it in `StoreSnapshotAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — src/EventStore/NBB.EventStore.AdoNet/AdoNetSnapshotRepository.cs:86
`_subscription` is declared `IDisposable` and nothing more, and every assignment to it takes a constructor parameter — so `HostedSubscription` can do exactly one thing with it, which is the release performed here (line 26), and it is the only reference left that can perform it. That release is the tail of an unprotected sequence: `_logger.LogInformation("Messaging subscriber for topic {TopicName} is stoppin...` runs first (line 24), and nothing in `Dispose` catches it. A single throw from that call skips the release entirely — and because a bare `IDisposable` carries no state to inspect and no second holder to fall back on, whatever it represents (a lock taken for this instance, a semaphore lease, a scope) is then held for the remaining lifetime of the process, with nothing left that could ever give it back. Wrap the calls that precede it in a `try` and move the release into the `finally`, so the one statement that must happen is the one that always happens. — src/Messaging/NBB.Messaging.Host/Internal/HostedSubscription.cs:26
`MessagingHost` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_stoppingSource` itself (line 33), which makes that instance its own. But `_stoppingSource` is named in none of the methods the disposal search covered: `Dispose` (line 235) — 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` (`_stoppingSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:33
`cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `SubscribeAsync` 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 cts = …;`), which releases it at the end of the scope on every path including a throw. — src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:54
`InMemoryTimeoutRepository` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_readerWriterLock` itself (line 15), which makes that instance its own. But `_readerWriterLock` is named in none of the methods the disposal search covered: `Dispose` (line 102), `Dispose` (line 110), `Dispose` (line 102), `Dispose` (line 110) — 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` (`_readerWriterLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Orchestration/NBB.ProcessManager.Runtime/Timeouts/InMemoryTimeoutRepository.cs:15

What to do

Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.

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 propagation9.3 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

Only 120/135 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. (×14) — samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:34, samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:42, samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:32, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — src/Messaging/NBB.Messaging.Host/IMessagingHost.cs:28
1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). — src/Messaging/NBB.Messaging.Rusi/RusiMessagingTransport.cs:40

What to do

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

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

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

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

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 materialisation5.5 / 10Adequate✓ Tool-verified

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.

`LogDebug` at line 44 is called with an argument built by `string.Join(", ", includePaths)` (line 44), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.cs:44
`LogDebug` at line 59 is called with an argument built by `string.Join(", ", includePaths)` (line 59), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.cs:59
`LogDebug` at line 77 is called with an argument built by `string.Join(", ", includePaths)` (line 78), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.cs:77

What to do

Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.

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 handling5.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs:309, src/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:66, src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:90, …

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 logging6.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×5) — src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:62, src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:94, src/Messaging/NBB.Messaging.Nats/Internal/StanConnectionManager.cs:70, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types2.3 / 10Critical✓ 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.

This method contradicts itself about `mementoProvider`: line 31 assigns it with `as IMementoProvider`, which hands back null rather than throwing when the value is not a `IMementoProvider`, but line 39 then dereferences it directly as `mementoProvider.SetMemento` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mementoProvider` once before the first use and handle the null case, or cast with `(IMementoProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Domain/NBB.Domain/EventSourcedAggregateRoot.cs:39
This method contradicts itself about `mementoProvider`: line 44 assigns it with `as IMementoProvider`, which hands back null rather than throwing when the value is not a `IMementoProvider`, but line 46 then dereferences it directly as `mementoProvider.CreateMemento` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mementoProvider` once before the first use and handle the null case, or cast with `(IMementoProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Domain/NBB.Domain/EventSourcedAggregateRoot.cs:46
This method contradicts itself about `activity`: line 26 writes `activity?.IsAllDataRequested`, which says `activity` can be null, but line 51 then dereferences it directly as `activity.AddEvent` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `activity` truly cannot be null here, the `?.` is misleading. Settle it one way — test `activity` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Tools/Serilog/NBB.Tools.Serilog.OpenTelemetryTracingSink/Internal/OpenTelemetryTracingSink.cs:51
4/93 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.
~0.4 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 2283 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

Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
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	52%	Adequate — gated by X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	78%	Strong	Solid.
Maturity	36%	Weak — gated by M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	63%	Adequate — gated by P8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	23%	Critical — gated by D36, C1, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	97%	Exemplary	Solid.
Event-Driven	83%	Strong	Solid.
Event Sourcing	100%	Exemplary	Strongest area.
Performance	76%	Strong	Solid.

Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

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

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

C3 Audit Trail — 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.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 23 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 — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence 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.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 25 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — applicable but not scored (6 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 aggregate root(s) (entities that raise its domain events); 13 aggregate root(s) (AggregateRoot/IAggregateRoot); 13 value object(s); 32 domain event(s); a Domain/Aggregates/ValueObjects layer; 2 repository port(s) loading or saving an aggregate/entity; 4 per-aggregate domain namespaces (…/BasketAggregate, …/OrderAggregate); a top-level samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
P9 Domain vs controller coverage — coverage data present for 142 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 67 finding(s)

D17 · Explicit Debt · NoWarnInCsproj · ×43

NoWarnInCsproj REDACTED:13 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.MicroServicesOrchestration/NBB.MicroServicesOrchestration.csproj:8 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj test/UnitTests/Projections/NBB.ProjectR.Mediator.Tests/NBB.ProjectR.Mediator.Tests.csproj:7 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj test/UnitTests/Orchestration/NBB.ProcessManager.Mediator.Tests/NBB.ProcessManager.Mediator.Tests.csproj:7 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Worker/NBB.Payments.Worker.csproj:13 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Worker/NBB.Invoices.Worker.csproj:13 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Worker/NBB.Contracts.Worker.csproj:13 — MSG0005 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Worker/NBB.Payments.Worker.csproj:18 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Application/NBB.Payments.Application.csproj:15 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Api/NBB.Payments.Api.csproj:17 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Worker/NBB.Invoices.Worker.csproj:18 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/NBB.Invoices.Application.csproj:15 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/NBB.Invoices.Api.csproj:17 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Worker/NBB.Contracts.Worker.csproj:20 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/NBB.Contracts.Application.csproj:15 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/NBB.Contracts.Api.csproj:19 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Worker/NBB.Payments.Worker.csproj:18 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Application/NBB.Payments.Application.csproj:15 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Payments/NBB.Payments.Api/NBB.Payments.Api.csproj:17 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Worker/NBB.Invoices.Worker.csproj:18 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/NBB.Invoices.Application.csproj:15 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/NBB.Invoices.Api.csproj:17 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Worker/NBB.Contracts.Worker.csproj:20 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/NBB.Contracts.Application.csproj:15 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/NBB.Contracts.Api.csproj:19 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
+ 18 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · EmptyCatchBlock · ×4

EmptyCatchBlock src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs:309 — 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/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:66 — 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/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:90 — 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/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:122 — 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.

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

Namespace dependency cycle src/MultiTenancy/NBB.MultiTenancy.Abstractions/TenantLogScope.cs:4 — The namespaces NBB.MultiTenancy.Abstractions ↔ NBB.MultiTenancy.Abstractions.Context depend on each other. The lightest dependency in the cycle is NBB.MultiTenancy.Abstractions → NBB.MultiTenancy.Abstractions.Context (NBB.MultiTenancy.Abstractions.TenantLogScope → NBB.MultiTenancy.Abstractions.Context.TenantContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Messaging/NBB.Messaging.Nats/StanMessagingTransport.cs:6 — The namespaces NBB.Messaging.Nats ↔ NBB.Messaging.Nats.Internal depend on each other. The lightest dependency in the cycle is NBB.Messaging.Nats → NBB.Messaging.Nats.Internal (NBB.Messaging.Nats.StanMessagingTransport → NBB.Messaging.Nats.Internal.StanConnectionProvider, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Orchestration/NBB.ProcessManager.Runtime/ProcessExecutionCoordinator.cs:5 — The namespaces NBB.ProcessManager.Runtime ↔ NBB.ProcessManager.Runtime.Persistence depend on each other. The lightest dependency in the cycle is NBB.ProcessManager.Runtime → NBB.ProcessManager.Runtime.Persistence (NBB.ProcessManager.Runtime.ProcessExecutionCoordinator → NBB.ProcessManager.Runtime.Persistence.IInstanceDataRepository, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.

D28 · Secrets (history) · High secret · ×2

REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×2

REDACTED
REDACTED

D17 · Explicit Debt · WriteOnlyPrivateField · ×1

WriteOnlyPrivateField test/UnitTests/Core/NBB.Core.Pipeline.Tests/PipelineTests.cs:268 — private IGuidProvider dependency — 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 · ×1

REDACTED

D5 · Coupling · Layer violation · ×1

Layer violation: Application → Infrastructure samples/MicroServices/NBB.Payments/NBB.Payments.Application/NBB.Payments.Application.csproj:25 — NBB.Payments.Application (Application) references NBB.Payments.Data (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).

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

Dual write (no outbox): ReadModelGenerator.Handle persists, ContractDomainEventHandlers.Handle publishes samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/DomainEventHandlers/ReadModelGenerator.cs:27 — `ReadModelGenerator.Handle` writes to the database while `ContractDomainEventHandlers.Handle` publishes to the message bus in the same command-handling flow, with no outbox referenced on either path. Splitting the persist and the publish across sibling methods (or two collaborating actors) doesn't make them atomic — a crash between the two either loses the message or emits a phantom event. Use the transactional outbox pattern so the message is committed in the same transaction as the state change and dispatched afterwards.

Serious — 221 finding(s)

D12 · Dependency Hygiene · Deprecated · ×41

Deprecated: STAN.Client src/Messaging/NBB.Messaging.Nats/NBB.Messaging.Nats.csproj:28 — STAN.Client 0.3.0 — Legacy — the publisher's replacement is `NATS.Client.JetStream`; migrate the reference to it.
Deprecated: xunit test/Integration/NBB.EventStore.IntegrationTests/NBB.EventStore.IntegrationTests.csproj:35 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/Integration/NBB.Messaging.Rusi.IntegrationTests/NBB.Messaging.Rusi.IntegrationTests.csproj:32 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Application/NBB.Application.Effects.Tests/NBB.Application.Effects.Tests.csproj:14 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/NBB.Application.Mediator.FSharp.Tests.fsproj:23 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Application/NBB.Application.Mediator.Tests/NBB.Application.Mediator.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Application/NBB.Application.MediatR.Tests/NBB.Application.MediatR.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Core/NBB.Core.Configuration.Tests/NBB.Core.Configuration.Tests.csproj:16 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Core/NBB.Core.DependencyInjection.Tests/NBB.Core.DependencyInjection.Tests.csproj:12 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Core/NBB.Core.Effects.FSharp.Tests/NBB.Core.Effects.FSharp.Tests.fsproj:20 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Core/NBB.Core.Effects.Tests/NBB.Core.Effects.Tests.csproj:14 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/NBB.Core.Evented.FSharp.Tests.fsproj:21 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Core/NBB.Core.Pipeline.Tests/NBB.Core.Pipeline.Tests.csproj:11 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Data/NBB.Data.Abstractions.Tests/NBB.Data.Abstractions.Tests.csproj:12 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Data/NBB.Data.EntityFramework.MultiTenancy.Tests/NBB.Data.EntityFramework.MultiTenancy.Tests.csproj:18 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Data/NBB.Data.EntityFramework.Tests/NBB.Data.EntityFramework.Tests.csproj:18 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Data/NBB.Data.EventSourcing.Tests/NBB.Data.EventSourcing.Tests.csproj:20 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Domain/NBB.Domain.Tests/NBB.Domain.Tests.csproj:22 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/EventStore/NBB.EventStore.AdoNet.Tests/NBB.EventStore.AdoNet.Tests.csproj:10 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/EventStore/NBB.EventStore.InMemory.Tests/NBB.EventStore.InMemory.Tests.csproj:12 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/EventStore/NBB.EventStore.Tests/NBB.EventStore.Tests.csproj:18 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Http/NBB.Http.Effects.Tests/NBB.Http.Effects.Tests.csproj:14 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Abstractions.Tests/NBB.Messaging.Abstractions.Tests.csproj:20 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.DataContracts.Tests/NBB.Messaging.DataContracts.Tests.csproj:11 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit test/UnitTests/Messaging/NBB.Messaging.Effects.Tests/NBB.Messaging.Effects.Tests.csproj:14 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
+ 16 more in this group — see findings.md.

D8 · Code Coverage · Low coverage · ×38

Low coverage: src/Core/NBB.Core.Effects/GenericSideEffectHandler.cs src/Core/NBB.Core.Effects/GenericSideEffectHandler.cs:1 — 0.0% line coverage (0/7).
Low coverage: src/Core/NBB.Core.Effects/Unit.cs src/Core/NBB.Core.Effects/Unit.cs:1 — 42.9% line coverage (3/7).
Low coverage: src/Core/NBB.Core.Effects/DependencyInjectionExtensions.cs src/Core/NBB.Core.Effects/DependencyInjectionExtensions.cs:1 — 40.0% line coverage (10/25).
Low coverage: src/MultiTenancy/NBB.MultiTenancy.Abstractions/TenantLogScope.cs src/MultiTenancy/NBB.MultiTenancy.Abstractions/TenantLogScope.cs:1 — 3.3% line coverage (1/30).
Low coverage: src/MultiTenancy/NBB.MultiTenancy.Abstractions/Repositories/CachedTenantRepositoryDecorator.cs src/MultiTenancy/NBB.MultiTenancy.Abstractions/Repositories/CachedTenantRepositoryDecorator.cs:1 — 18.4% line coverage (9/49).
Low coverage: src/Messaging/NBB.Messaging.InProcessMessaging/Internal/InProcessMessagingTransport.cs src/Messaging/NBB.Messaging.InProcessMessaging/Internal/InProcessMessagingTransport.cs:1 — 41.7% line coverage (15/36).
Low coverage: src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs:1 — 20.0% line coverage (11/55).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:1 — 0.0% line coverage (0/87).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs:1 — 21.8% line coverage (52/238).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/IMessagingTransport.cs src/Messaging/NBB.Messaging.Abstractions/IMessagingTransport.cs:1 — 42.9% line coverage (3/7).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/MessageBus.cs src/Messaging/NBB.Messaging.Abstractions/MessageBus.cs:1 — 0.0% line coverage (0/25).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/MessageBusSubscriber.cs src/Messaging/NBB.Messaging.Abstractions/MessageBusSubscriber.cs:1 — 0.0% line coverage (0/39).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/MessageTypeIdAttribute.cs src/Messaging/NBB.Messaging.Abstractions/MessageTypeIdAttribute.cs:1 — 0.0% line coverage (0/5).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/MessagingEnvelopeExtensions.cs src/Messaging/NBB.Messaging.Abstractions/MessagingEnvelopeExtensions.cs:1 — 13.3% line coverage (4/30).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/NewtonsoftJsonMessageSerDes.cs src/Messaging/NBB.Messaging.Abstractions/NewtonsoftJsonMessageSerDes.cs:1 — 26.7% line coverage (16/60).
Low coverage: src/Messaging/NBB.Messaging.Abstractions/SubscriptionTransportOptions.cs src/Messaging/NBB.Messaging.Abstractions/SubscriptionTransportOptions.cs:1 — 0.0% line coverage (0/12).
Low coverage: src/EventStore/NBB.EventStore.Abstractions/EventStoreUowDecorator.cs src/EventStore/NBB.EventStore.Abstractions/EventStoreUowDecorator.cs:1 — 0.0% line coverage (0/20).
Low coverage: src/EventStore/NBB.EventStore.Abstractions/IdentifiedEntityExtensions.cs src/EventStore/NBB.EventStore.Abstractions/IdentifiedEntityExtensions.cs:1 — 0.0% line coverage (0/6).
Low coverage: src/EventStore/NBB.EventStore.Abstractions/NullSnapshotStore.cs src/EventStore/NBB.EventStore.Abstractions/NullSnapshotStore.cs:1 — 0.0% line coverage (0/6).
Low coverage: src/Correlation/NBB.Correlation/CorrelationManager.cs src/Correlation/NBB.Correlation/CorrelationManager.cs:1 — 25.0% line coverage (4/16).
Low coverage: src/Correlation/NBB.Correlation/Internal/DisposableCorrelationScope.cs src/Correlation/NBB.Correlation/Internal/DisposableCorrelationScope.cs:1 — 0.0% line coverage (0/18).
Low coverage: src/Core/NBB.Core.Abstractions/ActivityExtensions.cs src/Core/NBB.Core.Abstractions/ActivityExtensions.cs:1 — 0.0% line coverage (0/54).
Low coverage: src/Core/NBB.Core.Abstractions/CancellationTokenExtensions.cs src/Core/NBB.Core.Abstractions/CancellationTokenExtensions.cs:1 — 0.0% line coverage (0/5).
Low coverage: src/Core/NBB.Core.Abstractions/ConcurrencyException.cs src/Core/NBB.Core.Abstractions/ConcurrencyException.cs:1 — 0.0% line coverage (0/6).
Low coverage: src/Core/NBB.Core.Abstractions/ConcurrencyUnrecoverableException.cs src/Core/NBB.Core.Abstractions/ConcurrencyUnrecoverableException.cs:1 — 0.0% line coverage (0/6).
+ 13 more in this group — see findings.md.

C2 · Access Controls · No authorization · ×15

No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:34 — `ContractsController.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 samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:42 — `ContractsController.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 samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:57 — `ContractsController.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 samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:64 — `ContractsController.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 samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:71 — `ContractsController.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 samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:32 — `InvoicesController.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 samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:39 — `InvoicesController.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 samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:48 — `InvoicesController.Create` 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 samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:55 — `InvoicesController.Process` 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 samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:30 — `PayablesController.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 samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:38 — `PayablesController.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 samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:45 — `PayablesController.Pay` 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 REDACTED:32 — `TodoController.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 REDACTED:37 — `TodoController.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.

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

Async method without CancellationToken: Get samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Get samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Controllers/ContractsController.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Get samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Controllers/InvoicesController.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UsingInvoiceLock samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/CommandHandlers/ProcessInvoiceCommandHandler.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Get samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Get samples/MicroServices/NBB.Payments/NBB.Payments.Api/Controllers/PayablesController.cs:38 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Get REDACTED:32 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Publish src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:132 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: TryStopAsync src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:106 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetConnectionStrings src/MultiTenancy/NBB.MultiTenancy.Abstractions/Configuration/TenantInfrastructure.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/Identifiers/HostTenantIdentifier.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/Services/DefaultTenantIdentificationService.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: TryGetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/Services/DefaultTenantIdentificationService.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: TryGetTenantIdAsync src/MultiTenancy/NBB.MultiTenancy.Identification/TenantIdentificationStrategy.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.

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

Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:79 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 79). Every use of it in `CreateDatabaseObjectsAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:88 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `DropDatabaseObjectsAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:73 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 73). Every use of it in `GetEventsFromStreamAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:104 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 104). Every use of it in `DeleteStreamAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:132 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 132). Every use of it in `AppendEventsToStreamExpectedVersionAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:178 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 178). Every use of it in `AppendEventsToStreamExpectedVersionAnyAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet/AdoNetSnapshotRepository.cs:44 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `LoadSnapshotAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/EventStore/NBB.EventStore.AdoNet/AdoNetSnapshotRepository.cs:86 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 86). Every use of it in `StoreSnapshotAsync` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:54 — `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `SubscribeAsync` 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 cts = …;`), which releases it at the end of the scope on every path including a throw.

D10 · Test Quality · No assertions · ×5

No assertions: RequireRegistration_should_accept_a_registration_made_after_the_call test/UnitTests/Core/NBB.Core.DependencyInjection.Tests/ServiceRegistrationValidationExtensionsTests.cs:27 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: RequireNonSingletonLifetime_should_accept_scoped_and_transient_registrations test/UnitTests/Core/NBB.Core.DependencyInjection.Tests/ServiceRegistrationValidationExtensionsTests.cs:38 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: RequireNonSingletonLifetime_should_not_report_a_missing_registration test/UnitTests/Core/NBB.Core.DependencyInjection.Tests/ServiceRegistrationValidationExtensionsTests.cs:64 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Should_not_require_a_classifier_for_publisher_only_apps test/UnitTests/Messaging/NBB.Messaging.MultiTenancy.Tests/TenantMiddlewareTests.cs:81 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: TestRepo test/UnitTests/Orchestration/NBB.ProcessManager.Tests/ProcessManagerInstanceUnitTests.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.

D17 · Explicit Debt · CommentedOutCode · ×5

CommentedOutCode samples/Monolith/NBB.Mono/Program.cs:36 — 4 consecutive commented-code lines
CommentedOutCode src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:231 — 4 consecutive commented-code lines
CommentedOutCode test/Benchmarks/EventStoreBenchmarks/Program.cs:14 — 4 consecutive commented-code lines
CommentedOutCode samples/NBB.Samples.ServiceDefaults/Extensions.cs:99 — 5 consecutive commented-code lines
CommentedOutCode test/UnitTests/Messaging/NBB.Messaging.InProcessMessaging.Tests/InProcessMessagingTests.cs:41 — 3 consecutive commented-code lines

ED5 · Idempotency · Non-idempotent mutation · ×5

Non-idempotent mutation: CommandHandlers.ContractCommandHandlers.Handle samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/CommandHandlers/ContractCommandHandlers.cs:39 — `CommandHandlers.ContractCommandHandlers.Handle` mutates persistent state (a database save) 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: DomainEventHandlers.ReadModelGenerator.Handle samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/DomainEventHandlers/ReadModelGenerator.cs:73 — `DomainEventHandlers.ReadModelGenerator.Handle` mutates persistent state (a database save) 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: CommandHandlers.ProcessInvoiceCommandHandler.Handle samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/CommandHandlers/ProcessInvoiceCommandHandler.cs:25 — `CommandHandlers.ProcessInvoiceCommandHandler.Handle` mutates persistent state (a database save) 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: CommandHandlers.PayPayableCommandHandler.Handle samples/MicroServices/NBB.Payments/NBB.Payments.Application/CommandHandlers/PayPayableCommandHandler.cs:23 — `CommandHandlers.PayPayableCommandHandler.Handle` mutates persistent state (a database save) 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: SideEffectHandlers.RequestTimeoutHandler.Handle src/Orchestration/NBB.ProcessManager.Runtime/SideEffectHandlers/RequestTimeoutHandler.cs:27 — `SideEffectHandlers.RequestTimeoutHandler.Handle` 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.

AX2 · Stateful singletons · Stateful singleton · ×4

Stateful singleton: MessagingHost src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:21 — `MessagingHost` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions, _subscriberStopSource, _stoppingSource; e.g. `_subscriptions` at line 116).
Stateful singleton: Storage src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs:12 — `Storage` is a singleton (one shared instance) but mutates instance state outside any lock (_subscriptions; e.g. `_subscriptions` at line 65).
Stateful singleton: StanConnectionProvider src/Messaging/NBB.Messaging.Nats/Internal/StanConnectionManager.cs:15 — `StanConnectionProvider` is a singleton (one shared instance) but mutates instance state outside any lock (_connection, _lazyConnection; e.g. `_connection` at line 68).
Stateful singleton: TimeoutsManager src/Orchestration/NBB.ProcessManager.Runtime/Timeouts/TimeoutsManager.cs:13 — `TimeoutsManager` is a singleton (one shared instance) but mutates instance state outside any lock (_startSlice; e.g. `_startSlice` at line 82).

D17 · Explicit Debt · TodoComment · ×4

TodoComment samples/MultiTenancy/NBB.Todo.Api/ProblemDetailsConfiguration.cs:14 — //TODO refactor ProblemDetails with AspNet.Core implementations — 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/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:64 — // TODO: when upgrading to .NET 8 remove the "suppressed" check since it doesn't throw any more
TodoComment src/Messaging/NBB.Messaging.InProcessMessaging/Internal/InProcessMessagingTransport.cs:45 — //TODO: push to DLQ — 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 test/UnitTests/Messaging/NBB.Messaging.Rusi.Tests/SubscriberTests.cs:52 — //TODO: use more reliable awaiting — 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.

D5 · Coupling · Off the main sequence · ×4

Off the main sequence: NBB.Core.DependencyInjection src/Core/NBB.Core.DependencyInjection/NBB.Core.DependencyInjection.csproj:1 — NBB.Core.DependencyInjection: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: NBB.Correlation src/Correlation/NBB.Correlation/NBB.Correlation.csproj:1 — NBB.Correlation: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: NBB.Domain src/Domain/NBB.Domain/NBB.Domain.csproj:1 — NBB.Domain: abstractness 0.82, instability 1.00, distance 0.82 — zone of uselessness — abstract and unstable, so it's likely unused.
Off the main sequence: NBB.Core.Effects src/Core/NBB.Core.Effects/NBB.Core.Effects.csproj:1 — NBB.Core.Effects: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.

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

Swallowed exception (empty catch) src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs:309 — 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/EventStore/NBB.EventStore.AdoNet.Migrations/AdoNetEventStoreDatabaseMigrator.cs:66 — 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/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:90 — 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/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:122 — 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.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D8 · Code Coverage · CRAP 42 · ×3

CRAP 42: AdoNetEventRepository.AppendEventsToStreamExpectedVersionAsync src/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.cs:122 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 42: DefaultDeadLetterQueue.Push src/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.cs:28 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 42: MessageBusSubscriber.SubscribeAsync src/Messaging/NBB.Messaging.Abstractions/MessageBusSubscriber.cs:30 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×3

Symbol treated as nullable, then dereferenced unguarded src/Domain/NBB.Domain/EventSourcedAggregateRoot.cs:39 — This method contradicts itself about `mementoProvider`: line 31 assigns it with `as IMementoProvider`, which hands back null rather than throwing when the value is not a `IMementoProvider`, but line 39 then dereferences it directly as `mementoProvider.SetMemento` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mementoProvider` once before the first use and handle the null case, or cast with `(IMementoProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/Domain/NBB.Domain/EventSourcedAggregateRoot.cs:46 — This method contradicts itself about `mementoProvider`: line 44 assigns it with `as IMementoProvider`, which hands back null rather than throwing when the value is not a `IMementoProvider`, but line 46 then dereferences it directly as `mementoProvider.CreateMemento` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mementoProvider` once before the first use and handle the null case, or cast with `(IMementoProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/Tools/Serilog/NBB.Tools.Serilog.OpenTelemetryTracingSink/Internal/OpenTelemetryTracingSink.cs:51 — This method contradicts itself about `activity`: line 26 writes `activity?.IsAllDataRequested`, which says `activity` can be null, but line 51 then dereferences it directly as `activity.AddEvent` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `activity` truly cannot be null here, the `?.` is misleading. Settle it one way — test `activity` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

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

Duplicated block (17 lines × 2) src/Core/NBB.Core.Abstractions/TypeExtensions.cs:27 — src/Core/NBB.Core.Abstractions/TypeExtensions.cs:27-43 | src/Core/NBB.Core.Abstractions/TypeExtensions.cs:65-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Core/NBB.Core.Abstractions/TypeExtensions.cs:27` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:243 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:243-259 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:206-222 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (10 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:96 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:96-105 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:98-107 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) samples/MicroServices/NBB.Invoices/NBB.Invoices.Data/DependencyInjectionExtensions.cs:36 — samples/MicroServices/NBB.Invoices/NBB.Invoices.Data/DependencyInjectionExtensions.cs:36-46 | samples/MicroServices/NBB.Invoices/NBB.Invoices.Data/DependencyInjectionExtensions.cs:54-63 — 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 `samples/MicroServices/NBB.Invoices/NBB.Invoices.Data/DependencyInjectionExtensions.cs:36` 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) · ×2

Duplicated block (12 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:184 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:184-195 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:152-163 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:263 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:263-274 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:226-237 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:276` calls `IsInExactNamespace`, `Equals` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:239` 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.

D8 · Code Coverage · CRAP 30 · ×2

CRAP 30: ActivityExtensions.SetException src/Core/NBB.Core.Abstractions/ActivityExtensions.cs:48 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 30: StatusHelper.GetTagValueForStatusCode src/Core/NBB.Core.Abstractions/ActivityExtensions.cs:134 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

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

Domain type reads the wall clock: InvoiceLock samples/MicroServices/NBB.Invoices/NBB.Invoices.Domain/InvoiceAggregate/InvoiceLock.cs:38 — `InvoiceLock` reads `DateTime.Now` inside `Acquire`, `Release`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: Payable samples/MicroServices/NBB.Payments/NBB.Payments.Domain/PayableAggregate/Payable.cs:31 — `Payable` reads `DateTime.Now` inside `Pay`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.

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

Unfinished stub — throws NotImplementedException src/MultiTenancy/NBB.MultiTenancy.Abstractions/Configuration/TenantConfiguration.cs:23 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MultiTenancy/NBB.MultiTenancy.Abstractions/Repositories/ConfigurationTenantRepository.cs:56 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

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

Schema created with EnsureCreated() outside the migrations samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/ContractsReadDatabaseMigrator.cs:14 — 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.
Schema created with EnsureCreated() outside the migrations samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/Migrator.cs:24 — 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.

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

Sync-over-async blocking — 1 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/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:89 — `t.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).

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

Owned disposable field is never released src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:33 — `MessagingHost` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_stoppingSource` itself (line 33), which makes that instance its own. But `_stoppingSource` is named in none of the methods the disposal search covered: `Dispose` (line 235) — 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` (`_stoppingSource?.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/Orchestration/NBB.ProcessManager.Runtime/Timeouts/InMemoryTimeoutRepository.cs:15 — `InMemoryTimeoutRepository` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_readerWriterLock` itself (line 15), which makes that instance its own. But `_readerWriterLock` is named in none of the methods the disposal search covered: `Dispose` (line 102), `Dispose` (line 110), `Dispose` (line 102), `Dispose` (line 110) — 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` (`_readerWriterLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.

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.

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

Fixed-sleep synchronisation: Shoud_reject_subsequent_restarts_When_restart_scheduled test/UnitTests/Messaging/NBB.Messaging.Host.Tests/HostTests.cs:181 — This test starts a background task and then orders itself against it with `Task.Delay(10)` — 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.

D12 · Dependency Hygiene · Prerelease dependency · ×1

Prerelease dependency: OpenTelemetry.SemanticConventions — OpenTelemetry.SemanticConventions resolves to 1.0.0-rc9.9, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.

D2 · Cognitive Complexity · TypeInfo.ParseInternal (cognitive 20) · ×1

TypeInfo.ParseInternal (cognitive 20) src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs:228 — TypeInfo.ParseInternal has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D22 · Internal API Consistency · The API exposes two distinct entry points for the same logical operations · ×1

The API exposes two distinct entry points for the same logical operations: the HTTP Controller and the Mediator. While this is a common architectural pattern (Controller as facade, Mediator as internal dispatcher), the signatures are nearly identical in intent. Specifically, `ContractsController.Post` and `Mediator.Send` accept the exact same command types (`CreateContract`, `AddContractLine`, `ValidateContract`). This creates redundancy for consumers who might wonder which entry point to use, although typically the Controller is the public API and Mediator is internal. However, the presence of both in the public surface without clear separation of concerns (e.g., one being internal or hidden) is a minor consistency issue. — Ensure that the Mediator is not part of the public API surface intended for external consumers, or clearly document that the Controller is the sole public entry point for these commands. If the Mediator is internal, it should not be exposed in the public API review. (signatures: ContractsController.Post(CreateContract command, ...) | ContractsController.Post(AddContractLine command, ...) | ContractsController.Post(ValidateContract command, ...) | Mediator.Send(AddContractLine request, ...) | Mediator.Send(CreateContract request, ...) | Mediator.Send(ValidateContract request, ...))

D30 · Dependency Vulnerabilities · Medium CVE · ×1

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

Duplicated block (30 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:109 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:109-138 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:111-140 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

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

Duplicated block (23 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:60 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:60-82 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:57-79 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1

Duplicated block (18–20 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:16 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:16-35 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:15-32 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (18 lines × 2) · ×1

Duplicated block (18 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:39 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:39-56 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:36-53 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (12–17 lines × 2) src/Projections/NBB.ProjectR.MediatR/DependencyInjectionExtensions.cs:19 — src/Projections/NBB.ProjectR.MediatR/DependencyInjectionExtensions.cs:19-30 | src/Projections/NBB.ProjectR.Mediator/DependencyInjectionExtensions.cs:24-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

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

Duplicated block (13 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:199 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:199-211 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:167-179 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (15 lines × 2) src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:215 — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:215-229 | src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs:183-197 — before extracting anything, compare `src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs` and `src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (13–14 lines × 2) src/Core/NBB.Core.Effects/TryFinallyEffect.cs:24 — src/Core/NBB.Core.Effects/TryFinallyEffect.cs:24-37 | src/Core/NBB.Core.Effects/TryWithEffect.cs:24-36 — 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/Core/NBB.Core.Effects/TryFinallyEffect.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (35 lines × 2) samples/Orchestration/ProcessManagerSample/OrderProcessManager.cs:26 — samples/Orchestration/ProcessManagerSample/OrderProcessManager.cs:26-60 | samples/Orchestration/ProcessManagerSample/OrderProcessManager.cs:85-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (15 lines × 3) · ×1

Duplicated block (15 lines × 3) samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/ContractsReadDbContextFactory.cs:21 — samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/ContractsReadDbContextFactory.cs:21-35 | samples/MicroServices/NBB.Invoices/NBB.Invoices.Migrations/InvoicesDbContextFactory.cs:21-35 | samples/MicroServices/NBB.Payments/NBB.Payments.Migrations/PaymentsDbContextFactory.cs:21-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.

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

Duplicated block (8 lines × 2) samples/MicroServices/NBB.Payments/NBB.Payments.Data/DependencyInjectionExtensions.cs:19 — samples/MicroServices/NBB.Payments/NBB.Payments.Data/DependencyInjectionExtensions.cs:19-26 | samples/MicroServices/NBB.Payments/NBB.Payments.Data/DependencyInjectionExtensions.cs:34-41 — 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 `samples/MicroServices/NBB.Payments/NBB.Payments.Data/DependencyInjectionExtensions.cs:19` 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.

D5 · Coupling · Unstable project NBB.Messaging.MultiTenancy · ×1

Unstable project NBB.Messaging.MultiTenancy src/Messaging/NBB.Messaging.MultiTenancy/NBB.Messaging.MultiTenancy.csproj:1 — NBB.Messaging.MultiTenancy has instability 0.56 with 4 dependents.

D5 · Coupling · Unstable project NBB.ProcessManager.Definition · ×1

Unstable project NBB.ProcessManager.Definition src/Orchestration/NBB.ProcessManager.Definition/NBB.ProcessManager.Definition.csproj:1 — NBB.ProcessManager.Definition has instability 0.71 with 2 dependents.

D8 · Code Coverage · No test project references NBB.Application.DataContracts.Schema · ×1

No test project references NBB.Application.DataContracts.Schema src/Application/NBB.Application.DataContracts.Schema/NBB.Application.DataContracts.Schema.csproj — No test project in this repository references NBB.Application.DataContracts.Schema (6 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Messaging.Noop · ×1

No test project references NBB.Messaging.Noop src/Messaging/NBB.Messaging.Noop/NBB.Messaging.Noop.csproj — No test project in this repository references NBB.Messaging.Noop (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Messaging.OpenTelemetry · ×1

No test project references NBB.Messaging.OpenTelemetry src/Messaging/NBB.Messaging.OpenTelemetry/NBB.Messaging.OpenTelemetry.csproj — No test project in this repository references NBB.Messaging.OpenTelemetry (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Messaging.JetStream · ×1

No test project references NBB.Messaging.JetStream src/Messaging/NBB.Messaging.JetStream/NBB.Messaging.JetStream.csproj — No test project in this repository references NBB.Messaging.JetStream (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Tools.Serilog.OpenTelemetryTracingSink · ×1

No test project references NBB.Tools.Serilog.OpenTelemetryTracingSink src/Tools/Serilog/NBB.Tools.Serilog.OpenTelemetryTracingSink/NBB.Tools.Serilog.OpenTelemetryTracingSink.csproj — No test project in this repository references NBB.Tools.Serilog.OpenTelemetryTracingSink (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Application.DataContracts · ×1

No test project references NBB.Application.DataContracts src/Application/NBB.Application.DataContracts/NBB.Application.DataContracts.csproj — No test project in this repository references NBB.Application.DataContracts (2 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Correlation.AspNet · ×1

No test project references NBB.Correlation.AspNet src/Correlation/NBB.Correlation.AspNet/NBB.Correlation.AspNet.csproj — No test project in this repository references NBB.Correlation.AspNet (2 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.MultiTenancy.AspNet · ×1

No test project references NBB.MultiTenancy.AspNet src/MultiTenancy/NBB.MultiTenancy.AspNet/NBB.MultiTenancy.AspNet.csproj — No test project in this repository references NBB.MultiTenancy.AspNet (2 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Correlation.Serilog · ×1

No test project references NBB.Correlation.Serilog src/Correlation/NBB.Correlation.Serilog/NBB.Correlation.Serilog.csproj — No test project in this repository references NBB.Correlation.Serilog (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.Correlation.Serilog.SqlServer · ×1

No test project references NBB.Correlation.Serilog.SqlServer REDACTED — No test project in this repository references NBB.Correlation.Serilog.SqlServer (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · No test project references NBB.EventStore.Effects · ×1

No test project references NBB.EventStore.Effects src/EventStore/NBB.EventStore.Effects/NBB.EventStore.Effects.csproj — No test project in this repository references NBB.EventStore.Effects (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 51.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.

D8 · Code Coverage · CRAP 108 · ×1

CRAP 108: TypeInfo.ParseInternal src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs:228 — Cyclomatic 14 with 21.8% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

D8 · Code Coverage · CRAP 48 · ×1

CRAP 48: DefaultMessageTypeRegistry.GetTypeByNameInternal src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.cs:49 — Cyclomatic 9 with 21.8% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

D8 · Code Coverage · CRAP 41 · ×1

CRAP 41: NewtonsoftJsonMessageSerDes.ResolveRuntimeType src/Messaging/NBB.Messaging.Abstractions/NewtonsoftJsonMessageSerDes.cs:67 — Cyclomatic 9 with 26.7% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).

IC1 · Incompleteness & stubs · Unfinished stub · ×1

Unfinished stub — throws NotImplementedException src/MultiTenancy/NBB.MultiTenancy.Abstractions/Repositories/ConfigurationTenantRepository.cs:56 — `GetByHost` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.

M1 · Documentation (README) · README may be stale · ×1

README may be stale — 64 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

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 · Blocking `WaitHandle.WaitOne` inside an `async` method · ×1

Blocking `WaitHandle.WaitOne` inside an `async` method src/Messaging/NBB.Messaging.InProcessMessaging/Internal/Storage.cs:78 — `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).

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

Sync-over-async (deadlock risk) src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:89 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.

X18 · Disposal-pattern correctness · Release token given back after an unprotected call · ×1

Release token given back after an unprotected call src/Messaging/NBB.Messaging.Host/Internal/HostedSubscription.cs:26 — `_subscription` is declared `IDisposable` and nothing more, and every assignment to it takes a constructor parameter — so `HostedSubscription` can do exactly one thing with it, which is the release performed here (line 26), and it is the only reference left that can perform it. That release is the tail of an unprotected sequence: `_logger.LogInformation("Messaging subscriber for topic {TopicName} is stoppin...` runs first (line 24), and nothing in `Dispose` catches it. A single throw from that call skips the release entirely — and because a bare `IDisposable` carries no state to inspect and no second holder to fall back on, whatever it represents (a lock taken for this instance, a semaphore lease, a scope) is then held for the remaining lifetime of the process, with nothing left that could ever give it back. Wrap the calls that precede it in a `try` and move the release into the `finally`, so the one statement that must happen is the one that always happens.

X2 · Cancellation propagation · Async method drops its CancellationToken · ×1

Async method drops its CancellationToken: PublishAsync src/Messaging/NBB.Messaging.Rusi/RusiMessagingTransport.cs:40 — Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).

Minor — 143 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×45

Orphaned file src/Messaging/NBB.Messaging.Abstractions/DefaultMessageTypeRegistry.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/EventStore/NBB.EventStore.AdoNet/AdoNetEventRepository.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/Messaging/NBB.Messaging.Host/Internal/MessagingHost.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/Core/NBB.Core.DependencyInjection/ReflectionExtensions.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/Core/NBB.Core.Abstractions/ActivityExtensions.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/Messaging/NBB.Messaging.Host/Builder/MessagingHostConfigurationBuilder.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/Messaging/NBB.Messaging.Abstractions/DefaultDeadLetterQueue.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/Messaging/NBB.Messaging.Rusi/RusiMessagingTransport.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/Messaging/NBB.Messaging.Nats/Internal/StanConnectionManager.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/EventStore/NBB.EventStore.AdoNet/AdoNetSnapshotRepository.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/Core/NBB.Core.Configuration/DotEnvConfigurationExtensions.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/Messaging/NBB.Messaging.Host/Builder/TypeSelector/TypeSourceSelector.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/Core/NBB.Core.DependencyInjection/ImplementationTypeFilter.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/EventStore/NBB.EventStore/EventStore.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/Messaging/NBB.Messaging.Host/MessagingPipeline/MessagingPipelineExtensions.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/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.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/MultiTenancy/NBB.MultiTenancy.Identification/Extensions/TenantServiceBuilder.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/Data/NBB.Data.EventSourcing/EventSourcedRepository.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/Messaging/NBB.Messaging.MultiTenancy/TenantMiddleware.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/Domain/NBB.Domain/Enumeration.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/Messaging/NBB.Messaging.MediatR/MediatRMessagingHostExtensions.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/EventStore/NBB.EventStore/SnapshotStore.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/Application/NBB.Application.DataContracts.Schema/JsonSchemaResolver.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/Messaging/NBB.Messaging.Abstractions/MessageBusPublisher.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/Core/NBB.Core.Configuration/DotEnvConfigurationProvider.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.
+ 20 more in this group — see findings.md.

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

README/code drift src/Orchestration/README.md:6 — src/Orchestration/README.md installs the package `NBB.ProcessManager.Definition` (`dotnet add package NBB.ProcessManager.Definition`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Orchestration/README.md:7 — src/Orchestration/README.md installs the package `NBB.ProcessManager.Runtime` (`dotnet add package NBB.ProcessManager.Runtime`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.DataContracts.Schema/Readme.md:6 — src/Application/NBB.Application.DataContracts.Schema/Readme.md installs the package `NBB.Application.DataContracts.Schema` (`dotnet add package NBB.Application.DataContracts.Schema`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.DataContracts/Readme.md:11 — src/Application/NBB.Application.DataContracts/Readme.md installs the package `NBB.Application.DataContracts` (`dotnet add package NBB.Application.DataContracts`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.MediatR.Effects/Readme.md:7 — src/Application/NBB.Application.MediatR.Effects/Readme.md installs the package `NBB.Application.MediatR.Effects` (`dotnet add package NBB.Application.MediatR.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.MediatR/Readme.md:7 — src/Application/NBB.Application.MediatR/Readme.md installs the package `NBB.Application.MediatR` (`dotnet add package NBB.Application.MediatR`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.Mediator.Effects/README.md:7 — src/Application/NBB.Application.Mediator.Effects/README.md installs the package `NBB.Application.Mediator.Effects` (`dotnet add package NBB.Application.Mediator.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.Mediator.FSharp/Readme.md:7 — src/Application/NBB.Application.Mediator.FSharp/Readme.md installs the package `NBB.Application.Mediator.FSharp` (`dotnet add package NBB.Application.Mediator.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Application/NBB.Application.Mediator/README.md:7 — src/Application/NBB.Application.Mediator/README.md installs the package `NBB.Application.Mediator` (`dotnet add package NBB.Application.Mediator`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.Abstractions/README.md:10 — src/Core/NBB.Core.Abstractions/README.md installs the package `NBB.Core.Abstractions` (`dotnet add package NBB.Core.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.Configuration/README.md:7 — src/Core/NBB.Core.Configuration/README.md installs the package `NBB.Core.Configuration` (`dotnet add package NBB.Core.Configuration`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.DependencyInjection/README.md:11 — src/Core/NBB.Core.DependencyInjection/README.md installs the package `NBB.Core.DependencyInjection` (`dotnet add package NBB.Core.DependencyInjection`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.Effects.FSharp/README.md:7 — src/Core/NBB.Core.Effects.FSharp/README.md installs the package `NBB.Core.Effects.FSharp` (`dotnet add package NBB.Core.Effects.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.Effects/README.md:10 — src/Core/NBB.Core.Effects/README.md installs the package `NBB.Core.Effects` (`dotnet add package NBB.Core.Effects`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.Evented.FSharp/README.md:7 — src/Core/NBB.Core.Evented.FSharp/README.md installs the package `NBB.Core.Evented.FSharp` (`dotnet add package NBB.Core.Evented.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.FSharp/README.md:7 — src/Core/NBB.Core.FSharp/README.md installs the package `NBB.Core.FSharp` (`dotnet add package NBB.Core.FSharp`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Core/NBB.Core.Pipeline/README.md:7 — src/Core/NBB.Core.Pipeline/README.md installs the package `NBB.Core.Pipeline` (`dotnet add package NBB.Core.Pipeline`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Correlation/NBB.Correlation.AspNet/README.md:7 — src/Correlation/NBB.Correlation.AspNet/README.md installs the package `NBB.Correlation.AspNet` (`dotnet add package NBB.Correlation.AspNet`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Correlation/NBB.Correlation.Serilog.SqlServer/README.md:8 — src/Correlation/NBB.Correlation.Serilog.SqlServer/README.md installs the package `NBB.Serilog.SqlServer` (`dotnet add package NBB.Serilog.SqlServer`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Correlation/NBB.Correlation.Serilog/README.md:7 — src/Correlation/NBB.Correlation.Serilog/README.md installs the package `NBB.Correlation.Serilog` (`dotnet add package NBB.Correlation.Serilog`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Correlation/NBB.Correlation/README.md:7 — src/Correlation/NBB.Correlation/README.md installs the package `NBB.Correlation` (`dotnet add package NBB.Correlation`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Data/NBB.Data.Abstractions/README.md:12 — src/Data/NBB.Data.Abstractions/README.md installs the package `NBB.Data.Abstractions` (`dotnet add package NBB.Data.Abstractions`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Data/NBB.Data.EntityFramework.MultiTenancy/README.md:9 — src/Data/NBB.Data.EntityFramework.MultiTenancy/README.md installs the package `NBB.Data.EntityFramework.MultiTenancy` (`dotnet add package NBB.Data.EntityFramework.MultiTenancy`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Data/NBB.Data.EntityFramework/README.md:13 — src/Data/NBB.Data.EntityFramework/README.md installs the package `NBB.Data.EntityFramework` (`dotnet add package NBB.Data.EntityFramework`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/Data/NBB.Data.EventSourcing/README.md:9 — src/Data/NBB.Data.EventSourcing/README.md installs the package `NBB.Data.EventSourcing` (`dotnet add package NBB.Data.EventSourcing`), 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.
+ 15 more in this group — see findings.md.

ED3 · Event naming · Event not named in past tense · ×8

Event not named in past tense: InvoiceEvent samples/MicroServices/NBB.Invoices.FSharp/NBB.Invoices.FSharp/Domain/InvoiceAggregate.fs:20 — `InvoiceEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: SomeEvent test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/EventPipelineTests.fs:13 — `SomeEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: SomeOtherEvent test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/EventPipelineTests.fs:18 — `SomeOtherEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: Event1 test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/Sample.fs:85 — `Event1` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: Event2 test/UnitTests/Application/NBB.Application.Mediator.FSharp.Tests/Sample.fs:97 — `Event2` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: DomainEvent test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/Tests.fs:12 — `DomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: DomainEvent test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/Sample2.fs:15 — `DomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: DomainEvent test/UnitTests/Core/NBB.Core.Evented.FSharp.Tests/Sample.fs:11 — `DomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.

IC1 · Incompleteness & stubs · Commented-out code · ×6

Commented-out code src/Messaging/NBB.Messaging.InProcessMessaging/Internal/InProcessMessagingTransport.cs:49 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Messaging/NBB.Messaging.JetStream/DependencyInjectionExtensions.cs:22 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:24 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs:25 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Tools/Serilog/NBB.Tools.Serilog.Enrichers.TenantId/TenantEnricher.cs:33 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Tools/Serilog/NBB.Tools.Serilog.Enrichers.TenantId/TenantEnricher.cs:34 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).

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

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 samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/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 samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Program.cs:10 — 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 samples/MicroServices/NBB.Payments/NBB.Payments.Api/Program.cs:10 — 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 samples/Monolith/NBB.Mono/Program.cs:22 — 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 samples/MultiTenancy/NBB.Todo.Api/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.

S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×6

No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
No app-layer HTTPS enforcement detected samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/Program.cs:13 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/Program.cs:10 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected samples/MicroServices/NBB.Payments/NBB.Payments.Api/Program.cs:10 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected samples/Monolith/NBB.Mono/Program.cs:22 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected samples/MultiTenancy/NBB.Todo.Api/Program.cs:16 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.

X10 · Duplicated predicate · Duplicated predicate · ×5

Duplicated predicate src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:205 — `currentTypeInfo.IsGenericType && currentTypeInfo.ContainsGenericParameters && GenericParametersMatch(genericTypeParameters, currentTypeInfo.…` appears character-identically in 2 files — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs, src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.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/Messaging/NBB.Messaging.Mediator/MediatorMessagingHostExtensions.cs:76 — `t.IsGenericType && handlerTypes.Any(typeInfo => typeInfo.GenericTypeDef == t.GetGenericTypeDefinition() && typeInfo.Condition.Invoke(t.GetGe…` appears character-identically in 2 files — src/Messaging/NBB.Messaging.MediatR/MediatRMessagingHostExtensions.cs, src/Messaging/NBB.Messaging.Mediator/MediatorMessagingHostExtensions.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/Messaging/NBB.Messaging.Mediator/MediatorMessagingHostExtensions.cs:78 — `typeInfo.GenericTypeDef == t.GetGenericTypeDefinition() && typeInfo.Condition.Invoke(t.GetGenericArguments())` appears character-identically in 2 files — src/Messaging/NBB.Messaging.MediatR/MediatRMessagingHostExtensions.cs, src/Messaging/NBB.Messaging.Mediator/MediatorMessagingHostExtensions.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/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:19 — `typeInfo.IsClass && !typeInfo.IsAbstract` appears character-identically in 2 files — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs, src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.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/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs:28 — `typeInfo.IsPublic || typeInfo.IsNestedPublic` appears character-identically in 3 files — src/Core/NBB.Core.DependencyInjection/ReflectionExtensions.cs, src/Messaging/NBB.Messaging.Host/Builder/TypeSelector/ImplementationTypeSelector.cs, src/Orchestration/NBB.ProcessManager.Definition/ReflectionExtensions.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.

X4 · Structured logging · Interpolated log message defeats structured logging · ×5

Interpolated log message defeats structured logging src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:62 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Messaging/NBB.Messaging.Host/Internal/MessagingHost.cs:94 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Messaging/NBB.Messaging.Nats/Internal/StanConnectionManager.cs:70 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Orchestration/NBB.ProcessManager.Runtime/Instance.cs:67 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/Orchestration/NBB.ProcessManager.Runtime/Instance.cs:76 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.

X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×3

Diagnostic log message is built whether or not it is wanted src/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.cs:44 — `LogDebug` at line 44 is called with an argument built by `string.Join(", ", includePaths)` (line 44), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted src/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.cs:59 — `LogDebug` at line 59 is called with an argument built by `string.Join(", ", includePaths)` (line 59), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted src/Data/NBB.Data.EntityFramework/EfReadOnlyRepository.cs:77 — `LogDebug` at line 77 is called with an argument built by `string.Join(", ", includePaths)` (line 78), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.

D12 · Dependency Hygiene · Outdated · ×1

Outdated: coverlet.collector test/Integration/NBB.Messaging.Rusi.IntegrationTests/NBB.Messaging.Rusi.IntegrationTests.csproj:38 — coverlet.collector 6.0.4 → 10.1.0 available (referenced by NBB.Messaging.Rusi.IntegrationTests).

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: src/Messaging/NBB.Messaging.JetStream/JetStreamMessagingTransport.cs. Pair on, review, or document these before any departure.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

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

REDACTED

D34 · Knowledge Freshness · Concentrated knowledge decay · ×1

Concentrated knowledge decay — 46 of 73 significant files have no living knowledge, while the repository is still being changed at a low rate (5 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 46 separate risks. Counted over 73 of the 337 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.

D34 · Knowledge Freshness · Most significant orphaned file · ×1

Most significant orphaned file src/Core/NBB.Core.DependencyInjection/ServiceCollectionExtension.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1

Benchmarks don't track allocations — A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way hot code pressures the GC) aren't being measured.

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

Not all async methods take a CancellationToken — Only 120/135 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.

X2 · Cancellation propagation · Some async methods drop the CancellationToken they accept · ×1

Some async methods drop the CancellationToken they accept — 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.

X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1

Nullable reference types not enabled everywhere — 4/93 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 — ~0.4 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 2283 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.

X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1

Silent fallback default on parse failure src/Messaging/NBB.Messaging.Abstractions/MessagingEnvelopeExtensions.cs:20 — `GetCorrelationId` falls back to `default` when `envelope.Headers.TryGetValue(MessagingHeaders.CorrelationId, out var value)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.

Minor — 191 finding(s)

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

XML-doc coverage: NBB.Samples.ServiceDefaults samples/NBB.Samples.ServiceDefaults/NBB.Samples.ServiceDefaults.csproj — NBB.Samples.ServiceDefaults: 0 % XML-doc coverage (0/5).
XML-doc coverage: NBB.MicroServicesOrchestration samples/MicroServices/NBB.MicroServicesOrchestration/NBB.MicroServicesOrchestration.csproj — NBB.MicroServicesOrchestration: 0 % XML-doc coverage (0/7).
XML-doc coverage: NBB.Contracts.Api samples/MicroServices/NBB.Contracts/NBB.Contracts.Api/NBB.Contracts.Api.csproj — NBB.Contracts.Api: 0 % XML-doc coverage (0/7).
XML-doc coverage: NBB.Contracts.Application samples/MicroServices/NBB.Contracts/NBB.Contracts.Application/NBB.Contracts.Application.csproj — NBB.Contracts.Application: 5 % XML-doc coverage (1/20).
XML-doc coverage: NBB.Contracts.Domain samples/MicroServices/NBB.Contracts/NBB.Contracts.Domain/NBB.Contracts.Domain.csproj — NBB.Contracts.Domain: 0 % XML-doc coverage (0/36).
XML-doc coverage: NBB.Contracts.Migrations samples/MicroServices/NBB.Contracts/NBB.Contracts.Migrations/NBB.Contracts.Migrations.csproj — NBB.Contracts.Migrations: 0 % XML-doc coverage (0/8).
XML-doc coverage: NBB.Contracts.PublishedLanguage samples/MicroServices/NBB.Contracts/NBB.Contracts.PublishedLanguage/NBB.Contracts.PublishedLanguage.csproj — NBB.Contracts.PublishedLanguage: 0 % XML-doc coverage (0/4).
XML-doc coverage: NBB.Contracts.ReadModel.Data samples/MicroServices/NBB.Contracts/NBB.Contracts.ReadModel.Data/NBB.Contracts.ReadModel.Data.csproj — NBB.Contracts.ReadModel.Data: 0 % XML-doc coverage (0/5).
XML-doc coverage: NBB.Contracts.ReadModel samples/MicroServices/NBB.Contracts/NBB.Contracts.ReadModel/NBB.Contracts.ReadModel.csproj — NBB.Contracts.ReadModel: 0 % XML-doc coverage (0/15).
XML-doc coverage: NBB.Contracts.WriteModel.Data samples/MicroServices/NBB.Contracts/NBB.Contracts.WriteModel.Data/NBB.Contracts.WriteModel.Data.csproj — NBB.Contracts.WriteModel.Data: 0 % XML-doc coverage (0/2).
XML-doc coverage: NBB.Invoices.Api samples/MicroServices/NBB.Invoices/NBB.Invoices.Api/NBB.Invoices.Api.csproj — NBB.Invoices.Api: 0 % XML-doc coverage (0/6).
XML-doc coverage: NBB.Invoices.Application samples/MicroServices/NBB.Invoices/NBB.Invoices.Application/NBB.Invoices.Application.csproj — NBB.Invoices.Application: 0 % XML-doc coverage (0/13).
XML-doc coverage: NBB.Invoices.Data samples/MicroServices/NBB.Invoices/NBB.Invoices.Data/NBB.Invoices.Data.csproj — NBB.Invoices.Data: 0 % XML-doc coverage (0/7).
XML-doc coverage: NBB.Invoices.Domain samples/MicroServices/NBB.Invoices/NBB.Invoices.Domain/NBB.Invoices.Domain.csproj — NBB.Invoices.Domain: 0 % XML-doc coverage (0/31).
XML-doc coverage: NBB.Invoices.Migrations samples/MicroServices/NBB.Invoices/NBB.Invoices.Migrations/NBB.Invoices.Migrations.csproj — NBB.Invoices.Migrations: 0 % XML-doc coverage (0/8).
XML-doc coverage: NBB.Invoices.PublishedLanguage samples/MicroServices/NBB.Invoices/NBB.Invoices.PublishedLanguage/NBB.Invoices.PublishedLanguage.csproj — NBB.Invoices.PublishedLanguage: 0 % XML-doc coverage (0/5).
XML-doc coverage: NBB.Payments.Api samples/MicroServices/NBB.Payments/NBB.Payments.Api/NBB.Payments.Api.csproj — NBB.Payments.Api: 0 % XML-doc coverage (0/5).
XML-doc coverage: NBB.Payments.Application samples/MicroServices/NBB.Payments/NBB.Payments.Application/NBB.Payments.Application.csproj — NBB.Payments.Application: 0 % XML-doc coverage (0/10).
XML-doc coverage: NBB.Payments.Data samples/MicroServices/NBB.Payments/NBB.Payments.Data/NBB.Payments.Data.csproj — NBB.Payments.Data: 0 % XML-doc coverage (0/7).
XML-doc coverage: NBB.Payments.Domain samples/MicroServices/NBB.Payments/NBB.Payments.Domain/NBB.Payments.Domain.csproj — NBB.Payments.Domain: 0 % XML-doc coverage (0/20).
XML-doc coverage: NBB.Payments.Migrations samples/MicroServices/NBB.Payments/NBB.Payments.Migrations/NBB.Payments.Migrations.csproj — NBB.Payments.Migrations: 0 % XML-doc coverage (0/8).
XML-doc coverage: NBB.Payments.PublishedLanguage samples/MicroServices/NBB.Payments/NBB.Payments.PublishedLanguage/NBB.Payments.PublishedLanguage.csproj — NBB.Payments.PublishedLanguage: 0 % XML-doc coverage (0/4).
XML-doc coverage: NBB.Mono REDACTED — NBB.Mono: 0 % XML-doc coverage (0/8).
XML-doc coverage: NBB.Todo.Api samples/MultiTenancy/NBB.Todo.Api/NBB.Todo.Api.csproj — NBB.Todo.Api: 0 % XML-doc coverage (0/11).
XML-doc coverage: NBB.Todo.Data samples/MultiTenancy/NBB.Todo.Data/NBB.Todo.Data.csproj — NBB.Todo.Data: 0 % XML-doc coverage (0/13).
+ 62 more in this group — see findings.md.

D12 · Dependency Hygiene · Outdated · ×63

Outdated: Microsoft.Extensions.Http.Resilience — Microsoft.Extensions.Http.Resilience 10.10.0 → 10.11.0 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: Microsoft.Extensions.ServiceDiscovery — Microsoft.Extensions.ServiceDiscovery 10.10.0 → 10.11.0 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: Microsoft.SourceLink.GitHub — Microsoft.SourceLink.GitHub 10.0.401 → 10.0.402 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: MinVer — MinVer 6.0.0 → 8.0.0 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: OpenTelemetry.Exporter.OpenTelemetryProtocol — OpenTelemetry.Exporter.OpenTelemetryProtocol 1.17.0 → 1.20.1 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: OpenTelemetry.Extensions.Hosting — OpenTelemetry.Extensions.Hosting 1.17.0 → 1.20.1 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: OpenTelemetry.Instrumentation.AspNetCore — OpenTelemetry.Instrumentation.AspNetCore 1.17.0 → 1.20.1 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: OpenTelemetry.Instrumentation.Http — OpenTelemetry.Instrumentation.Http 1.17.0 → 1.20.1 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: OpenTelemetry.Instrumentation.Runtime — OpenTelemetry.Instrumentation.Runtime 1.17.0 → 1.20.1 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: OpenTelemetry.Instrumentation.SqlClient — OpenTelemetry.Instrumentation.SqlClient 1.17.0 → 1.20.1 available (referenced by NBB.Samples.ServiceDefaults).
Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables — Microsoft.Extensions.Configuration.EnvironmentVariables 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Microsoft.Extensions.Configuration.UserSecrets — Microsoft.Extensions.Configuration.UserSecrets 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Microsoft.Extensions.Logging.Console — Microsoft.Extensions.Logging.Console 10.0.12 → 10.0.13 available (referenced by NBB.MicroServicesOrchestration).
Outdated: Swashbuckle.AspNetCore — Swashbuckle.AspNetCore 10.2.3 → 10.3.1 available (referenced by NBB.Contracts.Api).
Outdated: Microsoft.EntityFrameworkCore.Design — Microsoft.EntityFrameworkCore.Design 10.0.12 → 10.0.13 available (referenced by NBB.Contracts.Migrations).
Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 10.0.12 → 10.0.13 available (referenced by NBB.Contracts.ReadModel.Data).
Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 10.0.12 → 10.0.13 available (referenced by NBB.Contracts.ReadModel.Data).
Outdated: FSharp.Core — FSharp.Core 10.1.400 → 10.1.402 available (referenced by NBB.Invoices.FSharp.Api).
Outdated: Giraffe — Giraffe 8.2.0 → 8.3.0 available (referenced by NBB.Invoices.FSharp.Api).
Outdated: Microsoft.Data.SqlClient — Microsoft.Data.SqlClient 6.1.3 → 7.1.1 available (referenced by NBB.Invoices.FSharp).
Outdated: Microsoft.Extensions.Configuration.Abstractions — Microsoft.Extensions.Configuration.Abstractions 10.0.12 → 10.0.13 available (referenced by NBB.Invoices.FSharp).
+ 38 more in this group — see findings.md.

D10 · Test Quality · Mock framework · ×34

Mock framework: Moq — NBB.EventStore.IntegrationTests references Moq.
Mock framework: Moq — NBB.Messaging.Rusi.IntegrationTests references Moq.
Mock framework: Moq — NBB.Application.Effects.Tests references Moq.
Mock framework: Moq — NBB.Application.Mediator.Tests references Moq.
Mock framework: Moq — NBB.Application.MediatR.Tests references Moq.
Mock framework: Moq — NBB.Core.Effects.Tests references Moq.
Mock framework: Moq — NBB.Core.Pipeline.Tests references Moq.
Mock framework: Moq — NBB.Data.Abstractions.Tests references Moq.
Mock framework: Moq — NBB.Data.EntityFramework.MultiTenancy.Tests references Moq.
Mock framework: Moq — NBB.Data.EntityFramework.Tests references Moq.
Mock framework: Moq — NBB.Data.EventSourcing.Tests references Moq.
Mock framework: Moq — NBB.Domain.Tests references Moq.
Mock framework: Moq — NBB.EventStore.InMemory.Tests references Moq.
Mock framework: Moq — NBB.EventStore.Tests references Moq.
Mock framework: Moq — NBB.Http.Effects.Tests references Moq.
Mock framework: Moq — NBB.Messaging.Abstractions.Tests references Moq.
Mock framework: Moq — NBB.Messaging.DataContracts.Tests references Moq.
Mock framework: Moq — NBB.Messaging.Effects.Tests references Moq.
Mock framework: Moq — NBB.Messaging.Host.Tests references Moq.
Mock framework: Moq — NBB.Messaging.InProcessMessaging.Tests references Moq.
Mock framework: Moq — NBB.Messaging.Mediator.Tests references Moq.
Mock framework: Moq — NBB.Messaging.MediatR.Tests references Moq.
Mock framework: Moq — NBB.Messaging.MultiTenancy.Tests references Moq.
Mock framework: Moq — NBB.Messaging.Rusi.Tests references Moq.
Mock framework: Moq — NBB.MultiTenancy.Abstractions.Tests references Moq.
+ 9 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Domain · ×1

Domain: 1 contract type(s) expose producer-owned ids/enums — In Domain, 1 contract type(s) (TestEventSourcedAggregateRoot) expose strong-typed ids/value objects (IEventSourcedAggregateRoot); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · EventStore · ×1

EventStore: 1 contract type(s) expose producer-owned ids/enums — In EventStore, 1 contract type(s) (SideEffect) expose strong-typed ids/value objects (SideEffect); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · EventStoreDnIntegrationTests · ×1

EventStoreDnIntegrationTests: 1 contract type(s) expose producer-owned ids/enums — In EventStoreDnIntegrationTests, 1 contract type(s) (EventStoreDnIntegrationTests) expose strong-typed ids/value objects (EnvironmentFixture); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · NBB · ×1

NBB: 4 contract type(s) expose producer-owned ids/enums — In NBB, 4 contract type(s) (ContractCommandHandlers, ContractsController, CreateContract, ValidateContract) expose strong-typed ids/value objects (CreateContract, ValidateContract); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · SnapshotStoreDbIntegrationTests · ×1

SnapshotStoreDbIntegrationTests: 1 contract type(s) expose producer-owned ids/enums — In SnapshotStoreDbIntegrationTests, 1 contract type(s) (SnapshotStoreDbIntegrationTests) expose strong-typed ids/value objects (EnvironmentFixture); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · TestEvent · ×1

TestEvent: 1 contract type(s) expose producer-owned ids/enums — In TestEvent, 1 contract type(s) (TestEvent) expose strong-typed ids/value objects (TestEvent); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · samples · ×1

samples: 2 contract type(s) expose producer-owned ids/enums — In samples, 2 contract type(s) (LoopCompleted, LoopcycleCompleted) expose strong-typed ids/value objects (LoopCompleted, LoopcycleCompleted); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

Appendix B — Reproduction & audit trail

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

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-414a980cdc61425384ec05f482f51d1f/history.json --exit-code 0 --source .	0	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-414a980cdc61425384ec05f482f51d1f/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 .	15	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list NBB.slnx package --vulnerable --include-transitive --format json	3	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	0	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 25 file(s) — `src/Application/NBB.Application.MediatR.Effects/Mediator.cs`, `src/Application/NBB.Application.MediatR/MediatREventPublisher.cs`, `src/Application/NBB.Application.MediatR/MediatorUowDecorator.cs`, `src/Application/NBB.Application.Mediator.Effects/MediatorEff.cs`, `src/Application/NBB.Application.Mediator/MediatorEventPublisher.cs`, … (+20 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure 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 01a16148-2bb8-7718-8f40-e620f4838dd1 · 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 — 1 field(s) across 1 category, 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 — 1 field(s)

SchemaDefinition.FullName src/Application/NBB.Application.DataContracts.Schema/SchemaDefinition.cs:9

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 · 52% · Adequate · gated by X5 ·

At a glance — Architecture · 78% · Strong ·

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

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

At a glance — Security · 23% · Critical · gated by D36, C1, C2 ·

At a glance — Domain Modelling · 97% · Exemplary ·

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

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Performance · 76% · 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